What does Statio see?
Statio uses AI in a few places — to write a brief response after a journal entry, to synthesize your week, to notice the people who matter most in what you write. The phrase “uses AI” can mean almost anything, so this page is a plain accounting of what each AI feature receives, what it returns, and where it runs. Your words are yours; the infrastructure they pass through is Statio's.
Your raw text never leaves Statio's secure infrastructure.
Statio's server holds your encrypted journal AND the AI that reads it. When the AI needs to read your words, it reads them in-process on the same Statio-controlled server — no third-party data center, no training corpus, no third-party advertising telemetry. The one exception is the heavier weekly / monthly / yearly syntheses: when our server-side AI is overloaded, those calls can fall over to a Statio-managed secure cloud-provider lane that processes the request and returns the result. That failover is contractually bound to not retain or train on the data, and live status is visible at /admin/stats/llm.
AI surfaces, one at a time
01Your daily reflection
Right after you save a journal entry, a local model writes a brief, gentle response — asking more than it tells, and pointing back to scripture or to the person you trust outside Statio. The reflection is saved with your entry and never sent anywhere else.
Statio sends:
The plain text of the entry you just saved, your first name (so the response can feel a little more human), and your preferred Bible translation. Nothing else — no IP address, no device info, no other entries.
Statio receives:
A short response, usually 2-5 sentences, written in second person. Statio strips any HTML or formatting before storing it.
Runs on Statio’s secure serverThe model lives on the same server that holds your encrypted journal — bytes never leave the building, let alone the country.
02Your weekly reflection
Once a week (Sunday evening, your timezone), Statio reads the seven days of entries you wrote and writes a synthesis: themes that recurred, places God seemed to be moving, threads worth picking up. It augments rather than replaces — every regen layers on top of the previous version.
Statio sends:
The decrypted plain text of every entry you wrote in that week, the descriptors and topics already extracted from them, and your first name and Bible translation.
Statio receives:
A 4-8 paragraph weekly synthesis. Statio also runs a separate one-line "descriptors" pass over the synthesis so the result is labeled (e.g. "Week 18, 2026 : faith-practice, lament").
Runs on Statio’s secure server, with a Statio-managed secure cloud-provider failoverHeavy synthesis runs on Statio’s server-side AI by default. If that lane is overloaded (latency above 30 seconds or recent error rate above 20%), Statio routes this surface to a secure cloud-provider failover lane. /admin/stats/llm shows the live status.
03Your monthly reflection
On the first of each month, Statio rolls up the past month into a longer synthesis. Same intent as the weekly, wider lens.
Statio sends:
Every entry from the prior month plus that month's weekly syntheses, your first name, and your Bible translation.
Statio receives:
A 6-10 paragraph monthly synthesis with single-word descriptors.
Runs on Statio’s secure server, with a Statio-managed secure cloud-provider failover04Your yearly reflection
On January 1, Statio synthesizes the previous calendar year. The longest of the reflection forms — the kind you might come back to in five years and still recognize the season.
Statio sends:
Every entry, weekly synthesis, and monthly synthesis from the prior year, plus your first name and Bible translation.
Statio receives:
A 10-15 paragraph yearly synthesis with descriptors.
Runs on Statio’s secure server, with a Statio-managed secure cloud-provider failover05Weekly reflection descriptors
After Statio writes a weekly reflection, a tiny separate AI pass picks one or two single words that name what the week was actually about ("lament", "intercession", "ordinary"). These show up in the reflection card so you can scan a year of weeks at a glance.
Statio sends:
The text of the weekly reflection it just wrote.
Statio receives:
A comma-separated list of one to three single words. Statio rejects anything that doesn't match the format.
Runs on Statio’s secure server06Monthly reflection descriptors
Same as the weekly descriptors, applied to monthly syntheses.
Statio sends:
The text of the monthly reflection.
Statio receives:
One to three single words.
Runs on Statio’s secure server07Yearly reflection descriptors
Same as the weekly descriptors, applied to yearly syntheses.
Statio sends:
The text of the yearly reflection.
Statio receives:
One to three single words.
Runs on Statio’s secure server08Milestone banners
When you hit a meaningful threshold of discipline (your seventh day of journaling, your first answered prayer, a year-anniversary), Statio renders a soft banner on /today. The banner copy is written by Statio’s server-side model so it lands on you specifically — not a generic congratulations.
Statio sends:
The kind of milestone (e.g. "first answered prayer"), a small amount of context (e.g. the prayer body that was answered), and your first name.
Statio receives:
Two short lines: a one-line headline + a one-sentence note. Stored with the milestone and rendered on /today until you dismiss it; the archive lives at /milestones.
Runs on Statio’s secure server, with a Statio-managed secure cloud-provider failover09Topic extraction
After you save an entry, a small AI pass pulls the topics you actually wrote about (e.g. "marriage", "work-stress", "scripture-study"). Topics fuel the search bar on /journal and the topic chips on /reflections.
Statio sends:
The plain text of the entry.
Statio receives:
A short list of 1-5 lowercase, kebab-case topic tags. Anything malformed is dropped.
Runs on Statio’s secure server10Prayer suggestions from your journal
When your entry mentions someone you're praying for or something you're asking God about, Statio offers it as a candidate prayer for your prayers board. You decide whether to keep it. Statio never auto-creates prayers.
Statio sends:
The plain text of the entry.
Statio receives:
A short list of candidate prayer one-liners. They appear on the prayers board with a "from your journal" badge until you keep or dismiss them.
Runs on Statio’s secure server11Relationship awareness
Statio quietly notices the names that appear most often in your entries — your wife, your kids, your pastor, the friend you've been worrying about — so the weekly reflection can refer back to them by name without you having to remember to mention them again.
Statio sends:
Plain text of recent entries. Statio does NOT cross-reference any external "people" service or contact list — only what you yourself have written.
Statio receives:
A short structured list of names with relationship hints ("Krissy: spouse"). Stored locally; surfaced only inside your synthesis pipeline.
Runs on Statio’s secure server12Crisis safety net
A second small AI pass looks at every entry for language that suggests acute crisis (suicidal ideation, self-harm). When it sees something, the safety interstitial appears with the right hotline for your country and Statio waits before doing any other AI work on that entry. The deterministic keyword pass below is the primary trigger; this pass exists to catch what keywords miss.
Statio sends:
The plain text of the entry.
Statio receives:
A safety classification with a confidence score. Only the classification is stored — no narrative.
Runs on Statio’s secure serverThis is the only AI pass that runs synchronously and gates the rest of the entry-save flow. We bias toward "safer to interrupt than to miss" — false positives mean a momentary banner; false negatives mean we missed someone in pain.
13Community study pre-screen
When an author nominates a study they wrote for the public catalog, Statio’s server-side AI gives it a 0-10 score on three axes — alignment with mainstream Christian theology, content safety, and per-week completeness. Studies that pass move to a human moderator queue. Studies that fail return to the author with the AI's reasoning so they can revise.
Statio sends:
The study's title, description, and every week's teaching highlights, application challenges, and reflection prompt. Author identity is NOT included — the model scores the content only.
Statio receives:
A JSON object: { orthodoxy: 0-10, safety: 0-10, completeness: 0-10, reasons: [...] }. Stored on the study row + shown verbatim to the author.
Runs on Statio’s secure serverRuns only when an author actively nominates their study. Personal + Circle-only studies never touch this pass.
14Reviewer notes polish
When a Statio Studies reviewer rejects a community submission, they only have to type a few quick words about what needs revision. Statio rewrites those notes into a warm, pastoral, professional response that lands on the author’s /studies/mine and pings them by notification.
Statio sends:
The study title, description, the AI pre-screen scores + reasons, and the reviewer’s quick notes. Author identity is NOT sent.
Statio receives:
A 100-220 word warm response in plain prose. Saved as moderator_notes on the study row + delivered as the notification body.
Runs on Statio’s secure serverRuns only on reviewer rejection. Approvals do not invoke this pass.
15Lectio Divina invitation
Once every 3-5 weeks (random in that window per user), Statio’s server-side AI reads the themes of your recent journaling and quietly proposes a 3-day Lectio Divina (Divine Reading) journey on a passage that fits where you are. The card appears on /today; you can dismiss without consequence.
Statio sends:
The plain text of your last 7 days of journal entries plus your most recent weekly synthesis. Your first name and Bible translation. Nothing else.
Statio receives:
A passage reference (e.g. "Romans 8:18-30"), one to three themes that motivated the choice, and a 2-3 sentence empathetic invitation written in second person. Stored on the lectio_journeys row + shown verbatim in the /today invitation card.
Runs on Statio’s secure serverRuns at most once per user per 3-5 weeks. If you dismiss the invitation, the next one is composed fresh from whatever your journaling looks like 3-5 weeks from now.
16Lectio Divina daily reflection
During the 3-day Lectio journey, after you write your response (Day 1), meditation (Day 2), or prayer (Day 3), Statio’s server-side AI offers one or two sentences back — a gentle pointer or question grounded in what you just wrote, not a sermon.
Statio sends:
The passage you're sitting with this journey, the day's prompt, and the words you just wrote. Your first name. Nothing else.
Statio receives:
A 1-2 sentence reflection. Surfaced inline below your text; not stored as a separate journal reflection.
Runs on Statio’s secure serverFires once per day during an active journey, immediately after the user submits their writing.
17Solitude end-of-window summary
When you elect a solitude window and it ends, Statio’s server-side AI writes you a brief, gentle narrative of what landed in your inbox while you were away — instead of a cold bullet list. Two to four sentences, warm in tone, grounded in what actually happened.
Statio sends:
A list of the inbox items that fired during your solitude window — kind labels and their titles only (e.g. "reflection_ready: Your weekly reflection is ready"). No body text, no journal entries, no prayer content. Plus your first name so the prose can feel personal.
Statio receives:
A 2-4 sentence narrative summary written in second person. Replaces the original individual notifications with a single combined inbox row.
Runs on Statio’s secure serverRuns once per solitude end. The original notifications are then deleted; only the synthesized summary remains.
18Voice prayer polish
When you record a voice prayer or voice answer, the on-device transcript (Web Speech API — your raw voice never leaves your phone) is rambly. Statio’s server-side AI quietly cleans it into one or two sentences that capture exactly what you said, without inventing anything. You always edit before submitting.
Statio sends:
The plain-text transcript from your phone's on-device speech-to-text. Nothing else — no audio bytes, no name, no other prayers.
Statio receives:
A short polished version of the same text (max ~50 words for a prayer, ~80 for an answer). The original audio is also saved alongside your prayer so you can play it back later.
Runs on Statio’s secure serverOn-device speech-to-text + Statio’s server-side polish. Audio bytes are deleted 30 days after you archive the prayer.
19Insights themes
When you open /insights or refresh the themes panel, Statio looks across recent journal entries and names broad patterns without quoting you. It also writes a short narrative summary so the page reads like a reflection aid rather than a tag cloud.
Statio sends:
A bounded set of your recent decrypted journal-entry text, trimmed before sending, plus the instruction to avoid verbatim phrases. Statio checks the returned phrases against source text and drops anything that looks like a 4-word quote.
Statio receives:
Theme labels, short explanations, source entry IDs for internal linking, and a brief narrative paragraph. These are cached per user.
Runs on Statio’s secure serverRuns through local Ollama. No Claude route is used for this surface.
20Circle moderation classifier
When someone posts in a Circle, Statio checks whether the content appears to violate the Circle Guidelines before notifying other members. High-confidence violations can be hidden and queued for admin review.
Statio sends:
Only the plaintext content that was just posted: a thread, reply, prayer, answered-prayer note, or shared-entry excerpt. The prompt does not include the author’s profile, other Circle history, or unrelated journal entries.
Statio receives:
A confidence score, guideline categories, and one short reason for admin review. Benign classifications are not shown to members.
Runs on Statio’s secure serverRuns through local Ollama and is deliberately conservative to avoid unjust strikes.
21Legacy study draft helper
In the older study builder flow, an author can provide a passage, theme, and week count and ask Statio to draft a starter outline they can edit before saving.
Statio sends:
Only the author-entered passage, theme, and requested number of weeks. It does not receive journal entries, Circle posts, or author identity.
Statio receives:
A JSON study draft: title, description, weekly scripture references, teaching highlights, application challenges, journal prompts, and discussion questions.
Runs on Statio’s secure server22Study shell draft
The current study builder asks for a fast shell first: title-level description, leader overview, session flow, category, and a lightweight list of units. The author reviews and edits before publishing or sharing.
Statio sends:
The author-entered title and description prompt, study type, cadence, total unit count, selected Bible translation, and category options. It does not receive personal journal or Circle content.
Statio receives:
A strict JSON shell with description, overview bullets, session-flow bullets, category, and unit titles/scripture references/focus lines.
Runs in Statio’s secure cloud-provider laneThis uses the Claude CLI lane because long multi-unit study shells were timing out locally. The prompt is passed through stdin, not command-line argv.
23Study unit fill
After a study shell is saved, background workers fill each unit with richer teaching, discussion, journal, and challenge content. The author still owns the edit before use.
Statio sends:
The saved study title and description, study type, cadence, Bible translation, the unit title/focus/scripture references, and configured breakout labels. It does not receive journal entries or Circle member content.
Statio receives:
Strict JSON for that unit: icebreakers, teaching summary bullets, discussion questions, breakout questions, journal prompts, and challenges.
Runs in Statio’s secure cloud-provider laneThis uses the Claude CLI lane in small bounded calls so long daily studies can fill without request timeouts.
24Study artwork prompt draft
When an author asks Statio to suggest banner or icon artwork, a local model turns the study title and description into an image prompt. The author can edit the prompt before generating art.
Statio sends:
The study title, up to 600 characters of the study description, and an optional author visual hint. No journal entries or Circle posts are included.
Statio receives:
A single image-generation prompt for a banner or icon. The image generator receives that prompt, not the author’s private journal.
Runs on Statio’s secure server
What Statio explicitly does NOT do
- · Sell or license your entries to any third party for advertising, analytics, or training corpora.
- · Train any model on your entries — neither the on-server model nor the secure cloud-provider failover retains your text past the request.
- · Read your contacts, location, or device data to personalize responses. The only personalization is your first name and Bible translation.
- · Show ads. Anywhere. Statio is not ad-funded; there is no ad-stack.
- · Keep plaintext copies of your entries. Every entry, prayer, and reflection is encrypted at rest with AES-256-GCM keyed off a server-only secret.
Have a question this page doesn't answer? Send feedback and we'll add it. The aim is for this page to be specific enough that there's nowhere left to wonder.
See also:Privacy policyTerms of service