1. What we collect
Your account
When you sign up with email, we collect your email address and a password. The password is stored in hashed form by our authentication provider, Supabase; we can’t read it. If you continue with Apple or Google instead, we receive a sign-in token from that provider and the email address on your Apple ID or Google account, along with your name if the provider shares it. Google also sends a link to your profile picture, which we don’t use. With Apple you can choose Hide My Email, in which case we receive an Apple relay address instead of your real one.
After you sign in with Apple, our server also keeps a token from Apple. It exists for one reason: if you delete your account, we use it to tell Apple to end AmenAlarm’s access to your Apple ID.
Your answers during setup
Before you create your account, AmenAlarm asks a few questions and saves your answers with your profile: your first name, your age range, what you’d like to change about your mornings (for example, “I reach for my phone first”), roughly how many minutes your phone gets each morning, how many minutes you’d like to spend praying, and the time and days of your first alarm.
Setup also asks for your birthday, to check that you’re old enough to use AmenAlarm (section 14) and to work out one figure it shows you. Your birthday stays on your phone: only the age range it falls in (for example, 25 to 34) is saved with your profile.
Your mornings
When you finish a morning by tapping Amen, the app saves it to your journal: the date and time; which Bible passage you read (its reference, such as Psalm 46:1–3, not the text); your answers to the two questions in the prayer flow — how close God felt and how you’re doing, each saved as a number from 0 to 4; your prayer request, if you wrote one; the prayer itself; and whether the end of the prayer was written by the AI or came from our pre-written prayers. We also keep your streak: your current and longest streak, and the date of your last morning.
Your alarms
The time, the days, the label and whether each alarm is switched on. iOS schedules and rings the alarms on your iPhone; our copy is a backup, so your alarms come back when you log in on a new phone.
Feedback and support
If you use Give feedback in Settings, we store your message with your email address, the app version and your iOS version. Help opens your own email app, and we receive whatever you choose to send.
Subscription status
RevenueCat, our subscription provider, and Apple tell us whether your account has an active subscription or trial, which plan it is, and when it renews or ends. Apple handles payment entirely — we never receive your card or bank details.
Usage analytics
See section 3.
Service and security data
Our server counts how many prayers your account has asked the AI to write each day, to enforce a daily limit. Our backend provider processes your IP address and basic request details to run the service, keep short-lived logs, and limit repeated sign-in attempts.
From Apple
If you have chosen in iOS to share analytics with app developers, Apple may give us crash reports and aggregated usage statistics. Those come to us under Apple’s privacy policy.
What we don’t collect
AmenAlarm doesn’t access your location, contacts, photos, camera, microphone or health data. It contains no advertising SDKs, it doesn’t track you across other companies’ apps or websites, and it never records your screen. Alarms are scheduled on your phone, so we don’t collect push notification tokens.
2. Your prayer requests and the AI
In the morning flow, after the passage and its teaching, AmenAlarm asks what’s on your heart. That is the one place where something you write is sent to an AI service. Here is exactly what happens.
- When you continue, the app sends what you typed to our server over an encrypted connection, together with the opening half of that morning’s prayer. The opening was written in advance and is the same for everyone who reads that passage. If you tap Nothing today, only the opening is sent.
- Our server sends those two things to OpenRouter, an AI routing service, which passes them to Anthropic’s Claude model. OpenRouter may reach Claude through Anthropic directly or through a cloud company that runs Claude for Anthropic: Amazon Web Services, Google Cloud or Microsoft Azure. Claude writes the closing half of the prayer from your request, a second pass reads the whole prayer back to check that the two halves join, and the finished prayer comes back to the app.
- Only your request and the opening are sent. Your name, email address and account ID are never included, and because our server makes the request, the AI providers don’t receive your device’s IP address.
- Nothing else in AmenAlarm is ever sent to an AI — not your journal, your answers to the two questions, your setup answers, your alarms or your feedback.
- Our server doesn’t log your request or the prayer; it passes them through. The copy we keep is the entry in your journal (section 1), saved when you tap Amen.
- OpenRouter doesn’t store the content of requests unless an account turns on logging, and ours doesn’t. When Anthropic runs the request itself, it doesn’t train its models on the content, and deletes it within 30 days unless it is flagged for breaking Anthropic’s usage policy (then up to two years) or the law requires otherwise. When a cloud company runs it, that company handles it under its own business terms, which don’t let it use the content to train AI models. Each processes it as our service provider (section 6).
- If the AI can’t be reached — no signal, a timeout, or the daily limit — the app finishes the prayer on your phone from pre-written closings, with your request included word for word, and nothing is sent.
- When Claude writes the close, it also says whether your request mentions something like self-harm or abuse. When the AI isn’t used, a short word list on your phone makes the same check. If it does, the app shows a quiet card with ways to reach support. That result is never saved, and never sent to analytics.
Everything else in a morning — the passage, the teaching and the opening of the prayer — was written in advance and ships inside the app. No AI is involved when you read it.
3. Usage analytics
We use PostHog to understand how the app is used. PostHog receives:
- which screens you open, by name only (for example “/pray/request”) — never what is on them;
- when the app is installed, updated, opened and sent to the background;
- a short list of events: you signed up (and whether with email, Apple or Google), how you answered the alarm permission, a purchase (which plan), onboarding finished, and a morning finished (with your streak count, and whether the end of the prayer came from the AI or a pre-written one);
- device details its software attaches: device model, iOS version, app version, language and region setting, and time zone.
PostHog also receives your IP address with each request and may use it to estimate a rough location, such as your country and city.
These events are linked to your account ID — a random identifier — never to your email or name. Before you sign up, events are recorded under a random ID, which is linked to your account when you sign up.
PostHog never receives your prayer requests, your prayers, your journal, your answers to the questions in the prayer flow or during setup, your name or your email. There is no session replay and no recording of what you tap.
You can switch analytics off at any time in Settings → Share usage data. The choice stays on that phone, even if you sign out. When you delete your account, we also delete your analytics history from PostHog.
4. How we use it
- To run AmenAlarm — your account; backing up your journal, alarms and streak, and restoring them when you log in on a new phone; writing the end of your prayer; and your subscription.
- To speak to you — your name in the app, and your setup answers to shape what onboarding says back to you.
- To send account email only — the code that confirms your email when you sign up, and the code to reset your password. We never send marketing email to your account address.
- To keep the service safe — the daily limit on AI prayers, and limits on repeated sign-in attempts.
- To improve the app — through the analytics in section 3.
- To answer you — when you send feedback or email us.
We don’t sell or rent your personal information, we don’t show ads, and we don’t use your prayers to train AI models. We don’t read your journal except where it is strictly necessary — for example, to fix a problem with your account that you have asked us to look into, or where the law requires it.
5. What stays on your phone
AmenAlarm keeps a working copy of your data on your iPhone, so a morning works with no signal: your alarms, your most recent 120 mornings, your streak, your name and your haptics setting. Changes are saved on the phone first and backed up to your account when there is a connection. Your sign-in session is stored in the iOS Keychain, which is encrypted.
Signing out sends any last changes, then clears AmenAlarm’s data from the phone and cancels its alarms. Your account and its backup stay on our server until you delete the account, and logging back in restores them. iOS can keep the Keychain sign-in after the app is deleted, so reinstalling AmenAlarm may sign you straight back in — sign out first if you are passing the phone on.
6. Who we share it with
We use a small number of service providers to run AmenAlarm. Each receives only what it needs for its job, processes it on our behalf under its data processing terms, and is required to protect it at least as well as this policy describes.
- Supabase — hosts our database, accounts and server functions. Stores everything in section 1 except subscription status and analytics. (privacy policy)
- Resend — sends the sign-up and password-reset emails. Receives your email address and the email. (privacy policy)
- OpenRouter and Anthropic — receive your prayer request and the opening of the prayer, as described in section 2. Claude may be run for Anthropic by Amazon Web Services, Google Cloud or Microsoft Azure. (OpenRouter privacy policy, Anthropic privacy policy)
- RevenueCat — manages subscriptions. Receives your account ID, your purchase and renewal history from Apple, and basic app and device details such as app version and country. (privacy policy)
- PostHog — analytics, as described in section 3. (privacy policy)
- Apple — Sign in with Apple, App Store billing, the alarms (scheduled by iOS on your phone), and the rating prompt. (privacy policy)
- Google — Google Sign-In, if you use it. Google knows you signed in to AmenAlarm with your Google account. (privacy policy)
- Vercel — hosts this website. (privacy policy)
- LaunchList — keeps the list from the waitlist this website ran before launch (section 15). (privacy policy)
We may also disclose information when the law requires it, or to protect someone’s safety or our rights. If AmenAlarm is ever sold or transferred, your information would pass to the new owner only under the protections in this policy, and we would tell you before anything about it changed.
7. Where it’s stored
Your account and journal are stored with Supabase in the United States (Oregon). PostHog, RevenueCat, OpenRouter and Resend process data in the United States. The cloud companies that run Claude may process a prayer request in the United States or in another country where they operate.
If you use AmenAlarm from outside the US, your information is transferred to the US. For users in the EU, EEA, UK and Switzerland, we rely on the Standard Contractual Clauses in our providers’ data processing terms, or on the EU–U.S. Data Privacy Framework and its UK and Swiss extensions where a provider is certified under it.
8. Security
- Everything between the app, our server and our providers travels encrypted (HTTPS/TLS).
- Database access rules (row-level security) mean only your signed-in account can read or change your rows. Another person’s account can never read your journal.
- On your phone, your session is stored in the iOS Keychain, not in plain files.
- The keys for our AI provider and other services live only on our servers, never inside the app.
- Feedback can be sent from the app but never read back from it.
To be plain about it: your journal is not end-to-end encrypted. It is stored in our database, and like any service built this way, we as the operator are technically able to access it. We don’t read it except as described in section 4. Our database provider encrypts all stored data at rest (AES-256).
No system is perfectly secure. If a breach ever affects your information, we will tell you as the law requires.
9. How long we keep it
- Your account, profile, journal, alarms and streak — until you delete your account. Your phone keeps your newest 120 mornings; the server keeps all of them.
- AI usage counts and the Apple token — kept with your account and deleted with it.
- Deleting your account — Settings → Delete account immediately deletes your profile, every morning in your journal, your alarms, your streak, your usage counts and your Apple token; tells Apple to end Sign in with Apple for AmenAlarm; asks PostHog to delete your analytics history, which PostHog completes in the background; and removes your email address from any feedback you sent. It then clears the phone and cancels its alarms. This can’t be undone.
- Feedback — kept after your account is deleted, for our product records, with nothing left on it that says who sent it.
- Email you send us — kept as long as we need it to help you. Ask us and we’ll delete it.
- Backups — deleted data can remain in our database provider’s encrypted backups for a short time, no more than 30 days, until those backups are replaced.
- Server logs — short-lived, and deleted automatically by our backend provider.
- Analytics — kept for the retention period of our PostHog plan, at most seven years, unless you delete your account first.
- Subscriptions — Apple and RevenueCat keep their own transaction records. RevenueCat’s is linked to your account ID, not your name or email; email us if you’d like it deleted. Deleting your AmenAlarm account doesn’t cancel your subscription — that is done in your Apple ID settings.
- The waitlist — until you ask to be removed.
10. Your choices and rights
- Export — Settings → Export my prayers shares the mornings on your phone (your newest 120) as text through the iOS share sheet. For a copy of everything we hold about you, email us.
- Correction — tap your name in Settings to change it. For anything else, such as a journal entry, email us.
- Deletion — Settings → Delete account, as described in section 9. If the app is asking you to subscribe, the account button in the top corner of that screen has Delete account too. You can also email us from the address on your account and we will delete it for you.
- Analytics — Settings → Share usage data.
- The AI — the prayer request is optional. Tap Nothing today and nothing you write is sent.
- Alarms — iOS Settings → AmenAlarm.
- Apple and Google — you can disconnect AmenAlarm from your Apple ID (iOS Settings → your name → Sign-In & Security → Sign in with Apple) or from your Google account (myaccount.google.com/connections).
To use any of these rights, use the controls in the app or email support@amenalarm.app. We reply within 30 days, and may ask you to write from the email address on your account so we know the request is yours.
11. Religious beliefs and sensitive information
Using AmenAlarm, a Christian prayer app, can reveal your religious beliefs. So can what you write in a prayer request, which may also touch on your health, your family or other private matters. The GDPR and several US state laws treat this as sensitive information, and we handle it that way:
- We use it only to provide AmenAlarm to you, as this policy describes.
- We never use it for advertising, never sell it, never use it to build a profile of you, and never use it to train AI models.
- Where the law requires consent to process it, we rely on your explicit consent. You give it when you create your account and agree to this policy, and again each time you choose to write a prayer request. You can withdraw it at any time by deleting your account or emailing us, and you can stop sending new requests by tapping Nothing today.
Prayer requests often mention other people. Write only what you are comfortable having stored in your journal and sent to the AI as described in section 2.
12. For users in the EU, EEA and UK
The data controller is Thomas Bowen, who can be reached at support@amenalarm.app or +1 214-500-9656. We process your information on these legal bases:
- Performance of our contract with you — your account, the backup, writing your prayer, and your subscription;
- Your explicit consent — for information that reveals your religious beliefs (section 11). If you are under the age at which you can give this consent yourself where you live (13 to 16, depending on the country), your parent or guardian gives it for you;
- Our legitimate interests — keeping the service secure and preventing abuse, understanding how the app is used through the analytics in section 3 (which you can switch off), and replying to feedback;
- Legal obligations — keeping records the law requires, and responding to lawful requests.
You have the right to access, correct and delete your personal data, to receive a copy of it, to restrict or object to how we process it (including the analytics), and to withdraw consent at any time, which doesn’t affect processing before you withdrew it. The in-app tools in section 10 cover the most common requests; for anything else, email us. You also have the right to complain to your local data protection authority — in the UK, the ICO.
AmenAlarm makes no decisions about you by automated means that have legal or similarly significant effects. The AI writes the words of a prayer; it doesn’t decide anything about you.
13. US state privacy rights
California and a growing number of states — including Colorado, Connecticut, Texas and Virginia — give their residents rights over their personal information. In the last 12 months we have collected these categories: identifiers (name, email address, account ID, IP address); sensitive personal information (account log-in details, and religious beliefs revealed by your use of the app and your prayer requests); content you create (prayer requests, prayers, alarm labels, feedback); commercial information (subscription status); internet or other electronic activity (app events and screens viewed); and general location estimated from your IP address. We collect it from you, from your device and from the providers in section 6, use it for the purposes in section 4, and disclose it only to those providers.
We don’t sell personal information or share it for cross-context behavioral advertising, and we use sensitive personal information only to provide the service you asked for. You have the right to know and access what we hold about you, to delete it, to correct it, to get a portable copy, and not to be treated differently for using any of these rights. You can make a request yourself or through an authorized agent by emailing support@amenalarm.app. If we decline a request, you can ask us to reconsider by replying to our answer, and if you are still unhappy, you can contact your state attorney general.
14. Children and teens
AmenAlarm is for people aged 13 and older. It isn’t directed to children under 13, and we follow the US Children’s Online Privacy Protection Act (COPPA) by not collecting personal information from them. Setup asks for your birthday before anything you’ve entered leaves your phone. If it shows you’re under 13, the app stops there: nothing you entered is sent anywhere, usage analytics is switched off on that phone, and the app won’t ask again. If you believe a child under 13 has an account, email us and we will delete it.
If you’re 13 to 17, you need a parent’s or guardian’s permission to use AmenAlarm, and we ask that they read this policy and our Terms of Use with you. Your account works the same way as anyone else’s, and everything in this policy applies to you, including how your prayer requests are sent to the AI (section 2) and your right to delete your account at any time (section 10). AmenAlarm shows no advertising, and we never sell anyone’s information.
15. This website
amenalarm.app is a static website hosted by Vercel, which processes your IP address to serve the pages. Our code sets no cookies and runs no analytics. The pages load their fonts from Google Fonts, so your browser connects to Google, which receives your IP address and browser details.
Before AmenAlarm launched, the home page had a waitlist form. If you joined it, LaunchList keeps your email address on that list for us. We use it only to email you about AmenAlarm, and you can ask to be removed at any time. The site no longer collects email addresses or loads anything from LaunchList.
16. Changes to this policy
When we change this policy, we will post the new version here and update the date at the top. If a change meaningfully reduces your privacy, we will take reasonable steps to tell you in the app before it takes effect.
17. Contact us
Email support@amenalarm.app, or call +1 214-500-9656. AmenAlarm is operated by Thomas Bowen, a sole proprietor.