Privacy Policy

Overview

Bible Glide lets anyone search and read Bible passages without an account. Accounts are used for small groups, churches, communities, lesson planning, notes, comments, invitations, notifications, and paid church workspaces.

Information We Collect

On the website, we use PostHog for basic web analytics such as page views, page leaves, sessions, sanitized screen paths, referrers, timestamps, landing-page scroll depth, search-form engagement, tutorial engagement, analytics prompt outcomes, reader readiness, reader load-speed buckets, search no-result signals, invite auth handoff signals, reader active-time conversion milestones without passage references, and current or recently stored advertising attribution labels such as source, medium, campaign, creative, timestamp, and click identifier type. Partner referral links may also store and send the partner code and landing path so signups and subscriptions can be credited. We do not send or store the raw ad click identifier value. When advertising measurement is configured, Meta Pixel may receive standard website events such as page view, checkout started, and subscription started, with church plan type and price but without Bible passage, note, comment, or message content. We also use PostHog for operational diagnostics on the website, including handled and unhandled error reports needed to understand reliability issues. On the website, product analytics events can include app opens, screens viewed, passage references opened or shared, detailed reading engagement milestones, reading depth milestones, chapters reached while reading, selected Bible canon or translation, reader preference changes, offline download status, account actions, group and community activity, church onboarding, invitation events, notification settings, billing-flow status, form-validation failures, blocked actions, and flow status such as started, completed, or failed with coarse duration buckets. In the iOS app, these product analytics events run by default when PostHog is configured. The study API may also send redacted server logs to PostHog Logs, including rejected or failed request method, route or path, response status, latency, service environment, named account, group, church, and community lifecycle diagnostics, internal user/resource IDs, coarse counts, and anonymous PostHog distinct/session IDs when the app can provide them.

PostHog may also process technical information needed for analytics and diagnostics, such as an anonymous distinct ID, IP address, browser or webview details, device type, operating system details, timestamps, and network status.

If you create or use an account, Bible Glide collects the information needed to run those features, including email address, password authentication data, real name, public display name, optional profile image, church and group memberships, invitations, lesson plans, notes, comments, reports, notification preferences, billing entitlement status, optional AI personalization answers, AI chat messages, and prompts used to create custom daily Scripture plans. If your account is credited to a partner referral, we store the partner code, attribution timestamps, subscription ledger rows, and payout status needed to administer that program. Group leaders may optionally record lesson-planning audio so Bible Glide can transcribe the recording and fill editable lesson fields. Daily AI verse reminder delivery may store delivery status, provider, and action URL metadata. Group, community, church, profile, and AI content may include names, descriptions, images, audio recordings, transcripts, Scripture references, messages, and faith-context details that you or other members provide.

What We Do Not Collect

We do not ask for phone contacts, precise location, payment card numbers, seed phrases, or private keys. Voice input for AI prompts and lesson drafting is optional and depends on your browser or device controls. We do not use advertising identifiers, third-party ad tracking, raw advertising click identifiers, PostHog heatmaps, PostHog session replay, or automatic click capture by default. PostHog URLs are stripped of query strings and fragments before they are sent, and individual passage, group, community, and church detail paths are normalized. Server logs sent to PostHog are configured to redact emails, passwords, tokens, confirmation URLs, request bodies, secrets, private keys, and payment-provider payloads.

Analytics Choices

Basic website analytics, operational error diagnostics, and product analytics currently run by default where the tracker is configured, including the website and iOS app.

Analytics On

Retention and Choices

Reading Bible passages does not require an account, so analytics, diagnostics, and app events for reader-only visits are generally associated with an anonymous distinct ID rather than a named profile. Signed-in group, community, church, billing, and notification features are associated with the account that uses them, and PostHog People profiles may include your Bible Glide account ID, email address, name, church membership counts, church role, subscription status, and related account properties so we can understand product usage and reliability for account workflows. We retain analytics and diagnostic data in PostHog according to our project retention settings.

You can clear local Bible Glide data by deleting the app or clearing the website data for Bible Glide in your browser. Signed-in users can delete their account from the Account page. To ask questions, request deletion of analytics data associated with your device, ask about referral attribution tied to your account, or revoke consent where applicable, contact support@bibleglide.com.

On-Device Storage

Bible Glide stores some settings locally on your device, including preferred Bible text, reader preferences, recent searches, last reading position, and whether the verse-selection tutorial has been shown. The website may also store signed-in session state, pending invite or church-join intent, and sanitized first and last paid-attribution labels for up to 30 days, without raw ad click identifiers, so later direct-return engagement can still be credited to the earlier ad visit. Partner referral codes may be stored locally and in a first-party cookie for up to 180 days so signup or checkout can credit the referring partner. This local data helps the app remember your reading experience and understand which outreach is working.

Web Analytics

On the website, Bible Glide uses PostHog Web Analytics for lightweight traffic analytics, and PostHog Error Tracking for operational diagnostics. If configured for paid advertising, Bible Glide may also use Meta Pixel for standard web conversion events. Bible Glide may also send minimal website engagement events for sanitized screen views, the landing page, and reader, such as scroll milestones, search-form engagement, tutorial progress, analytics prompt outcomes, reader/search readiness or no-result signals, invite auth handoff signals, reader active-time conversion milestones, and whether a visit appears to have current or recently stored paid advertising attribution. These web analytics and web error-tracking paths are disabled in the iOS app build.

Third-Party Services

Web traffic analytics, operational diagnostics, website product analytics, and native product analytics are processed by PostHog when configured. PostHog may also process redacted study API server logs for operational diagnostics. Paid advertising conversion events may be processed by Meta when Meta Pixel is configured for website conversion measurement; we do not send identified iOS app activity to Meta for cross-app tracking. Email delivery may be handled by an email provider. Payment checkout, subscriptions, and billing portals are processed by Stripe on the web and by the relevant app-store provider in native apps. Push notifications use the platform notification services for the device. Public community posts, comments, moderation reports, leader lesson-plan draft requests, leader lesson audio recordings and transcripts, premium AI chat messages, and custom daily Scripture plan prompts may be processed by moderation, transcription, and AI providers to filter abuse, check safety, check Scripture relevance, draft lesson plans, answer Bible-study questions, and generate personalized Scripture-reference plans. Referral partners may receive payout reports with aggregate eligible revenue, commission, and payout status for their referral code, not your Bible reading, note, comment, group, or AI message content. Bible text is bundled with the app and normal reading does not require fetching Bible content from a third-party Bible API.

Contact

For privacy or support questions, contact support@bibleglide.com.

Read the Terms of Service.