Local-first by design

Every automation you create (battery and charger triggers, special date reminders, and their actions) is stored in the app's own local database on your device. This data is never uploaded, backed up to a server, or shared, unless you explicitly export it yourself as a file to move between your own devices.

Information handled by third-party services

Evoke uses a small number of Google services, and each independently handles a limited amount of information:

• Advertising (Google AdMob). The free version of Evoke shows ads served by Google AdMob. To serve and measure ads and to prevent fraud, AdMob collects your device's advertising identifier, your IP address (which gives an approximate location), how you interact with ads, and app performance information. Google handles this under its own privacy policy. You can reset the advertising identifier or turn off ad personalization anytime in your device's Google settings. Evoke Pro removes ads from the app.
• In-app purchases (Google Play Billing). The one-time Evoke Pro purchase is processed entirely by Google Play. We never see or store your payment details; that information is handled under Google's own Privacy Policy, not this one.
• App analytics (Google Analytics for Firebase). Evoke sends usage events to Google Analytics for Firebase, for example which type of automation you created (a battery trigger or a special date reminder), that a reminder fired, or that you opened the upgrade screen, along with general app state like whether Pro is unlocked or roughly how many automations you have. Google Analytics also records Evoke Pro purchases, an approximate location based on your IP address, a random app install identifier, and your device's advertising identifier. We use this to understand how Evoke is used and to measure and improve our ads, and it is shared with Google Ads for that purpose. Events never include the text you type: a Special Date's label, a Reminder's message, or a saved contact are never sent.
• Crash reporting (Firebase Crashlytics). If Evoke crashes, Crashlytics sends a diagnostic report (the crash's stack trace, your device model, Android version, the app version, and a random install identifier) so we can find and fix the bug. Crash reports don't include your automations, reminders, or any other content you've entered.

There are no accounts and no sign-in, and no way to give us your name, email, or any other personal identifier directly. None of the services above receive your automation or reminder content, only the information described above.

Permissions Evoke requests, and why

Each permission below, except the advertising identifier, exists solely to run the automations you create and is never used to collect or transmit information about you.

• Notifications. To show reminders, Critical Alerts, and status updates.
• Exact alarms. To fire Special Date reminders precisely on schedule.
• Boot-completed. To re-arm your alarms after a restart, since Android clears them on reboot.
• Battery status. To detect charging state and battery level for Battery and Charger automations.
• Advertising identifier. Used only by the ads and analytics described above.

Data deletion

Because Evoke doesn't operate a server, there is no remote copy of your automation or reminder content for us to delete on request. Uninstalling the app removes everything stored locally, immediately, and stops all analytics and crash reporting going forward. Firebase Analytics and Crashlytics data isn't linked to your name or email, so there's no account of yours to delete it from. For your advertising identifier and other data held by Google, use your device's Google settings and your Google account controls.

Security

Any data that does leave your device, solely through the Google services described above, is transmitted using industry-standard encryption in transit.

Children's privacy

Evoke is not directed at children under 13, and we do not knowingly collect information from children under 13. If you believe a child has provided us information in violation of this policy, contact us below and we'll address it.

Changes to this policy

We may update this Privacy Policy as Evoke's features change. Material changes will be reflected by updating the date at the top of this page.

Contact us

Questions, concerns, or feedback about this policy can be sent to wrenfoldlabs@gmail.com.