Privacy Policy
Last updated: 16 June 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 unless you choose, enable, or use an optional Cloud Assist feature. Website update signups, payment reconciliation, anonymous product analytics, platform-store purchase verification, and optional Cloud Assist requests use small server-side or third-party service records so launch emails, purchases, onboarding flows, quotas, and 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. If you choose, enable, or use optional Cloud Assist processing, selected text, OCR text, topic context, or photos 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 to extract editable photo text. Local OCR runs on your device. Optional Cloud Assist OCR may send the selected image to Prayer First servers and Qwen or OpenRouter-routed providers for processing after upload consent.
- 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 mobile product analytics: Prayer First may send limited events through PostHog, such as app opened, onboarding step completed, and paywall shown. Screen capture, session replay, automatic screen-view capture, and element-interaction capture are disabled. We do not send your journal text, photos, selected apps, foreground app names, Accessibility events, app usage history, or email address.
- 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 Tidy, cloud OCR, or enable Smart Topics, Prayer First may send the selected journal text, OCR text, photo, prompt, existing topic-label context, and request metadata to Prayer First servers and to Qwen or OpenRouter-routed providers for OCR, tidy-note drafting, smart topic suggestions, or related processing after upload consent. 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, image and token counts, provider and model, timestamps, and non-reversible hashes; it does not store raw journal text, photos, or model responses by default. Local OCR, local notes, 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, topic context, or photos 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. If you use it or enable a Cloud Assist feature such as Smart Topics, selected journal text, OCR text, photos, topic context, prompts, and responses may be processed by Prayer First servers and by Qwen or OpenRouter-routed providers after upload consent. Smart topic suggestions may run automatically on saved notes while enabled for a paid account. Local features remain available without Cloud Assist cloud processing.
Original notes remain canonical, and cloud 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, and raw uploaded images are deleted after processing unless a separate debug or support flow is clearly enabled. 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 Cloud Assist requests or enabled Cloud Assist features you consent to. 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