Privacy policy.

In short

• There are no accounts, cookies, or analytics on the website or the hosted server.
• The hosted server’s code does not log or store your tool arguments or results.
• Our hosting providers keep their own standard request logs, which include IP addresses.
• The command-line tool runs on your machine and has no telemetry.
• We do not sell your data. We share it only with the service providers listed below, or if the law requires it. We do not use it to train AI models.

What is collected

Hosted MCP server (mcp.biblecli.org)

The hosted server answers Bible study tool calls from AI clients. It has no accounts and no authentication, and it sets no cookies. Every request gets a fresh server instance, so there are no sessions and nothing carries over from one request to the next.

Each call carries tool arguments chosen by your AI client, such as a Scripture reference or a search term. The server uses them to query its bundled Scripture databases and returns the result. Its code does not write arguments or results to a log, a database, or a file. Every tool on the hosted server only reads those databases; the command-line tool’s study-session tools and raw SQL tool are not available there.

The server is hosted on Railway, whose proxy keeps HTTP request logs. Railway documents these fields: the requester’s IP address and user agent, the time, HTTP method, host, and path, the status code, request and response sizes, timing, the edge region, and a request ID. If you use the server through a hosted AI app, the IP address may be that app provider’s rather than yours.

Railway’s HTTP logs have no field for the request body, and tool arguments travel in the body, so they are not in those logs. Railway still carries that traffic as our host, and we cannot speak for its internal systems. Railway also keeps the server’s own output, which in normal operation is a single startup line.

Website (biblecli.org)

The website is a set of static pages hosted on GitHub Pages. It sets no cookies and has no analytics. It loads no third-party scripts, fonts, or embeds; everything it loads comes from biblecli.org itself. GitHub logs and stores visitors’ IP addresses for security purposes.

Command-line tool and npm package

The bible command runs on your machine and has no telemetry. After installation, the only network requests in its code download the Scripture databases and their checksum manifest from GitHub Releases. The core and study databases download on first use or when you run bible db download. The optional Septuagint and syntax databases download only when you run bible db download-lxx or bible db download-syntax. GitHub receives those requests like any other download, including your IP address. If you set BIBLE_CLI_RELEASE_BASE, these requests go to that mirror instead of GitHub. Installing through npm contacts the npm registry in the same way.

Translations you import are stored on your machine in bible-user.db. Study sessions and notes are also stored on your machine. Bible CLI does not upload them, and the local bible mcp server does not contact the hosted server. If you connect bible mcp to an AI client, that client receives what the tools return, which can include imported text and study notes. A cloud-based client sends that to its provider under its own privacy policy.

Your AI client

The AI client you use, such as ChatGPT, Claude, Cursor, or Grok Bot, decides when to call a tool and sends the tool arguments. What you type into that client, and the results it receives, are governed by its own privacy policy, not this one.

Support messages

If you email us, we receive your email address and whatever you include. GitHub issues are public and are hosted by GitHub.

How it is used

• Tool arguments are used only to answer the request they arrive in.
• Request logs are used to run the service, fix problems, and respond to abuse.
• Support messages are used to reply to you and resolve your issue.

We do not use any of this for advertising or profiling. Divine Creative Ministries does not use queries or user content to train AI models.

Storage and retention

• Tool arguments and results: the hosted server does not store them, so there is nothing for us to retain.
• Railway logs: Request logs are retained according to our hosting provider’s (Railway) log retention policy and are not used for any purpose other than operating the service and preventing abuse, unless the law requires otherwise. We cannot shorten that retention or remove individual entries. See Railway’s logging documentation for current details.
• GitHub logs: GitHub keeps these under its own policies.
• Support email: we keep messages for as long as they are useful for support. Email us to ask for deletion.
• Local data: everything the command-line tool stores is kept on your machine until you delete it. By default its data is in ~/.bible-cli. An AI client connected to bible mcp receives tool results, as described above.

Third-party sharing

We do not sell personal data or share it with anyone except the service providers below, unless the law requires it.

Your choices

• Hosted server: you choose whether to connect it, and you can disconnect it in your AI client at any time. There is no account to close.
• Request logs: we cannot delete individual entries. They expire on Railway’s and GitHub’s schedules.
• Support email: email us to ask us to delete your messages.
• Command-line tool: delete ~/.bible-cli, or the folder set in BIBLE_CLI_DATA, to remove its databases, imported translations, and study notes. Run bible study delete <name> to remove one session. Set BIBLE_CLI_NO_AUTO_DOWNLOAD=1 to stop automatic downloads.

Children

Bible CLI is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has sent us personal information, email us and we will delete it.

Changes

If this policy changes, we will update this page and its effective date.

Contact

Questions or requests about privacy: hello@divinecreative.org.