Checklist for engineering teams

DPDP technical readiness checklist

60 checks across data, consent, security and vendors, each with the evidence to keep. Tick what you already have, then download the rest as a spreadsheet and turn it into tickets.

Download as CSVNothing is stored
60 checks

Four areas, twelve groups

DataMap, retention and erasure, transfers
ConsentNotice, proof, withdrawal, rights, children
SecuritySafeguards, logs, breach readiness
VendorsProcessors, AI tools, mobile SDKs
Evidence named for each checkCore duties start 13 May 2027, by our count
For engineering teams

How to use it.

The DPDP Rules were notified on 13 November 2025. Most duties start 18 months later, which we count as 13 May 2027. Some law firms count from 14 May.

What it is

A working list for the people who build and run the systems. Each check says what to do and what evidence to keep. Start with the data map, because every later check depends on it. Our guide to starting DPDP work with a data map shows how, and the DPDP data mapping template gives you the sheets.

What it is not

It is not the Act or the Rules, and ticking every box does not prove compliance. The checks and evidence are our suggestions. Where we cite a section or rule, read the source text. This page is general information, not legal advice. Mono is not a law firm, an auditor or a certification body.

What it leaves to other pages

The Rule 6 checklist quotes each security safeguard and has its own list of checks. This page gives you five quick tests from it and sends you there for the rest. To see how ready you are before you start, try the DPDP self-check.

How to read the summary boxes

The short box under each heading is our summary of the source in plain words. It is not a quotation from the Act or Rules.

All 60 checks, in four areas.

Tick what you already have. Nothing is saved or sent, so download the CSV to keep your progress in your own tracker.

0 of 60 done
Data 1, Act ss.5 and 8, Rule 3

Know what personal data you hold

Our summary: you cannot write a notice, honour a withdrawal or erase data for a system you have not found.
  • EvidenceA system register with a named owner for each system.

  • EvidenceA field-level inventory per system.

  • EvidencePurpose and basis columns in the map.

  • EvidenceA data flow diagram and a vendor list that match each other.

  • EvidenceA dated change log.

Data 2, Act ss.8(7), 8(8) and 12, Rule 8

Retention and erasure

Our summary: erase when the purpose ends or consent is withdrawn, whichever is earlier, unless a law requires you to keep the data.
  • EvidenceA retention schedule that links to the data map.

  • EvidenceJob configuration and dated run logs.

  • EvidenceA contract clause and deletion confirmations.

  • EvidenceUser counts, and a warning notice and job for inactive accounts.

  • EvidenceA backup expiry policy and a restore procedure that re-applies erasures.

Data 3, Act s.16, Rule 15

Where data is stored and sent

Our summary: DPDP allows transfers abroad unless the government notifies a country. Sector rules can still require data to stay in India.
  • EvidenceStorage and processing region for each system and vendor.

  • EvidenceA written conclusion from your own legal adviser for each sector rule that applies.

  • EvidenceRegion settings, and a named person who watches the Gazette.

  • EvidenceA dated note of the review.

  • EvidenceThe transfer mechanism you use, agreed with your legal adviser.

Security 1, Act s.8(5), Rule 6(1)

The safeguards test

Our summary: Rule 6 sets a minimum. These five checks are a quick test. The full clause-by-clause list is on the Rule 6 checklist.
  • EvidenceAn export of encryption settings per store.

  • EvidenceA role and access matrix.

  • EvidenceA list of masked fields and the test data refresh procedure.

  • EvidenceDated restore test results.

  • EvidenceThe downloaded Rule 6 CSV, dated and signed off by an owner.

Security 2, Rules 6(1)(c), 6(1)(e) and 8(3)

Logs and monitoring

Our summary: you need to see who accessed personal data, and keep that record for at least one year.
  • EvidenceA list of log sources with sample entries.

  • EvidenceRetention settings for each log store.

  • EvidenceThe log pipeline and the list of people who can change it.

  • EvidenceAlert rules, and one alert that was investigated.

  • EvidenceA sample log scan and the masking rules.

Security 3, Act s.8(6), Rule 7, CERT-In Directions

Breach readiness

Our summary: every personal data breach is reported to the Board and to each affected person, with no risk threshold.
  • EvidenceThe runbook, with a timeline for both.

  • EvidenceAn on-call rota and an escalation list.

  • EvidenceA notice template and the channels it uses.

  • EvidenceBoth templates, filled in during a drill.

  • EvidenceA dated exercise report with the fixes you made.

Vendors 1, Act s.8(1), 8(2) and 8(5), Rule 6(1)(f)

Processors and contracts

Our summary: you stay responsible for personal data your processors handle, and each one needs a valid contract.
  • EvidenceA vendor register linked to the data map.

  • EvidenceSigned contracts and a clause checklist.

  • EvidenceA dated evidence file per vendor.

  • EvidenceThe breach notice clause and a named contact at the vendor.

  • EvidenceExit terms and a deletion confirmation from a past exit or test.

Vendors 2, Act ss.5, 6 and 8

AI tools and model providers

Our summary: the Act does not ban AI tools. It applies to the personal data you put into them.
  • EvidenceAn AI tool register with an owner for each tool.

  • EvidenceDated screenshots or links to the vendor’s settings and documentation.

  • EvidenceA written AI policy and single sign-on logs.

  • EvidenceMasking test cases and results.

  • EvidenceThe purpose and basis row for each AI use in the data map.

Vendors 3, Act ss.5, 6 and 8, app store rules

Mobile SDKs and analytics

Our summary: every SDK in your app is a processor or a recipient. Know what each one collects, and when it starts.
  • EvidenceA dependency list per release.

  • EvidenceA network capture of a clean install, and the SDK settings you changed.

  • EvidenceA test showing no calls to those SDKs before consent.

  • EvidencePrivacy manifest status for each listed SDK and the ATT prompt flow.

  • EvidenceThe store forms, reviewed on every release that changes an SDK.

Why vendor settings need a date.

DPDP does not require data to stay in India. But where an AI vendor stores and processes data decides what you can tell customers, and it differs by product and plan. The same vendor can store data in India and still run the model elsewhere. Our data mapping template sets out dated examples for the main AI vendors and gives you a sheet to record each tool. Vendors change these settings, so check the current documentation before you record a region.

Readiness checklist FAQs.

Does finishing this checklist make us DPDP compliant?

No. It shows you where your engineering stands. The Act and Rules set the duties, and this list is our suggestion for how to check and evidence them. It does not cover every duty, such as sector rules, and it is not legal advice. Ask a qualified lawyer how the law applies to your business.

Can we get a DPDP certificate once we pass?

No. Neither the Act nor the Rules provide for a DPDP compliance certificate or a certifying body. Mandatory audits apply only to Significant Data Fiduciaries, and none have been notified as of November 2026. What buyers can ask for is evidence: policies, logs, contracts and test results. This checklist names the evidence for each check.

How long should we keep consent records?

The Act asks you to prove notice and consent in any proceeding (s.6(10)), so keep records long enough to do that, and at least the one-year minimum in Rule 8(3). The seven-year period in the Rules applies to registered Consent Managers, not to ordinary fiduciaries. Ask your legal adviser whether other laws need a longer period.

Is anything I tick on this page saved or sent to Mono?

No. Ticks stay in your browser tab and are lost when you close or refresh it. Use the CSV download to keep your progress in your own tracker. Mono does not see it.

Not sure where your gaps are? We will find them.

Sources: Digital Personal Data Protection Act, 2023 (sections 5 to 9, 11 to 14 and 16). Digital Personal Data Protection Rules, 2025, Rules 3, 6, 7, 8, 10, 14 and 15 (G.S.R. 846(E), Gazette of India, 13 November 2025; corrigendum G.S.R. 892(E), December 2025). CERT-In Directions, 28 April 2022. RBI circular RBI/2017-18/153, 6 April 2018. Last reviewed 20 November 2026. See also our DPDP compliance page.