[{"data":1,"prerenderedAt":273},["ShallowReactive",2],{"focus:retention-erasure-and-localisation":3},{"id":4,"title":5,"body":6,"decision":261,"description":262,"extension":263,"eyebrow":264,"focusArea":12,"lead":265,"meta":266,"navigation":267,"order":268,"path":269,"seo":270,"stem":271,"__hash__":272},"content\u002Fenterprises\u002Ffocus-areas\u002Fretention-erasure-and-localisation.md","How long data stays, how it goes, and where it lives",{"type":7,"value":8,"toc":250},"minimark",[9,13,18,22,31,35,42,48,54,60,64,67,172,175,179,183,186,189,193,212,216,230],[10,11],"self-assessment-scorecard",{"slug":12},"retention-erasure-and-localisation",[14,15,17],"h2",{"id":16},"what-the-law-requires","What the law requires",[19,20,21],"p",{},"Personal data must be erased when the person withdraws consent or the purpose it was collected for is no longer being served, unless the law requires you to keep it. That is a legal duty. Tax rules, KYC directions and sectoral regulations often force fixed retention periods, and those duties override deletion.",[19,23,24,25,30],{},"On localisation, be precise: the DPDP Act does not generally force personal data to stay in India. It restricts transfers to countries the Government notifies as off-limits. Do not assume \"DPDP requires India hosting\"; it does not. Some sectoral rules do require India storage for specific data, the payments data directions from the banking regulator are the standard example, and many regulated customers insist on India-only hosting in their contracts. The ",[26,27,29],"a",{"href":28},"\u002Fenterprises\u002Fdata-sovereignty","data sovereignty page"," goes deeper.",[14,32,34],{"id":33},"the-framework-four-moves","The framework: four moves",[19,36,37,41],{},[38,39,40],"strong",{},"Move 1: Build the schedule from the inventory."," One row per record class. Purpose first, then legal minimums; record which law sets each floor. Where a retention duty and an erasure duty collide, record which law wins and why.",[19,43,44,47],{},[38,45,46],{},"Move 2: Execute erasure with proof."," Write the deletion method per class: live systems, archives, backups, who runs it, how often. Automate the runs; deletion jobs with logs beat calendar reminders with good intentions. Keep the proof of each run. And be honest about backups: instant deletion from every backup is not how backups work, so state the restore-and-re-delete routine instead.",[19,49,50,53],{},[38,51,52],{},"Move 3: Resolve the conflicts on paper."," A conflict register: where duties collide, the resolution, its legal basis, and who decided. Legal holds override deletion; record who can place one.",[19,55,56,59],{},[38,57,58],{},"Move 4: Decide the localisation posture deliberately."," Map which datasets fall under sectoral India-storage rules. For the rest, choose the hosting posture as a policy decision and record the reasoning. If your contracts with banks or government bodies demand India-only storage and no remote production access from outside India without written authorisation, the posture must match.",[14,61,63],{"id":62},"template-the-retention-schedule","Template: the retention schedule",[19,65,66],{},"One row per record class. Copy this and fill it in.",[68,69,70,101],"table",{},[71,72,73],"thead",{},[74,75,76,80,83,86,89,92,95,98],"tr",{},[77,78,79],"th",{},"Record class",[77,81,82],{},"Purpose",[77,84,85],{},"Kept until",[77,87,88],{},"The law behind any minimum",[77,90,91],{},"Deletion method",[77,93,94],{},"Owner",[77,96,97],{},"Last run",[77,99,100],{},"Proof kept where",[102,103,104,130,154],"tbody",{},[74,105,106,110,113,116,119,122,125,127],{},[107,108,109],"td",{},"Example: loan files",[107,111,112],{},"Service the loan",[107,114,115],{},"3 years after closure",[107,117,118],{},"Sectoral record rules",[107,120,121],{},"Purge job, live + archive; restore-and-re-delete on backups",[107,123,124],{},"Lending ops",[107,126],{},[107,128,129],{},"Deletion log store",[74,131,132,135,138,141,144,147,150,152],{},[107,133,134],{},"Example: marketing consents",[107,136,137],{},"Marketing while consented",[107,139,140],{},"Until withdrawal",[107,142,143],{},"None",[107,145,146],{},"Immediate suppression + purge",[107,148,149],{},"Marketing ops",[107,151],{},[107,153,129],{},[74,155,156,158,160,162,164,166,168,170],{},[107,157],{},[107,159],{},[107,161],{},[107,163],{},[107,165],{},[107,167],{},[107,169],{},[107,171],{},[19,173,174],{},"The downloadable file adds the conflict register and a column guide.",[176,177],"template-download-card",{"slug":178},"retention-schedule",[14,180,182],{"id":181},"what-good-looks-like-at-the-end","What good looks like at the end",[19,184,185],{},"You should have: a retention schedule with legal bases, deletion procedures that actually run, proof of deletion runs, the backup handling stated honestly, and a recorded localisation posture with contract terms to match.",[19,187,188],{},"The live test: pick a record class whose retention period ended last quarter. Produce the proof that deletion ran, across live systems, archives and backups, including at processors holding copies.",[14,190,192],{"id":191},"where-enterprises-go-wrong","Where enterprises go wrong",[194,195,196,200,203,206,209],"ul",{},[197,198,199],"li",{},"Retention rules written but never executed.",[197,201,202],{},"\"Delete\" that means \"hide\".",[197,204,205],{},"No record that deletion happened, so compliance cannot be shown.",[197,207,208],{},"Promising instant deletion from backups, then failing to deliver it.",[197,210,211],{},"Assuming the DPDP Act forces India hosting, or assuming it forbids nothing. Neither is true.",[14,213,215],{"id":214},"the-decisions-to-make","The decisions to make",[194,217,218,221,224,227],{},[197,219,220],{},"Erasure depth: live systems only, or archives and backups too.",[197,222,223],{},"How legal holds override deletion, and who can place one.",[197,225,226],{},"The hosting posture per data class, and the reasoning you will show a regulator.",[197,228,229],{},"How sectoral localisation rules stricter than the general law are tracked.",[231,232,233,238],"blockquote",{},[19,234,235],{},[38,236,237],{},"Next step",[19,239,240,244,245,249],{},[26,241,243],{"href":242},"\u002Fenterprises\u002Ffocus-areas\u002Fsecurity-and-technical-controls","Security controls that make protection real",", the safeguards the data you keep still needs. If you need help with any of this, ",[26,246,248],{"href":247},"\u002Fcontact","write to us"," and we will help.",{"title":251,"searchDepth":252,"depth":252,"links":253},"",3,[254,256,257,258,259,260],{"id":16,"depth":255,"text":17},2,{"id":33,"depth":255,"text":34},{"id":62,"depth":255,"text":63},{"id":181,"depth":255,"text":182},{"id":191,"depth":255,"text":192},{"id":214,"depth":255,"text":215},null,"Data that is deleted on time cannot leak, cannot be breached and does not inflate your audit effort. This page covers three connected disciplines: deciding...","md","Focus area 09","Data that is deleted on time cannot leak, cannot be breached and does not inflate your audit effort. This page covers three connected disciplines: deciding how long personal data stays (retention), actually deleting it when time is up (erasure), and controlling where in the world it sits (localisation).",{},true,9,"\u002Fenterprises\u002Ffocus-areas\u002Fretention-erasure-and-localisation",{"title":5,"description":262},"enterprises\u002Ffocus-areas\u002Fretention-erasure-and-localisation","dWjoX23BILb3hXU8RyKB3kk935KCVINF5LZqcxiFUqU",1795073010241]