Skip to content

Security and privacy

Diadems runs the infrastructure and the agent’s intelligence. You define its access, its authorised correspondents and the actions you approve.

Each agent works in an isolated capsule with its own resources, files and limits. It cannot access other agents’ spaces.

The workspace is hosted in France. The location shown with the plan or the model indicates where processing takes place.

Seven days after the first agent in your space is created, every member must have turned on two-factor authentication to open an agent, configure it, change its plan, create an additional agent or buy budget. The first agent can be created without it. The temporary code comes from the authenticator app of your choice (Google or Microsoft Authenticator, Authy, 1Password, Bitwarden…), using the TOTP standard. The secret is stored encrypted and each recovery code can only be used once. See Create your account.

My account → Security offers email alerts, for example for a new sign-in from an unknown network or two-factor authentication being turned off, as well as the log of your sign-ins and sensitive changes.

The secret values added to the Vault stay in the agent’s private space, where it uses them, and are never shown again. Diadems’ database keeps no copy of them: it only keeps the name of each variable and the access record, encrypted. Remote backups that contain these values are encrypted. In an instruction, reference only the name of the secret.

Diadems can provide and manage access to France/EU models. You can also choose your own API key or connect your OpenAI subscription. Personal keys are encrypted and are never shown again.

Web search and page reading go through Firecrawl access managed by Diadems. The provider’s key is never placed in the agent’s space: its capsule only uses credentials specific to that agent, revocable and isolated from other customers.

  • Email contacts must be on the authorised list.
  • A channel must be explicitly linked to the agent.
  • Team members occupy named seats.
  • Third-party access, such as Google, GitHub or Grok, can be revoked from the portal.
  • A sensitive action can be subject to approval.

The email address managed by Diadems works within strict limits: the agent can reply without message-by-message approval, but only to authorised contacts and in the direction you chose. Other sensitive actions remain subject to the approvals you have configured.

Review the results before publishing them or making an important decision. Grant only the access that is needed and remove it as soon as it is no longer used. Avoid putting sensitive data in an instruction when it is not essential.

Deleting an agent destroys its space, its memory and its access. First export the files you want to keep. For retention rules and for exercising your rights, see the Privacy policy.