Why does my AI agent route European health data through a US server without warning?
Opportunity
Multi-step AI workflows route personal data through agent chains, tool calls, embedding models, and LLM inference endpoints spread across cloud regions and jurisdictions. No orchestration layer lets you tag data with residency constraints and enforce them at runtime across the full pipeline. A piece of EU personal data can silently cross a jurisdictional boundary inside a single tool call, as a European insurance company discovered when fined in May 2025 after its claims processing agent routed medical data through a US LLM provider for four months without adequate transfer mechanisms. GDPR and the EU AI Act, which reaches full enforcement for high-risk systems in August 2026, create hard legal obligations, but there is no technical enforcement primitive that sits between the application and the infrastructure to verify compliance in real time.
Why it matters
Data residency enforcement is the single blocker most enterprises name when explaining why they cannot run AI on regulated personal data, and the infrastructure to solve it does not yet exist.
How I score the opportunity
The Opportunity Score is my own read, not a measurement: how much it hurts, how often it bites, and how little exists to solve it today. Higher means I think it is more worth building.
How much pain it causes when it shows up.
How often people actually run into it.
How little good tooling exists for it today.
More problems worth solving
Why is the software we depend on most the worst to use?
TechWhy do I still own none of the data I generate?
TechWhy can I not get a receipt proving my data was actually deleted?
TechWhy can I not know if what is running matches what my SBOM declared?
TechWhy does every C2PA provenance chain break the moment content hits social media?
TechWhy do my AI-generated tests pass on the bugs they were meant to catch?