Deep Dive Bible is run by Larry Sanger for the site’s Bible study groups, the first being In-Depth Bible Study. This page says what the site keeps about you, where it goes, and who can see it.

What you see on the site, and who else sees it

• Your account: your name as shown, your username, your profile photo if you add one, and your password, stored only as a one-way hash. If you sign in with Telegram, your Telegram ID is kept to recognize you.
• Messages in topics are seen by every member of the group. They travel encrypted (HTTPS), but they are stored as written, so whoever runs the server can read them (but Larry won’t unless legally required to), as in any forum. A deleted message disappears for everyone, but its text stays in the database. In-Depth Bible Study’s history from Telegram, back to its first message in February 2023, was brought here with the names of those who wrote it.
• Private messages are encrypted on your device, so only you and the other person can read them: their text, photos, and files, and the setup of your calls. The server stores them sealed and cannot open them. It does see who wrote to whom and when, message sizes, reactions, and read receipts; and for calls, who called whom, when, for how long, and whether it connected (no sound, picture, or network address).
• Your highlights, bookmarks, notes, and reading place are seen by you alone. They are not encrypted, so whoever runs the server can read them (but Larry won’t unless legally required to).
• A translation you upload for yourself is encrypted on your device with a password you choose. The server cannot read its text; it keeps its name, copyright line, and size.

Logs

• Each sign-in, failed sign-in, and refusal is recorded with its network address and time, for the admins to review. Sign-in attempts are limited per address and per account.
• To keep out automated sign-ups, the sign-up and password reset forms check how they were filled in, and from what kind of network; nothing is shared.
• The data API (on the Downloads page) counts each address’s requests to enforce its limits. It keeps the address only in scrambled (hashed) form beside the counts and the app’s name; all of it is deleted after two days.
• The web host keeps the usual web-server logs: the network address, the page asked for, the browser, and the time. These are the logs any website keeps, and they are shared with no one unless the law requires it.

Cookies and your device

• One cookie keeps you signed in, for up to 90 days. Another holds your time zone, so the day’s reading turns over at your midnight.
• Your browser keeps some things for the site on your device: your theme, text size, and reading settings; unsent drafts; copies of what you have read, so it opens without a signal; and, while you are signed in, the key that opens your private messages. Logging out removes the key, your drafts, and that device’s notifications.
• There are no advertising or analytics scripts, and no tracking cookies. The site counts its own visits from the web server’s log: how many visitors a day, which pages are opened, what is searched for on the site, the addresses of the pages that linked here (for email and social sites that hold private data, such as Gmail and Facebook, only the site’s name), and phone or computer. Each visitor is counted under a scrambled code that changes every day and is then deleted, so no one can be followed from day to day or identified, and no page, search, or link is recorded with who opened it. To count each browser once a day, as the industry’s standard measure does, each page also keeps a random code in your browser for that day only and sends it to the site once (and once more if you stay 10 seconds or open a second page). The code holds nothing about you; the site scrambles it as soon as it arrives and deletes it when the day is over, and your browser makes a new one the next day. Only the totals are kept, and nothing goes to any other company.

Other services

• Notifications go through your browser’s own push service (Google’s, Apple’s, or Mozilla’s). They are encrypted for your device; a private message’s says only “New message.”
• Calls use servers from Cloudflare and Google to connect the two browsers, and Cloudflare’s relay when a direct link is not possible. These see the network addresses, not the call itself, which is encrypted between the two browsers.
• Video lectures (David Pawson’s) play in YouTube’s player, which is loaded from YouTube only when you tap Play. From then on YouTube sees your network address and what you watch, under its own privacy policy.
• GIF search sends your search words to KLIPY from the site’s server. The pictures in the search results load from KLIPY into your browser, so KLIPY sees your network address. A GIF you send is copied onto the site.
• Link previews: when a message contains a link, the site’s server fetches the page to show a preview. The linked site sees the server, not you. Private messages get no previews.
• Sign in with Telegram loads Telegram’s button on the sign-in page.
• ZWIBook: when your account is set up, your username and your password’s hash are sent once to ZWIBook (zwibook.org, also Larry Sanger’s), to make you a sign-in there. Nothing else is sent, and the two accounts are separate from then on.
• The group’s commentary notes are written by an AI (Claude, by Anthropic) from the group’s discussions in the topics, so those messages are sent to Anthropic for that purpose. Private messages are never used for them.
• Questions to Claude: when you ask Claude (an AI, by Anthropic) a question, in a topic or in a private conversation with it, the question goes to Anthropic so that it can answer, with your profile’s description; your own last three messages there from the past three days, and any messages they replied to; and that topic’s last five questions to Claude from the past week, with its answers. No one’s name is sent: each member appears as a code, and the site puts the names back in Claude’s answers. Nothing else from the group is sent. To be left out, write “@Claude exclude me”: Claude then won’t answer you, and none of your messages is sent with anyone’s question (“@Claude include me” undoes it). A private conversation with Claude is the one kind that is not end-to-end encrypted: the site holds Claude’s key, so it can open those messages. It stores them sealed, never in plain text. But, because our server must be able to read your messages to Claude in order to send them to Claude, we hold keys to unlock those messages (only). We (human beings) will not be reading such private messages unless we are required to by law.
• What Anthropic does with it: by its own terms (as of October 30, 2026), Anthropic does not train its AI on what the site sends it, for the notes or for questions, and deletes it within 30 days, unless its automatic safety checks flag it, when it may keep it for up to two years.

Your choices

• Deep Dive Bible is a small Christian ministry, not yet affiliated with any organization or church, that will never seek profit. Nothing is sold, and nothing is shared for advertising.
• You can delete your own messages, highlights, bookmarks, and notes, and save your marks as a file.
• You can delete your account, on My account: at once, or closed now and deleted after 30 days, in which signing in reopens it. You choose whether your messages stay, with your name removed, or are deleted with it. Your profile, settings, marks, notes, and personal study areas are deleted either way, and a group you own passes to the site’s owner.

For how the encryption works, see the project’s security notes (SECURITY.md in Chatiferous’s code).