GDPR Oversight
See the personal data your AI sends
to cloud models, and stop what should not go.
A gateway that checks calls to cloud AI services for personal data, then alerts, redacts, or blocks according to your policy. Each event it handles is logged, so your DPO has a record to work from when the 72-hour Article 33 clock starts.
The GDPR gap your AI tools created
Cloud AI tools often arrive before the controls around them. These are the four gaps GDPR Oversight is built for.
No visibility into what AI receives
Your employees and agents are sending prompts to OpenAI, Anthropic, and Google every day. Without an egress monitor, you do not know whether those prompts contain customer names, health records, account numbers, or other Article 4 personal data. Not knowing is no defense under GDPR.
Breach notification requires evidence you do not have
Article 33 requires you to notify the supervisory authority within 72 hours. That notification must describe the categories of data affected, the approximate number of data subjects, and the likely consequences. Without an immutable egress log, you cannot produce that evidence. You cannot notify what you cannot prove.
AI vendors are sub-processors you may not have assessed
Sending personal data to an LLM API makes that provider a sub-processor under Article 28. Many companies have not completed data protection impact assessments for their AI tool stack, have not verified standard contractual clause compliance for US providers, and have not updated their records of processing activities to reflect AI data flows.
Policy in documents does not stop data egress
An acceptable use policy that says "do not enter personal data into AI tools" is not a technical control. Employees forget, agents do not read policies, and pressure to move fast overrides caution. GDPR Oversight enforces the policy at the gateway, on the call itself.
Five-stage governance pipeline
Each LLM API call routed through the gateway goes through the same five steps.
Intercept
Outbound LLM API calls pass through the GDPR Oversight gateway, whether a person or an autonomous agent made them. No changes to application code required for proxy-mode deployment.
Classify
The PII scanner analyzes the request payload against configured data categories: names, email addresses, national IDs, health data, financial data, location data, and custom enterprise-specific categories. Each detection is tagged with risk level: Low, Medium, or High.
Enforce
Policy rules determine the action: Pass (monitor only), Alert (notify DPO, allow through), Redact (strip PII before forwarding), or Block (reject the request). Rules are configurable per data category, destination endpoint, user group, or agent identity.
Log
Each egress event the gateway handles is written to an immutable breach register, whatever action was taken: timestamp, source, destination, PII categories detected, risk level, action taken, and user or agent identity. Your DPO can draw on it for Article 33 notifications and Article 33(5) breach documentation.
Notify
High-risk events trigger automated DPO notification via email and dashboard. The breach register tracks the 72-hour Article 33 clock automatically. For Article 34 events affecting high-risk data subjects, the system generates a notification draft for the DPO to review and dispatch.
What GDPR Oversight delivers
From detection to a notification draft your DPO reviews.
| Capability | What it does | GDPR article |
|---|---|---|
| Egress monitoring | Real-time view of personal data in calls that pass through the gateway to cloud AI endpoints | Art. 32 — Technical and organizational measures |
| PII classification | Automated detection of personal data categories in LLM request payloads with risk scoring | Art. 4 — Definition of personal data |
| Block & redact | Policy-enforced blocking or PII redaction before data reaches the LLM provider | Art. 25 — Data protection by design and by default |
| Immutable breach register | Immutable log of each egress event the gateway handles, with full context, retained per your retention policy | Art. 33(5) — Documentation of breaches |
| DPO alert dashboard | Real-time alert feed, breach register, 72-hour clock tracker, and notification workflow | Art. 33 — Breach notification to supervisory authority |
| Evidence package generator | Drafts Article 33 notification documentation from breach register data for your DPO to review | Art. 33 — Notification within 72 hours |
| Sub-processor register | Automated mapping of AI endpoints used, data categories sent, and transfer mechanism status | Art. 28 — Processor obligations; Art. 30 — Records of processing |
| Transfer compliance checks | Flag transfers to third-country endpoints lacking an adequate transfer mechanism (SCCs, adequacy decision) | Art. 44–46 — Transfers to third countries |
Common questions
GDPR Oversight sits between your users, your agents, and the cloud AI endpoints they call — OpenAI, Anthropic, Google, Azure OpenAI, and others. Outbound LLM API calls routed through the gateway are checked as they pass. We scan the request payload for personal data categories (names, email addresses, national ID numbers, health data, financial data, location data, and other Article 4 GDPR categories), classify the risk level, and decide in real time whether to pass, alert, redact, or block. The gateway writes an immutable egress event record for each call it handles, whatever action it took. Your DPO can use that log as evidence when preparing an Article 33 breach notification.
GDPR Oversight deploys as a transparent proxy in front of your LLM API calls — no changes to your application code required in most cases. For organizations already routing LLM calls through an API gateway, we integrate at that layer. For direct SDK usage, we provide lightweight SDK wrappers for the major providers. We also support webhook-based integration for alerting into existing SIEM, DLP, or incident management systems (Splunk, Datadog, PagerDuty, Jira Service Management). The DPO dashboard is a standalone web application requiring no infrastructure on your side.
For a high-risk event: the request is blocked before it reaches the LLM provider; an immutable breach record is written with full context (timestamp, source system, destination endpoint, PII categories detected, user/agent identity); the DPO receives an automated alert via email and dashboard notification; and the 72-hour Article 33 clock is noted in the breach register. For medium-risk events, the default action is to alert without blocking — this is configurable per policy rule. The DPO can review, escalate, dismiss, or initiate a formal breach notification workflow directly from the dashboard.
Yes. GDPR Oversight supports logical tenant isolation within a single deployment — relevant for holding groups, law firms with multiple practice areas, or SaaS providers processing data on behalf of multiple controllers. Each tenant has its own policy rules, egress event log, breach register, and DPO notification settings. Cross-tenant data cannot be accessed by tenant-level users. Platform administrators can see aggregated metrics without accessing individual tenant data. Data processor agreements, sub-processor lists, and record-of-processing activities can be scoped per tenant.
PII classification accuracy depends on the classifier engine configured for your deployment — we support multiple options including Microsoft Presidio, AWS Comprehend, and fine-tuned transformer-based classifiers. Structured identifiers (names, emails, ID numbers, IBANs) are easier to catch than personal data in free text, such as a health condition mentioned in passing or an implied location, so we do not quote a single accuracy figure. During setup we measure detection on a sample of your own data and set the threshold per data category. Stricter detection catches more and also flags more harmless text, so the threshold depends on your risk appetite and on how many edge cases your team can review.
Whether a deployment meets your GDPR obligations is for your DPO and counsel to decide. What we can tell you is where the data sits. GDPR Oversight can run fully on-premise or in a private cloud in your jurisdiction, in which case personal data does not pass through our infrastructure. The breach register, egress event logs, and policy configuration are stored in your environment. For cloud-hosted deployments, we sign a data processing agreement covering our role as processor, our sub-processor list, and where data is held. We do not use customer data for model training, product improvement, or anything outside the contracted service. Records of our own processing are available to your DPO on request.
When the boundary is the EU
This product detects personal data heading to a cloud model and keeps the evidence. When prompts, documents, outputs, and logs must stay in the EU, the engagement is Sovereign AI. When a generated client is what sends the data out, start with AI Code Cleanup.
Find out what your AI tools send out
Tell us your AI tool stack and the obligations your DPO works to. On the call we go through what GDPR Oversight would check in your environment and what records it would give your DPO.