What this lesson is
Compliance for an AI PM is not a law school course. It is a small, repeatable set of questions you ask before code ships and before a vendor sees your data. The questions don't change the law. They change whether your DPO walks into the room saying "we have a problem" or saying "we have a process."
Two things make AI features more interesting than the privacy reviews you've done before. One — AI eats free text. Users paste account numbers, phone numbers, passport scans, names of their accountant, into prompts that classical forms would never have collected. Two — your AI vendor is a data processor in the legal sense, even when they feel like a stateless API. What they do with your prompts after the response is sent — log, train, fine-tune, share with sub-processors — is your problem on paper.
So this lesson teaches awareness, not law. By the end you should be able to (a) draw the PII flow through any AI feature on a whiteboard, (b) read a vendor's data-use clause and know what to push back on, (c) tell DPDP from GDPR in the four ways that matter to a PM, and (d) recognise the five situations where you stop and email Legal before the next sprint.
The six dimensions every AI PM must know
"Privacy" is too big a word to be useful in standup. Break it into six concrete dimensions. For each one there is a question, an artefact, and a fix. If your feature is silent on any one of these, that silence is the bug.
DPDP vs GDPR — the four-page version, in six rows
You will hear "DPDP" in India and "GDPR" in Europe and they are not the same regime. But for the PM-level decisions you make every sprint, they overlap more than they differ. Here is the laminated comparison. Read it once; come back for the rows that match the geography you ship in.
| Dimension | DPDP (India) | GDPR (Europe) |
|---|---|---|
| Jurisdiction | Applies to processing of digital personal data of "Data Principals" inside India, plus offers of goods/services into India. | Applies to processing of personal data of subjects in the EU/EEA, regardless of where the processor sits. |
| Consent | Specific, informed, free, unconditional, unambiguous — and presented in a clear notice in plain language. Withdrawable. | Specific, informed, freely given, unambiguous. Same shape — withdrawable, granular, no pre-ticked boxes. |
| Data residency | Cross-border transfers allowed unless government notifies a country as restricted. Sectoral rules (e.g. RBI, IRDAI) may add stricter localisation. | Transfers outside the EEA need an adequacy decision, Standard Contractual Clauses (SCCs), or another lawful basis. |
| Data-subject rights | Access, correction, completion, erasure, grievance redressal, nominee. Acted on within a reasonable period. | Access, rectification, erasure, restriction, portability, objection, automated-decision opt-out. Generally one month to respond. |
| Breach notification | Notify the Data Protection Board and affected Data Principals. Timing per Board rules — assume hours, not days. | Notify the supervisory authority within 72 hours of becoming aware; notify subjects if high risk. |
| Fines (ceiling) | Up to ₹250 crore per instance, set by the Data Protection Board against the data fiduciary. | Up to €20 million or 4% of global annual turnover, whichever is higher. |
Scenario — BoraPay's fraud explainer hits the DPO desk
Amina ships fraud UX at BoraPay in Nairobi. The fraud explainer she's been building (Lesson 09) goes from "Transaction declined" to a short, honest reason in Swahili or English. The model pass rate is comfortably over her gate. Canary is two weeks away. On a Tuesday she gets a calendar invite from Esther, the Data Protection Officer, titled "AI-feature 1-pager: PII flow + vendor clauses."
The ask is small but precise. Esther wants one A4 page that shows: which fields cross which servers, who the vendor is and what they may do with prompts, where the logs sit, and how a deletion request is honoured. No legal language. Just the picture and the answers. Without it, the launch gate fails.
Amina has a model that works and a vendor she likes. What she doesn't have is the artefact. The next four sections are how she builds it.
How PII actually flows — the strip Amina draws first
Esther wants to see the bytes move. So Amina starts with a strip diagram: where the user types, where redaction happens, where the prompt goes, where the response comes back, and where the log lives. If she can draw this and label each box with a server location, the rest of the 1-pager almost writes itself.
Three things to notice. One — the redactor sits inside BoraPay, not at the vendor. Sending raw PII to the vendor "for them to redact" defeats the point. Two — re-hydration (putting the user's name back into the response) happens server-side after the model responds, never in the client. Three — the log stores the redacted prompt plus a PII-flag pointer, never the raw value. Forensics and deletion both rely on that pointer.
The PM's risk matrix — severity × reversibility
Compliance decisions are not all equally scary. The two axes that matter for a PM are severity if it goes wrong and reversibility once it does. Plot every privacy decision on this 2×2; the top-right is where you stop and email Legal before the next commit.
The 1-pager Amina hands to her DPO
This is the artefact Esther asked for. It is one page. It uses no legal language. It maps directly to the six trait cards and the flow strip you saw above. PMs in the cohort produce one of these per AI feature — it lives next to the PRD in Notion.
flows/fraud_explainer_v1.json.The AI connection
Real AI teams operationalise compliance through three pieces of plumbing — a PII detector in front of the model, a contract clause that disables vendor training, and an append-only audit log keyed to model version. The PM owns the policy decisions; engineers own the implementation; the DPO signs off the artefact. pii-redactionno-train-clauseaudit-logdata-residencyretention-policy
🛑 Stop and escalate to Legal when…
- A vendor's free or default tier may train on customer prompts. Do not ship before this is confirmed in writing.
- Data crosses a border and you don't have SCCs or an adequacy basis on file.
- The feature processes children's data, biometric data, or health data — these have stricter rules under both DPDP and GDPR.
- You're asked to "log everything for debugging" — raw PII in logs is the single most common fine-trigger.
- A user asks for deletion and you can't honour it because the data is locked inside an eval set, a fine-tune, or a vendor index.
Mini challenge — write the 1-pager for a feature you use
Pick any AI feature you actually use. Spend 30 minutes writing its compliance 1-pager.
User input → ? → ? → vendor → ? → log. Put a region label on every box ("US-East", "EU-West", "phone"). Circle every box that holds PII. If you can't fill a box, that gap is your finding.
Open the privacy policy of the AI vendor behind the feature. Search for "train" and "improve." Highlight the one sentence that decides whether your prompts feed their next model. Three to five lines, max.
Pick three: PII in logs, training-data clause, retention window, cross-border, vendor lock-in. Drop each on the severity × reversibility 2×2. The top-right ones are the ones you would email Legal about today.
Interview questions
If you didn't do your job — and the golden set has raw PII or quotes — you have two choices, and both have costs. One: purge those entries on deletion and re-curate replacements. This is the right answer under both DPDP erasure and GDPR Article 17, but it shrinks your eval coverage and you'll lose comparability with prior model versions. Two: argue the eval set is anonymised aggregate research data and qualifies for an exception. That is a Legal/DPO call, not a PM call, and you should not assume it will hold.
The senior-PM move is to prevent the question from arising. Three controls. (a) Redact at curation, not at use — the golden set never sees raw PII. (b) Tag every entry with the source user-id (hashed) so that on a deletion request you can verify there is nothing to remove, and prove it. (c) Treat the golden set as a regulated artefact in your data map — it shows up on the PII flow strip with its own residency and retention policy. The same logic applies, even more sharply, to fine-tune sets — once a user's data is fused into model weights, deletion is effectively impossible without re-training, which is why sensible AI PMs avoid fine-tuning on PII at all.
Test your knowledge
Common mistakes first-time AI PMs make
Key takeaways
- Compliance is six dimensions: PII redaction, data residency, vendor data-use, consent, audit logs, retention. Silence on any one of them is the bug.
- DPDP and GDPR converge on four PM-level questions: do you have consent, do you know where the data sits, can you delete on request, can you tell us within hours if something leaked.
- Draw the PII flow strip first. If you can't label every box with a region and a retention rule, you can't ship.
- Treat the no-train clause and cross-border transfers as the top-right of the severity × reversibility 2×2 — escalate to Legal before code, not after.
- Your job is awareness and the artefact (the 1-pager). Your DPO's job is the legal answer. Confusing the two is how launches slip.
You now know what compliance asks.
Next — decide what to buy and what to build.
Join the Best AI Program: The AI-Era Agentic Engineer — 5 months, fully online, with placement assistance. Week 1 is free.
Explore The AI-Era Agentic Engineer →