Your data stays yours, and in France.

An assistant that reads your documents and acts in your systems has to be the most careful part of your stack. This page says exactly what Clemali stores, who can see what, where it runs, and what it never does.

Last reviewed September 2026 · report a vulnerability
01 — Who sees what

Permissions follow the person, on every question.

Employee
Asks a question
Signed in with the company SSO. Sees answers, sources, proposed actions.
question →← answer
Clemali, Paris region
Retrieves only what this person may read
The index stores each document with its access list, mirrored from the source. Retrieval filters on the person before the model sees anything.
read / act →← result
Your systems
Drive, Notion, databases, tools
Receive authenticated requests. Actions carry the name of the person who confirmed.
An employee sees
  • Answers built from documents they could already open
  • The sources behind each answer, as links to the original
  • Their own conversations, and nobody else’s
Nobody sees
  • Credentials, OAuth grants or connection strings, not even admins
  • Other people’s conversations; admins see counts and sources, not text, unless the company opts in
  • Anything in a model provider’s logs: no training, no retention
02 — Hosting

Paris region by default. Your datacentre when that is the rule.

Managed cloud
Hosted in France

Index, conversations, vault and logs run in the Paris region on a French provider, under French and EU law. Backups stay in the region. Models run in the EU under contracts with no training and no retention.

Self-hosted
Your network, your rules

The same software, installed in your datacentre or your private cloud. Nothing leaves your network; models can run on your own hardware. Updates ship as signed images you apply on your schedule.

Encryption

TLS 1.2+ on every hop. AES-256-GCM at rest, one data key per assistant, wrapped by a master key that never sits with the data.

Credentials in a vault

Connections are stored once, encrypted, and used at call time. No screen or API ever returns a value. Rotation replaces it; there is no read.

Retention you set

Conversation history from 30 days to keep, per company. Question text is not written to the activity log unless you opt in. Deleting a source deletes its index.

Isolation

Each company is a separate tenant with its own keys. Each assistant is a wall: a credential used by one cannot be referenced from another.

03 — Actions

Proposed, then confirmed

The assistant never acts on its own. It shows exactly what it is about to do, in which tool, and waits for a click. Admins decide which actions each assistant may propose at all.

Logged with a name

Every action carries the person who confirmed it, the assistant, the tool and the time. The audit log is exportable and cannot be edited.

Someone leaves
Remove them from SSO. Their access, conversations and developer URLs stop the same minute.
A credential leaks upstream
Rotate it in the vault. Every source using it follows. Nobody has to reconfigure anything.
A document is shared too widely
Fix it at the source. The index mirrors the change within minutes and answers follow.
04 — Identity

Single sign-on

Google Workspace and Microsoft on Team. SAML, OIDC and SCIM provisioning on Enterprise. Passwords, when used, are hashed with Argon2id.

Roles

Owner, admin, member. Members ask; admins configure assistants, sources and access; only owners touch billing, retention and deletion.

Access review

One list of every member, every assistant they can reach and every developer URL they hold, with last use. Revoke from the list.

Developer access

A developer URL is a capability scoped to one person and one assistant. Rotating it does not affect anyone else.

05 — Compliance
GDPRData processing agreement on request, sub-processors listed in the docs, data residency in France. Clemali acts as processor; your company stays controller.
SOC 2 Type IIn progress. Audit window opened in Q3 2026; report expected early 2027.
HDS and SecNumCloudRoadmap. Available today through the self-hosted edition on a qualified provider of your choice.
Model providersEU-hosted inference with contractual no-training and zero retention. Provider list in the docs; pinnable per assistant.
Responsible disclosureReport through the contact page. We acknowledge within two business days and publish fixes in the changelog.

Your documents, your permissions, your country.