Skip to content

This page is in English.Overview in five languages

Privacy

The questions people ask about their data, answered one at a time, starting with where it goes.

Updated 2026-11-15. This page is in English. · Overview in five languages · Machine-readable guide · What the * means

What leaves, and to whom

These are the main routes named by the code and our deployment records, checked against production settings on 6 October 2026; the songs row, added on 15 November, follows the code's default. They are not a record of each request, and what each party can observe is still being inventoried.⁠*

See this as one drawing, in five languages, on Trust →

Stays with Sathi

Your archive and what Sathi understands from it
On one server we operate. Documents and photos are encrypted at rest; songs are plain files in the music library, so the player can stream them.

Leaves today, by default

Relevant excerpts for a reply
The text model, DeepSeek's hosted API by default — to write the reply.
Images and scanned pages
Google's Gemini — to read them. Gemini also answers when the text model fails.
Text you keep, a piece at a time
Google, for search embeddings — so search can find things by meaning. In time, most of what you keep passes this way.
Songs you add, and the rest of the library a few a night
Google's Gemini — a short clip of each, with its file name and tags, to name the song, fix its tags and learn its language and mood. The operator can turn this off.
Your voice, when you speak
Google speech — to turn it into text.
Reply text to be spoken
An OpenAI-family voice model, through OpenRouter — to read it aloud.
Account and team mail
Resend — to deliver it.
Nightly backups of the database and your files
Google Drive and an Oracle Cloud server — so they can be restored. Encrypted by restic before they leave; the key stays with us.

Depends on configuration, or on what you connect

Other model and speech providers
When a route is changed.
Searches
The search engines the deployment's SearXNG asks.
Your connected mailboxes, telephone calls and notification services
Those services, when you connect them.
Assistants you connect through Sathi's MCP door
When it is turned on.

Gets nothing

Advertisers and data buyers
Nothing. No data is sold.

Each provider may keep what it receives under its own terms. The terms, and how the routes are configured, are under Current processing routes and terms; the maintained entry is on Trust.

Questions

Is my data the product?

No. There is no advertising, no engagement optimization, no data sale, or advertiser access. External processors do receive the task data described above. Sathi should know you because you chose to let it know you — that is the founding rule.

What does Sathi know about me?

What you gave it: conversations, documents you keep, connected calendar and mailboxes, imports you ran — and the understanding derived from them as claims, each with provenance and confidence. The memory panel shows every claim and why it is believed.⁠* Corrections teach it; rejected hypotheses stay rejected.

Can the operator read my data?

During the beta, yes by default: operator support access starts on for each account so problems can be found and fixed, unless its owner switches it off — shown in your account as a beta default rather than something you granted, and one tap to switch off. It becomes opt-in, granted only from your own account and recorded on the relationship graph, once Sathi runs reliably without us looking. Every admin request lands in a tamper-evident audit log. The limit: this is application-level enforcement, audited but not yet cryptographic — the operator still runs the database.

Can Sathi forget something?

The deletion path removes live records and their derived understanding. Encrypted backup snapshots expire separately; downstream processors may retain copies under their own terms. What a deletion keeps depends on the operation: leaving keeps the words you already sent into shared conversations with their other members, while erasing removes them too; neither reaches an organization's workspace records, the admin audit log, guest logs, feedback sent through the public form or an in-app report, or the usage (unlinked from you), purchase and mail-relay records kept to run the service. Leaving issues a signed receipt, which authenticates the recorded operation and is not proof that every copy is gone; erasing issues none. See the current deletion entry.

Can I export everything? Can I leave?

Not everything yet. Export covers your supported records and files: a sealed, cryptographically signed archive of your profile, memories, conversations, documents, notes, lists, tasks and reminders, in readable formats (a JSON record, or a ZIP that also carries your files). Derived search embeddings are left out, an organization's workspace records stay with the organization, and an archive past the fixed size limits is refused rather than cut short. The front door restores supported sections onto a fresh account; notes and lists are export-only records that restore does not import. Leaving issues a signed receipt of what was destroyed and of the account records that remain, with their operational retention reasons. Its category notice is not a complete inventory of copies or a legal-basis assessment. The receipt does not establish that backup or downstream copies have already expired. What happens if Sathi itself disappears is on About.

Does Sathi learn from my mail?

With a mailbox connected, Sathi learns in the background from the conversations you have written in. The subject and first lines of those messages go to the text model, and only your own words become what it remembers about you. What others wrote is kept as theirs: searchable, never taken as yours. Promotions are skipped. Turn it off any time in Account › Connected services.

Is a Private chat the same as guest chat?

No. Signed in, a Private chat still uses what Sathi knows about you, but saves no conversation and no trace; usage is metered without content. Guest chat needs no account and uses nothing personal, and its conversations are logged for testing, as the next answer says. Choose Private before your first message, from the rings icon at the top of a new chat or the Private button under the greeting.

What about guests?

Guest chat requires no account. Nothing a guest says becomes memory. Guest conversations, with the reply and identifiers derived from the network address and session, are logged for testing and feedback, and a nightly job deletes them after the number of days an operator setting sets (30 by default; an operator can also set no limit, and which maximum to promise is an open decision). Deleting an account does not reach these logs, because they belong to no account.

Where is it stored?

Today, on one Sathi-operated server, in its own Postgres database and disk. Documents and photos are encrypted at rest; songs sit as plain files in the music library, so the player can stream them. Nightly encrypted backups are kept off-site: where, and for how long, is the deletion entry on Trust. A home device is being tested, keeping work local is planned, and dedicated or fully independent deployments are a future offering.

What is encrypted?

Documents, photos and generated files: encrypted at rest with authenticated encryption. Songs are not: they sit as plain files in the music library, so the player can stream them. Cached document text: stored no more readably than the file it came from. Nightly backups: encrypted by restic before they leave the node. Transport: HTTPS everywhere with HSTS. Database rows (claims, messages) are protected by disk, access control, and audit rather than per-row encryption.

What would a server compromise expose?

Assume an attacker with application-level access could read what the application can read — that is the baseline for any hosted system, including this one. What limits the damage: at-rest encryption on documents and photos, short-lived scoped tokens, quotas and rate limits, tamper-evident audit logs, and a single small attack surface instead of a fleet of integrations. What we refuse to do is pretend the risk is zero; the mitigation roadmap (cryptographic operator separation) is public on /security.

Does Sathi use OpenAI?

Sathi is not affiliated with OpenAI or Meta. The models and serving providers depend on the configured route and task, including direct APIs and intermediaries such as OpenRouter. A model family’s name is not proof of who receives the request. Relevant context, images, audio and reply text can leave Sathi for processing. See the provider and processing account.

Current processing routes and terms

The maintained implementation entries are on Trust. The text adapter defaults to DeepSeek’s hosted API; its endpoint is configurable. Google hosts Gemini processing, with Vertex AI and Gemini API client routes supported by configuration. An OpenAI-family voice model is reached through OpenRouter; the model name alone does not identify its actual upstream host. Live routing and per-account retention settings are not verified here.

For Google processing, consult the terms for the configured service: Google Cloud data governance or Gemini API terms. For voice routing, OpenRouter’s data handling also depends on the selected provider. These links are not a claim that zero-retention settings have been enabled for Sathi.