Your prayers deserve care.

The short version

• Reminders, guided pauses, devotionals, the offline KJV Bible, private prayer writing, and your journal do not need an account.
• Your journal stays on your device. It is not sent to AI or shared with the community.
• Online prayer is optional. When you turn it on, your request is processed by our backend and AI services.
• Community requests and replies are shared with signed-in members. Prayer memory is a separate, optional account feature.
• The app has no advertising or cross-app advertising tracking. Tips are optional Apple purchases.

Your device-local information

Reminder times, Bible reading position, and journal entries are stored on your device. The complete KJV text and its search are bundled in the app; Bible reading and search do not contact a Bible service. Reminders use local iOS notifications.

The journal uses iOS complete file protection. Entries may be included in ordinary device backups depending on your settings. There is no journal cloud sync, separate passcode, or biometric lock in this version; someone using the unlocked app can read it.

Saving a prayer, your own community content, saved prayer memory, devotional, or verse to the journal creates an independent local copy. It does not remove its source. Deleting your online account does not delete this separate journal. Deleting the app or losing the device without a usable backup can erase your entries.

Accounts and prayer memory

If you choose an account, Supabase handles your email, credentials, account identifier, and authentication session. When you sign in with Apple or Google, their sign-in service handles your password; the app does not receive it. Transactional account emails are sent using Resend. We use these services to authenticate you, send confirmation and recovery messages, and provide account features.

Prayer memory is off by default and is tied to the account that enabled it on this device. When enabled, submitted online requests and generated prayers are saved under that account so later prayers can use recent context. You can review and delete individual memory entries or clear prayer memory in the app.

Online prayer and AI screening

Private prayer responses are composed on-device by default. If you turn on the online companion, the words you submit are sent through a Supabase Edge Function to OpenRouter and the model provider used for the response. The current configured model is Google Gemini 3.1 Flash Lite through OpenRouter. When prayer memory is enabled, excerpts from up to five recent saved requests and prayers can be included.

Community requests, replies, prayer updates, and their display names also go through AI safety screening before publication. This screening is part of community posting even when your private online prayer companion is turned off. Automated responses and screening can be mistaken.

Our OpenRouter requests require routes marked for zero data retention and deny provider data collection. These settings restrict eligible routes; they are not a promise that every service has no operational, billing, or security records. OpenRouter and model-provider policies still apply. Please avoid sending sensitive identifying information about yourself or another person.

For abuse prevention, the backend stores a keyed, one-way hash of an account identifier or gateway-provided network address with a daily request count. That pseudonymous value may be sent as an AI safety identifier; the raw account ID or network address is not sent for that purpose. Quota rows older than eight days are removed during later requests. Community posting limits use account identifiers and time-window counts.

Community visibility and moderation

Requests, replies, author updates, display names, and prayer statuses are stored so signed-in members can see them. Choosing an anonymous display name does not remove the account association used by backend safety systems. These are community conversations, not private messages.

“I prayed” stores an account-linked acknowledgement to prevent duplicate counts and allow you to undo it. Members see aggregate counts, not the identities of people who prayed. Reports, block relationships, moderation notes, and audit records are used to handle safety concerns. Authorized moderators can review reported content and take moderation actions.

Blocking hides your requests and replies from each other in ordinary member views; authorized moderators keep review access. You can delete your own messages, close replies on your request, and mark a request answered or closed. Deleting a request deletes its discussion. Other people may have already seen or copied content you shared.

Community conversations and the support inbox are not continuously monitored emergency services. Contact local emergency services if someone is in immediate danger.

Optional tips

Apple processes optional one-time tips through StoreKit. The app receives transaction information to verify completion and recover interrupted purchases, not your payment-card or bank details. Tips do not unlock features. Apple manages payment records and refund decisions under its own policies.

Service providers and technical records

Supabase provides authentication, database hosting, and backend functions. OpenRouter routes AI requests to model providers. Resend delivers account emails. Apple provides app distribution, device services, sign-in, and purchases. Google provides its sign-in service when you choose it. These providers can process technical information needed for delivery, security, and operation, such as network addresses, request metadata, authentication events, or delivery records.

Reading this support website also sends normal browser and network information to the hosting infrastructure. We have not added advertising, analytics trackers, a prayer form, or a journal-upload feature to this website. Contacting support sends your email address and the message you choose to send to our support inbox.

Provider information: Supabase privacy, OpenRouter privacy, OpenRouter retention controls, Resend privacy, Apple privacy, and Google privacy. Our backend project is hosted in the United States; service providers may process information in other locations.

Retention, deletion, and your choices

Account data, community content, and prayer memory are kept to provide the associated features until you delete the relevant content or account. Reports and moderation records follow the related account/content deletion relationships; a departing moderator’s identifier is removed from retained audit entries. Limited technical logs, service-provider records, and backup copies can remain under the relevant provider’s retention practices. We do not promise immediate removal from all backups.

To delete an account and its associated hosted content, open More → Account → Delete account. Apple-linked accounts require a fresh Apple confirmation so the protected deletion service can revoke Apple authorization; the short-lived authorization code is not retained for future use. Local journal entries and Apple’s purchase records are separate from the online account.

You can leave online prayer and memory off, delete memory or your own community content, undo prayer acknowledgements, block or report members, sign out, and turn off notification permission in iOS Settings. For access, correction, deletion, or other privacy questions, email support@dmcmgp.com. We may ask for information needed to verify ownership. Do not send your password.

Updates and contact

We will update this page when the app’s privacy practices change and revise the date above. Questions about this notice or a concern about information shared with the app can be sent to support@dmcmgp.com.