Policy 01
Enforce document anonymization
Every uploaded document is automatically anonymized before any AI model sees it. No bypassing, no forgetting, no exceptions.
GDPR-compliant AI.
Without restrictions.
Your compliance tools.
Confidentiality preserved. Professional secrecy protected. Audit-safe documentation. With anymize, compliance isn't a detour – it's the foundation of your AI usage, whether you handle mandates, patient files, trade secrets or personal data.
The foundation
One tool.
All compliance cases.
GDPR. The German Federal Data Protection Act (BDSG) and equivalent national data protection laws across the EU. Professional-confidentiality rules across European jurisdictions – in Germany: § 203 StGB (medical and legal confidentiality under the German Criminal Code), § 43e BRAO (lawyer confidentiality), § 26a BNotO (notary confidentiality). Professional codes in medicine, tax consulting, psychotherapy, financial services. All these regulations share the same core requirement: Sensitive data should not be sent unprotected into a third-party AI system.
anymize meets that requirement automatically – because anonymization happens before any AI interaction. What the AI sees cannot be traced back to your client, patient or business partner. What you get is the answer to your real case.
The legal core
What is not transmitted cannot be disclosed or requested. No transfer to third parties. No disclosure within the meaning of professional-confidentiality rules (in Germany: § 203 StGB). No Cloud Act. No data protection incident.
Admin controls
Compliance you enforce.
Not hope for.
In Team and Enterprise plans, admins decide at the organization level how uncompromisingly anonymization is enforced. Four policies, granular per workspace – each one optionally changeable by team members (or mandatory):
Policy 02
Enforce prompt anonymization
Every chat message is automatically anonymized before being sent to GPT, Claude, Gemini or Mistral. Even when typing freely.
Policy 03
Require manual document review
The four-eyes principle as policy: documents must be manually reviewed and confirmed before sending. Nothing goes out that a human hasn't cleared.
Policy 04
Enforce anonymization countdown
A 12-second window before every send to review the anonymized message. Time to take one last look – without stopping the workflow.
Granular release: For each policy, the admin decides separately whether members can change it in their personal settings. That way, compliance fits your team's culture – strict where needed, open where it makes sense.
Manual review & countdown
Speed
AND control.
Two features no pure anonymization gateway offers:
Manual review: built-in four-eyes principle
Before sending, the user sees exactly what has been anonymized and what will be sent to the AI. They actively confirm before the data leaves the anymize platform. For compliance-critical law firms, auditors or internal audit departments, this is the bridge between efficiency and regulatory due diligence.
Countdown review: the 12 seconds that decide
When the team needs to work fast – but slip-ups mustn't happen – admins activate the 12-second countdown. In that time, you see the fully anonymized version, can abort and correct. When the countdown expires, it's sent. A safety net that doesn't slow down your workflow.
The compliance advantage
Both mechanisms are fully traceable in documentation. Who saw, reviewed and cleared what, and when – all in the audit log.
Data retention
Delete, when
it should be deleted.
The mapping between placeholders and original data (needed for automatic re-translation) is kept only as long as you need it. Five retention modes – configurable per workspace:
Delete immediately
Full anonymization – no re-translation possible
24 hours
Short follow-up phase, maximum data minimization
7 days
Standard for ongoing mandates / cases
30 days
For projects and ongoing analyses
Unlimited
For knowledge bases and long-term use cases (manually deletable)
After the period expires, the mappings are automatically removed. The anonymized versions remain – the link to the originals does not. From that point on, re-identification is no longer possible.
Special case “Delete immediately”: full anonymization
If you choose this mode, the mapping table is deleted immediately after de-anonymization. You receive the AI's answer once in full form – in chat history, audit log and database, only the anonymized version remains afterwards. Re-translation is technically impossible.
The GDPR consequence: The result is considered under Recital 26 GDPR as fully anonymous – and therefore no longer personal data. For any subsequent processing (storage, transfer, analysis, archiving), GDPR no longer applies: no processing agreement, no data subject rights, no transfer restrictions. For highly sensitive individual cases, this is the highest compliance standard anymize offers.
GDPR principles automated. All retention modes automatically fulfill two GDPR principles:
- Data minimization (Art. 5(1)(c)): No data longer than necessary.
- Storage limitation (Art. 5(1)(e)): Strict deletion periods.
And additionally: a right-to-erasure request (Art. 17 GDPR) is effectively anticipated by the timer-based deletion. On request, we delete mappings and chat history immediately – with no waiting time.
Access & audit
Who sees what.
And who sees what was seen.
Role-based access control
| Role | Permissions |
|---|---|
| Admin | Workspace settings, policies, user management, billing, audit export |
| Manager | Team overview, permission assignment · own chat & anonymization · no access to other users' chats or anonymizations |
| User | Chat & anonymization (own data, private – not visible to managers or admins) |
Admin
Workspace settings, policies, user management, billing, audit export
Manager
Team overview, permission assignment · own chat & anonymization · no access to other users' chats or anonymizations
User
Chat & anonymization (own data, private – not visible to managers or admins)
Audit logs
Every security-relevant action is logged – with timestamp, user and context: login, policy changes, API key rotations, permission changes, exports, deletions. Admins can view audit trails any time and export them for external audits.
Workspace isolation
Every workspace is strictly separated from every other. No cross-queries. No shared mapping tables. Even within a tenant, sensitive data stays where it belongs.
Single sign-on (Enterprise)
SAML- and OIDC-based SSO for centralized authentication. Integrates with your existing identity management (Azure AD, Okta, Keycloak). Includes role-based mapping from the identity provider.
Legal framework
The regulations
we cover.
GDPR & BDSG
for everyone
anymize is fully GDPR and BDSG compliant. We are a processor within the meaning of Art. 28 GDPR, the data processing agreement (DPA) takes effect automatically with acceptance of the terms – no separate signature needed. The technical and organizational measures (TOM) are fully documented and available for audits.
§ 203 StGB
for professionals bound by secrecy
Anyone bound by professional secrecy commits a criminal offense by disclosing the secrets without authorization. Relevant for:
- Lawyers
- Tax advisors, auditors
- Physicians, dentists, pharmacists
- Psychotherapists
- Other healthcare professionals
- Social workers in public administrations
anymize replaces the secret with a placeholder before third parties (here: AI providers) see it. No disclosure within the meaning of § 203 StGB – because no identifiable information is transmitted.
§ 43e BRAO
for lawyers
Since 2017, § 43e BRAO allows the use of external service providers – provided there is a written confidentiality agreement under § 43a BRAO. anymize provides this as a BRAO consent statement, signable online in text form (§ 126b BGB). This makes the use of the service provider compliant with professional law.
§ 26a BNotO
for notaries
For notaries, the written-form requirement (§ 126 BGB) also applies. anymize therefore also offers the confidentiality agreement as a signed PDF. Just download, sign, send back – we counter-sign.
Other professional regulations
For physicians (medical professional code), psychotherapists (PsychThG), tax advisors (StBerG), social data (§ 78 SGB X) and employee data protection (§ 26 BDSG): the combination of DPA + TOM documentation + technical anonymization meets the usual requirements. Individual agreements are available on the Enterprise plan.
Documents
Everything your
audit asks for.
We provide all compliance-relevant documents – partly automatically, partly at the click of a button:
Data processing agreement (DPA)
- What
- Contract under Art. 28 GDPR
- For whom
- Everyone
- How
- Automatically with terms acceptance · PDF downloadable in settings
BRAO consent statement
- What
- Confidentiality agreement under § 43e BRAO
- For whom
- Lawyers
- How
- Online acceptance (text form) · PDF download
Written-form variant (§ 26a BNotO)
- What
- Signed confidentiality agreement
- For whom
- Notaries
- How
- PDF download, return to legal@anymize.ai
TOM documentation
- What
- Technical and organizational measures
- For whom
- Data protection officers, auditors
- How
- On request
Compliance reports
- What
- Audit log exports, activity records
- For whom
- Enterprise customers
- How
- Self-service in admin panel
Privacy policy
- What
- Our data protection practice
- For whom
- Everyone
- How
- Anytime at /datenschutz
Note
Inside the product, the DPA and BRAO consent statement are available directly in the compliance settings for download. No support request, no waiting for legal.
Certifications & standards
Solid foundation.
Clear path.
Active today
Data center (today)
anymize runs on European infrastructure at Hetzner Online GmbH (Falkenstein / Nuremberg, Germany). The data centers are ISO 27001 and SOC 2 Type II certified. The data is subject exclusively to EU data protection law (GDPR, plus the German Federal Data Protection Act / BDSG at the operator level). No US Cloud Act.
ISO 27001SOC 2 Type IIHetzner DE
Roadmap
anymize's own certifications
- ISO 27001 (anymize platform)in preparation, planned for 2026
- SOC 2 Type II (anymize platform)in preparation, planned for 2026
- BSI C5 (Cloud Computing Compliance)planned for 2027
Enterprise customers with urgent compliance requirements receive the full TOM documentation and a detailed security questionnaire report on request today.
Who it's for
When compliance is your job –
or your duty.
anymize is for everyone whose profession or role is subject to special regulations:
Also: Data protection officers, Compliance officers, Internal audit and IT security teams that finally want to roll out AI in their organization – without incalculable risk.
What you should know about AI compliance.
Frequently asked questions
Not in its standard form. Inputs go to OpenAI – a US company – and are therefore subject in principle to the US Cloud Act. As soon as personal data is transmitted, a transfer event occurs that is hardly tenable without appropriate measures (standard contractual clauses + transfer impact assessment). With anymize, personal data never leaves the platform: only placeholders go out. That makes using the same frontier models – including ChatGPT – GDPR-compliant, because no personal data transfer takes place anymore.
We stand behind anymize. And we know – when an AI tool touches client, patient or employee data, a demo video isn't enough. That's why we give you 14 days of full access – all models, all features, no credit card. Enough time to be certain, before you trust us.
Your AI workplace awaits.