Privacy Policy

Last updated: 20 July 2026

Prayer First ("the app", "we") is built and operated by Brian Tan as an independent developer. This policy describes what data the app handles and what it does not.

Summary

Prayer First is designed to keep the core app on your device. We do not have ads or cloud journal sync. Your journal entries, photos, settings, chosen apps, and app-usage decisions stay on your phone during normal app use. Photo OCR runs on your device, and photos and images are never uploaded to Prayer First servers, Qwen, or OpenRouter. Power Pack users on supported Apple devices may also use on-device Apple Intelligence models provided by the operating system to clean up recognized photo text, tidy notes, or suggest smart topics without journal text or photos leaving the phone. Website update signups, payment reconciliation, anonymous product and website analytics, platform-store purchase verification, and optional Cloud Assist text requests use small server-side or third-party service records so launch emails, purchases, onboarding flows, quotas, attribution, and text cloud processing can work.

What the app accesses on your device

• Android Accessibility and app usage permissions: Prayer First uses Android Accessibility and app usage permissions, where you grant them, for app selection, detecting selected app activity, and applying lock rules. Permission state, selected app identifiers, and local diagnostics are stored in the app's private storage and are not sent to us during normal local app use.
• Journal entries and optional photos: Stored locally on your device in the app's private storage. They are not uploaded by Prayer First during normal local app use. Photos are never uploaded by Prayer First. If you choose, enable, or use optional Cloud Assist text processing, selected journal text, OCR text, or topic context may be sent to Prayer First servers and cloud processing providers for that request or enabled feature after upload consent.
• Local journal search and topic data: To power journal search, wiki views, and topic organization, Prayer First may store derived search text, normalized text, non-reversible hashes, on-device embedding vectors, and topic labels from your journal and OCR text in app-private storage. These remain local unless you use or enable a Cloud Assist feature.
• Camera, photo picker, and local OCR: If you choose to add a journal photo, Prayer First may access the selected image and run on-device OCR, using iOS Vision or Android ML Kit, to extract editable photo text. Photos and images are not uploaded to Prayer First servers, Qwen, or OpenRouter. Power Pack users on supported Apple devices may also use on-device Apple Intelligence models provided by the operating system to clean up recognized photo text; if Apple Intelligence is unavailable, Prayer First shows the raw locally recognized text.
• Notifications: If you enable reminders, Prayer First uses local notification permissions to show setup or Bible-time reminders. Reminder contents are generated by the app and are not used to upload your journal, chosen apps, or usage history.
• Settings and entitlement cache: Your lock rule, chosen unlock paths, paid status, student discount email if you enter one, and similar preferences are stored locally on your device.

What leaves your device

• Anonymous product and website analytics: Prayer First may send limited events through PostHog, such as app opened, onboarding step completed, paywall shown, website page viewed, store link clicked, and successful waitlist submission. Website analytics use a random session-only identifier and may include the page path, referring website host, destination store, and campaign tags included in a link. Query-string contents, email addresses, form contents, screen capture, session replay, automatic element interaction, journal text, photos, selected apps, foreground app names, Accessibility events, and app usage history are not sent in analytics events.
• Website waitlist: If you join the free waitlist, we store your email address, platform choice, signup source, and signup time so we can send launch updates.
• Website checkout records: If a website checkout flow is explicitly active and you complete it through Stripe, Prayer First stores your email address, platform choice, checkout/session identifiers, payment status, amount, currency, and purchase time so we can reconcile the purchase and send the relevant launch invite. We do not see or store your full card number.
• In-app purchase and entitlement records: In-app purchases are processed by Google Play or Apple's App Store when available for your platform and may be verified through RevenueCat. Prayer First receives and caches only the limited entitlement status, product identifier, and purchase state needed to unlock paid features and restore purchases.
• Optional Cloud Assist requests: If you use cloud Tidy or enable cloud Smart Topics as a text fallback, Prayer First may send selected journal text, locally recognized OCR text, prompts, existing topic-label context, and request metadata to Prayer First servers and to Qwen or OpenRouter-routed providers for tidy-note drafting, smart topic suggestions, or related text processing after upload consent. Photos and images are never sent for Cloud Assist. Smart Topics may process saved note text automatically while the feature is enabled for your eligible account. Prayer First stores quota and usage metadata such as account ID, feature, request, token counts, provider and model, timestamps, and non-reversible hashes; it does not store raw journal text, photos, prompts, or model responses by default. Local OCR, local notes, on-device Apple Intelligence where available, and local search remain available without Cloud Assist cloud processing.
• No cloud sync, no backups managed by us, no social features.
• No selling or sharing of personal information. We do not have access to your journal, photos, chosen apps, or usage history except for selected journal text, OCR text, or topic context processed through optional Cloud Assist requests or enabled Cloud Assist features after upload consent.

Payments

In-app subscriptions and one-time purchases are processed by Google Play or Apple's App Store when available for your platform and may be verified through RevenueCat. Prayer First does not see or store your full payment details. The platform store's and RevenueCat's privacy policies govern their handling of payment and purchase-verification data. The app receives only the limited purchase records needed to verify or reconcile your entitlement.

Permissions and platform controls

Prayer First uses Android Accessibility and app usage permissions, where you grant them, for app selection, detecting selected app activity, and applying lock rules. You may revoke these permissions at any time in Android system settings; the lock feature will then no longer function.

Optional Cloud Assist processing

Cloud Assist processing is optional and text-only. If you use it or enable a Cloud Assist feature such as Smart Topics, selected journal text, locally recognized OCR text, topic context, prompts, and responses may be processed by Prayer First servers and by Qwen or OpenRouter-routed providers after upload consent. Photos and images are never uploaded for Cloud Assist. Smart topic suggestions may run automatically on saved notes while enabled for a paid account. Local features remain available without Cloud Assist cloud processing.

Power Pack users on supported Apple devices may also use on-device Apple Intelligence models provided by the operating system to clean up recognized photo text, tidy notes, or suggest smart topics. This processing happens on the device; no journal text or photos leave the phone for it. Original notes remain canonical, and cloud or on-device intelligent results are drafts until you accept them. Raw note text, photos, prompts, and model responses are not logged or stored by default by Prayer First. Prayer First may retain limited usage metadata, such as request time, provider, model identifier, quota status, and non-reversible hashes, to operate quotas, troubleshoot abuse, and support deletion requests.

Service providers

Prayer First may use service providers to operate limited parts of the app and website, including PostHog for anonymous product analytics, RevenueCat for in-app entitlement verification, Google Play or Apple's App Store for in-app purchases, Supabase for update signups, payment reconciliation, and quota records, Resend or similar email infrastructure for launch, support, or internal signup/payment alerts, and Qwen or OpenRouter only for optional text Cloud Assist requests or enabled text Cloud Assist features you consent to. On-device Apple Intelligence models are provided by the operating system and are not a data recipient for journal text or photos. These providers process data for the purposes described in this policy.

Children

Prayer First is not directed at children under 13. It is intended for adults choosing to manage their own attention.

Your rights

Most Prayer First data stays on your device. If you join the waitlist or later use Cloud Assist processing, you can ask us to delete the server-side waitlist record or Cloud Assist usage records associated with it. Payment records may need to be retained where required for accounting, tax, fraud prevention, or dispute handling. To remove local app data, uninstall Prayer First or delete its data from system settings.

Changes to this policy

If this policy changes, the "Last updated" date above will change and the new version will be published at this URL. Material changes will also be noted in the app's release notes or store listing.

Contact

Questions or requests: radiansnail@gmail.com

Back