Your prayer space is yours.

Information we use

• Account: Google or Apple sign-in provides an account identifier and may provide an email address and display name. Supabase stores the authentication account.
• Prayer data: We store your prayer preferences, reminder setting, optional custom prayer topic, and completed prayer sessions with their time, duration, type, and any memo in your Supabase account.
• On your device: Onboarding and unfinished prayer drafts, app language, downloaded Bible text, and local reminder schedules may be stored on your device.

We use this information to sign you in, restore your settings and records, show your prayer history, and schedule reminders you choose. We do not use prayer text or Bible reading to target ads.

Services and sharing

Google or Apple handles the sign-in step you choose. Supabase hosts account and prayer data in the United States. Cloudflare hosts this public information site. We do not sell your personal information. The current production app does not enable PostHog analytics; if analytics are introduced, we will update this policy and in-app disclosures first.

Scripture and reminders

Complete Bible source files are downloaded from public Supabase storage. Reading a passage does not create a server-side reading-history record. Prayer reminders are scheduled locally on your device; you can turn them off in app settings or device settings.

Retention and your choices

Account and prayer records remain while your account is active. You can export your prayer data from the app’s Account & Data screen. To request account and associated data deletion, follow the deletion instructions. Removing the app or its device storage clears local drafts and downloaded files on that device. We may retain information only if required by law or necessary to address a security or abuse issue, and will explain any such retention when responding to a deletion request.

Contact and changes

Questions or privacy requests: asagyu2038@gmail.com. If our data practices materially change, we will revise this page and its effective date before applying the new practice.