For your IT and your DPO
The answers before the questions.
Everything IT and a DPO ask before rolling Kaviar out to a team: architecture, flows, retention, legal roles, deployment. No needless jargon, and the limits stated plainly.
In one minute
The essentials.
| What Kaviar is | A desktop app (Mac, Windows, Linux). Not a network proxy, not an extension, nothing to install server-side. |
|---|---|
| Where the replacement happens | On the user’s computer, as the message is sent. Both detection layers, instant rules and an entity-recognition model, run locally. |
| What leaves the computer | The protected version of the message: names, companies, dates, identifiers and, in Strict, amounts and places replaced with made-up equivalents. |
| What never leaves | The original details, and the mapping between originals and stand-ins. They stay on the computer. |
| What Kaviar sees | Never the content. We process the account (email address, plan) and, for teams, a numeric record: how many details were protected, of what kind, when. |
| The team record | Counts and dates, never the text. The content cannot be recovered, by you or by us. |
The flows
Where data travels.
| With Kaviar credits | From the computer to our infrastructure, then to the AI provider. The protected version passes through; it is not kept. |
|---|---|
| With the company’s or the user’s own API keys | From the computer to the AI provider, directly. Kaviar sees nothing go by and stores nothing. |
| Sync between devices (optional) | End-to-end encrypted on the computer before anything is sent. The passphrase never reaches us: we host data we cannot read. |
| Network flows to allow | The chosen AI provider, app.usekaviar.com for the account and credits, GitHub for updates. Nothing else. |
Retention
What we keep, and for how long.
| Content of messages and files | Never kept. It exists on our servers only in transit, and only in credits mode. |
|---|---|
| Account data | Email address, plan, organisation. For the life of the account, then 30 days. |
| Team record | Counts per kind of detail, timestamped. Never the text. |
| Billing | Handled by Stripe. Kept 10 years, as required by law. |
| Usage measures | Anonymous, no IP address, 13 months. |
| Where | Authentication and application database in the European Union (Frankfurt). The full list of providers, with nationality and location, is in the privacy policy. |
Deployment
A few minutes per computer. No server.
Install
Signed installers for Mac, Windows and Linux. No admin rights needed on Windows. Signed updates, distributed from GitHub.
Invitations
You invite colleagues by email. Everyone is protected from their first conversation, at the Enhanced level by default.
Keys and credits
Each person uses the company’s API keys, their own, or Kaviar credits. Either way, the AI only receives the protected version.
Shared routines
Your best instructions, published once for the whole team, and editable at any time.
Legal
Who is responsible for what.
For account data, Kaviar is the data controller. For content passing through our infrastructure (credits mode) or hosted encrypted by us (sync), we act as a processor under Article 28 GDPR. A data processing agreement is available on request.
AI providers only receive the protected version. That sharply reduces what reaches them; it does not remove the need to govern their use in your organisation. Transfers outside the EU, where they exist, are covered by standard contractual clauses. The provider-by-provider detail is in the privacy policy.
What Kaviar does not do: it does not make an organisation compliant just by being installed, it does not replace your DPO’s analysis, and it does not guarantee perfect detection. It reduces, verifiably and on every message, what goes out.
Security
Verifiable on every message.
A button on every message shows word for word what the AI received. Protection levels are described in the detection help.
The questions that keep coming up.
Can the Kaviar team read our messages?
No. Clear content never leaves the computer. In credits mode, the protected version passes through our infrastructure without being kept. With your own API keys, we see nothing at all.
Who chooses the protection level?
The Enhanced level applies by default on every computer. Each person can raise or lower it, conversation by conversation.
What exactly is in the team record?
For each seat: how many details were protected, of what kind (name, company, amount…), and when. Never the text, never the values.
Can people bypass the protection?
They can leave a detail visible with one click when that is intended, and it shows: the AI view shows what was sent.
Do we need a proxy, an agent or network configuration?
No. Kaviar is an ordinary desktop app. The outbound flows are the ones listed above.
What happens when detection gets it wrong?
Detection combines deterministic rules with a local entity-recognition model. Anything that slips past both can be protected or added to the Vault in one click; the Strict level and the Vault cover terms specific to your business.
Do you offer a data processing agreement?
Yes, on request at support@usekaviar.com. It follows Article 28 GDPR and lists our sub-processors.
What happens to the account of someone who leaves?
You remove their seat; their access to the organisation, shared credits and shared routines ends. Their account data is deleted 30 days after the account is closed.
A question this page doesn’t cover?
Related