[{"data":1,"prerenderedAt":148},["ShallowReactive",2],{"content:\u002Fenterprises\u002Fdata-sovereignty":3},{"id":4,"title":5,"body":6,"decision":137,"description":137,"extension":138,"eyebrow":139,"focusArea":140,"lead":140,"meta":141,"navigation":142,"order":143,"path":144,"seo":145,"stem":146,"__hash__":147},"content\u002Fenterprises\u002Fdata-sovereignty.md","Data sovereignty: where your data lives, and who can reach it",{"type":7,"value":8,"toc":126},"minimark",[9,14,18,22,25,35,38,42,75,79,82,86,97,101,110],[10,11,13],"h2",{"id":12},"what-data-sovereignty-means-in-practice","What data sovereignty means in practice",[15,16,17],"p",{},"Data stored anywhere answers to the laws of the place it sits, and often to the laws of the places its operator answers to. For an Indian enterprise the practical questions are: is our data stored where we think it is, which laws can compel access to it, and could our vendor move it without telling us. Sovereignty is less about borders on a map and more about knowing and controlling these answers.",[10,19,21],{"id":20},"what-indian-law-actually-requires","What Indian law actually requires",[15,23,24],{},"Two things are true at once, and confusing them causes most mistakes here:",[26,27,28,32],"ul",{},[29,30,31],"li",{},"India's data protection law does not generally force personal data to stay inside India. It allows cross-border transfer, subject to restrictions the Government notifies, and it expects you to keep meeting your duties wherever the data goes.",[29,33,34],{},"Some sectoral rules do force local storage. The standard example is payment system data, which the banking regulator requires to be stored in India. Banks, government bodies and regulated entities frequently make India-only storage a hard contract condition for their vendors.",[15,36,37],{},"So the first step is not a hosting decision; it is a classification: which of our data falls under a localisation rule, and which is simply ours to place wisely.",[10,39,41],{"id":40},"how-to-actually-control-where-data-lives","How to actually control where data lives",[26,43,44,51,57,63,69],{},[29,45,46,50],{},[47,48,49],"strong",{},"Choose regions deliberately."," Every serious cloud provider lets you pin workloads to Indian regions. Set it, then verify it, including backups and disaster-recovery copies, which quietly replicate elsewhere by default.",[29,52,53,56],{},[47,54,55],{},"Read the vendor's terms on transfer."," Look for where data is stored, whether support access happens from abroad, and what happens to data on termination.",[29,58,59,62],{},[47,60,61],{},"Contract the residency you need."," If India-only storage matters to you or your regulator, say it in the contract: storage, processing, backups and remote access.",[29,64,65,68],{},[47,66,67],{},"Watch the hidden copies."," Exports, analytics exports, logs, support tickets with attachments, and AI features inside vendor platforms all copy data sideways. Your residency rule should cover them.",[29,70,71,74],{},[47,72,73],{},"Keep a transfer inventory."," In your record of processing activities, note for each flow where the data goes and under what terms. You cannot govern what you have not listed.",[10,76,78],{"id":77},"the-enterprise-benefit","The enterprise benefit",[15,80,81],{},"Beyond compliance, residency discipline buys negotiating strength and resilience: you know your exposure before a regulator, a customer or an incident asks about it. Enterprises that can answer \"where is our data\" in one minute pass vendor assessments faster and sleep better.",[10,83,85],{"id":84},"where-organisations-go-wrong","Where organisations go wrong",[26,87,88,91,94],{},[29,89,90],{},"Assuming a vendor's \"India data centre\" marketing covers backups, logs and support access.",[29,92,93],{},"Signing standard terms that permit the vendor to relocate data with notice, then never reading the notices.",[29,95,96],{},"Applying one blanket rule to everything: over-restricting data that could move freely, and under-protecting the data that cannot.",[10,98,100],{"id":99},"go-deeper","Go deeper",[26,102,103],{},[29,104,105],{},[106,107,109],"a",{"href":108},"\u002Fenterprises\u002Ffocus-areas\u002Fretention-erasure-and-localisation","09 · How long data stays, how it goes, and where it lives",[111,112,113,118],"blockquote",{},[15,114,115],{},[47,116,117],{},"Next step",[15,119,120,121,125],{},"When you deal with customers, vendors or group companies abroad: ",[106,122,124],{"href":123},"\u002Fenterprises\u002Fglobal-rules","data protection rules around the world",".",{"title":127,"searchDepth":128,"depth":128,"links":129},"",3,[130,132,133,134,135,136],{"id":12,"depth":131,"text":13},2,{"id":20,"depth":131,"text":21},{"id":40,"depth":131,"text":41},{"id":77,"depth":131,"text":78},{"id":84,"depth":131,"text":85},{"id":99,"depth":131,"text":100},"where your enterprise's data should physically sit, and how to make sure it stays there.","md","Enterprise guide",null,{},true,8,"\u002Fenterprises\u002Fdata-sovereignty",{"title":5,"description":137},"enterprises\u002Fdata-sovereignty","gepO7nlNzub5JHUTUIviUtZCzvgRHuphDFJc1YYCYNs",1795073009848]