Skip to main content
The General Data Protection Regulation (GDPR) applies to all EU/EEA residents’ data, regardless of where your company is located. When you send personal data to AI providers like OpenAI or Anthropic, you’re transferring it to a third-party processor — often outside the EU. Blindfold solves this by tokenizing personal data in the EU region before it reaches any AI provider. The LLM only sees anonymized tokens like <Person_1> — never real names, emails, or addresses.

Key GDPR Requirements for AI Applications

Requirement: Only process the minimum personal data necessary for the purpose.Risk with AI: Sending full user messages to an LLM means the AI provider processes all personal data in the text — far more than necessary.With Blindfold: PII is replaced with tokens before the AI call. The LLM only receives what it needs to generate a useful response, without real personal data.
Requirement: Data collected for one purpose must not be used for another.Risk with AI: AI providers may log, train on, or analyze the personal data you send them.With Blindfold: Since only tokens reach the AI provider, there’s no real personal data to repurpose.
Requirement: Personal data transfers outside the EU/EEA require adequate safeguards (Schrems II ruling).Risk with AI: Most LLM providers (OpenAI, Anthropic) process data in the US, triggering Chapter V transfer rules.With Blindfold: Use the EU region (region="eu") — PII is tokenized on EU servers. Only anonymized tokens cross borders, which are no longer personal data under GDPR.
Requirement: Data subjects can request deletion of their personal data.Risk with AI: Data sent to AI providers may be retained in their logs and training data — deletion is impossible.With Blindfold: No real personal data reaches the AI provider. For your own records, use redact() to permanently remove PII.
Requirement: Formal agreements must exist between data controllers and processors.With Blindfold: Since tokenized data is no longer personal data, your DPA requirements with AI providers are simplified. Blindfold offers its own DPA — contact hello@blindfold.dev.

How Blindfold Maps to GDPR

EU Region + gdpr_eu Policy

Region Selection

Use the EU region to ensure personal data is processed on EU-based servers:

What gdpr_eu Detects

The gdpr_eu policy covers all GDPR Article 4(1) personal data types:

Code Examples

Tokenize Before Sending to OpenAI

The most common pattern: protect EU user data before any AI API call.

Right to be Forgotten (Article 17)

When a data subject requests deletion, use redact() to permanently remove their PII:

Batch Processing Support Tickets

Process multiple EU support tickets in a single API call:

Data Residency

When you use region="eu":
  • Processing: PII detection runs on EU-based servers at eu-api.blindfold.dev
  • No cross-border transfer: Personal data never leaves the EU during processing
  • Tokens are not personal data: The anonymized output (<Person_1>) can safely cross borders
  • Your API key works globally: No separate keys needed per region
See Regions for full details on data residency.

Audit Trail for DPAs

Every Blindfold API call is logged in your audit trail, providing documentation for Data Processing Agreements:
  • What was detected: Entity types and counts per request
  • When: Timestamp of every PII operation
  • Which policy: The detection policy used
  • Processing region: EU or US
Export audit logs from the Blindfold Dashboard for DPA compliance reviews.

Cookbook Example

For a complete, runnable GDPR + OpenAI integration, see the cookbook:

GDPR + OpenAI Python Example

Full working example with EU region, gdpr_eu policy, single queries, and batch ticket processing.

GDPR Compliance Checklist

Use this checklist when integrating Blindfold for GDPR compliance:
1

Use the EU region

Set region="eu" in your SDK client to ensure PII is processed in Europe.
2

Apply the gdpr_eu policy

Use policy="gdpr_eu" on all tokenize/redact/encrypt calls handling EU data.
3

Tokenize before AI calls

Always call blindfold.tokenize() before sending text to any LLM provider.
4

Implement Right to be Forgotten

Use blindfold.redact() to permanently remove PII when data subjects request deletion.
5

Sign a DPA with Blindfold

Contact hello@blindfold.dev to sign a Data Processing Agreement.
6

Review audit logs regularly

Export audit logs from the dashboard for compliance documentation.
7

Document your data flows

Record where PII enters your system, how it’s protected, and where anonymized data is sent.