The search box taught the world to confess in keywords; the conversational machine upgraded the confession to paragraphs. Because the interface is a dialogue, people supply what dialogue partners need — context, names, history, feelings — and the resulting record is unlike anything a household has ever produced: not the query diary of intentions, but full-text narrations of the family's inner life, phrased for maximum comprehension. Whatever holds that record holds something new in the world. The only question that matters is: what is it, and whose is it?
Where prompts actually go
On mainstream conversational services, the honest map has three layers:
- The conversation is retained — by default, on the provider's infrastructure, tied to the account, often indefinitely. The "deleted" chat typically leaves the visible list long before it leaves the systems; retention policies are paragraphs deep and change on the provider's schedule.
- The conversation may train. Depending on service and settings, what your family typed can become tuning material — your phrasings, your situations, dissolved into the next model's patterns. Opt-outs exist, are buried, and reset across product changes — the same decaying-toggle pattern as every mainstream protection.
- The conversation profiles. The account that asked about the health symptom, the debt strategy, and the teenager's struggles has composed a household dossier no advertiser could have bought a decade ago — held by companies whose business models the community has already learned to read.
The community-specific edge is sharper still: shidduch-season questions, a family's halachic edge cases, the kehilla-identifiable details woven through ordinary asks — the discretion culture's entire subject matter, typed voluntarily into an external archive.
“The machine's interface says "conversation." The infrastructure underneath says "deposition." Families should decide which one they believe before the third week of use.”
kolbo.life
Privacy by architecture
The platform answer inverts every default, on the same principle as the rest of the family's stack — KolBo AI's guardrailed layer inside a platform whose posture is that family data stays in the family:
- The prompt serves the answer, not a profile. Conversations exist for the household's use — continuity where you want it, nothing accumulated where you don't — the private-search covenant extended to dialogue: infrastructure funded as infrastructure has no second customer for your questions.
- No training on the family's life. What the household types is not tuning material — structurally, not as a buried toggle.
- The tiers scope the record. The children's tutor sessions, the teen's visibility per the family's ladder, the parents' own quiet — one architecture, per-person postures, the household governing itself instead of a provider governing everyone.
- The sensitive classes get the handoff anyway. The deepest privacy protection is the routing table itself: the questions that most deserve discretion — the shailah, the crisis, the guidance — were never supposed to reach any machine, and an honest layer points them home before privacy is even at stake.
The household's habits
Architecture carries the defaults; three habits finish the job: de-identify by reflex — the parenting question works as well about "my nine-year-old" as with a name; teach the family to ask in types, not identities, on any machine anywhere. Route the crown jewels away — financial account specifics, health records, anything shidduch-adjacent: composed questions in general terms, real data never, per the same crown-jewel discipline as the money rails. And audit the third-party habit — the family member using an open chatbot at work or school carries the household's stories with them; the de-identification reflex is the protection that travels, which is why it gets taught at the table and not just configured in settings.
Frequently asked questions
Are "incognito" or temporary-chat modes on mainstream services enough?
They shorten the visible record, not necessarily the infrastructure's — and they reset the burden onto the user per conversation, which is the decaying-toggle problem in miniature. Better than nothing; not an architecture.
Does de-identification really work — can't patterns re-identify?
Against casual profiling, types-not-identities does real work; against determined correlation, less — which is exactly why the layered answer matters: de-identify by habit and run the sensitive classes on architecture that never archives them. Habits reduce exposure; architecture removes the archive.
What about the business's AI use — quotes, client letters?
The parnassah layer has its own dossier problem: client names, deal terms, and firm finances in prompts are the business-inbox crown jewels in a new wrapper. Same rules, work tier: general phrasings on open services, real data only on the firm's private layer.
Is retained conversation history ever good?
On the household's own terms, genuinely — the tutor that remembers where the child struggled, the project thread that resumes. The distinction was never memory versus amnesia; it is whose memory: continuity the family controls versus a record someone else owns. Architecture decides which one you have.
Protection for the device already in your pocket
KolBo Secure protects any iPhone or Android — tamper-resistant enforcement, a self-service portal, and real human support. Starting at $14.99/month.
Secure a deviceEnrollment, configuration, and billing in one portal — minutes, not appointments.