The “Data Residency” Slide Deck: A Masterclass in Half-Truths
Why a map of server locations is not a map of legal safety, and the three sales phrases that should trigger an immediate veto.
The Geography of Deception
The slide deck was polished, the fonts were sans-serif, and the coffee was expensive. The Sales Director, a man who spoke in exclamation points, clicked to slide number four. It was a map of Europe, covered in reassuring green dots.
“We have true Data Residency,” he declared. “We have opened a new zone right here in the capital. Your Citizen data will never cross the border. It is safe.”
He looked at me, expecting a nod of approval.
“And who owns the keys to that facility?” I asked, my voice low. “And under which country’s laws is the parent company incorporated?”
“Well, our parent is in California, but the subsidiary is local LLC…”
“Then the map is irrelevant,” I closed my notebook. “If the parent company is subject to extra-territorial subpoenas, that server is not in our country. Legally, it is in yours. This proposal is rejected.”
The Trap: Geography as a mask for Jurisdiction
Vendors use “Data Residency” to lull procurement teams into a false sense of security. They know that if they put a server on our soil, we feel protected. But in the age of the cloud, physical location is secondary to Corporate Allegiance.
There are three phrases in these presentations that act as red flags. When you hear them, you are not being sold a service; you are being sold a dependency.
- “Global Infrastructure”: They frame this as a feature. For a municipality, it is a vulnerability. We do not need our water metering data to be optimized via a node in Virginia. We need it to remain under our statute.
- “Seamless Data Mobility”: This translates to “We move your data where electricity is cheapest.” Mobility is the opposite of sovereignty.
- “Follow-the-Sun Support”: This means a technician in a non-adequate jurisdiction has root access to your database while you sleep. They are importing foreign legal risk into your local database.
[TO EDITOR: A diagram showing two servers side-by-side. One is labeled “Sovereign” with a solid wall. The other is labeled “Residency” with a back door leading to a foreign flag.]
The Exit Strategy: The “Reverse RFP”
We cannot simply say “No” without a framework. We must counter-attack with precision. When a vendor leads with geography, I issue what I call the “Jurisdictional Interrogation.”
I do not ask “Where is the data?” I ask:
- “Can you provide a binding legal guarantee that no entity outside of this jurisdiction, including your parent company, possesses the technical capability to decrypt this data?”
If they answer with “Policy,” “Process,” or “Compliance,” the answer is No. If they answer with “Technical architecture,” “External Key Management,” and “Contractual Indemnity,” we can proceed.
We must stop buying maps. We must start buying legal shields. If the vendor cannot protect the Citizen from their own government, they are not fit to serve ours.
FAQs
What is the difference between residency and sovereignty?
Residency is where the hard drive sits. Sovereignty is which judge can demand the hard drive. They are rarely the same.
Does 'Global Reach' benefit the municipality?
No. For a municipality, 'Global Reach' usually means 'Global Liability'. We do not need our data to travel; we need it to stay put.
How do I politely stop a sales pitch?
Ask them to name the specific legal entity that will sign the contract. If it is a subsidiary, ask if the parent company guarantees the liabilities. The answer tells you everything.