Security and confidentiality

Data confidentiality, step by step

Every technical choice in SAUL starts from one rule: client data is confidential material, and the AI model does not read it in clear.

Try SAUL Privacy notice

Into the firm's encrypted volume

The model works on facts, not on people

Before any reasoning, a detector finds people and companies in every document and SAUL replaces them with pseudonyms that stay consistent across the whole case file.

The same name gets the same pseudonym in every document, short forms included ("Meridiana S.r.l." and then "Meridiana").
The table of correspondences stays in the firm's encrypted volume.
Real names come back only in the lawyer's interface and in exported documents.
Searches in the legal sources also start from the already pseudonymised text.

One encrypted volume per firm

A firm's documents, analyses and client records are stored in its own AES-256 encrypted volume, with its own key. Firms share nothing outside.

Each firm's key is protected by a system master key (envelope encryption) and never appears in environment variables.
Each processing job runs in a separate container, started for that job only and closed at the end, with access only to that firm's volume.
Client records are not in the general database, but in the encrypted volume.

Servers in Europe, declared providers

Data at rest is on servers in Germany. Every provider processing data on the firm's behalf is listed in the privacy notice, with its role and location.

Provider	Role	Location
Contabo GmbH	Servers and storage	Germany, EU
Brevo	Service emails, no case file content	France, EU
Anthropic	AI models, data not used for training	United States, standard contractual clauses

Questions about security?

The privacy notice and terms of service describe roles, legal bases and retention in detail. For a firm's specific requests, the team answers directly.

Privacy notice Contact