Session
Whose Law Is Your Database Under?
Data from five countries, stored in a sixth, owned from a seventh. Whose law applies? All of them, at once.
Data sovereignty isn’t a privacy footnote; it’s an architecture constraint. Your pipelines, your DR replica, your seven-year backups, your dashboards, your support team’s remote access, and the prompt you just sent to an AI model can all be cross-border transfers waiting to be noticed.
A practitioner’s session on the laws that actually reach your data estate, why residency isn’t sovereignty and encryption isn’t an exit, and the design choices that survive all of it. No legal advice, no vendor pitch: just the questions to ask before an auditor does. Bring the region pair you never questioned.
1) Map any dataset to the laws that reach it using three hooks: where the people are, where the data sits, and who controls it.
2) Find the transfers hiding in replication, backups, encryption keys, dashboards and AI prompts.
3) Leave with the questions to ask any cloud or sovereign provider, and a design pattern that survives them: regional partitions, in-country DR, and aggregate-only federation.
Michael Wall
Architect/DBA at 3Cloud Consulting
Vancouver, Washington, United States
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top