Trust

What Sonar stores, and what it does not.

Sonar reads your content to classify it and keeps none of it. This page is the whole of what persists, written as it is implemented. Your own audit log records every change to the settings named here.

Data processing agreement What it does not do yet

Subject	What is kept	What is not
Document and message content	Nothing. Content is read into memory, classified, and discarded when the job ends.	No document text, message body, attachment, matched value or snippet is written to the database, to a queue, to storage, to a log line, to an error message or to a temporary file that outlives the job.
Findings	The category, how many values were found, how many were distinct, the confidence, and a position reference such as a page, a sheet or a cell.	Never the value at that position.
Filenames and paths	The name and path of an item, so a finding links back to the file in Microsoft 365 or Google Workspace.	They are personal data by our own definition. They are never written to a log line and never sent to the Pritect platform.
Container owners	The account that owns a site, a drive or a mailbox, including a display name and an address, and whether that account is still active.	This is the only individual-level personal data Sonar holds. Showing it is a workspace setting that is off by default, and while it is off the database returns nothing for those fields rather than the interface hiding them.
Sharing and labels	How an item is shared, with whom in broad terms, and the sensitivity label it carries.	Not the contents of a shared link or the identity of every recipient.
Credentials for your tenant	Encrypted under a key that belongs to your workspace alone, which is itself wrapped under a master key held outside the database.	Deleting your workspace destroys that key, which is what makes the deletion a shred rather than a row delete.
Audit records	Who did what and when, as identifiers, counts, enumerations and durations.	No name, address, filename, path or document excerpt appears in an audit record. The records cannot be edited or deleted by anyone, including us.

Off by default

The one exception, and it is off

A workspace can choose to keep a masked snippet beside a finding, so a reviewer sees the shape of a value without seeing the value. It is off by default, it is a setting only a workspace administrator can turn on, and every change to it is recorded in your audit log. At this stage it is a place in the schema rather than a feature you can switch on.

Where it runs

A workspace is pinned to one region when it is created. The choice cannot be changed afterwards, which is why it is a required step rather than a setting with a default.

EU FrankfurtGermanyAvailable: Your workspace, its database and the scanning worker all run here.
EU StockholmSwedenBy arrangement: Available by arrangement. Talk to us before you create the workspace: the region is fixed at creation and cannot be changed afterwards.

Component	Where	Content	What it does
The web application	EU, Frankfurt	Never	What you sign in to. It reads findings and inventory rows and never touches content.
The database	EU, Frankfurt	Never	Findings, inventory, audit records and encrypted tenant credentials. There is no column in it that could hold content.
The scanning worker	EU, Frankfurt	In memory	The one component that reads your content. It holds it in memory for the life of a job, writes nothing to disk, and its temporary filesystem is asserted empty after each job.
Contextual classification	EU endpoint	In memory	Short passages, sent only where pattern matching cannot decide, for the length of the call. No prompt or completion is stored.
The Pritect platform feed	EU, Ireland	Never	Only if you link the two products. Findings metadata, plus an asset owner's work email address where there is one. No content, no item names, and no other individual. Frankfurt to Ireland is one EU member state to another.

What leaves

Three destinations, and no fourth. Nothing else leaves your workspace except what you export yourself.

Back to Microsoft 365 and Google Workspace: Requests to read. Nothing else.; Sonar has read access only. It cannot write, move, delete, label, share or unshare anything in your tenant, and it never sends content back.
To contextual classification, in the EU: Short passages of your content, where pattern matching cannot decide on its own.; Only the passage, never the document. It is sent for the length of the call, no prompt or completion is stored, and nothing from your tenant is used to train a model.
To the Pritect platform, if you link it: Findings metadata about an asset, plus that asset's owner work email address where it has one.; Only if you link the two products, and only then. No content, no item names and no other individual. Frankfurt to Ireland, one EU member state to another, and either side can break the link.

Sub-processors

Contract references open

Four sub-processors, each in the EU. What each one receives, and whether content ever reaches it, is confirmed against the system itself. The published contract reference and the transfer basis for each are not yet recorded.

Supabase

No content

Database, authentication and job queue for the workspace.

Contracting entity: Supabase, Inc., United States
Processing location: EU, Frankfurt, eu-central-1, Frankfurt
What reaches it: Findings, inventory rows, filenames and paths, container owner fields, audit records and encrypted tenant credentials.
Contract reference: Supabase's published data processing addendum.
Why it is still open: The published addendum could not be read from the session that wrote this register, so its version and its transfer terms are not recorded. The supplier is incorporated in the United States, so the region alone does not settle the transfer position.

Vercel

No content

Hosts the web application.

Contracting entity: Vercel Inc., United States
Processing location: EU, Frankfurt, fra1, Frankfurt
What reaches it: Requests from signed-in users, and whatever a page renders in the course of answering them. No scanning happens here.
Contract reference: Vercel's published data processing addendum.
Why it is still open: The published addendum could not be read from the session that wrote this register, so its version and its transfer terms are not recorded. The supplier is incorporated in the United States, so the region alone does not settle the transfer position.

Fly.io

Content, in memory

Runs the scanning worker that reads content in memory.

Contracting entity: Fly.io, Inc., United States
Processing location: EU, Frankfurt, fra, Frankfurt
What reaches it: Document and message content, in memory, for the life of a job. Nothing is written to disk that outlives the job, and the machine's temporary filesystem is asserted empty after each one.
Contract reference: Fly.io's published data processing addendum.
Why it is still open: The published addendum could not be read from the session that wrote this register, so its version and its transfer terms are not recorded. The supplier is incorporated in the United States, so the region alone does not settle the transfer position. This is the row to close first: it is the supplier through which content passes.

Mistral AI

Content, in memory

Contextual classification of short passages. No prompt or completion is stored.

Contracting entity: Mistral AI SAS, France
Processing location: EU, EU endpoint, api.mistral.ai
What reaches it: Short passages of content, sent only where the deterministic layer cannot decide, and only for as long as the call takes.
Contract reference: Mistral's published terms and data processing terms for its API.
Why it is still open: The published terms could not be read from the session that wrote this register, so the version, the retention commitment and the position on training are not recorded. The supplier is established in the EU, so no transfer outside the EEA is expected, which is a statement to verify rather than assume.

Microsoft and Google

Microsoft and Google are not on this list and will not be. They are your own processors under your own agreements with them, reached with permissions your administrator granted in your own tenant, and your administrator can withdraw those permissions without involving us.

The worksheet in docs/legal/subprocessor-confirmation.md names the five things to record for each supplier and the page to read them on. It is one sitting's work for anyone with ordinary network access, and until it is done the data processing agreement's Annex III carries the same state as this page.