Know the law
Which regimes reach this agent, in which jurisdictions?
- Regulatory compliance
- Industry-specific controls
Every agent action is a data processing event. Governance decides what your organization allows; compliance is what the law requires — and it applies whether or not anyone wrote it down.
Not “is the agent good?” but: what law reaches this processing, what personal data actually flows, and can you prove both to a regulator.
Which regimes reach this agent, in which jurisdictions?
Engineer safeguards into the system, not only the policy.
People can demand access, erasure, and human review.
The deck organizes compliance around regulatory obligations, privacy controls, rights under GDPR and CCPA/CPRA, data governance, and sector-specific controls.
Obligations arrive on three axes at once. Most teams discover the third one late, and usually from a customer’s procurement questionnaire.
Privacy by design means the safeguard is in the code path, not in the policy document. For agents, that means controlling what enters the context window in the first place.
Two regimes, one structural difference in the deck: Europe requires a lawful basis before processing, while California centers consumer opt-out rights — and both reach automated decisions directly.
You cannot protect, delete, or justify data you cannot locate. Governance is knowing what you hold, where it came from, where it went, and when it goes away.
Sector rules predate AI and constrain what an agent may see, do, and keep — often more tightly than privacy law.
PHI, minimum-necessary access, business-associate agreements, and audit logging of record access.
Recordkeeping and supervision of communications, model risk management, and operational resilience.
Cardholder data must never enter a prompt, a log, or an agent’s memory.
Adverse-action explanations, anti-discrimination testing, and actuarial justification.
A user asks to be forgotten. Deleting their source row may leave personal data in vector indexes, agent memory, logs, caches, backups, and potentially model weights.
An agent that approves, prices, screens, or denies is making an automated decision. The deck highlights duties around notice, contestability, and meaningful human review.
Retrofitting compliance onto a deployed agent is the expensive path. Design the data flows first; the legal obligations follow them.
The page preserves the source deck’s legal disclaimer: verify current obligations with counsel because this area changes quickly.