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.
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.
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.
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.
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.
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.
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.
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.
Every action carries the person who confirmed it, the assistant, the tool and the time. The audit log is exportable and cannot be edited.
Google Workspace and Microsoft on Team. SAML, OIDC and SCIM provisioning on Enterprise. Passwords, when used, are hashed with Argon2id.
Owner, admin, member. Members ask; admins configure assistants, sources and access; only owners touch billing, retention and deletion.
One list of every member, every assistant they can reach and every developer URL they hold, with last use. Revoke from the list.
A developer URL is a capability scoped to one person and one assistant. Rotating it does not affect anyone else.