BibleMind

Updated 2026-10-21

Privacy Policy

Who this covers

This policy describes BibleMind as implemented today: a local-first study product with optional hosted inference, optional user-owned (home) inference, and downloadable corpus packs. Church and Seminary subscriptions are not for sale.

Accounts

Email accounts store a salted scrypt password hash, display name, tradition profile choices, and session records. Verification and password-reset tokens are single-use and expiring when that adapter is configured. If the deployment still uses the log-only mail adapter, those messages are not delivered by SMTP until an operator configures real mail.

Newsletter (only if you opt in)

Having an account does not sign you up for the newsletter. You get it only if you tick the unticked box at signup or turn it on in Settings, and then open the confirmation link we email you and press Confirm subscription (double opt-in). We record when and how you agreed (signup or Settings), the policy version you agreed to, and a keyed hash of your IP address at that moment, never the address itself. Once you confirm, your email address and display name are copied to our self-hosted newsletter tool (listmonk, on our own server) so it can send each issue; nobody else receives your list entry, and we do not sell or share it. Every issue has a one-click unsubscribe link, and you can also turn it off in Settings; unsubscribes take effect immediately and are synced back to your account. We never sign you up again unless you ask. Your newsletter consent history is included in your account export, and deleting your account deletes your newsletter entry too (if the newsletter tool cannot be reached at that moment, we keep only what is needed to finish that deletion and retry until it is done). Account emails such as verification and password reset are separate and are not affected by this choice. Open and click tracking stays off.

Hosted inference

When you use BibleMind-hosted AI, prompts and model completions are sent to the configured hosted provider (launch default: OpenRouter). BibleMind does not silently copy a private/home prompt to hosted AI. Hosted usage is metered on the server when paid checkout is enabled.

Private / home inference

Ollama, LM Studio, and other OpenAI-compatible endpoints you save run on machines you control. BibleMind stores encrypted endpoint settings and optional keys in the provider vault. Traffic stays between the API process and that endpoint. Fallback to hosted AI happens only under the policy you chose (never / ask / hosted / deterministic).

Offline corpus packs

Scripture and lexical packs download into this browser’s IndexedDB metadata and Origin Private File System. They are not uploaded to BibleMind as a corpus database. Licenses and attribution for each pack are shown on the download UI and at /legal/attribution.

Study Packs and handoff

Study Packs are research archives you export as files. Optional short-lived handoff links/QR codes store the archive on the server until expiry or revoke so another signed-in device can import it. This is not live multi-member congregation sync.

Feature voting (Roadmap)

When you vote on the Roadmap, we store which ideas your account voted for and when, so each account gets one vote per idea and can take it back. Everyone sees only the total count for each idea, never who voted. To spot vote stuffing, each vote also keeps a pseudonymous code made from the network address and browser string it came from, using a secret key, so we can compare votes without storing the address itself; those codes are dropped after 90 days. The history of when you voted or took a vote back is kept for 90 days. Your votes and that history are included when you download your account data. Deleting your account deletes your votes.

What we do not do

We do not sell Church or Seminary seats. We do not sync notes across devices. We do not claim Google OAuth unless that server capability exists. We do not use corpus packs as Ask evidence without the ordinary citation path.

Crisis resources (coarse country)

When distress safeguards trigger, the API may derive a country code for that request only (offline IP Geolocation by DB-IP, or a CDN country header only when your operator sets BIBLEMIND_TRUSTED_CDN_CIDRS and the ingress hop matches). Your IP address and that country code are not stored with your account or question history. Saved Ask threads still store your question text and engine reasoning as usual. Optional analytics, if enabled, receives only day-bucketed aggregate counts by country—not who asked.