GDPR-Ready PII Scrubber: Remove Personal Data Before AI

GDPR PII Scrubber: Remove EU Personal Data Before AI

GDPR fines hit €7.1 billion cumulatively by 2025¹, and enforcement in 2026 has expanded to AI system interactions. Sending personal data about EU residents to third-party AI providers without a data processing agreement, without a lawful basis, or across an unauthorized border is a GDPR violation, one that organizations trigger routinely by pasting prompts into ChatGPT, Copilot, or Claude.

Removing EU personal data before it reaches an AI provider eliminates the most common data transmission violation entirely. The scrubber processes text locally, so no cross-border transfer occurs at the scrubbing step, and it replaces personal identifiers with tokens that carry no identifying information under GDPR's definition of personal data.

GDPR-relevant data the scrubber detects

Under GDPR, personal data includes any information that can directly or indirectly identify an individual, and this broad definition covers far more data types than most teams initially realize. The scrubber targets the most commonly exposed types in AI prompt workflows: email addresses and phone numbers as direct identifiers, IBANs and credit card numbers as financial identifiers, SSNs as national identifiers, IP addresses as indirect identifiers confirmed as personal data under GDPR by the CJEU in Breyer v. Germany², internal domain names as organizational identifiers that can be linked to specific individuals, and JWT tokens as session identifiers tied to authenticated users. Replacing each of these with a token before AI submission prevents any identifiable data from leaving the processing jurisdiction, which eliminates the cross-border transfer concern entirely.

Direct versus indirect identifiers under GDPR

Direct identifiers, such as email addresses and phone numbers, uniquely identify a person without additional context. Indirect identifiers, such as IP addresses or internal hostnames, require supplementary information to link back to an individual but still qualify as personal data under GDPR. The scrubber treats both categories with equal priority, tokenizing indirect identifiers alongside direct ones to ensure comprehensive de-identification before any prompt reaches an external AI provider.

GDPR Articles relevant to AI prompt submission

Article 5 requires data minimization³, meaning personal data should not be processed beyond what is strictly necessary for the stated purpose. Sending full customer records to an AI tool just to get a date formatted is a clear example of excess processing that violates this principle. Article 46 governs transfers to third countries, so if your AI provider servers are in the US, transmitting EU personal data requires a valid transfer mechanism such as Standard Contractual Clauses. Building on this, Article 28 requires a data processing agreement with any vendor that processes personal data on your behalf⁴, and most public AI tools do not qualify as GDPR-compliant processors under this article. Scrubbing before transmission sidesteps all three article obligations at the prompt level because the AI provider receives only non-identifying tokens.

Local processing and the data processing agreement question

When you use the scrubber, a local browser tool that never transmits your text to any server, no data processing agreement with CapyToolkit is required because no controller-processor relationship exists. The tool processes data entirely in your browser memory, which GDPR treats as within your own processing environment rather than a third-party processing event. Consequently, the scrub step adds zero GDPR compliance overhead to your workflow. The scrubbed output, containing only tokens rather than personal data, may be sent to an AI provider without triggering Article 46 transfer requirements, because tokens are not personal data under GDPR and carry no information that can identify an individual even if the AI provider stores the prompt indefinitely.

GDPR Article 35 Data Protection Impact Assessments and AI tool use

GDPR Article 35 requires a Data Protection Impact Assessment before any processing likely to result in high risk to the rights and freedoms of natural persons. Using an AI tool to process personal data at scale qualifies as likely-high-risk processing in most DPA guidance, because the processing involves systematic evaluation or profiling of individuals, uses new technology, or occurs at significant scale. Organizations that routinely use AI tools on customer or employee data without a completed DPIA expose themselves to enforcement under Article 83(4), which carries fines of up to €10 million or 2% of global annual turnover⁵.

A DPIA for AI tool use must describe the processing purposes, assess necessity and proportionality, evaluate risks to data subjects, and identify mitigating measures. List pre-submission tokenization as a DPIA safeguard: it is a documented technical measure that directly mitigates the risk of unauthorized disclosure to the AI provider, and naming it explicitly gives assessors a concrete control to point to in the DPIA documentation. Several European DPAs, including the French CNIL and the UK ICO, publish template DPIAs for AI tool use that you can adapt for your organization's specific context.

DPIA checklist for teams using AI for personal data processing

A practical DPIA checklist for teams using AI tools with personal data includes: identifying the Article 6 legal basis for general personal data processing (and the Article 9 condition for special categories), confirming a valid transfer mechanism exists if the AI provider is outside the EU (SCCs under Article 46 or an adequacy decision), documenting the categories of personal data involved, assessing whether data minimization measures including pre-submission scrubbing are in place, and obtaining a written opinion from your Data Protection Officer before processing begins. Each of these checklist items has a direct corresponding GDPR obligation, making the DPIA both a compliance tool and an operational planning document.

Schrems II and transatlantic AI data transfers

The Schrems II judgment (Data Protection Commissioner v. Facebook Ireland, C-311/18) invalidated the EU-US Privacy Shield in 2020⁶ and established that Standard Contractual Clauses alone are insufficient when the recipient country's surveillance law makes effective data protection impossible. US cloud providers including Google, Microsoft, and OpenAI are subject to FISA Section 702 and Executive Order 12333⁷, which permit US government access to data stored on US infrastructure. For EU organizations sending personal data to US-based AI providers, the legal basis for the transfer requires either SCCs supplemented by additional technical safeguards, or BCRs reviewed by a competent DPA.

The EU-US Data Privacy Framework (adopted July 2023) established a new adequacy mechanism for transfers to certified US companies⁸. US AI providers certified under the DPF can receive EU personal data under an adequacy decision, which simplifies the legal basis compared to the SCC route. Verify DPF certification on the official DPF Program Website before relying on it as the transfer mechanism for your AI tool data flows. Certification is voluntary and must be renewed annually by the US company, so an organization certified today may become uncertified if it fails to renew.

Selecting EU-hosted AI options for maximum GDPR coverage

Several AI providers offer EU-hosted deployment options that keep data within the European Economic Area. Microsoft Azure OpenAI Service can be deployed in the West Europe or North Europe Azure regions. Google Cloud Vertex AI supports EU-only data residency for Organization customers. Mistral AI, headquartered in France, operates EU infrastructure for its La Plateforme API. Choosing an EU-hosted provider eliminates the transatlantic transfer concern entirely and removes the need to verify SCCs or DPF certification for the AI processing step, simplifying both the DPIA and the legal basis documentation for EU teams.

Scrubbing before submission complements an EU-hosted provider by removing identifiers regardless of where the AI processes the data. CapyToolkit runs locally in your browser, so no personal data reaches any server during scrubbing, and the tokens that result are not personal data under GDPR, which keeps the cross-border transfer question closed even for non-EU providers.

When to use this

Use this before sending any prompt containing EU personal data to an AI provider, especially when no valid DPA exists with that provider or when cross-border transfer mechanisms are unclear.

Examples

Help me draft a refund email to Lena Müller ([email protected], +49-89-123456) about order #DE-2026-00123.

Help me draft a refund email to Lena Müller ([EMAIL_1], [PHONE_1]) about order #DE-2026-00123.

We received a DSAR from [email protected] (IP: 85.214.132.117). List which data fields we hold.

We received a DSAR from [EMAIL_1] (IP: [IP_1]). List which data fields we hold.