Privacy
What we collect, why, how long we keep it, and how to take it all back. Effective 9 October 2026.
Draft — not yet in force
This document is complete in substance and describes what the platform actually does, but two things are still outstanding: the legal entity that operates the service, and the governing law. It also has not been reviewed by a lawyer. Until both are settled and that review has happened, treat this as a statement of practice rather than a binding agreement.
Dia Logos is a place to read Scripture and the Christian tradition and to write honestly about it, sometimes alone and sometimes with a group. Much of what you write here is the most personal kind of material there is. This page tries to describe exactly what happens to it, in plain language, without the usual hedging.
Two commitments shape everything below. Your writing is yours, and it is never shown to another person — leader, pastor or administrator — unless you chose to share it. And we do not sell, rent or trade anything about you, to anyone, ever. There is no advertising on this platform and no business model that depends on your data leaving it.
What we do not do
It is easier to start here, because the list is unusually short and every item is verifiable in the code:
- No third-party analytics or tracking. No Google Analytics, no tag manager, no Segment, no Mixpanel, no PostHog, no Hotjar, no advertising or social pixels. None of it is installed.
- No advertising, and nothing sold or shared for marketing.
- We do not keep what you send to the AI. When an AI feature runs, our own record of the call stores the names of the fields sent and a one-way SHA-256 hash of the content — never the prompt, never the response. See “AI features” below.
- No leader or pastor dashboard shows an individual’s private writing. Group-level views are aggregates by default, and small groups are suppressed entirely rather than reported (below a cohort of three, we show nothing rather than something re-identifiable).
What we collect
Your account. Your name, your email address, and a password stored only as a bcrypt hash — we never hold your actual password and cannot recover it. We also keep your access status, when you joined, and a coarse “last active” timestamp updated at most once an hour.
What you write. This is the bulk of it, and it exists because the platform does not work without it: notebook entries, journal entries, prayer requests and prayer threads, testimony drafts and anything you choose to share, community posts and replies and reactions, check-ins, walk notes, shared reflections, Bible notes, reading annotations, action steps, your responses to reflective prompts, your course and journey progress, and the insights the platform drafts for you.
Security. A session record per device you sign in from. If you turn on two-step sign-in, the secret your authenticator app shares with us and one-way hashes of your recovery codes.
A place, only if you give us one. If you want to find a church near you, you can type a place — a city, or an address. We send that text to OpenStreetMap to turn it into coordinates, and keep the coordinates and the label so “near me” works. This is optional, you can clear it, and we never ask for or store precise device location.
Operational records. An audit log of consequential acts (an account approved or suspended, a data export requested, a retention sweep) holding who, what, when and a little redaction-safe metadata — never your writing. A record of each AI call for cost and transparency, holding no content. Error reports when something breaks.
Cookies
Five, all first-party, all functional. There are no tracking or advertising cookies, so there is no consent banner to dismiss.
dialogos_session— keeps you signed in. HTTP-only, secure, same-site.dl-returning— remembers that this device has signed in before, so a page that needs an account offers you sign-in rather than an introduction. Holds no name or account, only “1”. It stays after you sign out, for up to 400 days; clearing your cookies removes it.dl-theme— remembers light or dark.dl-tour-*— remembers that you dismissed an explainer.dl-visit-*— remembers where an administrator last read up to, so “since your last visit” means something. Only set for administrators.
Why we are allowed to hold it
To provide the thing you signed up for: we cannot show you your notebook without storing your notebook. For the parts that go beyond that — the AI features, the group-sharing features — the lawful basis is your consent, given by choosing to use them, and withdrawable by stopping. We keep security and audit records because we have a legitimate interest in an account system that cannot be quietly tampered with, and because you have an interest in the same.
AI features
Some features use AI: drafting an insight from your own writing, helping shape a testimony, suggesting tags, composing a week’s reading from works in our library. When one runs, the text it needs is sent to Anthropic (the Claude API) to produce a response, and to Voyage AI when something needs to be turned into a numerical embedding for search or for grouping your own notes by theme.
Three things worth being precise about:
- We do not retain what was sent. Our record of the call keeps field names and a content hash, so we can tell you an AI call happened and what it cost, without keeping the material.
- Your own writing can be embedded. The feature that groups your session notes by theme sends those notes to Voyage AI to be embedded. It runs for your account only and surfaces to nobody else.
- You can see and revoke it. Your AI transparency page lists every AI call made on your behalf, and you can remove records from it.
AI output is drafting help, not counsel. See the Terms for what that means.
Who processes data for us
We use a small number of providers to run the platform. They process data on our instructions and for no purpose of their own. This is the complete list:
- Vercel — hosting and content delivery. Sees requests and the usual server logs.
- Neon — the Postgres database where everything above is stored, in the United States (US East).
- Anthropic — the Claude API. Receives the text an AI feature needs, at the moment it runs.
- Voyage AI — embeddings. Receives library text, search queries, and your session notes for the theme-grouping feature.
- Resend — sends transactional email (sign-in help, notifications). Receives your email address.
- Inngest — runs scheduled and background jobs.
- OpenStreetMap (Nominatim) — turns a place you type into coordinates. Receives only that text.
- bible-api.com — fetches public-domain Scripture. Receives verse references, never anything about you.
- YouTube / Vimeo— only if a leader embeds a video. Loading an embed means that provider sees your request; we use YouTube’s no-cookie host where we can.
We will update this list before adding a provider that handles your data, not after.
How long we keep it
The governing rule is that retention never deletes something you wrote. The sweeps below clear operational residue — a prompt nobody answered, an insight closed without a word — and pass over anything carrying your writing.
- Unanswered reflective prompts: 180 days.
- Closed insights with no note on them: 365 days.
- Archived testimony drafts: 365 days.
- Community posts no longer active: 90 days.
- Audit records: 730 days.
- A data export you requested: 7 days, after which the download is emptied. We keep the bare fact that an export happened, because that is an audit record about your account.
Everything else we keep while your account exists, because it is your material and you may want it.
Your rights, and how to actually use them
These are buttons in the product, not a request form that goes to a queue.
- Get a copy. Settings → Your data produces a machine-readable export of everything listed above.
- See what happened to your account. Settings → Account activity shows changes to your account, your access and your data — including when an administrator acted.
- See what the AI did. Settings → AI transparency.
- Correct it. Your profile and your writing are editable in place.
- Delete everything. Settings → Your data schedules deletion. Your sessions end immediately; the account and its contents are destroyed after 30 days, which exists so a change of mind is possible. You can cancel within that window. After it, we cannot recover any of it. Audit records about the account are redacted rather than deleted, so the fact that an account existed and was deleted survives without identifying you.
- Object or complain. Write to us, and if you are in the UK or EU you may also complain to your data protection authority.
Children
Dia Logos is not designed for children and we do not knowingly create accounts for anyone under 13 — or under 16 where local law sets that bar. If you believe a child has an account here, write to us and we will remove it.
Security
Passwords are bcrypt-hashed. Sessions are HTTP-only, secure, same-site cookies, checked against the database on every request so that suspending an account takes effect immediately rather than whenever a cookie expires. Two-step sign-in with an authenticator app is available to everyone and required of administrators who have enrolled. Access to the administrative area is restricted to a named list, every administrative action is recorded, and changes to that list are noticed and logged automatically.
No system is perfect. If we discover a breach affecting your data we will tell you and the relevant regulator without undue delay, and we will tell you what we actually know rather than what sounds best.
Where your data lives
Primarily the United States. If you are in the UK or EU, using Dia Logos means your data is transferred there, and our providers rely on standard contractual clauses or an equivalent mechanism for that transfer.
Changes
If we change this in a way that materially affects you, we will say so in the product rather than quietly updating the date at the top.
Contact
Privacy questions, requests, or a correction to something on this page: privacy@dialogos.app.
Operated by an individual — no company has been formed for Dia Logos yet. See also our Terms of Service and Accessibility statement.