Diadems TechDiadems Tech
Log inGet started

privacy

Privacy policy

Courtesy translation. This English version is provided for information only. Only the French version, Politique de confidentialité, is legally binding and prevails in the event of any difference or discrepancy between the two versions. Acceptance always relates to the French text.

This policy describes how Diadems Tech SARL (“Diadems”) collects, uses, retains and protects personal data when you use the diadems.fr service and the agents it enables you to create. Last updated: 16 November 2026 (2026-11-16).

1. Data controller

Diadems Tech SARL — La Joutelière, 638 Route de Clefs-Vaulandry, 49150 Baugé-en-Anjou, France. SIREN 938 381 290.
Contact for personal data: [email protected].

Diadems acts as data controller for your account, billing and platform usage data. For the personal data that your agent processes on your behalf in the course of your business (contacts, correspondence, documents), Diadems acts as a processor within the meaning of Article 28 GDPR, under the conditions of the data processing agreement annexed to our terms and conditions.

2. Data we process

  • Account and authentication: name, email address, organisation, password (hashed), session tokens, login logs, two-factor authentication settings (encrypted secret and fingerprints of the backup codes).
  • Agent configuration and use: settings, conversations, scheduled tasks, the agent’s memory and files, technical logs necessary for operation and security.
  • Agent vault: the credentials you save remain in its capsule. New remote backups include these values and their associated SSH key files in an archive encrypted with a public recovery key; the private key is kept separately, off the servers. OpenAI and Google OAuth tokens and browser sessions are not included.
  • Agent communications: emails sent and received by the agent and its authorised contacts, Telegram messages, voice exchanges (synthetic voice, transcriptions).
  • Billing: subscriptions, amounts, history; bank details are processed by our payment provider — we do not store them.
  • Free trial: where an organisation’s first agent begins with a free trial, the bank card fingerprint provided by our payment provider (a code from which the card number cannot be recovered), the identifiers of the organisation and of the account that took it out, and the dates of the trial.
  • Support and site chat: the email address left in the chat widget, the content of messages, IP address (kept in the form of a non-reversible fingerprint).
  • Notifications: device tokens (web/mobile push) when you enable them.
  • Offline mode: the content of conversations is not stored on the device. Only your unsent drafts may remain locally so that they reappear after you reconnect; they are deleted when you sign out and, on Android, excluded from backups and device transfers.
  • Google user data: only if you connect a Google account to an agent, and only for the services you tick (see §7-8).
  • OpenAI account: if you connect it to an agent, its OAuth credential remains exclusively in that agent’s capsule. Diadems keeps no copy of it in its database or in its backups.

3. Purposes and legal bases

  • Providing and performing the service (creation, hosting and operation of the agents) — performance of the contract (Article 6(1)(b) GDPR).
  • Billing and accounting obligations — performance of the contract and legal obligation (Article 6(1)(b) and 6(1)(c)).
  • Security, prevention of fraud and abuse, logging — legitimate interest (Article 6(1)(f)).
  • Preventing multiple free trials (one trial per organisation, per account and per bank card), using the card fingerprint and the dates described in §2 — legitimate interest of Diadems in reserving the free trial for new customers (Article 6(1)(f)).
  • Responding to your requests via the site chat and following them up — legitimate interest, and pre-contractual measures at your request.
  • Push notifications and connection of third-party services (Google, OpenAI, Telegram) — your consent (Article 6(1)(a)), which may be withdrawn at any time.

Google user data falls only within the first purpose above: providing the agent features you use, subject only to the security and legal compliance exceptions described in §8 (see also §7).

4. Recipients and processors

We do not sell your data. We use the following technical processors, only to the extent necessary for the service and under contractual safeguards:

  • Scaleway SAS (France) — hosting of the agents, their memory and their files.
  • Mistral AI (European Union) — inference for the “France” Engine and voice processing (synthesis and transcription).
  • TensorX — inference for certain catalogue models and for the site assistant, depending on the route selected.
  • Firecrawl — web search and page extraction; the queries and the addresses of the pages to be consulted are transmitted when these tools are used.
  • treg (Superdesign, United States) and the associated data providers — market data used by the agents (search engine optimisation, advertising, social networks, companies); the agents’ queries (keywords, sites, public accounts) are transmitted to them when these tools are used. Each agent can disable them in its configuration.
  • Higgsfield (United States) and the publishers of the associated generation models — creation of images and videos by the agents; the descriptions requested and the files used as a starting point (photos, logos, videos) are transmitted to them when these tools are used. Higgsfield may use the content transmitted to it to improve its models, within the limits of its terms; Diadems disables the use of the creations produced and deletes the files from Higgsfield as soon as they have been copied into the agent’s space. Each agent can disable these tools in its configuration.
  • Backblaze B2 — storage of backups in a European region, separate from the main hosting in France.
  • Cloudflare — routing and protection of access to the site and its APIs.
  • OpenRouter, Inc. (United States) and the associated model providers — inference for non-European engines and for the options that provide for it.
  • OpenAI (United States) — inference when models from this provider are chosen in the catalogue or linked through a connection of the customer.
  • Sinch / Mailgun (European Union region) — email delivery.
  • Stripe (United States / Ireland) — payment and billing.
  • Google (United States) — mobile push notifications (Firebase Cloud Messaging) and, if you connect it, Google Workspace.
  • Telegram (outside the EU) — only if you connect this channel to an agent.

Experts invited by the customer. The owner or an administrator of a customer organisation may open expert access to an external consultant (Team → Experts). This expert, who uses their own Diadems account, becomes a recipient of the data covered by their access: the agents within their scope and their configuration, their memory and their activity, the conversations that belong to the expert or are shared with them, and the files of those agents; in addition, if the customer opens them to the expert, the team’s internal chat and the organisation’s notifications. The expert has no access to billing or to team management. The expert is not a processor of Diadems: it is the customer who authorises them, and the customer may withdraw this access at any time.

5. Transfers outside the European Union

The main hosting of the capsules, their memory and their files is located in France; remote backups are stored in the European Union. The place of hosting does not on its own determine where processing takes place: the conversation and memory models, the web tools and the connected services follow their own routes. The Diadems catalogue also includes OpenAI and OpenRouter models with no guarantee of processing within the EU. Certain technical, notification and payment providers may also process data outside the EU. These transfers are covered either by an adequacy decision of the European Commission (Article 45 GDPR — in particular the EU–US Data Privacy Framework for certified recipients), or by standard contractual clauses (Article 46 GDPR). You may obtain a copy of the applicable safeguards by writing to us. The choice of a model or the connection of a third-party service does not, on its own, constitute the consent of the persons whose data is processed. Location guarantees already granted contractually remain applicable under the conditions provided for in the terms and conditions.

6. Third-party data processed through your agent

Where your agent processes the data of third parties (email recipients, contacts, correspondents), you remain responsible, as a professional, for informing those persons and for establishing the necessary legal bases with them. The agent’s outgoing emails carry a statement indicating that they were prepared with the assistance of an AI agent, together with a contact for reporting abuse. Any third party may exercise their rights by writing to [email protected]; we will pass the request on to the responsible customer where we act as processor.

7. Google data: access and purposes

Connecting a Google account to Diadems is optional and specific to the agent chosen. Diadems requests the identity permissions needed to recognise the connected account, and then only those for the services you tick before the Google consent screen opens. Depending on this selection, the agent may access the following categories of data:

  • Google identity (openid and userinfo.email) — account identifier and primary email address, used to display the connected account and to link its authorisation to the right agent;
  • Google Calendar (calendar) — calendars, events, times, attendees and associated settings, in order to view, create, modify, share or delete them when you ask;
  • Google Docs (documents) — content, structure and formatting of documents, in order to view, create and modify them at your request;
  • Google Sheets (spreadsheets) — sheets, cells, formulas and spreadsheet metadata, in order to view, create and update them at your request;
  • Google Contacts (contacts.readonly) — names, email addresses, telephone numbers and other contact details, read-only, to find the contact you are looking for;
  • Google Slides (presentations) — content, structure and formatting of presentations, in order to view, create and modify them at your request;
  • Google Forms (forms.body) — structure, questions and settings of forms, but not the responses, in order to view, create and modify forms at your request;
  • Google Tasks (tasks) — lists, tasks, notes, due dates and statuses, in order to view and organise them at your request;
  • Google Merchant Center (content) — accounts, products and associated commercial information, in order to manage the catalogue you have authorised;
  • Google Analytics (analytics.readonly) — properties, configurations and measurement reports, read-only, in order to analyse the audience you select;
  • Google Search Console (webmasters.readonly) — verified sites and search, performance and indexing data, read-only, in order to carry out the SEO analyses requested;
  • Google Ads (adwords) — accounts, campaigns, ads and associated metrics, in order to view and manage the campaigns you have authorised;
  • YouTube (youtube.readonly) — account, channel, videos and associated metadata, read-only, in order to answer your requests concerning your channel;
  • Google Business Profile (business.manage) — locations, listings and associated information, in order to view and manage the locations you have authorised.

Use. Diadems uses Google user data only to provide the user-facing features of Diadems that you use: carrying out the requests you make to your agent and the automations you have configured yourself. For example, the agent may look for an availability slot, prepare a document, update a spreadsheet or produce a requested analysis.

Google user data is used for no other purpose: not for advertising, marketing, profiling, audience measurement or statistics about your use, resale, creditworthiness assessment or lending decisions, or the development or training of AI models. Diadems carries out no bulk collection or hidden synchronisation of your Google account and does not call a service you have not selected.

8. Storage, sharing, protection and deletion of Google data

Token and connection metadata. The single-use OAuth code is exchanged in the agent’s capsule. The Google token is protected by the permissions of that capsule’s private volume and remains there exclusively; it is kept neither in PostgreSQL nor in Diadems’ backups, and is never transmitted to the AI model provider. The control plane keeps only the email address of the connected account, the list of authorised services and scopes and the connection date, in order to display and administer the connection without exposing the token.

Content obtained from Google APIs. The data strictly necessary for a request is processed in the capsule. Where a user-facing feature requires it, a result or an extract may appear in a conversation, a file, a task or the agent’s memory so that you can find it again. These items are then stored in the agent’s private volume and follow the periods set out in §10; Diadems does not create a general and permanent copy of your Google account.

Sharing and transfer. To respond to your request, the strictly necessary Google content may be transmitted to the provider of the AI model you have chosen in the cockpit (for example Mistral AI, OpenAI or, depending on the option chosen, OpenRouter and the associated model provider). This processing serves exclusively to produce the requested feature; the Google token is not transmitted to these providers. Apart from this processing and the technical processors identified in §4 for the hosting, security and operation of the service, Diadems does not disclose Google data to third parties.

Protection. The data is protected by the isolation of each capsule, network segregation, encryption of secrets at rest, access controls limited to authorised members and logging of security operations. Authorised persons are bound by confidentiality.

Revocation and deletion. You may revoke access at any time from the agent’s page (“Disconnect”), or from your Google account’s permissions. Disconnection revokes the authorisation and immediately deletes the token from the capsule. It stops any new access, but does not automatically delete the results you chose to keep in the agent’s conversations, files, tasks or memory. You may delete these items from Diadems or delete the agent; the deletion periods are set out in §10.

Limited use. Diadems’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

  • we do not use Google user data for advertising purposes;
  • we do not sell this data and do not transfer it to data brokers or information resellers;
  • raw or derived data obtained from Google APIs is never used to develop, improve or train generalised or non-personalised AI or machine-learning models;
  • no human reads this data, except with your explicit and documented consent for specific data, where necessary for security purposes, to comply with the law, or where the data is aggregated and anonymised for authorised internal operations;
  • our employees, contractors and providers involved in this processing are required to comply with these same restrictions.

Google user data — summary in English. Diadems uses Google user data only to provide the user-facing features of Diadems that the user uses: the requests the user makes to their agent and the automations the user configured. Google user data is not used for any other purpose, including advertising, marketing, profiling, analytics about the user, resale, credit or lending decisions, or developing or training AI or machine-learning models.

Diadems' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is shared only with the AI model provider chosen by the user, solely to perform the requested feature, and with the hosting and security sub-processors listed in section 4. It is never sold. No human reads it unless the user gives explicit consent for specific data, it is necessary for security purposes or to comply with applicable law, or the data is aggregated and anonymized for internal operations.

9. Agents’ voices

An agent may have a synthetic voice. The voice samples used for this synthesis are added only with the consent of the person whose voice is reproduced, and are processed in the European Union. The sounds produced by the agent are artificially generated.

10. Retention periods

  • Account and agent data: for the duration of the contractual relationship; on closure or termination, the agent’s data (memory, files, conversations) is deleted within a maximum of thirty (30) days, backup copies being destroyed at the end of their rotation cycle (not exceeding fourteen additional days).
  • Vault credentials: removed from the capsule when deleted; their encrypted recovery copies expire no later than fourteen days afterwards. A restoration must re-apply the deletions and revocations made since the point chosen.
  • Billing: kept for up to ten (10) years to meet accounting and tax obligations.
  • Free trial: the card fingerprint, the identifiers and the dates of each trial are kept for three (3) years from its subscription, then deleted during the daily deletion run. This period also continues after the deletion of the organisation or account and after the anonymisation of the account: the deleted identifiers are then erased, only the card fingerprint and the dates being kept until the end of the three years.
  • Site chat and support: the IP address fingerprint and the browser information linked to the thread are deleted within 48 hours of its creation. The daily anti-abuse counters expire within 48 hours of their creation. Threads, messages and attachments are purged no later than one year after the thread was created, even if it is still active.
  • Application security log: events expire after 180 days, during the daily deletion run. Login attempts used to limit abuse expire after two days, during that same run. Administrative events classified as operational expire after 365 days. Contractual and accounting evidence follows its own periods. Other technical logs and blocking measures remain limited to security and evidential needs.
  • Google connection and data: the token is deleted immediately on disconnection or deletion of the agent. The results or extracts you chose to keep in conversations, files, tasks or memory follow the retention period of the agent’s data above; backups expire no later than fourteen days after their deletion from the active volume.
  • OpenAI credential: deleted from the capsule as soon as you disconnect the account or delete the agent; it is not included in Diadems’ backups.

11. Your rights

In accordance with the GDPR, you have the right of access, rectification, objection, erasure, restriction of processing and portability of your data, as well as the right to withdraw your consent at any time. To exercise them: [email protected]. You may also lodge a complaint with the CNIL, the French data protection authority (www.cnil.fr).

12. Deletion of data

You may request the deletion of your data at any time by deleting your agents and following our account deletion procedure (in French). Disconnecting a Google account revokes and then immediately deletes the corresponding token from the agent’s capsule. Certain data may be retained where required by law (notably billing).

13. Cookies

With your separate audience-measurement consent, Diadems also uses Google Analytics 4, provided by Google Ireland Limited. Google receives cookie identifiers, technical browsing information, public pages or page categories without private URLs, and the first paid subscription per billing organisation (amount, currency and opaque identifier) and verified expert applications. No name, email, message, file, form content or conversation content is sent. Google Signals, ad personalisation and automatic form collection are disabled. Statistics may be linked to Google Ads campaigns; conversions are not imported a second time for bidding. Analytics is not contacted before this consent. Analytics cookies last up to 90 days without automatic extension. GA4 user and event data retention is set to two months without resetting on activity; aggregated reports may remain longer. Google may process data outside the EU under the safeguards described in its link below. Your choice lasts six months and can be withdrawn through “Privacy”, removing Analytics cookies. Previous internal-measurement consent does not cover Google Analytics: a new choice is requested.

Google Ads measurement is a separate choice, off by default. With your consent, Google Ireland Limited receives advertising identifiers, technical browsing information and events for a billing organisation’s first paid subscription (amount and currency) or a verified expert application submission. An opaque transaction identifier prevents duplicates. This tracking sends no email, name, message, file or mission content. Personalised advertising and enhanced conversions are disabled. The tag is not contacted before consent. Attribution cookies last up to 90 days; your choice lasts six months and can be withdrawn through “Privacy”. Google may process data outside the EU under its transfer safeguards: Google’s use of data. Internal conversion receipts are kept for up to 90 days. Only receipts after consent and less than seven days old may be sent during a signed-in visit. Declining does not restrict any Diadems feature.

Cookies for authentication, security and remembering your choice are necessary for the service. Optional measurement of the pages and steps of your visit starts only after your consent. You may accept, refuse or withdraw your consent from the “Privacy” button, without any effect on access to the service. The choice is kept for six months; the visit identifier lasts for the session and the attribution of origin for no more than thirty days. Audience events are kept for no more than 90 days, with the version and date of the consent, without being linked to the account. No message, file or assignment content is recorded in them. The account and payment events necessary for operation remain separate and follow their own purposes and periods.

14. Security

We implement appropriate technical and organisational measures: isolated runtime environment per agent, network segregation, encryption of secrets at rest, access control and logging, hosting in France. Authorised persons are bound by a duty of confidentiality.

15. Changes

This policy may change; the dated version in force is available at all times on this page. You are informed of any substantial change by appropriate means.

16. Contact

For any question about this policy: [email protected].

DiademsDiadems

The fully equipped AI agent, designed in Anjou and hosted in France.

Contact

Diadems Tech
AI support around the clock · A human team during office hours

Anjou (49) & La Flèche (72)

Discover

ProductUse casesHermes AgentHermes Agent hostingHermes vs OpenClawHosted in FranceExpertsAI expert directoryBecome an AI expertPricingDocumentation

Diadems

AboutPressCreate my agentLog inLegal noticePrivacyTerms of sale
  • Français
  • English

© 2026 Diadems Tech SARL — SIREN 938 381 290 — VAT FR85938381290 — Baugé‑en‑Anjou (49), France.

Diadems is a trademark registered with INPI, the French intellectual property office.