ANONIMATOR
Anonimator pseudonymises names, emails, IBANs, national IDs and other personal data on your own premises before a prompt or document reaches an external AI provider, and restores the original values in the answer.
The external provider receives no identifying data; the key never leaves your premises.
Your teams keep the AI tools they already use. Lab, study, research, teaching, legal and administrative documents contain names, dates, contact details and AHV/AVS numbers: Anonimator keeps those identities at home. For labs, universities, law firms and in-house legal teams.
The cloud AI only sees placeholders; the real data is put back into the answer.
Mapping only in memory, on premises, destroyed after each query.
A local gateway checks every outgoing prompt and blocks it if any identifying data remains.
Names, IDs, contacts and full dates are pseudonymised by default. Configurable policies for special categories (health, minors): domain packs on the roadmap.
Oversight with counts and hashes only, without creating new records of identities.
Word, Excel, PowerPoint, PDF, text (ODF, CSV, RTF, HTML, email, OCR optional). ES, DE, FR, IT, EN.
Designed to support data minimisation, pseudonymisation and privacy by design under the GDPR (Art. 4(5), 5, 25, 32) and the Swiss revFADP (Art. 6–8), and responsible use of AI under the EU AI Act.
Pseudonymisation, data minimisation, privacy by design and security of processing, and PII-free accountability evidence. Policies for special categories and children: domain packs on the roadmap.
Proportionality, privacy by design and by default, data security, and a supporting measure for cross-border disclosure. Runs entirely on Swiss/customer premises.
Central policy for what data may reach external AI tools, enforced in the browser and API, with PII-free audit evidence.
| Regulation | Article / requirement | How Anonimator supports it |
|---|---|---|
| EU GDPR | Art. 4(5) pseudonymisation; Art. 5(1)(c) data minimisation; Art. 25 data protection by design and by default; Art. 32 security of processing | Detects personal data on-premises and replaces it with typed placeholders before any prompt leaves the network; key kept in RAM only, per query, then destroyed; purpose-based keep/generalise/redact policies; the local gateway checks every outgoing prompt and blocks it if any identifying data remains |
| EU GDPR | Art. 44–46 international transfers (supporting measure) | The external AI provider receives only pseudonymised text; the re-identification key never leaves your premises (supplementary technical measure, not a substitute for a transfer mechanism) |
| EU GDPR | Art. 9 special categories; Art. 8 / Recital 38 children | Personal identifiers (names, IDs, contacts, full dates) are pseudonymised by default, also in documents about minors. Configurable policies for special categories such as health data: domain packs on the roadmap |
| EU GDPR | Art. 30 / accountability, Art. 5(2) | Audit trail without personal data (counts and hashes only, hash-chained) |
| Swiss revFADP / nDSG | Art. 6 principles (proportionality, purpose), Art. 7 privacy by design and by default, Art. 8 data security, Art. 16 cross-border disclosure (supporting measure) | Same mechanisms as above; runs entirely on Swiss/customer premises, no cloud component |
| EU AI Act | Art. 4 AI literacy and responsible use of general-purpose AI by staff; Art. 10 data governance (only if the customer builds high-risk systems) | Central admin policy for what data may reach external AI tools, enforced in the browser and API; PII-free audit evidence |
Pseudonymised data remains personal data for your organisation. Anonimator is a technical measure and does not by itself make processing lawful or certify compliance.
Every point above is about technical support; legal responsibility stays with you as the controller.
Requests to ChatGPT, Claude or Copilot go through Anonimator, an OpenAI-compatible proxy on your premises.
Names, emails, phone numbers, IBAN, AHV/AVS, DNI/NIE, dates and plates: Anna Meier → [PERSON_7f3a]. If identifying data remains, the gateway blocks the request.
The cloud AI answers with placeholders; Anonimator puts the real data back. The key is then destroyed.
| DIY toolkits (e.g. Presidio) | Cloud DLP (Google, AWS, Azure) | Anonimator | |
|---|---|---|---|
| Where your data is processed | Locally (library) | In the provider's cloud | On your premises |
| Fail-closed gateway in front of cloud AI | No, building blocks to assemble | No built-in AI proxy | Yes: nothing leaves unchecked |
| Real data restored in the AI answer | Only if you build it | Varies by service | Automatic |
| The re-identification key | Up to you | Data goes to the provider | Per query, RAM-only, then destroyed |
Other on-premise tools also keep data local. Anonimator's focus: one fail-closed gateway with a per-query, RAM-only mapping, not a toolkit you have to assemble.
| Anonimator (gateway) | Anonimator MCP | |
|---|---|---|
| What it does | Local gateway that pseudonymises personal data before prompts and documents reach cloud AI, and restores it in the answer. | Lets AI assistants and agents send documents and prompts through the local Anonimator gateway, so the external AI provider receives no identifying data; the key never leaves your premises. |
| Status | Pre-release · demo on request | Coming soon |
| Licence | Proprietary (closed source) | To be announced |
| Deployment | On-premise only, standard CPUs, OpenAI-compatible proxy | Works with the local Anonimator gateway |
| Flyer | Download flyer (PDF, EN) · ES | — |
| Security | Security policy | — |
| How to get it | Request a demo | Get notified |
Get in touch to request a demo of Anonimator for your lab, university, law firm or legal team in Switzerland or the EU.
Anonimator performs pseudonymisation (GDPR Art. 4(5)). Pseudonymised data remains personal data for your organisation (CJEU, C-413/23 P). Anonimator is a technical measure and does not by itself make processing lawful or certify compliance. "Anonimator" is a working name. ChatGPT, Claude, Copilot and Presidio are trademarks of their respective owners.
Security policy · © Antonio Castellon · [email protected]