Your data at DailyAmen
Privacy
This notice covers the DailyAmen app and this website. Last updated November 10, 2026.
Without an account, your personal content stays on your iPhone. With an account, it syncs between your devices. Comments on the verse of the day are public, requests you share in a prayer circle are seen by its members, and your private notes and prayer history are never shown to anyone else. We don’t run ads or analytics, and we don’t sell data.
Who is responsible
Kahyalar Solutions LLC30 N Gould St Ste N, Sheridan, WY 82801, USA
privacy@dailyamen.io
Write to this address with any privacy question, to withdraw consent, or to ask about the data we hold about you.
Using DailyAmen without an account
Everything you enter stays on your iPhone: the name you’d like to be called, your faith tradition, goals and prayer times, your prayer history and progress, bookmarks, highlights, notes, private journal entries, your private prayer list, special days, prayer routine and season of life, story progress and reading positions. We don’t upload any of it unless you sign in. The Bible texts are part of the app.
Private app content is stored encrypted on the device, with a device-bound key kept in the iOS Keychain. This storage is left out of regular device backups, so to move to a new iPhone, use account sync or make a deliberate export of your guest data. Without either, guest data is lost if you delete the app or lose the device.
Widgets read a small summary that the app keeps in storage shared between the app and its widgets. A widget can show personal information on your Home Screen or Lock Screen; you decide which widgets to add.
Your language settings in DailyAmen (the app language for menus and the language for content and voices) are stored only on your device, in storage shared by the app, its widgets and the pause screen so they all use the same language. If you have an account, we also save the app language in your profile so notifications and inbox messages reach you in that language.
Signing in and syncing
When you sign in, we process an account ID, your email address, the sign-in provider you chose and technical sign-in data. With Apple or Google, we receive the identity details that provider shares for sign-in, never your Apple or Google password. Email sign-in uses short-lived codes, or a password for existing password accounts; that password goes to Supabase when you sign in and isn’t stored by DailyAmen on your device. Your session is kept in the iOS Keychain.
With an account we store and sync your display name, faith tradition, goals, prayer times, prayer history, personal prayer plans, saved verses, notes, private journal entries, your private prayer list, special days, prayer routine and season of life, saved stories and story progress, highlights, reading positions, and display and reading settings. None of this is shared with other users. Content already on your device can be moved into your account when you first sign in.
Faith details, your prayer history and what you pray about can reveal religious beliefs, which the GDPR treats as special category data. We therefore ask for your explicit consent before processing them in your account (Art. 6(1)(a) and Art. 9(2)(a) GDPR). The app explains this right next to the sign-in options, and you give consent by continuing. If you don’t, you can keep using DailyAmen locally without an account. Providing and securing the sign-in you asked for is based on Art. 6(1)(b) and (f) GDPR.
If you delete an account linked to Apple, the app asks you to confirm with Apple again. Our server checks the one-time authorization code and identity proof and sends the code to Apple to revoke the connection. The Apple tokens involved are used only in memory for this step, never stored and never written to our application logs.
Friends, prayer circles and comments
We process usernames, display names, friend requests, invitations and circle memberships. People can find you by your username or your full email address and send you a request. The app never uploads your address book and never publishes a list of email addresses.
In a prayer circle, shared requests, occasion times, later updates and prayer confirmations are visible to that circle’s members, including members who join later. Your personal history and private Bible notes are never shared with the group. Please don’t share other people’s confidential information without their permission; once someone has copied something, we can’t take it back.
We process religious content you choose to share based on your consent. Managing friendships and invitations is part of the account feature you asked for, and our measures against abuse rest on our legitimate interest in running a safe service (Art. 6(1)(f) GDPR).
Reports and blocking
When you report a post, we store the account IDs involved, the circle and post it relates to, the reason, any note you add, the time, and a copy of exactly the reported content. The operator can see this to review it; other users can’t. When a report is handled, we record its status, the decision, who handled it, why and when. Authorized moderators and administrators can review reports and hide or restore content. Role assignments are logged, and only administrators can manage the moderation team.
When you block someone, we store both account IDs and when the block started and ended. This history also stops old notifications from being delivered after an unblock. You both stay members of shared circles. Blocking and moderation can limit which content and contacts you see.
Without an account you can also report public comments in the app. We then store the comment, the reason, your optional text and the time, but no account ID and no device identifier. If you block someone without an account, this is stored only on your iPhone. For this the app receives, with each comment, an identifier of its author that does not lead back to their account.
Team administration, suspensions and support
DailyAmen administrators can view account data for support and moderation: display name, username, bio, language, sign-in method, time of registration and last sign-in, Plus status and its source, and the number of your circles, friends, comments and reports. Prayers, journal, notes and requests in prayer circles are not visible there. Your email address is shown only in individual cases, and every reveal is logged. If the community rules are broken, an administrator can suspend your account from publishing for a limited time or permanently (comments, requests, friend requests and invitations) or reset your display name, username, bio and profile picture. Private use remains possible. We store the reason, duration, time and the person who acted.
With an account, you can send us a message via “Contact support”. We store the topic, text, app version, app language, time and our reply so we can answer you in the app. We delete log entries and answered or closed messages after 12 months, and immediately when you delete your account. The legal basis is handling your request (Art. 6(1)(b) GDPR) and our legitimate interest in secure operation (Art. 6(1)(f) GDPR).
Public comments and reactions
Comments on the verse of the day, with your display name, username and reaction counts, are visible to every app user, even without an account. The friends filter only changes what you see, not who can see a comment. For comments and likes we store the link to your account, the verse or comment, and the time. A Plus supporter sign appears only if you choose one. None of this makes your private notes or prayers public.
We store the language each comment is written in (English, German, Spanish, Portuguese, French, Italian, Polish, Russian, Ukrainian, Romanian or Dutch). Comments in all languages appear together. If you press and hold a comment and choose “Translate”, Apple’s translation feature translates it on your device or on Apple’s servers; DailyAmen receives nothing from this.
Before your first comment, the app asks in its own dialog whether your comment drafts may be sent to OpenAI for an automated content check; you can decline, and you can stop it at any time with “Stop the text check by OpenAI” below the comment field. Only the comment text is sent, never your profile, email address or private prayers. We also check for spam and obvious insults. If a comment is rejected or the check fails, the draft isn’t published or stored as a comment. Technical timestamps and counters help limit abuse. The filter can make mistakes, and you can always contact support. Reports about published posts are also reviewed by people.
Profile picture, badges and encouragement
Your profile picture, an optional bio and the badges you’ve earned are visible to confirmed friends on your profile. You can change or remove the picture and bio at any time. The app shrinks the picture and removes its metadata before upload. People who aren’t your friends can’t load these profile details. “Encouragements sent” counts confirmed prayers for other people’s requests, once per person and request; your private history isn’t revealed to friends.
App lock and notifications
The app lock uses Apple’s Screen Time interfaces. You grant permission in iOS and choose the apps yourself. The selection tokens and lock permissions Apple issues stay on your device. We don’t send your selection to Supabase and never use it for advertising or to analyze how you use your phone.
Prayer time reminders, a daily reminder for the verse of the day and any feast day reminders you turn on are scheduled locally on your iPhone. The in-app notification list shows community events, badges and local notifications still on the device. For community events, read markers are saved in your account; local markers stay on the device. For prayer circle notifications we store a technical device token for Apple Push Notifications and your notification settings. A push notification contains a general message and technical references to the circle or invitation, never the private text of a prayer request. Apple handles delivery. You can turn notifications off in DailyAmen and in iPhone Settings.
AI features
AI companion
The AI companion is available with confirmed Plus, with or without an account. Before your first question, the app asks in its own dialog whether OpenAI may process your questions, including any faith details; only “Allow” turns the chat on, and you can decline. Your question and a limited amount of conversation context go to OpenAI through our server. Private app content is never attached automatically. Finished conversations are stored protected on your device; with an account, they are also synced privately through your DailyAmen account in Supabase. You can withdraw consent at any time under AI chat → Chat history → “Stop AI processing”, and delete individual conversations there; with an account, deletions reach your other devices once they sync. Drafts stay on the device. The service that produces answers doesn’t log questions or answers. Usage counters and aggregate token counts limit abuse and cost and contain no questions or answers. AI answers can be wrong and are no substitute for personal pastoral, medical or legal advice.
Read aloud with DailyAmen voices
Read aloud is part of Plus, and its voices are generated with AI. When you tap “Listen”, the app sends the current paragraph of app or Bible text and the voice you chose to our server. Only if that paragraph hasn’t been recorded yet does the server send the text, and nothing else, to OpenAI to turn it into speech. Your name, account, notes and prayer requests are never sent. We keep the finished recording in a public storage area at Supabase under a file name calculated from the voice and the text, and reuse it for everyone; it contains nothing but the app or Bible text being read. A copy stays in your iPhone’s cache so texts you’ve heard also play offline.
To confirm Plus, the server processes your account ID and your verified Plus status. To keep costs in check, we count newly generated recordings per account and day. You can play the voice samples in “Voice & speed” without Plus or an account; for those we count requests under a daily-changing hash derived from your IP address with a secret value. We never store the IP address itself. Daily counts are deleted after seven days, and an account’s counts as soon as the account is deleted. The legal bases are providing the feature you signed up for (Art. 6(1)(b) GDPR) and our legitimate interest in preventing abuse and runaway costs (Art. 6(1)(f) GDPR). Without an account, the app sends Apple’s signed record of your Plus subscription instead; the server checks Apple’s signature and the expiry date, doesn’t store the record, and counts new recordings under a hash of the subscription made with a secret value.
Purchases and gifts
Purchases go through Apple, and DailyAmen never sees payment or card details. To link a purchase to your account and check access, we process signed Apple purchase records, technical transaction IDs, the product, its term, refund status and your DailyAmen account ID. If you enter a Creator Code or open a creator’s link, we store the code with your DailyAmen account ID. If you then subscribe to Plus, we attribute the subscription to that creator. To calculate the creator’s commission, we keep the transaction ID, product, time of purchase, price, currency, App Store country, offer type and refund status of each payment for up to twelve months, without your name, email address or account ID. Creators only see aggregated numbers and never learn who you are. The legal basis is our legitimate interest in settling accounts correctly with advertising partners (Art. 6(1)(f) GDPR); we keep billing records for as long as commercial and tax law requires (Art. 6(1)(c) GDPR). You can remove a code under Plus before you subscribe, and deleting your account removes it too. Without an account, Plus works on your device: for the AI chat and the DailyAmen voices, the app sends Apple’s signed record of your Plus subscription with each request. The server only checks it; it stores neither the record nor its transaction ID, only a hash of the subscription made with a secret value to count usage limits, deleted after seven days. A Creator Code you enter without an account stays on your device: to show its discount, the app looks the code up on our server without sending any account or device details, and the code is linked to an account only if you sign in later. With it, the app receives an identifier that contains only the creator and the time of the lookup. If you buy Plus without an account, the app passes this identifier to Apple; Apple notes it in the purchase records of your subscription so that we can settle the creator’s commission as described above without you needing an account. The identifier contains nothing about you or your device.
For Plus gifts we store the buyer’s and recipient’s accounts, the occasion, the purchase record, activation and expiry. Buyer and recipient each see their own gift status; nobody else does. If the buyer deletes their account, an already purchased gift stays with the recipient without the buyer’s name or email address. Technical purchase and refund IDs prevent a gift from being redeemed twice. When an administrator grants free access, we also store its term, the reason and a change history, which only authorized administrators can manage.
Verse images, fonts and church search
Custom backgrounds and verse image editing happen on your device. A photo you pick is never uploaded for AI image generation; it only leaves your device when you share an image through the iOS share sheet with an app or person you choose. Extra fonts you select are downloaded from the Google Fonts project via GitHub, which involves the usual connection data; no notes or prayers are sent.
Church search uses Apple MapKit. If you allow location access, it can search near you; you can also type a place. We don’t keep a location history in your account. Apple processes search and map requests under its own privacy policy.
Service providers and international transfers
- Supabase: sign-in, account data, sync, prayer circles and read-aloud recordings. Our project database is in Frankfurt, Germany. Supabase processes data as our technical provider; other countries may be involved for operations, support and subprocessors. Supabase privacy policy.
- Resend: sends sign-in emails, which involves the recipient address, the sign-in code and delivery information. No prayer content is ever sent by sign-in email. Resend privacy policy.
- Apple: optional sign-in, Screen Time, widgets, push delivery and distribution through TestFlight or the App Store. In TestFlight, Apple may collect diagnostics and test information depending on your settings. Apple privacy policy.
- Google: only if you choose “Continue with Google”. We request basic account details for sign-in, never contacts, calendars or Drive files. Google privacy policy.
- OpenAI: the automated check of a comment draft after your consent, answers in the optional AI chat, and turning app and Bible texts into speech for read aloud with Plus. OpenAI doesn’t use data sent through its API to train its models; where the API allows it, our requests are sent with storage turned off, and OpenAI may keep them for up to 30 days to detect abuse. Processing can take place outside Europe. OpenAI’s data usage and retention terms.
- GitHub: delivers the extra fonts you choose from the Google Fonts project. This involves only the usual connection data. GitHub privacy statement.
- Website hosting: this static website is served by Netlify, Inc. Each visit creates technically necessary connection data such as IP address, time, requested page and browser details, used to deliver the site, fix errors and keep it secure, based on our legitimate interest (Art. 6(1)(f) GDPR). Netlify privacy policy.
Each provider listed here receives personal data only for the purpose described and is bound by its data processing agreement or terms of service to protect it at least as well as this notice describes and as Apple’s App Store Review Guidelines require.
We are based in the United States, and our providers and their subprocessors may also process data outside the EEA. A database in Frankfurt therefore doesn’t mean every step happens only in the EU. Ask our privacy contact for details about the safeguards and recipients involved.
How long we keep data
Content on your device stays until you delete it in the app or remove the app. Signing out closes the active view but keeps pending changes encrypted for the next sign-in to the same account; deleting the account removes its data from the device. An older backup that can’t be read may remain as an encrypted recovery copy, unused by the app, if it can’t be safely matched to an account. Account content stays as long as you use the account and don’t delete it. To sync deletions across devices, technical deletion markers without the deleted content may remain.
You can delete your account under “You → Settings → Account & sync → Delete account”. This removes your account data, synced content and your own circle content from the live database, including circles you created. Time-limited backups may still contain data until they are overwritten on schedule; they’re never used to run the app. How long backups are kept depends on our provider’s backup configuration; our privacy contact can tell you more.
We keep support requests as long as needed to handle them and to keep required records. Legal retention duties remain unaffected, and we’ll tell you the retention period that applies to your request.
Closed or rejected reports, including the content copy and handling history, are deleted by a daily cleanup 90 days after they’re resolved; open reports stay until reviewed. Deleting an account removes its links to reports, but the content copy needed to review abuse stays until the report is closed and the 90 days have passed, so it may still contain personal details from the reported text. Logs of moderation role assignments are deleted after 180 days, with links to deleted accounts removed. Block history is removed when one of the accounts is deleted. Cleanup logs only contain times and counts and are deleted after 90 days. Daily read-aloud counts are deleted after seven days. Read-aloud recordings contain no personal data and are kept as long as the related app or Bible text is offered.
Children and age
DailyAmen is rated 13+. Where Apple reports that a law requires an age check (for new Apple Accounts in Texas, Utah and Louisiana), the app asks Apple for your age range through Apple’s Declared Age Range interface before the account step. The answer stays on your iPhone and only decides whether an account can be created. Under 13, no account is offered and DailyAmen works without an account.
Your rights
You can ask for access to, correction and deletion of your personal data and, where the conditions are met, restriction of processing and data portability. Where we rely on legitimate interests, you can object for reasons relating to your situation. You can also complain to a data protection authority, in particular where you live.
You can withdraw consent at any time with effect for the future, by deleting your account in the app or by writing to our privacy contact. Signing out only pauses syncing on that device and doesn’t delete account data. Withdrawal doesn’t affect processing that happened before.
We make no automated decisions that have legal or similarly significant effects on you. Your faith tradition is only used to tailor prayer suggestions.
Ads, analytics and security
DailyAmen contains no advertising or analytics SDK, and we don’t sell personal prayer data. The app doesn’t collect usage analytics in normal use; local usage reports from earlier test versions are removed with the update. Technical test runs use separate test data only, and analysis reports are never sent automatically. This website sets no advertising or analytics cookies, serves its fonts and images itself and embeds no social feeds. If you pick a language or close the language hint on the website, only your browser remembers it in local storage; nothing is sent to us.
Connections to our account services are encrypted, and access controls limit data to its account or to the members of a circle. This isn’t end-to-end encryption: administrators and technical providers authorized for operations and support can access data where necessary.
Contact and changes
When you contact us, we process your message and contact details to handle your request. Please don’t send passwords, sign-in codes or private prayer content we don’t need. Changes to features or services may require updates to this notice, and we’ll ask for new consent whenever a change requires it.
privacy@dailyamen.io · Legal notice
This notice is also available in German. Both versions describe the same processing; if they ever differ, the German version prevails.