Library

Browse and read the Hebrew/Greek text with English glosses.

1. Click a book card.
2. Pick a chapter from the chapter navigation.
3. Toggle "transliteration" if you want it shown alongside the original text.

Try: click Ruth, then chapter 1.

Search

Find every verse using a particular word or phrase.

1. Type a search term.
2. Scan the matching verses.
3. Click a result to jump to it in Read.

Try: search chesed to see every verse using that Hebrew word.

Read

A one-shot, plain-language explanation of a passage — no project or setup, just a quick answer.

1. Pick a passage.
2. Optionally type a specific question.
3. Click "Explain this."

Try: Ruth 1, question "Why does Naomi change her name?"

Structures

Visual maps of a passage's discourse structure — chiasms, parallelism, repeating patterns.

1. Pick a passage.
2. View the generated structure map.
3. Click a unit to highlight its mirrored counterpart.

Try: Genesis 1 to see the creation week's repeating pattern.

Exegesis

Full AI-powered discourse analysis, using your own AI provider account (needs an API key — see Account below). You can also upload reference material (PDF/txt/md) or search the web for scholarly sources to include as secondary support.

1. Pick a passage range.
2. Choose your AI provider.
3. Optionally add reference material via upload or "Search the web."
4. Click Analyze — a full chapter can take a few minutes.

Try: Ruth 1, focus question "Where is the pivot of this passage?"

Research

Multi-stage research projects following the Theophilus Method (Observe → Analyze → Interpret → Correlate → Evaluate → Synthesize → Communicate → Apply → Transform) — every claim needs evidence or gets flagged "unevidenced." From a solid research project you can draft a full journal article (Write) or a ministry artifact (sermon outline, lesson plan).

1. Create a project (passage or topic).
2. Work through each Method stage in order.
3. Once the interpretive stages are solid, use Write or Ministry to generate a finished document.

Try: create a passage project for Ruth 1, then draft its Observe stage.

Logos & Zotero

Neither of these is an "account link" — Logos doesn't offer one, and only one of the two Zotero paths below crosses the network at all. Read the fine print before you rely on either.

Zotero — file import (works everywhere, including this hosted site). The reliable path. In Zotero: File → Export Library…, format BibTeX or RIS. In a research project's Sources section, upload the resulting .bib/.ris file.

Zotero — live "Pull from Zotero" button. Only works when you're running TheophilusAI locally (the desktop app, or theophilus serve on your own machine) with the Zotero desktop app also running on that same computer, with Zotero's Settings → Advanced → "Allow other applications on this computer to communicate with Zotero" turned on. On the hosted site this button will always fail — "localhost" means Render's own server, never your computer, so no amount of getting Zotero running on your end fixes it. Use the file import above instead.

Logos. Local-only, macOS-only, and there's no cloud account to connect — the integration reads Logos's own on-disk library/notes databases directly and sends deep-link URLs to open a passage in the Logos app. This only works running TheophilusAI locally on the same Mac that has Logos installed; it cannot work on the hosted site at all, on any platform. If that's your setup: open a passage-based research project, and Connectors will show logos: available ✓ along with an "Open [passage] in Logos" button and a catalog search box. If it instead shows "unavailable," the reason listed there is the actual cause (not on a Mac, or Logos has never been run). Importing your own Logos notes as a source is possible today only from the command line (theophilus logos open / theophilus logos catalog) — there's no button for that specific action yet.

Appearance

Accent color, font pairing, text size, and light/dark mode — all client-side, remembered across visits.

1. Click ⚙ Appearance in the sidebar.
2. Pick a preset or customize each option.
3. Changes apply instantly — no save button needed.

Account & sign-in

Sign in (Google/GitHub/Microsoft, or create an email+password account) to save your own AI provider keys — encrypted at rest, used automatically for your own analyses instead of the server's shared key, if any.

1. Sign in from the sidebar.
2. Open "Your API keys" and paste in a key from your AI provider.
3. Every Exegesis/Research call you make now uses your own key.

Contact us

Feature request, feedback, or a bug — click ✉ Contact us in the sidebar. No account needed, and we read every message.

Last updated: [date]

1. The service

TheophilusAI ("the Service") is a research platform over the Hebrew Old Testament and Greek New Testament: browsing and searching the text, plus AI-powered tools (Read, Structures, Exegesis, Research) that use a large-language-model provider — either our own account or an API key you supply yourself — to generate analysis. Browsing and Search are free and don't require an account. The AI-powered tools require signing in.

2. Accounts

You may sign in with Google, GitHub, Microsoft, or Apple, or create an email-and-password account. You're responsible for keeping your credentials secure and for all activity under your account. Sessions last until you close your browser or sign out — we don't keep you signed in indefinitely on a shared device.

3. Trial, subscription, and AI usage costs

New accounts get a free 3-day trial. After the trial, continued access to the AI-powered tools requires an active subscription (currently $2.99/month or $29/year, billed via Stripe, cancel any time). The subscription pays for platform access — it does not include unlimited AI usage.

AI-powered requests are billed separately from the subscription: you get 3 free AI requests total (not renewed each trial or billing period), after which you must either supply your own API key for your chosen AI provider (Anthropic, OpenAI, or Google — subject to that provider's own terms and billing) or purchase credits from us. You may optionally enable automatic top-ups (charging your saved card when your credit balance falls below a threshold you set) — this is off by default and only applies once you've turned it on in My Profile. Prices, the free-request allowance, and the trial length may change; we'll try to give notice of material changes.

4. Acceptable use

Don't use the Service to violate the law, infringe anyone's rights, attempt to extract or resell the underlying corpus data at scale, abuse the free-trial or free-request mechanism (e.g. creating repeated accounts to bypass it), or attempt to disrupt or gain unauthorized access to the Service.

5. AI-generated content

Read, Structures, Exegesis, and Research output is generated by third-party AI models and may contain errors, omissions, or interpretations you disagree with. It is offered as a research aid, not as authoritative scholarship, pastoral counsel, or a substitute for consulting qualified scholars or clergy. You're responsible for verifying anything you rely on.

6. Your content

Reference materials you upload, research projects, claims, and drafts you create remain yours. We store them to provide the Service and don't sell them. See the Privacy Policy for what we collect and why.

7. Disclaimer and limitation of liability

The Service is provided "as is," without warranties of any kind. To the maximum extent permitted by law, we aren't liable for indirect, incidental, or consequential damages arising from your use of the Service, including reliance on AI-generated content.

8. Changes

We may update these Terms from time to time; we'll update the date above when we do. Continued use after a change means you accept the update.

9. Contact

Questions about these Terms — use ✉ Contact us in the sidebar.

Last updated: [date]

What we collect

• Account info: email, display name, and provider identifier from Google/GitHub/Microsoft/Apple sign-in, or a hashed password if you register with email — we never store your password itself.
• Your own API keys, if you save one — for an AI provider (Anthropic, OpenAI, Google) or a research connector (e.g. CrossRef, OpenAlex). Encrypted at rest, and never sent back to your browser once saved. You can save more than one key per AI provider and switch which is active.
• Content you create: uploaded reference material (PDF/txt/md), research projects, claims, drafts, items you save to My Library (Read/Exegesis/ Structures/Search results you choose to keep), and contact-form submissions.
• Usage data: which tools you use and the text of queries you submit to them, so we can improve the Service. Not sold or shared for advertising.
• Billing data: subscription and credit-purchase amounts, plus Stripe-issued reference IDs (customer, subscription, and — only if you opt into automatic top-ups — a saved payment method ID) needed to process billing. We never see or store your actual card details; Stripe handles those directly.
• Your IP address, briefly: sent to Cloudflare Turnstile for bot detection on sign-up and the contact form, and held in server memory (not written to our database) for a short window to rate-limit repeated sign-up/login attempts from one address.

Third parties we share data with

• Stripe — payment processing for subscriptions and credit purchases, including a saved payment method if you opt into automatic top-ups.
• Anthropic, OpenAI, or Google — whichever AI provider you select receives the passage/query text needed to generate a response, either via our account or, if you've supplied one, your own API key.
• Research connectors (e.g. CrossRef, OpenAlex) — only if you use Research features that query them, via our account or your own saved key.
• Cloudflare Turnstile — bot protection on sign-up and the contact form; receives your IP address.

We don't sell your personal data.

Cookies

We use a single session cookie to keep you signed in. No advertising or cross-site tracking cookies.

Data retention and deletion

We keep account and content data for as long as your account is active. To request deletion of your account and associated data, use ✉ Contact us in the sidebar.

Children

The Service isn't directed at children and we don't knowingly collect data from anyone under 13.

Changes

We may update this policy; we'll update the date above when we do.

Contact

Questions about this policy, or a data deletion request — use ✉ Contact us in the sidebar.