Frequently Asked Questions

Zero-knowledge design means original text is never stored on anonym.legal servers — the tool itself cannot be a source of data requiring erasure. For organizations processing data through anonym.legal, the tool supports GDPR-compliant anonymization (replacing PII with tokens or encrypted values) that satisfies data minimization requirements. The Desktop App's local processing ensures no cloud retention to complicate erasure requests. Example: A retail company's DPO receives a surge of right-to-erasure requests following a DPA awareness campaign. The company uses anonym.legal to anonymize customer purchase history for analytics — replacing names and contact details with tokens before analytics processing. When erasure requests arrive, the analytics datasets do not contain real customer data — erasure from operational systems is sufficient. The DPO demonstrates GDPR-compliant data minimization to the investigating DPA.

EU data storage (Hetzner data centers, Germany). Zero-knowledge architecture means original text is not stored on servers at all — no EU data transfer issue. For organizations requiring absolute local processing, the Desktop App handles everything locally with no data leaving the device. Example: A French marketing agency processes customer email lists for targeted campaigns. They previously used a US-based data cleaning tool that received raw PII on US servers. Following the TikTok fine, their legal team flags this as a potential GDPR Article 46 violation. They switch to anonym.legal — EU-based Hetzner servers, zero-knowledge design — for all PII handling. The legal team documents EU data residency in their Article 30 records of processing activities.

All processing occurs on Hetzner infrastructure in EU data centers. Zero-knowledge architecture means original text never reaches anonym.legal servers — only encrypted output is stored. The DPIA is complete and available to enterprise customers. The Data Processing Agreement is governed by EU law. This directly resolves the compliance paradox: using anonym.legal to anonymize data does not itself create a GDPR data transfer.

anonym.legal explicitly offers both modes: irreversible anonymization (Replace/Redact/Mask/Hash — no recovery possible, output is truly anonymous under EDPB guidelines) and pseudonymization (Encrypt — reversible with key, output is pseudonymized personal data under GDPR). This explicit distinction allows DPOs to choose the appropriate method for their use case and document their choice correctly for regulatory purposes.

anonym.legal offers all five methods: Replace (pseudonymization — GDPR still applies), Redact (near-anonymization — if comprehensive), Mask (pseudonymization), Hash (one-way — approaching anonymization), and Encrypt (pseudonymization with controlled reversibility). The Encrypt method with client-held keys provides the strongest pseudonymization control. Documentation helps organizations understand which method produces which GDPR outcome. Example: A Dutch data analytics company offers anonymized customer datasets to third-party researchers. Their DPO needs to determine whether their "anonymized" data removes GDPR obligations. Using anonym.legal's Redact method (permanent removal of PII with no token mapping), the resulting dataset has no pathway to re-identification — meeting GDPR's anonymization threshold. The DPO documents this determination in the DPIA. GDPR scope is removed for the analytics dataset.

ISO 27001 certified. DPIA complete. EU data storage (Hetzner). Zero-knowledge design (original text never stored — minimal data processor footprint). Data Processing Agreement available. Transparent architecture documentation available for DPO review. Example: An Austrian insurance company's DPO is completing a DPIA for their customer complaint anonymization process. The DPIA requires vendor assessment of anonym.legal as the anonymization tool. anonym.legal's ISO 27001 certificate, EU hosting documentation, DPIA, and DPA are provided. The DPO includes these in the DPIA documentation. The supervisory authority's subsequent audit finds the DPIA complete and compliant.

Batch processing (1-5,000 files) with GDPR-compliant anonymization presets enables bulk DSAR preparation. A preset configured for "third-party PII removal" automatically detects and anonymizes references to other individuals in documents being prepared for DSAR response. The same preset can be applied across all documents in a DSAR batch. Example: A German telecommunications company receives 300 DSARs monthly following a DPA awareness campaign. Each DSAR requires reviewing communications (emails, service notes) to remove third-party PII (other customers mentioned in the records) before sending to the requesting subject. anonym.legal's batch processing with a "DSAR response" preset processes 50 documents per request in minutes, reducing DSAR response time from 3 weeks to 3 days.

ISO 27001 certified with 114 security controls. The certification allows enterprise customers to submit the certificate to their procurement team and bypass most of the 100-200 question custom questionnaire. Procurement cycles measured in weeks, not months. Example: A major German bank's vendor risk team receives an application to add anonym.legal to their approved vendor list. The vendor risk process normally takes 4-6 months for non-certified vendors. anonym.legal's ISO 27001 certificate allows the bank to map the certification to their internal control requirements, reducing the assessment to 3 weeks. The bank's CISO approves the tool in time for the Q1 compliance project deadline.

By choosing anonym.legal (ISO 27001 certified), enterprise customers' security teams can satisfy their vendor assessment requirements without extensive custom questionnaire completion. The certification is the evidence package. This is particularly relevant for anonym.legal's enterprise customers who themselves use anonym.legal for PII processing. Example: A legal tech startup using anonym.legal faces enterprise customers asking "what security certifications does your PII vendor have?" anonym.legal's ISO 27001 certificate is included in the startup's vendor security documentation pack, satisfying the enterprise customer's third-party risk requirement without the startup needing to conduct their own PII tool security assessment.

ISO 27001 certification covers 114 security controls across 14 domains — addressing administrative, physical, and technical safeguard requirements that satisfy HIPAA's BAA evidentiary requirement. anonym.legal can provide the certification and control mapping to HIPAA requirements. Example: A large regional health system's compliance office is renewing vendor assessments. anonym.legal is a business associate processing PHI for de-identification. The compliance office requests evidence of "appropriate safeguards" per the existing BAA. anonym.legal provides the ISO 27001 certificate and control summary. The compliance office maps ISO controls to HIPAA 164.308-316 and documents the satisfactory assurances in the BAA file — satisfying OCR audit requirements.

ISO 27001 annual surveillance audits maintain certification currency. DORA-relevant financial institution customers can reference the current ISO 27001 certificate in their annual ICT vendor register as evidence of ongoing security controls. The certification's surveillance structure satisfies DORA's continuous oversight requirements. Example: A Dutch bank subject to DORA must maintain an ICT register with annual security evidence for all material vendors. anonym.legal is a material ICT vendor providing PII anonymization. The bank's third-party risk team pulls anonym.legal's current ISO 27001 certificate annually. No custom assessment required — the certificate satisfies DORA Article 28's due diligence requirements. The bank saves 60 hours of assessment time per year.

ISO 27001 certification satisfies most non-US-federal government procurement security requirements globally. For EU government contracts, ISO 27001 is typically the required standard. For UK government, Cyber Essentials and ISO 27001 are recognized. anonym.legal's EU data residency additionally satisfies data sovereignty requirements for EU government bodies. Example: A UK government agency's digital transformation program requires all vendors to hold ISO 27001. anonym.legal's certification satisfies the procurement requirement. The agency can approve anonym.legal for their document anonymization project without requiring a lengthy security assessment.

ISO 27001 certification covers all 114 controls across 14 domains. TLS 1.2/1.3 in transit. AES-256-GCM at rest. CSP headers. Regular third-party audits. This documentation package satisfies enterprise procurement requirements and accelerates sales cycles at regulated enterprises.

Named presets encode the full configuration: which entity types to detect, which anonymization method to apply, language settings, custom entities, and confidence thresholds. Presets can be shared with the entire team or organization. New team members start with the approved preset rather than configuring from scratch. Compliance templates (GDPR Minimum, HIPAA Safe Harbor, FOIA Exemption 6) are pre-built starting points. Example: A legal department processes client documents with 8 different paralegals. Without presets, each paralegal's approach to anonymization varied. After an audit finding that inconsistent redaction created liability, the department's privacy counsel creates a "Client Document Review" preset (names, addresses, phone numbers, national IDs — all Redact method). All 8 paralegals apply this preset by default. Inconsistency eliminated. Audit trail shows consistent application.

Presets can be named and organized by regulatory framework. A "GDPR Standard" preset detects EU-relevant entity types. A "HIPAA Safe Harbor" preset includes all 18 identifier categories including dates and geographic data. A "CCPA Consumer Data" preset focuses on consumer PII categories. Each preset is one click to apply, and presets can be shared with the compliance team to ensure consistent framework application across the organization. Example: A multinational SaaS company's privacy team processes documents for EU customers (GDPR), US healthcare clients (HIPAA), and California consumers (CCPA) in the same workflow. Three saved presets — applied based on client type — ensure the right entities are detected and redacted for each regulatory context. Error rate from manual reconfiguration drops from ~15% to near zero. Annual compliance audit passes without findings related to inconsistent anonymization.

Saved presets with the exact entity selection, anonymization method (Replace is preferred for ML training data to preserve statistical properties), and language settings create a reproducible anonymization pipeline. The preset acts as a compliance guardrail — users apply the preset without being able to accidentally deviate from approved settings. This supports both GDPR compliance and ML reproducibility requirements. Example: A European fintech company's ML team uses a "Training Data - GDPR" preset for all training dataset preparation. The preset is created and approved by the DPO, then used by 12 data scientists without modification ability. Audit trail shows every dataset preparation used the approved configuration. The annual AI compliance audit passes without findings. Previously, inconsistent anonymization across 12 team members had generated 3 audit findings in the prior year.

The Presets System allows compliance managers to create named configurations (e.g., "GDPR Standard," "HIPAA Clinical Notes," "Financial Reports") with per-entity method settings (e.g., replace names, hash SSNs, redact bank accounts). These presets are shared to all Basic+ team members. Built-in compliance presets (GDPR, HIPAA, PCI-DSS, SOX) encode regulatory best practices out of the box, reducing the compliance manager's configuration burden.

Presets can be exported and imported across accounts, enabling MSPs to build a library of compliance configurations (GDPR Starter, HIPAA Safe Harbor, FOIA Standard, etc.) and deploy them to client organizations efficiently. Industry-specific presets (healthcare, legal, financial services) can be built once and shared. This makes anonym.legal an enabling tool for compliance consulting practices. Example: A GDPR consulting firm serves 35 SMB clients in Germany. They've built a "German SMB GDPR Baseline" preset covering the entity types most commonly encountered in their clients' document workflows. Each new client receives this preset on day one of engagement. Configuration time per client drops from 3 hours to 15 minutes. The firm can onboard 4x more clients with the same team.

Presets encode the organization's approved configurations as named, shareable objects. New team members are given access to the team's preset library and instructed to use specific presets for specific workflows. The learning curve compresses from weeks to hours. Configuration errors drop because new users apply tested, approved presets rather than configuring from scratch. Institutional knowledge persists even through team turnover. Example: A legal process outsourcing firm onboards 50 new document review staff annually. Previous onboarding required 3 weeks of PII tool configuration training. With presets, new staff are trained in 1 day: "For European documents, use the GDPR Standard preset. For US medical records, use the HIPAA Safe Harbor preset." First-week configuration error rate drops from 22% to 3%. Annual training cost savings: approximately €45,000 in staff time.