Uncategorized

DPDP Compliance Calendar, Document Retention, DR on Cloud: What Indian Businesses Must Do Before May 2027

Published on Nov 18, 2026

— —

India’s data protection law becomes fully operational on 13 May 2027, and most businesses have about six months left to get ready. The DPDP Rules were notified on 13 November 2025 and apply in three phases. The next milestone, on 13 November 2026, opens registration for Consent Managers. It is not a deadline for most companies, but it is a useful reminder that the clock is running.

In our work with companies in Gujarat and western India, DPDP readiness almost always brings up two other questions. How long must we keep our records, and where? And could we actually recover our systems and data if our server room went down tomorrow? The three are connected: data you can’t find, data you keep too long and data you can’t restore are all compliance risks.

This guide brings them together: a dated compliance calendar, a practical document retention policy, and a checklist for disaster recovery (DR) on cloud for systems that still run on-premise.

The compliance calendar: DPDP and the dates around it

DateWhat changesWho it affects
Since 2022CERT-In Directions: report cyber incidents within 6 hours; keep ICT logs for 180 days in IndiaAlmost every organisation
Since Aug 2022Companies (Accounts) Rules: daily backup of electronic books of account on servers in IndiaAll companies
13 Nov 2025DPDP Rules notified; Data Protection Board provisions in forceFramework only
1 Apr 2026Income-tax Rules, 2026: electronic books must be accessible in India, with a daily backup on servers in IndiaTaxpayers keeping books electronically
1 Apr 2026Only internet-connected CCTV cameras certified against MeitY’s Essential Requirements may be soldAnyone buying or replacing cameras
31 Jul 2026RBI’s new cybersecurity, technology risk and resilience Directions take effect immediatelyBanks, NBFCs, UCBs and other RBI regulated entities
13 Nov 2026DPDP Rule 4: Consent Manager registration opensCompanies that want to become Consent Managers
13 May 2027Most DPDP duties start: notice, consent, security safeguards, breach intimation, retention and erasure, data-principal rights, children’s dataEvery organisation processing digital personal data
1 Apr 2028RBI cyber-resilience framework applies to small non-bank payment system operatorsSmaller payments and fintech firms

Still to watch: in January 2026 MeitY proposed bringing some duties forward for large “Significant Data Fiduciaries”. As of October 2026, reviews found no notified amendment. The list of Significant Data Fiduciaries and the rules on cross-border transfers are also still to be notified. Plan to May 2027, and keep a plan that could move earlier if you are a large consumer platform.

What DPDP asks you to build before May 2027

DPDP readiness is mostly an engineering and process job, not a policy-writing one, and typical programmes take 9 to 12 months. These are the building blocks:

1. A personal data map.

Every place you collect customer, employee, dealer, patient, visitor, CCTV and biometric data, with its purpose, lawful basis, storage location, processors and retention period.

2. Clear notices and consent.

Plain-language notices, consent that can be withdrawn as easily as it was given, and records that prove both.

3. Reasonable security safeguards (Rule 6).

Encryption, access control, monitoring and the ability to detect and contain a breach.

4. Logs kept for at least one year.

Personal data, associated traffic data and processing logs must be retained for at least a year.

5. A breach response you can run.

Inform affected people and the Data Protection Board without delay, with full details to the Board within 72 hours (Rule 7).

6. Rights and grievance handling.

A working process for access, correction, erasure and grievance requests.

7. Erasure on schedule.

Personal data is deleted once its purpose is served, unless another law requires you to keep it.

8. Processor contracts.

Security and breach-notification duties written into every cloud, SaaS and IT service contract.

Penalties under the Act run up to ₹250 crore for failing to take reasonable security safeguards. They attach to duties that start in May 2027, which is exactly why the work needs to start now

Document storage and retention: how long, and where

A good retention policy answers three questions for every record type: how long it must be kept, where it must be kept, and when it must be deleted. Indian law sets different minimums for different records, and where several apply, the longest one governs.

Record typeMinimum retention and locationSource
Books of account and vouchers (companies)8 financial years; electronic books accessible in India at all times, with a daily backup on servers in IndiaCompanies Act s.128(5); Companies (Accounts) Rules r.3
Books of account (taxpayers under the new Income-tax Act)7 tax years from the end of the relevant tax year; daily backup on servers in India from 1 Apr 2026Income-tax Rules, 2026, r.46(8)–(9)
GST accounts and records72 months from the due date of the annual return; longer while proceedings are pendingCGST Act s.36; CGST Rules r.56–57
KYC and transaction records (banks, NBFCs, intermediaries)Typically 5 years after the relationship or transaction endsPMLA s.12 and the regulator’s KYC directions
ICT and security logs180 days, kept in IndiaCERT-In Directions, 2022
Personal data and processing logsLogs at least 1 year; personal data erased once its purpose is served, unless another law requires retentionDPDP Act s.8(7); DPDP Rules
Indoor-patient medical recordsAt least 3 yearsMedical Council regulations
Pharma batch, QC and stability recordsAt least 1 year after product expiry; longer for export marketsRevised Schedule M

Retention is not “keep everything forever”

Under DPDP, keeping personal data longer than you need it is itself a risk. A sound policy pairs every retention period with an auditable deletion step, and a legal hold that pauses deletion when litigation, an audit or a tax or GST proceeding is pending.

Digitising paper records safely

Scanning paper files into a document management system (DMS) saves space and makes records searchable, but the scanned copy has to hold up legally.

Capture proof at scan time.

The IT Act accepts an electronic record for retention if it stays accessible and accurately represents the original. Record the operator, device, date and a hash value, so you can produce the certificate that the Bharatiya Sakshya Adhiniyam, 2023 (s.63) requires for electronic evidence.

Don’t destroy originals by default.

Wills, powers of attorney, trusts, property sale contracts and most negotiable instruments fall outside the IT Act, and stamped documents usually need the original. Dispose of paper only under a schedule your legal team has approved.

Treat scanning as data processing.

Use chain-of-custody logs, vetted staff and onsite scanning for the most sensitive files, and mask Aadhaar numbers where you are not permitted to store them.

Use archive-grade formats.

PDF/A, consistent resolution and quality checks you can show an auditor.

Designing the archive: on-premise or cloud

Most organisations keep years of inactive data on expensive primary storage. Moving it to a cold or archive tier, either on-premise tape or object storage, or India-hosted cloud, usually pays for itself. Whichever you choose, insist on:

  • Immutability (WORM or object lock) for books, audit trails and logs, so they can’t be altered or encrypted by ransomware.
  • Encryption, with keys and data kept in India.
  • Search and indexing good enough to answer a tax notice or a 72-hour records request on time.
  • Regular restore and readability tests, so the archive still works years later.

DR on cloud for systems that still run on-premise

You don’t need a second data centre to have real disaster recovery. With DR on cloud (often called DRaaS), production stays in your server room or data centre. Critical systems are replicated to an India-hosted cloud, and you pay for full compute only during drills or a real disaster. For mid-sized businesses, this is usually the most affordable route to a tested DR site.

Signs you need it: a single server room with no secondary site, tape or USB-only backups, no full-system restore in the last year, a ransomware incident at a peer, or an auditor or customer asking for DR evidence.

A DR-on-cloud checklist

  1. Real geographic separation. The DR site must not share your primary site’s power grid, flood or seismic risk, or network carrier. For a production site in Gujarat, a DR site in Navi Mumbai or the NCR is a common pattern.
  2. Recovery targets per application. Agree a recovery time objective (RTO) and recovery point objective (RPO) for each system, and match the replication method to each. One number for the whole estate is a warning sign.
  3. Security parity. The DR environment needs the same patching, access control, MFA, logging and monitoring as production. A neglected DR copy is an easy way in for attackers.
  4. An immutable, isolated backup copy. Replication copies ransomware along with everything else. Keep at least one copy that can’t be altered or deleted, and scan it before you restore.
  5. Data kept in India. This is needed to meet daily India-backup rules for books of account and, for many regulated sectors, data localisation.
  6. Drills with evidence. Scheduled failover tests with runbooks, timed results, an issues log and a re-test. Test failback too.
  7. Clear responsibilities and exit terms. Who declares a disaster, who fails over, and how your data comes back if you change provider.

If you are in a regulated sector

  • Banks and NBFCs: RBI’s 2026 Directions expect DR drills for critical systems at least every six months, with the DR site run as primary for a full working day. Cloud contracts must also carry the audit, inspection and exit terms in RBI’s 2025 outsourcing Directions.
  • SEBI-regulated entities: SEBI’s cloud framework requires data and logs to stay within India, with an empanelled cloud provider.
  • Hospitals: clinical systems need a tested downtime procedure, not only a backup.

A 90-day plan to get started

Starting in November 2026 leaves enough time to be ready by May 2027, with room for testing, if the first 90 days go like this:

  1. Days 1–15, take stock. List your systems, data stores, paper record rooms, backups and vendors. Note which laws and regulators apply to you.
  2. Days 16–30, find the gaps. Map personal data flows, draft a retention schedule by record type, and run a full restore test on one critical system.
  3. Days 31–60, fix the biggest risks. Tighten access control and logging, set up an immutable backup copy, update vendor contracts, and start digitising or archiving the highest-risk records.
  4. Days 61–75, prove it works. Run a DR failover drill and a breach tabletop exercise with a timed 6-hour CERT-In report. Collect the evidence in one place.
  5. Days 76–90, make it routine. Put retention, deletion, backup and DR tests on a calendar with named owners and monthly reporting.

How Silicon Computech can help

Silicon Computech helps businesses produce the evidence auditors and regulators expect, not just the policies. We run DPDP readiness and gap assessments; managed SOC, backup and immutable storage; document digitisation and DMS; India-hosted archival; and DR on cloud. These run on data centres and cloud platforms from partners including Yotta and Sify, and Microsoft Azure.

Three short assessments are a good place to start:

  • Records & Retention Health Check: your paper and electronic records mapped against the retention rules above.
  • Storage Tiering Assessment: how much of your primary storage could move to a cheaper, compliant archive.
  • DR Readiness Assessment: recovery targets per application, a live restore test and a DR-on-cloud design.

Contact Silicon Computech Pvt. Ltd. to book one

This article is general information as of 18 November 2026, not legal advice. Rules change and their application depends on your business, so confirm specific obligations with your legal or compliance adviser.

Share this article

Leave a Comment