ChatMasqué

Professionals: GDPR, FADP and professional secrecy

Last updated: 16 November 2026

This page is for professionals bound by secrecy and for those who advise them: DPOs, lawyers, compliance officers. It sets out, law by law, what ChatMasqué brings when you use an AI service, and what it does not.

In short. ChatMasqué is neither certified nor “compliant” with any law: no tool is, on its own. It applies a technical measure, pseudonymisation, that these laws themselves name. It reduces what you share; it does not replace your own assessment or your DPO’s advice.

The problem

Pasting a case file into an AI service means disclosing its content to a provider, often based outside Switzerland and the European Union. For a professional bound by secrecy, that may be a disclosure. For any organisation, it is processing of personal data by a third party, with a contract, transfers and risks to justify.

ChatMasqué acts before anything is sent: names, e-mails, IBANs and ID numbers are replaced by tokens on your computer. The AI service only receives [PERSONNE_1] or [IBAN_1]; the link to the real values never leaves your browser.

GDPR (European Union)

  • Article 4(5): pseudonymisation. This is what ChatMasqué does: the information needed to restore the real values is kept separately, encrypted on your device, out of the AI service’s reach.
  • Article 25: data protection by design and by default. The text gives pseudonymisation as an example. ChatMasqué masks by default, at the moment of pasting, without the user having to think about it.
  • Article 32: security of processing. Pseudonymisation is the first measure listed (paragraph 1(a)). The mappings are also encrypted (AES-GCM) and erased after the chosen period.
  • Article 5 and Articles 44 to 49: minimisation and transfers. Less personal data goes to the AI provider, including outside the Union. The Court of Justice of the European Union has held that pseudonymised data may not be personal data for a recipient with no reasonable means of re-identifying the people concerned (judgment of 4 September 2025, EDPS v SRB, C-413/23 P). This is assessed case by case: the context of a text can be enough to recognise someone.

FADP (Switzerland)

  • Article 7: data protection by design and by default. Same approach as the GDPR: masking applies from the start, on the device.
  • Article 8: data security. Pseudonymisation, encrypted mappings, automatic erasure; no ChatMasqué server.
  • Articles 16 and 17: disclosure abroad. Masked values are not disclosed to the AI provider, wherever it is based.

Professional secrecy

  • Switzerland: Article 321 of the Criminal Code (lawyers, notaries, auditors, doctors, psychologists, other health professions and their assistants) and Article 47 of the Banking Act.
  • France: Article 226-13 of the Penal Code, which protects secrets entrusted to anyone who holds them by status, profession or function.

Secrecy covers what links a piece of information to a person. By letting only tokens through, ChatMasqué greatly reduces the risk of disclosure. It does not eliminate it: a detail in the file (a rare job title, a place, a date) can be enough to recognise a client or patient. The preview before pasting shows exactly what is sent, and your own data types (case numbers, internal references) are masked like the rest.

West Africa

In Côte d’Ivoire, Law No. 2013-450 of 19 June 2013 on the protection of personal data also governs data security and transfers out of the country. ChatMasqué recognises ID numbers from several West African countries.

What you can show

  • Status certificate you can export: version, active protection, sites, masked types, fingerprint of the enforced configuration. It contains no real data and can be attached to an audit file or to the record of processing activities.
  • Enforced configuration by IT (GPO, Intune, Google Admin): users cannot turn off what is locked.
  • Security sheet for the DPO and CISO: data path, network connections, encryption, limits.

What remains your responsibility

  • Checking the AI service’s terms (use of data for training, retention period, place of processing) and signing the contract required.
  • Carrying out an impact assessment where required (Article 35 GDPR, Article 22 FADP).
  • Rereading what is sent: no detection is 100% complete.

This page provides general information, not legal advice. For a professional licence or any question, write to developer@chatmasque.com.

← Back to home