Skip to content
LitanyGet it on Google Play

Privacy Policy — Litany

Version 3 — last updated September 28, 2026

Litany (“the app”) is developed by Esteban Feldman (“we”, “us”, “our”). This policy explains what happens to your information when you use the app.

The short version

Your affirmations and ritual data still never leave the phone for us; we have no server. The app does show ads, and the SDK that serves them collects some device and usage information on Google’s behalf. The app also sends anonymous usage events and crash reports to Google Firebase so we can see how the app is used and fix crashes — never your affirmation text. See below for both.

Data we collect

Permissions the app requests, and why

Permission Purpose
Notifications Sends the daily reminder you set up in Settings. Fully optional — decline or revoke it anytime in your device’s system settings.
Receive boot completed Re-schedules your daily reminder after your device restarts, since Android clears scheduled alarms on reboot.
Advertising ID (com.google.android.gms.permission.AD_ID) Lets Google’s ad SDK read the advertising ID. Added automatically by the SDK.

The notification and boot permissions collect or transmit no data; they exist only to deliver the reminder feature you configure and control. The advertising ID permission is covered by the Advertising section above.

Where your data can go

Your data only leaves your phone in these ways, and none of them send it to us:

Data deletion

Uninstalling the app deletes its data from your device. If Android backup was on, a copy may remain in your Google account’s device backup; you can delete it from your Google account’s backup settings. Any backup files you exported stay wherever you saved them. There is nothing to delete on our end, because we never had your data.

Children’s privacy

The app is not directed at children and does not knowingly collect information from anyone, regardless of age. Ads shown in the app are not directed at children.

Changes to this policy

If we add a feature that collects data beyond what’s described above, we will update this policy first, clearly describing what’s collected, why, and how you can control it, before that feature ships to users.

Version history

Contact

Questions about this policy: esteban.feldman@gmail.com