Updated November 2, 2026
Your reading. Your writing.
This Android privacy policy applies to Biblegram, package app.biblegram.android, operated by Blooms AI technologies LLC. Contact info@biblegram.life about privacy.
Device and account libraries
You can use three fixed reading previews, keep personal writing and write prayers without an account. An optional account uses your email address and an email code or existing password. Supabase Authentication, database and private Storage then sync your account identifier, optional name and photo, Study highlights, notes and excerpts, follows, reading preferences, prayers, original recordings, transcripts and separate processing results. Writing you choose to save may contain personal or religious information; Biblegram does not require a religious affiliation. Signed-out and account libraries stay separate, and guest items are copied only when you select them for import. Android session credentials and offline access leases use Android Keystore encryption. App data stays in private Android storage and Android app-data backup is disabled. Cloud sync is access-controlled; it is not described as end-to-end encryption.
Reading continuity and conversations
For signed-in full-access readers, Biblegram stores delivered public post IDs, delivery times, last-active time, a time zone and publisher follows in Supabase for reading continuity and personalization. Private prayers and recordings are not used for the public feed or advertising. Public like totals are anonymous; there is no public liker list or public reader profile. Optional approved comments, your chosen discussion name and public @handle, and an optional prepared square account photo appear in conversations. Your email and private writing are not automatically published. Android’s photo picker supplies only the photo you select; the app uploads a small square JPEG without the original metadata.
Community safety and private notifications
The community agreement explains before submission that your comment, discussion name and public @handle are sent through Biblegram’s private Supabase service to OpenRouter and the configured DeepSeek model provider for AI safety screening. Uncertain submissions can be held for human review. The photo, private Study, prayers, transcripts and audio are not included in those screening requests. Supabase stores community consent, submitted comments, moderation and provider receipts, reports, blocks, mention targets, watches and your private notification inbox/read status. Mentions bind to the selected reader when submitted; later handle changes do not redirect them. You can report concerns, block or unblock readers, remove your comments or contact support.
Google Play subscriptions
Android trials and subscriptions use Google Play Billing. Google processes payment; Biblegram does not receive payment-card or bank details. The app sends the purchase token and Android package name to Biblegram’s private verification service. That service fetches the current purchase from Google, checks its obfuscated Biblegram account binding, acknowledges it and keeps a service-only account association, purchase token and hash, product, state, expiry, verification time, test/production status and receipt hash. These records support access, restoration, expiry and security. Google subscription-status notifications, when enabled, cause another current purchase lookup and do not directly grant access. Offline access is account-bound and limited to the server’s verified deadline. After full access ends, saved personal writing and three fixed previews remain available, and new written prayers remain free. Deleting a Biblegram account does not cancel a Google Play subscription; manage or cancel it separately in Google Play.
Recordings and on-device speech
The microphone is used only for recordings you start. Original saved audio is retained when recording is interrupted. An optional account syncs recordings in private Supabase Storage. Saved-recording transcription uses Android’s on-device speech service and a supported installed language model; availability and quality depend on the device. The app retains original audio and recovered transcript drafts when recognition cannot finish. You can listen, export audio and edit a transcript. Audio is not sent to OpenRouter for private writing.
Optional private AI writing
Private cloud writing is optional and asks for account-level consent. Selected Study scripture and notes, written prayer text or transcripts are sent through Biblegram’s private Supabase service to OpenRouter and the configured DeepSeek model provider. Generated commentary stays separate from your original writing and can contain errors. Sources, durable request identities, results and provider usage receipts are saved privately so an interrupted response can reconcile the same request. Results for earlier writing stay labelled. Provider routing requires no prompt retention or model training; provider billing, request and security metadata may still be retained under provider policies. Biblegram does not use private writing for the public feed, advertising or model training.
Optional notifications
Daily reading reminders are scheduled locally. In builds with new-reading alerts available, explicitly enabling them and allowing Android notifications registers a Firebase Cloud Messaging installation/token with your account in Supabase. Google delivers a generic alert containing an opaque reading-batch identifier. Private prayers, notes, audio, email and account names are not in notification payloads. The app checks the current account before opening that batch. Server claims use completed reading groups, at least three new posts and at most two alerts per local day. Invalid tokens are disabled. Signing out disables registration when connected, and account deletion removes it. You can turn notifications off in the app or Android Settings.
Providers, transfers and exports
Supabase provides account authentication, app data and private files. OpenRouter and the configured model provider process selected text as described above. Google handles Play purchases and optional push transport. Providers receive ordinary request/security metadata, such as IP addresses, request times and delivery status, to operate and secure the service. App/server transfers use HTTPS. Biblegram Android has no advertising SDK, advertising identifier, cross-app tracking, Google Analytics or third-party product-analytics SDK. Sharing and saving artwork add the Biblegram watermark and use destinations you choose. Private-library archives include saved records, readable writing, drafts and available original recordings. Choose a private destination: exported or shared copies are managed by you and the recipient or destination service.
Retention, removal and your choices
Account data is retained to provide your library until you remove it or delete the account. Confirmed removal of a synced prayer removes its active server recording and writing jobs. Account deletion removes active private writing and recordings, account-linked Biblegram purchase records, reader photo, community acceptance, the author’s public comment text and private moderation data, handle, inbox and follows. Other readers’ replies, non-content deletion receipts and reports needed to review concerns may remain. Previous exports, cached copies on another device and provider security logs/backups may persist under their own retention settings. Removing active data does not instantly purge every backup or recall exports. You can keep a signed-out library, select guest items to import, manage permissions, withdraw optional writing consent, edit transcripts, export, sign out and request account deletion in the app or through the published deletion-support route. Account ownership is verified before private data is disclosed or removed.
Account-deletion instructions · Support · Community guidelines
