Privacy Policy

• 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’s Cloudflare Worker to OpenAI.
• The current application code does not install advertising trackers or a first-party analytics package, and it does not intentionally write browser cookies.

Verum uses browser local storage to remember theme and text-size 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 storage stays associated with the browser profile on that device until it is cleared, overwritten, or migrated into an account-specific local record. Other people using the same unlocked browser profile 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 stores the resulting session in browser local storage.

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’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.

The AI Study Assistant is optional. When you submit a question, Verum 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 does not need that information to provide a Bible-study response.

Cloudflare serves the website, static assets, API traffic, rate limiting, and operational observability. Like most web infrastructure, it may process standard connection and request information needed for delivery, reliability, abuse prevention, and security.

The site 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.

A review of the current Verum application code found no advertising network, behavioral-advertising tracker, Google Analytics, or similar first-party analytics integration, and no application code that intentionally creates cookies. Infrastructure or linked third-party services may apply their own technical measures under their policies.

• Use Verum 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 site data in your browser to remove guest and locally cached Verum information from that browser.
• A self-service cloud-account deletion control and verified public privacy inbox are not currently available in the app. This limitation will be updated when a verified process is published on the Contact page.

Verum 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 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.