Privacy Policy

• Verum Bible is owned and operated by Ryan Knaggs, a sole proprietor.
• Guest reading data is stored in your browser’s local storage.
• If you create an account, Supabase handles authentication and syncs selected study data to your account.
• If you use the AI Study Assistant, the question you submit is sent through Verum Bible’s Cloudflare Worker to OpenAI.
• Verum Bible uses Clevaryn Analytics to understand general use of the Services and interactions. Verum Bible does not use advertising trackers or intentionally write browser cookies.

The Services use local device storage—browser local storage on the website and corresponding app storage where a mobile application provides these features—to remember theme, text-size, Scripture-font, high-contrast display, and other Reader appearance preferences, selected Bible translation, recent and last reading locations, highlights, bookmarks, notes and note tags, reading-plan progress, Path progress, reading streak dates, study history, local account identity, and—when signed in—the Supabase session needed to keep the account active.

Local device storage stays associated with the browser profile or app installation on that device until it is cleared, overwritten, or migrated into an account-specific local record. Other people using the same unlocked browser profile or device may be able to view it.

When Supabase account features are configured and you choose to sign up or sign in, Supabase receives your email address, password credentials, optional display name, and authentication information. Verum Bible stores the resulting session in local storage available to the Services.

Signed-in sync can send preferences, notes, highlights, bookmarks, reading location, reading-plan progress, Path progress, reading streak activity, and recent passage-study history to Supabase. Supabase’s authentication service handles password-reset emails.

Passwords are submitted to Supabase for authentication and are not added to Verum Bible’s study-data records. Do not place confidential information in Bible notes if you do not want it stored locally or, while signed in, synced to your account.

Friends is an optional signed-in feature. Friend search returns only a display name, a unique username when one has been chosen, an optional low-resolution avatar, and the internal identifier needed to send a request; it does not expose email addresses, credentials, notes, or other private profile information. Friendship and Journey invitations are visible only to the people involved.

Automatic friend activity sharing is off by default. If you enable it, the selected milestone or progress events may be shown only to current friends. Turning automatic sharing off makes prior automatic events unavailable to friends. A verse, chapter, or short reflection that you deliberately share is treated as an explicit share and can remain available to current friends even while automatic sharing is off.

Private notes, highlights, bookmarks, prayer content, AI Study conversations, private messages, and detailed private reading history are never copied into friend activity events merely because Friends or activity sharing is enabled. Removing or blocking a friend immediately removes friend-based access to activity; permissions for an existing shared Journey continue to follow that Journey’s separate membership controls.

Account-linked application rows are designed to remain available while the account is active. The repository does not define one fixed numeric retention period for this data. When a signed-in user completes the Delete account flow, the server verifies the session and asks Supabase Auth to delete the identity. The database deletion trigger handles applicable Journey-group cleanup, and Supabase’s configured foreign-key cascades remove the linked profile, preferences, notes, highlights, bookmarks, reading state, plan and Path progress, reading activity and streaks, study history, word highlights, prayer notes, audio progress, friend requests and relationships, friend activity and encouragement, account membership rows, user-authored Journey posts/replies/reactions, private conversations and their messages/reads/notifications, and AI usage and reservation rows attached to that identity.

A Journey group with other members is transferred to a remaining member when the deletion service can do so; an empty group is removed with its group-owned records. Other members’ records and a retained group can remain, while rows tied to the deleted user are removed by their own cascades. Group-level realtime events do not carry an account foreign key and can remain while their group remains. The administrator audit log intentionally keeps historical action and target identifiers for audit integrity, so it follows a different lifecycle and is not represented as ordinary user study data.

Analytics, Cloudflare operational records, provider-side AI records, and backups are controlled by the relevant service and may follow their own processes. Account deletion does not necessarily remove information that Verum Bible or a service provider must legitimately retain, where applicable, for security, fraud prevention, legal obligations, transaction records, dispute handling, or essential operational purposes. Verum Bible does not state a fixed period for those records or promise immediate physical removal from every backup. Guest and other local device data remains on each browser or app installation until that device’s site or app data is cleared; a server request cannot clear a different device’s local storage.

The AI Study Assistant is optional. When you submit a question, Verum Bible sends the question to a Cloudflare-hosted API, which forwards it to OpenAI to generate a response. The current integration requests that OpenAI not store the generated response by setting store: false.

Do not include private notes, names, contact information, health details, financial information, passwords, or other sensitive data in an AI question. Verum Bible does not need that information to provide a Bible-study response.

Cloudflare serves the Services, including website and mobile-application traffic, static assets, APIs, rate limiting, and operational observability. Like most infrastructure, it may process standard connection and request information needed for delivery, reliability, abuse prevention, and security.

The website loads Leaflet styling from the unpkg CDN, and interactive maps also request Leaflet software and map tiles from CARTO, with OpenStreetMap attribution. Those providers receive the network request needed to deliver their resource. Supabase and OpenAI receive data only when you use the associated optional features described above.

Private account tables are protected by Supabase authentication and row-level access rules. Account deletion is authorized on the server; the privileged Supabase key is not sent to the browser. Verum Bible uses HTTPS for deployed requests and limits operational logging to information needed to diagnose and protect the service, but no internet service can promise absolute security.

Verum Bible uses Clevaryn Analytics to understand general use of the Services. Verum Bible serves a reviewed, pinned copy of the analytics client from its own origin, while analytics events are sent to Clevaryn. The analytics script creates randomly generated visitor and session identifiers in browser local or session storage and sends usage information to Clevaryn, including page paths and titles, referral and campaign information, device and viewport measurements, non-content interaction labels, form-start and submission events, scroll depth, session duration, performance measurements, and JavaScript error categories.

The integration is configured to respect a browser’s Do Not Track setting when that setting is reported as enabled. The current script does not intentionally read password or other form-field values. Verum Bible does not use this information for advertising and does not intentionally create browser cookies.

• Use Verum Bible as a guest to keep study data in the browser rather than sync it to an account.
• Sign out to remove the active Supabase session from local storage.
• Clear website data in your browser or app data on your device to remove guest and locally cached Verum Bible information from that device.
• Signed-in users can use the Profile page’s Delete account control. It requires typing DELETE and sends the request to a server-authorized endpoint. If the request does not complete, contact support@verumbible.com.
• For account deletion, access or correction requests, questions about stored information, or other privacy questions, email support@verumbible.com. Account ownership may need to be verified before an account-specific request is acted upon. Do not send a password, authentication code, or private study notes.

Verum Bible is not designed as a service directed specifically to children and does not knowingly build profiles for advertising. Parents and guardians should supervise account use and the sharing of personal information.

This policy will be revised when Verum Bible adds or materially changes data collection, service providers, account controls, or contact methods. The updated date at the top of this page identifies the current version.