Readiness assessment
The Act
The DPDP Act, explainedThe DPDP Rules 2025

Ch IPreliminary

S.1 Short title and commencementS.2 DefinitionsS.3 Application and scope

Ch IIObligations of Data Fiduciary

S.4 Grounds for processingS.5 NoticeS.6 ConsentS.7 Certain legitimate usesS.8 Data Fiduciary obligationsS.9 Children’s dataS.10 Significant Data Fiduciary

Ch IIIRights and duties of Data Principal

S.11 Right to accessS.12 Correction and erasureS.13 Grievance redressalS.14 Right to nominateS.15 Duties of the Data Principal

Ch IVSpecial provisions

S.16 Transfer outside IndiaS.17 Exemptions

Ch VData Protection Board of India

S.18 Establishment of the BoardS.19 Composition of the BoardS.20 Salary and term of officeS.21 DisqualificationsS.22 Resignation and vacanciesS.23 Proceedings of the BoardS.24 Officers and employeesS.25 Members as public servantsS.26 Powers of the Chairperson

Ch VIBoard powers and procedure

S.27 Powers and functions of the BoardS.28 Procedure followed by the Board

Ch VIIAppeal and dispute resolution

S.29 Appeal to the Appellate TribunalS.30 Tribunal orders as a decreeS.31 Alternate dispute resolutionS.32 Voluntary undertaking

Ch VIIIPenalties

S.33 Penalties and the ScheduleS.34 Penalties to Consolidated Fund

Ch IXMiscellaneous

S.35 Good-faith protectionS.36 Power to call for informationS.37 Blocking of accessS.38 Consistency with other lawsS.39 Bar of jurisdictionS.40 Power to make rulesS.41 Laying of rules before ParliamentS.42 Power to amend the ScheduleS.43 Power to remove difficultiesS.44 Amendments to other Acts
Industries
Implementation
Training
Resources
About
StoreReadiness assessment

DPDP Guide · Self-assessment

The Complete Guide to DPDP Compliance Self-Assessments in India: A Practical Framework for Startups and Small Businesses

How an Indian startup or small business can check its DPDP readiness with a structured method, an evidence test for every answer, and a clear view of what a questionnaire can and cannot prove.

In short

A DPDP compliance self-assessment is a structured internal review of how your business collects, uses, shares, stores and deletes personal data, measured against the duties in the Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025. It tells you where you stand and what to fix first.

It does not certify compliance, and most of the duties it tests begin on 13 May 2027.

Since 13 Nov 2025
Framework live
Definitions, the Data Protection Board framework and rule-making powers are in force.
From 13 May 2027
Main duties start
Notice, consent, security, breach intimation, retention, rights, children's data and penalties.
Status · as of 13 November 2026

The duties a self-assessment tests are not yet in force. They start on 13 May 2027 under G.S.R. 843(E) and Rule 1.

  • Date basis: the Gazette notifications are dated 13 November 2025. Some commentators compute the later dates as the 14th. We follow the Gazette date.
  • We found no official notification appointing the Chairperson or Members of the Data Protection Board.
  • We found no notification of any Significant Data Fiduciary, no section 17(3) exemption for startups, and no country restricted under section 16. These findings rest on our searches, not on an official statement.
  • A challenge to parts of the Act is before the Supreme Court. Press reports say no interim stay was granted on 27 October 2026 and the next hearing is listed for 17 November 2026.

DPDP readiness is a business issue before it is a legal one. The Act asks questions that only operations can answer: which forms collect data, which vendor holds it, who deletes it, who picks up the phone when something goes wrong. A privacy policy cannot answer these. A structured review can.

A bare checklist falls short for a simple reason. Ticking "we have a privacy notice" says nothing about whether the notice matches what your app collects. This guide therefore pairs every question with the evidence that should exist if the answer is yes.

You will learn how to decide whether the Act applies to you, which sixteen areas to assess, how to run the review in twelve steps, how to score it without fooling yourself, and how to rank the gaps. It is written for founders, CTOs, HR and operations leads, compliance officers and owners of Indian startups and small businesses. It is general information, not legal advice.

The self-assessment at a glance

Mind map: a DPDP compliance self-assessment covers sixteen domains in four groups, namely foundation, people-facing duties, protection, and third parties and scale DPDP self-assessment16 domains Foundation1 Scope and roles2 Data inventory and mapping3 Purpose and lawful grounds13 Governance and ownership15 Documentation and evidence16 Timeline readiness People-facing duties4 Notices and consent5 Data Principal rights11 Children's personal data12 Grievance management Protection6 Retention and erasure7 Breach preparedness8 Security safeguards Third parties and scale9 Vendors and Data Processors10 Employee and HR data14 Significant Data Fiduciary

What Is a DPDP Compliance Self-Assessment?

A DPDP compliance self-assessment is a review your own team carries out, using a fixed set of questions and an evidence check, to find where current practice differs from what the Act and Rules will require. The output is a gap list with owners and dates, not a certificate.

The term is often mixed up with other reviews. They differ in who does the work and what the result can be relied on for.

Seven kinds of DPDP review compared
ReviewWho does itWhat it producesWhat it does not do
Self-assessmentInternal teamReadiness picture and gap listGive independent assurance
Compliance gap assessmentInternal team or adviserRequirement-by-requirement gaps with a remediation planFix the gaps
Data mapping assessmentProcess owners with ITInventory of personal data and its flowsJudge legal sufficiency
Privacy auditIndependent reviewerTested findings against set criteriaDesign your controls
Legal compliance reviewQualified lawyerLegal opinion on applicability and interpretationTest technical controls
Technical security assessmentSecurity specialistFindings on safeguards and vulnerabilitiesCover notice, consent or rights
Formal independent assessmentIndependent data auditorData audit and Data Protection Impact AssessmentApply to everyone
The law

Only a Significant Data Fiduciary must appoint an independent data auditor and carry out a periodic Data Protection Impact Assessment and data audit, once in every twelve months (section 10(2), Rule 13). No provision requires every business to run a self-assessment.

Recommendation

Run one anyway. Section 8(4) will require technical and organisational measures that make compliance effective, and you cannot build those without knowing your gaps.

What it can establish
Which duties are likely to apply, where personal data sits, which controls exist, which are missing, and what to do next.
What it cannot establish
That you are compliant, that your reading of an unclear provision is correct, or that a control works under pressure. Those need evidence over time, and sometimes a lawyer or an independent reviewer.

Who Should Conduct a DPDP Self-Assessment?

Any organisation that decides why and how digital personal data is processed should run one. Size is not the test. A five-person firm with a customer database is a Data Fiduciary in the same way a large company is.

Who should assess, and what deserves extra attention
Business typeTypical personal dataWhat deserves extra attention
StartupsSign-up, usage, investor and employee dataOwnership: someone must be named
SaaS companiesCustomer account data; end-user data processed for customersWhether you act as Data Fiduciary, Data Processor or both
E-commerce businessesOrders, addresses, payment referencesMarketing consent; retention; the Third Schedule if registered users in India reach two crore
Digital service providersApp and device dataNotice at each collection point; SDKs
Small businesses with employee dataPayroll, attendance, ID documentsSection 7(i) limits; HR vendors
Businesses handling customer informationCRM, WhatsApp, spreadsheetsShadow copies and exports
HR and recruitment platformsCandidate profiles, background checksConsent for candidates; sharing with employers
Healthcare-related digital businessesAppointment, prescription and report dataSector rules apply alongside the Act; the Act itself has no separate "sensitive data" class
Businesses on third-party platforms and cloudAll of the above, held by vendorsContracts and vendor evidence

Four things change how deep the review must go:

  • the volume of data;
  • the kind of people it relates to, such as children, patients or borrowers;
  • how many vendors touch it;
  • which other laws apply.

Two businesses of the same size can have very different obligations. On healthcare: this guide covers the DPDP layer only, and clinical or sector regulations need their own review.

For role-specific starting points, see the pages for founders and HR teams, or your industry page.

How to Determine Whether the DPDP Act Applies to Your Business

The Act applies if you process digital personal data in India, or outside India in connection with offering goods or services to people in India (section 3). It does not depend on turnover, headcount or sector.

Applicability decision tree

Decision tree showing whether the DPDP Act applies to an Indian business and whether it acts as a Data Fiduciary or a Data Processor Do you handle data about identifiable individuals? Is it in digital form, or digitised after collection on paper? Is it processed in India, or outside India to offergoods or services to people in India? Is it only personal or domestic use by an individual,or data the person made public? Do you decide the purpose and means of processing? Data Processor for that activity: duties flow through your contract Outside the Act Outside the Act for that data Outside the Act Excluded: section 3(c) Data Fiduciary:all general duties apply NoNoNoYesYes YesYesYesNoNo

Read the tree with four points in mind.

  • Digital personal data. Paper records that are never digitised are outside the Act. A scanned form is inside it.
  • Exclusions are narrow. Section 3(c) excludes personal or domestic use by an individual, and data made public by the person or under a legal duty. Section 17 lists purpose-based exemptions, such as enforcing a legal right or processing by courts. Even where section 17(1) applies, sections 8(1) and 8(5) continue to apply.
  • There is no small-business exemption. Section 17(3) lets the Central Government notify classes of Data Fiduciaries, including startups, to whom sections 5, 8(3), 8(7), 10 and 11 would not apply. As of 13 November 2026, we found no such notification. Do not plan on one.
  • Roles are per activity. A SaaS company is a Data Fiduciary for its own customer and employee data and a Data Processor for the end-user data it handles for clients. Assess each role separately. See Data Fiduciary vs Data Processor.

What is in force today

The Act and Rules start in three phases under G.S.R. 843(E) and Rule 1.

DPDP Act and Rules: phased commencement
DateWhat startsWho it concerns
13 November 2025Definitions, the Data Protection Board framework, rule-making powersGovernment and the Board
13 November 2026Section 6(9), section 27(1)(d), Rule 4Entities seeking to register as Consent Managers
13 May 2027Notice, consent, legitimate uses, security, breach intimation, retention, rights, children's data, Significant Data Fiduciaries, penaltiesEvery Data Fiduciary and Data Processor

For a business that is not a Consent Manager, 13 November 2026 adds no new duty. The months to May 2027 are preparation time, and that is what a self-assessment is for. More detail is on our compliance timeline page and in what changes between 13 November 2026 and 13 May 2027.

The DPDP Compliance Self-Assessment Framework

The framework has sixteen domains. Each one states what it covers and why it matters, then gives questions to ask, evidence to inspect, common gaps, corrective actions, a priority with its reason, and the provisions behind it.

How to read your answers

A "yes" counts only if you can show the evidence listed. "Yes, but nothing is written down" is a partial. "We think the vendor does that" is not assessed. "Not applicable" needs a one-line reason. Priorities are recommendations for a typical small business, not statutory ranks. All section and rule references are to provisions that start on 13 May 2027 unless stated.

1Applicability and organisational scopeImmediate

This fixes which entities, products and roles the review covers. Without it, every later answer is a guess.

Ask
Which legal entities process digital personal data? For each activity, do we decide the purpose and means, or act for someone else? Do we serve people in India from outside India? Does any section 17 exemption apply to a specific purpose?
Inspect
Entity list, product list, customer contracts that describe your role.
Common gaps
Treating the whole company as "only a processor"; assuming a startup exemption exists.
Fix
Write a one-page scope note with roles per activity.
Priority
Immediate. Everything else depends on it.
Law
Sections 2(i), 2(k), 3, 17.

2Personal data inventory and data mappingImmediate

A record of what personal data you hold, about whom, why, where, and who receives it. Our reading: the Act does not name data mapping as a duty, but notice, erasure, rights and breach duties cannot be met without it.

Ask
Can we list every point where personal data enters the business? Every system and vendor that stores it? Is there an owner for each process?
Inspect
Inventory sheet, system list, vendor list, form and API field lists.
Common gaps
Spreadsheets and exports left out; marketing and support tools forgotten.
Fix
Build the inventory process by process. See the data mapping guide.
Priority
Immediate. It feeds eight other domains.
Law
Supports sections 5, 6(10), 8(1), 8(4), 8(7), 11 and 12.

3Purpose identification and lawful processingNear term

Personal data may be processed only for a lawful purpose, on one of two grounds: the person's consent, or one of the "certain legitimate uses" listed in section 7. There is no open-ended business-interest ground in the Act.

Ask
For each purpose in the inventory, is the ground consent or a named clause of section 7? Is any purpose running with no ground recorded?
Inspect
Purpose column in the inventory, with the ground and clause noted.
Common gaps
Marketing treated as covered by a contract; section 7(a) stretched to purposes the person never had in mind.
Fix
Record a ground per purpose; stop or re-base purposes with none. See consent vs certain legitimate uses.
Priority
Near term. It decides where you need notices and consent.
Law
Sections 4, 6, 7.

4Consent management and noticesNear term

Where you rely on consent, a notice must accompany or precede the request, and the consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action. Withdrawal must be as easy as giving it. The Data Fiduciary carries the burden of proving that notice was given and consent obtained.

Ask
Does every consent point show an itemised notice of the data and the purpose? Can a person withdraw as easily as they agreed? Can we produce the consent record for a named user? Have we planned notices for people who consented before commencement?
Inspect
Screenshots of live forms, notice text, consent logs with timestamp and notice version, withdrawal flow.
Common gaps
Pre-ticked boxes; one bundled consent for several purposes; no record of which notice version was shown.
Fix
Redesign consent points, version notices, log consent events. See the consent management guide.
Priority
Near term. Design and engineering work takes time.
Law
Sections 5, 6(1) to (6), 6(10); Rule 3.

5Data Principal rights handlingNear term

People will be able to ask for a summary of their data and how it is processed, for correction, completion, updating and erasure, and to nominate someone to act for them on death or incapacity.

Ask
Is there a published way to make a request? Who receives it? Can we find all of a person's data across systems? How do we confirm identity?
Inspect
Request channel on the website or app, request register, a test request run end to end.
Common gaps
No single intake point; data found in the main database but not in vendor tools.
Fix
Publish the channel and identifiers required, keep a register, rehearse one request.
Priority
Near term.
Law
Sections 11, 12, 14; Rule 14(1).

6Data retention and erasureNear term

Personal data must be erased when consent is withdrawn or when it is reasonable to assume the purpose is no longer being served, whichever is earlier, unless a law requires retention. Processors must erase too.

Ask
Is there a retention period for each data set, with its reason? Does deletion actually run? Do backups and vendors follow it? Do we hold logs and data for the one-year minimum the Rules set?
Inspect
Retention schedule, deletion job logs, vendor deletion confirmations.
Common gaps
"Keep everything" by default; deletion in the app but not in the CRM or backups.
Fix
Set periods per data set, automate deletion, record exceptions required by other laws. See retention and erasure mapping.
Priority
Near term. The fixed three-year rule and 48-hour prior notice in the Third Schedule apply only to e-commerce and social media entities with two crore registered users in India and online gaming intermediaries with fifty lakh.
Law
Sections 8(7), 8(8); Rules 6(1)(e), 8; Third Schedule.

7Personal data breach preparednessImmediate

On a personal data breach, the Data Fiduciary must inform the Board and each affected Data Principal. This domain tests whether you could do that in practice. It has its own section below.

Ask
Would we know a breach happened? Who decides it is a breach? Who drafts and sends the intimations?
Inspect
Incident response plan, escalation contacts, incident log, draft templates.
Common gaps
A security incident plan with no step for telling affected people.
Fix
Add DPDP steps to the incident plan and rehearse once.
Priority
Immediate to prepare. It carries the second-highest penalty ceiling in the Schedule, up to Rs 200 crore.
Law
Section 8(6); Rule 7.

8Technical and organisational security safeguardsImmediate

A Data Fiduciary must protect personal data in its possession or control, including data held by its processors, with reasonable security safeguards. Rule 6 sets a minimum list.

Ask
Is personal data encrypted, masked or tokenised where appropriate? Is access controlled and reviewed? Are logs kept and looked at? Are there backups? Are logs retained for one year?
Inspect
Access lists, encryption settings, log retention settings, backup restore test, security terms in vendor contracts.
Common gaps
Shared admin logins; logs kept for thirty days; no restore test.
Fix
Close the Rule 6 minimums first, then wider hardening.
Priority
Immediate. This duty has the highest penalty ceiling, up to Rs 250 crore, and survives the section 17(1) exemptions.
Law
Sections 8(4), 8(5); Rule 6(1)(a) to (g).

9Vendor and Data Processor risk managementNear term

A Data Fiduciary stays responsible for processing done on its behalf and may engage a Data Processor only under a valid contract. This domain also has its own section below.

Ask
Which vendors touch personal data? Is there a contract with each? Does it cover security, breach reporting to us, deletion and sub-processing?
Inspect
Vendor register, signed agreements, vendor security evidence.
Common gaps
Click-through terms never read; no duty on the vendor to tell you about a breach.
Fix
Tier vendors by risk and close contract gaps for the top tier first.
Priority
Near term.
Law
Sections 8(1), 8(2), 8(7); Rule 6(1)(f).

10Employee and HR data handlingNear term

Section 7(i) permits processing for the purposes of employment, and to safeguard the employer from loss or liability. It is not a blanket permission for everything HR does.

Ask
Which HR processing is for employment purposes, and which is optional (wellness apps, photos for marketing, referrals)? What do we keep after an employee or candidate leaves?
Inspect
HRMS field list, background check vendor terms, candidate data retention.
Common gaps
Rejected candidates' data kept for years; monitoring tools with no stated purpose.
Fix
Split HR purposes by ground; set candidate and ex-employee retention. See section 7(i) and employee data.
Priority
Near term.
Law
Sections 7(i), 8.

11Children's personal data, where applicableIf applicable

A child is anyone under eighteen. Processing a child's data needs verifiable consent of the parent, and tracking, behavioural monitoring and targeted advertising directed at children are barred, subject to the exemptions in Rule 12 and the Fourth Schedule.

Ask
Could under-18s use our product? How would we know? If yes, how is parental consent verified?
Inspect
Age signals at sign-up, parental consent flow, ad and analytics settings.
Common gaps
"Our terms say 18+" with no check on reality.
Fix
Decide whether children are in scope; if so, take legal advice on the verification design.
Priority
Immediate if children are users (penalty ceiling up to Rs 200 crore); otherwise record "not applicable" with the reason.
Law
Section 9; Rules 10 to 12; Fourth Schedule.

12Grievance managementNear term

Every Data Fiduciary must run a grievance mechanism and publish the period within which it will respond, which may not exceed ninety days. A person must use this route before going to the Board.

Ask
Where does a complaint go? Is the response period published? Is each complaint tracked to closure?
Inspect
Published contact details, grievance register, sample closed complaint.
Common gaps
A generic support inbox with no tracking.
Fix
Name a person, publish the contact and response period, keep a register.
Priority
Near term; low effort.
Law
Sections 8(9), 8(10), 13; Rules 9, 14(3).

13Governance, accountability and ownershipImmediate

Someone must own the programme. The Act requires every Data Fiduciary to publish the contact of a person who can answer questions about processing. A Data Protection Officer is required only for a Significant Data Fiduciary.

Ask
Who is accountable at leadership level? Who runs it day to day? Is privacy on any management agenda?
Inspect
Named owner, role description, meeting notes, training records.
Common gaps
Ownership assumed to sit with "legal" or "IT" with nobody named.
Fix
Name an owner and a deputy; set a quarterly review.
Priority
Immediate. Unowned gaps do not close.
Law
Sections 8(1), 8(4), 8(9); section 10(2)(a) for Significant Data Fiduciaries.

14Significant Data Fiduciary applicabilityLater

The Central Government may notify a Data Fiduciary or a class as a Significant Data Fiduciary, weighing factors such as the volume and sensitivity of data and the risk to Data Principals. As of 13 November 2026, we found no such notification. See who may be a Significant Data Fiduciary.

Ask
Do our volumes or data types make designation plausible in future?
Inspect
User counts, data categories, sector.
Common gaps
Small firms spending on DPO and audit duties that do not apply to them; large platforms assuming they will not be notified.
Fix
Record a short view; revisit when a notification is issued.
Priority
Later, unless you operate at very large scale.
Law
Section 10; Rule 13.

15Documentation and evidence managementImmediate

Evidence is what turns a claim into something you can show a customer, an investor or the Board. Recommendation: keep one folder per domain.

Ask
For every "yes" above, where is the proof, and is it dated?
Inspect
Evidence index with owner and date for each item.
Common gaps
Policies approved but never applied; screenshots with no date.
Fix
Create the index during the assessment, not after.
Priority
Immediate, alongside step 7 of the workflow.
Law
Section 6(10) on proof of notice and consent; Rule 6(1)(c) and (e) on logs. Beyond these, evidence keeping is good practice.

16Implementation timeline readinessImmediate

This checks that your plan fits the commencement dates and that nothing is treated as already enforceable when it is not.

Ask
Does the plan end before 13 May 2027 with time to test? Who watches for new notifications?
Inspect
Dated plan, a named person tracking official updates.
Common gaps
Plans built on the draft Rules; panic over dates that do not apply.
Fix
Re-base the plan on G.S.R. 843(E) and Rule 1. See the 2027 compliance roadmap.
Priority
Immediate; one hour of work.
Law
G.S.R. 843(E); Rule 1(2) to (4).

How to Conduct a DPDP Compliance Self-Assessment Step by Step

A first assessment for a small business usually fits in two to four weeks of part-time effort. That estimate is a planning suggestion, not a legal period. The twelve steps run in order; steps 3 and 4 take the longest.

  1. Define the scope
  2. Identify processes and data owners
  3. Identify the personal data
  4. Map collection, use, storage, sharing and deletion
  5. Review applicable obligations
  6. Assess policies, processes and controls
  7. Collect and review evidence
  8. Identify and classify gaps
  9. Prioritise remediation
  10. Assign responsibility and deadlines
  11. Validate implementation
  12. Schedule reassessment
Twelve steps: action, owner, output and an example
StepActionResponsible roleExpected outputExample
1. Define the scopeList entities, products, locations and roles coveredFounder or COOOne-page scope noteA Pune logistics startup covers its driver app, customer portal and payroll, and leaves out a dormant subsidiary
2. Identify processes and data ownersName each business process and one ownerProgramme ownerProcess list with ownersSales lead owns "lead capture"; HR manager owns "hiring"
3. Identify the personal dataFor each process, list data fields and whose data it isProcess ownersDraft inventoryA Jaipur D2C brand finds it stores delivery addresses in four tools
4. Map collection, use, storage, sharing, deletionTrace each data set from entry to erasureProcess owners with ITData mapSupport tickets flow from web form to helpdesk tool to an outsourced team in Indore
5. Review applicable obligationsMark which of the sixteen domains apply and whyCompliance or legal leadApplicability sheetChildren's data marked not applicable for a B2B invoicing tool, with the reason
6. Assess policies, processes, controlsAnswer the questions for each domainProgramme owner with process ownersCompleted questionnaire"Withdrawal of consent" answered as partial: possible by email only
7. Collect and review evidenceAttach proof to every "yes" and "partial"Process ownersEvidence indexScreenshot of the consent screen, dated, with notice version
8. Identify and classify gapsTurn each "no", "partial" and "not assessed" into a gap statementProgramme ownerGap register"No contract clause requires our CRM vendor to report breaches to us"
9. Prioritise remediationRank gaps using the prioritisation method in this guideLeadershipRanked planSecurity logging ranked above cookie banner redesign
10. Assign responsibility and deadlinesGive each gap one owner and one dateLeadershipAction trackerCTO, log retention to one year, by 31 January
11. Validate implementationRe-test the control and file new evidenceSomeone other than the fixerClosure noteHR confirms deletion of rejected candidates' data by sampling ten records
12. Schedule reassessmentFix the next review date and the events that trigger an earlier reviewProgramme ownerCalendar entryReview every six months and on any new product, vendor or official notification

How to Assess Data Mapping Gaps

Data mapping is the exercise of recording what personal data you hold, where it came from, where it goes and when it is deleted. It is foundational because nearly every duty in the Act assumes you already know this. A data mapping gap assessment asks one question: what does the map miss?

  • Find collection points. Walk through each way data arrives: website and app forms, sign-up flows, payment pages, chat widgets, WhatsApp and phone calls logged by staff, CSV uploads from partners, HR forms, CCTV and visitor registers that are digitised.
  • Find systems and vendors. List production databases, analytics tools, CRM, helpdesk, email and SMS platforms, HRMS, payroll, cloud storage, shared drives and personal laptops. Finance is a good cross-check: every paid SaaS subscription is a possible data store.
  • Map the flows. For each data set, note the route from collection to storage to sharing to deletion. Mark every hop to another company and every hop outside India.
  • Hunt for undocumented processing. Ask each team three questions: what do you export, what do you paste into other tools, and what did the last person in your role set up that nobody maintains? Browser extensions, free-tier tools and old integrations are the usual finds.
  • Check retention and deletion. For each row, ask whether a period exists, whether deletion runs, and whether backups and vendors follow.

The table below is illustrative. The business and its data are fictional.

Sample data mapping table (illustrative)
Business processPersonal dataData PrincipalPurposeCollection sourceStorage systemData sharingRetentionOwnerGap identified
Customer onboardingName, email, phone, companyCustomer userCreate and run the accountSign-up formApplication databaseCloud hostLife of account plus 1 yearProduct leadNo deletion on account closure
Lead captureName, email, phoneProspectSales follow-upWebsite form, eventsCRMEmail platformNot setSales leadNo notice at event collection; no period
SupportName, email, ticket contentCustomer userResolve queriesHelpdesk widgetHelpdesk toolOutsourced support firm3 yearsSupport leadContract silent on breach reporting
HiringCV, ID proof, referencesCandidateAssess for a roleCareers page, emailHRMS, recruiter inboxesBackground check vendorNot setHR managerCVs sit in personal inboxes
PayrollBank details, PAN, salaryEmployeePay salary, meet tax lawHR formPayroll softwareBank, accountantAs tax law requiresFinance leadPeriod not documented

A full method is in how to conduct a data mapping exercise, and is data mapping mandatory covers what the law does and does not say. All mapping guides and worksheets are listed in the data mapping collection.

How to Assess Personal Data Breach Readiness

Breach readiness means you can detect a personal data breach, decide quickly what happened, and tell the right people in the form the Rules set. Assess it by walking one imagined incident through your organisation and noting every point where someone says "I am not sure who does that".

Who must be told, under which law

Flow diagram: after a personal data breach, DPDP Rule 7 requires intimation to affected Data Principals and to the Data Protection Board, while CERT-In reporting within six hours is a separate requirement under the Information Technology Act You become awareof a breach Affected Data PrincipalsInform without delay. DPDP Rule 7(1). Data Protection BoardWithout delay, then a detailed report within 72 hours. Rule 7(2). Separate law: CERT-InSpecified cyber incidents within 6 hours. IT Act, section 70B(6).
The law · from 13 May 2027 (section 8(6), Rule 7)

On becoming aware of a personal data breach, a Data Fiduciary must:

  • inform each affected Data Principal without delay, in a concise and clear manner, through the user account or a registered mode of communication, covering the nature, extent and timing of the breach, likely consequences, mitigation measures, safety steps the person can take, and a contact who can answer questions;
  • inform the Board without delay, with a description of the breach including its nature, extent, timing, location and likely impact;
  • give the Board a detailed report within seventy-two hours of becoming aware, or a longer period the Board allows on a written request, covering updated facts, the events and causes, mitigation, findings about who caused it, steps to prevent recurrence, and a report on the intimations given to Data Principals.

So the Rules set two steps for the Board (first intimation, then a detailed report) and a separate "without delay" duty to affected people. Reading this as one flat 72-hour deadline is a mistake. As of 13 November 2026, we found no official notification appointing the Board's Chairperson or Members, and no published reporting form or portal.

Separate regime · CERT-In

The CERT-In Directions of 28 April 2022, issued under section 70B(6) of the Information Technology Act, 2000, require specified cyber incidents to be reported to CERT-In within six hours of noticing them. These Directions are in force now, cover cyber incidents whether or not personal data is involved, and are independent of the DPDP Act. One incident can trigger both. Sector regulators may add their own reporting rules.

Breach readiness checklist

  • Detection: alerts exist for unusual access, large exports and failed logins, and someone reviews them
  • Reporting channel: every employee and vendor knows where to report a suspected incident, at any hour
  • Escalation: a written path from first report to a decision-maker, with phone numbers
  • Ownership: a named incident lead and a deputy
  • Assessment: a short test for "is this a personal data breach, and whose data"
  • Containment: authority to disable accounts, rotate keys and take systems offline
  • Data map: you can tell within hours which people are affected and how to reach them
  • Templates: draft intimations for Data Principals and for the Board, matching the Rule 7 items
  • CERT-In: a decision step for whether the incident is reportable there, and by whom
  • Vendors: contracts require processors to tell you promptly; contacts are current
  • Documentation: an incident log with times, decisions and evidence
  • Review: a post-incident review that feeds fixes into the plan
Sample tabletop scenario · fictional

At 9 pm on a Friday, a support agent at your outsourced helpdesk vendor reports that a former colleague's login was used to export 4,000 customer tickets, including names, phone numbers and some order details. Ask the team: Who is told first? Who can disable the account tonight? Is this a personal data breach? Which customers are affected and can we contact them? Who drafts the messages? Is CERT-In reporting triggered? What does the vendor contract oblige the vendor to give us? Record each answer, the time it took to reach it, and every "not sure". Those are your gaps.

The reporting procedure itself is in our breach guide, with a worksheet for this exercise.
How to report a personal data breach → Breach readiness worksheet →

How to Conduct a Vendor Risk Assessment Under the DPDP Framework

A DPDP vendor risk assessment checks whether the companies that process personal data for you let you meet your own duties. The Data Fiduciary remains answerable for its Data Processors (section 8(1)) and needs a valid contract with each (section 8(2)).

Identify the vendors. Start from the data map and the payments ledger. Typical categories: cloud hosting, CRM, HRMS and payroll, marketing automation and email, analytics, payment service providers, outsourced customer support, background verification, and consultants with system access.

Decide the relationship. A vendor that processes data only on your instructions is your Data Processor. A vendor that decides its own purposes for the data, as many payment and advertising platforms do for part of what they handle, may be a Data Fiduciary in its own right. Our reading: the label in the contract does not settle this; what the vendor does with the data does. Where it is unclear, take advice.

Assess in proportion. Not every vendor needs the same scrutiny. Tier them by the data they hold and the harm if it leaked, then match the depth of review to the tier.

Vendor risk assessment matrix (tiers and cycles are recommendations, not legal requirements)
FactorTier 1: highTier 2: mediumTier 3: low
Data handledLarge volumes, or financial, health, children's or identity dataContact and account dataMinimal or incidental personal data
ExamplesCloud host, HRMS and payroll, outsourced support, payment processorCRM, email platform, analyticsScheduling tool, design tool
ContractNegotiated or reviewed data processing termsStandard terms read and filedStandard terms filed
Security evidenceIndependent report or certificate, plus answers to a questionnairePublished security documentationNone beyond terms
Breach escalationNamed contact, tested; duty to tell you promptlyDuty to tell you in termsStandard terms
Deletion on exitWritten confirmationDocumented processAccount closure
Sub-processorsList reviewed; change noticesList availableNot reviewed
Review cycleYearly, and on any incidentEvery two yearsOn renewal

Contract points to check:

  • processing only on your instructions;
  • security measures (Rule 6(1)(f) calls for appropriate provisions in the contract);
  • prompt notice of any breach so you can meet Rule 7;
  • deletion or return of data at the end, and on your instruction when a person withdraws consent (section 8(7));
  • sub-processing only with your knowledge;
  • cooperation with rights requests;
  • location of processing.

Review vendor evidence, not vendor promises. Ask for the document: the security report, the sub-processor list, the deletion confirmation. With large cloud providers you will rarely negotiate terms. The assessment then becomes: read the standard terms, configure the service securely, and record that you did.

The data flow and processor mapping guide and its worksheet help build the vendor register.

How to Assess Readiness for Different Business Functions

Each function sees a different slice of personal data, so give each its own short set of questions.

DPDP readiness questions by business function
FunctionTypical processingQuestions to askPotential gapsNext action
HR and recruitmentCVs, ID documents, payroll, attendance, background checksWhich processing is for employment purposes under section 7(i)? What happens to rejected candidates' data?CVs kept indefinitely; ID copies on shared drivesSet candidate retention; restrict HR folder access
Sales and marketingLeads, event lists, email campaigns, tracking pixelsWhere did each list come from? Is there consent for marketing? Can a person opt out easily?Purchased lists; one consent for everythingTag lead source and consent in the CRM; add withdrawal links
Customer supportTickets, call recordings, chat logsWho can see tickets? Does the outsourced team have a contract and access limits?Shared logins; recordings kept foreverIndividual logins; retention for recordings
Finance and paymentsBank details, invoices, payment referencesWhich records does tax or company law require us to keep, and for how long?Legal retention used as a reason to keep unrelated dataDocument statutory periods per record type
IT and cybersecurityLogs, backups, access rights, device dataDo we meet each Rule 6 minimum? Are logs kept one year?No log review; no restore testClose Rule 6 minimums; schedule a restore test
Product and engineeringSign-up flows, analytics, SDKs, test dataDoes each new feature get a privacy check? Is production data used in testing?Third-party SDKs sending data nobody listedAdd a privacy step to release; mask test data
Leadership and governanceOversight, budget, risk decisionsWho owns this? What is reviewed, and how often?No named owner; no budget lineAppoint an owner; quarterly review

DPDP Self-Assessment Scoring Methodology

Score to see progress and to rank work, not to award yourself a result. Use five response options and define them before you start.

Response options and points
ResponseMeaningPoints
Implemented and supported by evidenceControl operates and dated proof exists2
Partially implementedControl exists in part, or exists without proof1
Not implementedNo control0
Not assessedNobody has checked0, and counted separately
Not applicable, with justificationDomain or question does not apply, reason recordedExcluded
Why one percentage misleads

A total of 78 per cent can hide an unencrypted customer database behind a row of well-kept policies. Averages treat a missing breach process and a missing training record as equal. "Not assessed" answers inflate or deflate the figure depending on how you count them. And a high score invites the word "compliant", which no questionnaire can support.

Report three things per domain instead: the maturity level, the number of open high-priority gaps, and the share of questions not yet assessed.

Five maturity levels

Staircase chart of five maturity levels for DPDP self-assessment scoring, from level 0 not assessed to level 4 controls evidenced and periodically reviewed Level 0Level 1Level 2Level 3Level 4 Not assessedInitial awarenessProcesses documentedControls implementedEvidenced andreviewed A domain sits at the highest level that every applicable question meets.
Maturity levels defined
LevelNameDefinition
0Not assessedThe domain has not been reviewed
1Initial awarenessThe team knows the requirement; little is in place
2Basic processes documentedPolicies or procedures are written but not consistently followed
3Controls implementedControls operate in day-to-day work
4Controls evidenced and periodically reviewedDated evidence exists and someone re-tests on a schedule

One weak answer holds the domain down, which is the point.

Sample scoring table (illustrative)
DomainApplicable questionsEvidence-backedPartialNot implementedNot assessedMaturityOpen high-priority gaps
Security safeguards8332012
Breach preparedness6023113
Consent and notices7241011
Vendor management6121212
Grievance management4310020

Sample interpretation. This business has started on security and consent but has almost nothing ready for a breach, and a third of its vendor questions are unanswered. The next month should go to breach preparedness and finishing the vendor review, not to polishing grievance handling. Nothing in this table says the business is, or is not, compliant with the Act.

How to Prioritise DPDP Compliance Gaps

Rank each gap on a few practical factors, then sort it into one of four buckets.

Factors for ranking a gap
FactorQuestion to ask
Legal applicabilityDoes the duty apply to us at all, in our role?
Nature of the requirementIs it a named duty in the Act or Rules, or good practice?
Data sensitivity and contextWhose data is it: children, patients, borrowers, employees?
Impact on Data PrincipalsWhat happens to people if this fails?
Likelihood of failureHas it nearly failed before? Does it depend on one person?
Existing controlsIs something already reducing the risk?
Implementation effortDays, weeks or months? Does it need a vendor or engineering release?
Commencement dateWhen does the underlying provision start?
1. Immediate foundational actions
Work that other work depends on, and protections worth having regardless of the Act. Name an owner; build the data inventory; close basic security gaps; set up incident escalation.
2. Near-term preparation
Duties that start on 13 May 2027 and need design, engineering or negotiation. Notices and consent flows; rights request process; vendor contract changes; retention schedule.
3. Later phased requirements
Duties that depend on something not yet in place or not applicable to you today. Significant Data Fiduciary duties if ever notified; integration with registered Consent Managers; any transfer restriction notified under section 16.
4. Context-dependent improvements
Useful, but driven by your sector, customers or contracts. Certifications a customer asks for; privacy tooling; advanced monitoring.

Two cautions. Long-lead items belong early even though their provision starts later, because a consent redesign cannot be done in the last fortnight. And any internal deadline you set is your own project date. The only dates the law gives are the commencement dates.

DPDP Compliance Self-Assessment Tools

Seven kinds of tool can support the work. Most small businesses start with the first three. No product names or prices are given here, because features change and should be checked with each provider.

Small business compliance tools for a DPDP self-assessment, compared
Tool categoryIdeal userBenefitsLimitationsUse it whenNot enough when
Manual spreadsheet checklistSmall teams with simple data flowsFree, flexible, easy to shareNo evidence store; goes staleYou are starting outMany systems, vendors or products
Online readiness questionnaireFounders wanting a quick first viewFast; highlights weak areasSelf-reported; no evidence checkYou need to know where to look firstYou need a remediation plan
Data mapping workbookProcess owners and ITBuilds the inventory other domains needManual upkeepBefore notices, retention or rights workData changes weekly across many systems
Breach preparedness assessmentIT, security and operations leadsTests people and process, not paperCovers one domainYou have an incident plan to test, or none at allYou need technical security testing
Vendor risk assessment questionnaireProcurement, IT, legalConsistent vendor evidenceVendors may answer looselyYou have more than a handful of processorsLarge vendors will not fill it in; read their terms instead
Privacy management softwareLarger or fast-growing teamsAutomates inventory, requests and recordsCost; setup effort; still needs correct inputsManual tracking is failingYou have not yet mapped your data
External expert assessmentBusinesses with complex or high-risk processingIndependent view; legal interpretationCost; depends on the adviser's qualityThe triggers in the expert help section applyNever a substitute for internal ownership

On this site, the free readiness assessment is an online questionnaire of the second kind, and the worksheets under downloads are of the third and fourth kinds. Both are starting points and neither certifies anything. All tools are listed on the DPDP Act tools page.

Common Mistakes Businesses Make During DPDP Self-Assessments

  1. Treating a checklist as proof of compliance. A completed list shows what you believe, not what is true.
  2. Assuming all organisations have the same obligations. Children's data, Third Schedule retention and Significant Data Fiduciary duties apply only to some.
  3. Ignoring Data Processors and vendors. You remain responsible for what they do with your data.
  4. Failing to identify all data flows. Exports, inboxes and free tools are where surprises sit.
  5. Creating policies without implementing controls. A retention policy with no deletion job is a gap, not a control.
  6. Ignoring evidence. If you cannot show it, score it as partial.
  7. Overlooking retention and deletion. Collection gets attention; erasure rarely does.
  8. Confusing cybersecurity compliance with DPDP compliance. An ISO 27001 certificate covers security management. It does not cover notice, consent, rights or erasure. See DPDP Act vs ISO 27001.
  9. Ignoring phased commencement. Some teams panic over duties not yet in force; others assume nothing matters until 2027 and leave no time to build.
  10. Treating a one-time assessment as permanent readiness. New products, vendors and notifications change the picture.
  11. Assuming a small business is automatically exempt. No such exemption has been notified, as far as we found on 13 November 2026.
  12. Using GDPR terminology or assumptions incorrectly. The DPDP Act has consent and certain legitimate uses, not six lawful bases. It has no "legitimate interests" ground, no "controller" or "data subject", and no separate class of sensitive data. See DPDP Act vs GDPR.

Practical DPDP Self-Assessment Example

Fictional scenario

This example does not describe a real company, client or result. It shows how the method plays out.

"LedgerLeaf" is a Bengaluru SaaS startup with 25 employees. It sells invoicing software to small traders. It runs customer onboarding through its web app, a CRM for sales, a cloud-hosted application, an HRMS, a third-party customer support firm and a marketing email platform.

Scope and roles. LedgerLeaf is a Data Fiduciary for its customers' account users, its leads and its employees. It is a Data Processor for the buyer details its customers enter on invoices. Children's data is marked not applicable: the product is sold to businesses and collects no age-linked data. Significant Data Fiduciary duties are marked not applicable today.

Initial gaps and assessment findings (fictional)
DomainFindingEvidence seenPriority
GovernanceNo named owner; the CTO "looks after privacy" informallyNoneImmediate
Data inventoryNothing written; engineers know the database, nobody knows the CRM exportsDatabase schema onlyImmediate
SecurityEncryption at rest on; three shared admin accounts; logs kept 30 daysCloud console settingsImmediate
Breach preparednessOn-call rota exists; no step for telling customers or the BoardRota documentImmediate
VendorsSupport firm works on a one-page service agreement with no data termsAgreementNear term
Consent and noticesSign-up shows one "I agree" covering service and marketingScreenshotNear term
RetentionClosed accounts never deleted; CVs kept since 2022Database queryNear term
Rights and grievanceRequests go to the support inbox; no register or published periodInbox searchNear term
Processor roleCustomer contracts say little about LedgerLeaf's duties as processorStandard termsNear term

Risk prioritisation. Leadership ranked shared admin accounts, log retention and the missing breach process first: they protect customers now and take days, not months. The data inventory ran in parallel because consent, retention and rights work depend on it. Consent redesign was scheduled next because it needs a product release.

Remediation actions and evidence collected (fictional)
ActionOwnerEvidence filed
COO named programme owner; quarterly review setCEOMinuted decision
Inventory of 14 processes and 11 vendors builtCOO with process ownersInventory workbook
Individual admin logins with multi-factor sign-in; logs kept one yearCTOAccess list; log setting screenshot
Incident plan extended with Rule 7 and CERT-In decision steps; one tabletop runCTOPlan; tabletop notes
Data terms added to the support firm contractCOOSigned addendum
Sign-up split into service notice and separate marketing consent; consent events loggedProduct leadScreenshots; sample log
Deletion job for closed accounts; candidate data deleted after 12 monthsCTO, HRJob log; HR sample check
Request and grievance channel published with a response periodSupport leadWeb page; register

Reassessment. Three months later, the team re-scored. Security moved from level 1 to level 3, breach preparedness from 1 to 2, vendors from 1 to 2. Two gaps stayed open: legacy marketing contacts with no consent record, and standard cloud terms the team had not yet read in full. LedgerLeaf recorded both, set dates, and booked a legal review of its processor terms. It did not describe itself as compliant.

DPDP Compliance Self-Assessment Checklist

Copy this table into a spreadsheet and fill the last five columns. It is a starting point drawn from the sixteen domains. It does not replace a complete compliance review.

DPDP compliance self-assessment checklist
Assessment domainQuestionEvidenceStatusGapOwnerPriorityDue date
1. ScopeHave we listed entities, products and our role for each activity?Scope note
1. ScopeHave we checked section 3 exclusions and section 17 exemptions?Applicability sheet
2. InventoryIs every collection point, system and vendor listed with an owner?Data inventory
3. PurposeDoes each purpose have consent or a named section 7 clause?Purpose and ground column
4. NoticeDoes each consent point show itemised data and purpose, and how to withdraw and complain?Screenshots; notice text
4. ConsentIs consent a clear affirmative action, separate per purpose?Screenshots
4. ConsentCan we produce a consent record for a named person?Consent log sample
4. ConsentIs withdrawal as easy as giving consent?Withdrawal flow test
5. RightsIs the request channel published, with identifiers needed?Web or app page
5. RightsCan we find and correct or erase a person's data across systems?Test request record
6. RetentionDoes each data set have a period and a reason?Retention schedule
6. RetentionDoes deletion run in systems, backups and vendors?Deletion logs
7. BreachIs there an incident plan with steps for the Board and affected people?Incident plan; templates
7. BreachHave we run a tabletop exercise?Exercise notes
8. SecurityAre the Rule 6 minimums in place (encryption or masking, access control, logs, backups)?Settings; access list
8. SecurityAre logs retained for one year?Log retention setting
9. VendorsIs there a register of vendors that process personal data, tiered by risk?Vendor register
9. VendorsDo contracts cover security, breach notice, deletion and sub-processing?Signed terms
10. HR dataAre HR purposes split between employment purposes and optional ones?HR data sheet
10. HR dataIs candidate and ex-employee data deleted on schedule?HR deletion record
11. ChildrenHave we decided whether under-18s use our service, with reasons?Decision note
12. GrievanceAre a contact and a response period (not over 90 days) published?Web or app page
12. GrievanceIs each grievance tracked to closure?Grievance register
13. GovernanceIs there a named owner and a review rhythm?Decision record; minutes
13. GovernanceHave relevant staff been trained?Training record
14. SDFHave we recorded a view on Significant Data Fiduciary designation?Short note
15. EvidenceIs there an evidence index with dates and owners?Index
16. TimelineDoes the plan finish before 13 May 2027 with time to test?Dated plan
16. TimelineIs someone tracking official notifications?Named person

A longer list is in the DPDP Act compliance checklist, and the free Starter Kit includes a readiness checklist and a twelve-month calendar.

Want a first view in a few minutes?

The free readiness assessment asks about scope, notice, consent, security, breach, retention and vendors, and shows your weakest areas. It is a starting point, not a certificate.

When Should a Business Seek Expert Help?

Many small businesses can run a first self-assessment unaided. Outside help earns its cost when one of these applies:

  • Complex processing: several products, entities or data-sharing arrangements.
  • Unclear applicability: you cannot tell whether you are a Data Fiduciary or a Data Processor for a key activity, or whether an exemption applies.
  • Significant Data Fiduciary concerns: very large user bases or data that could affect many people.
  • Children's data: verifiable parental consent and the tracking bar need careful design.
  • High-volume or complex data flows: many integrations, data brokers or analytics partners.
  • Cross-border processing: especially where sector rules, such as those for payments or insurance, add their own limits. See cross-border data transfer.
  • Significant vendor exposure: critical processors that will not accept your terms.
  • Serious security or breach concerns: a recent incident, or gaps you cannot close internally.
  • Uncertain interpretation: any point this guide marks as "our reading".
  • No internal owner or expertise: nobody has the time or background to run the review.

If none of these applies, start on your own and decide after the first pass. A lawyer is the right person for legal interpretation, a security specialist for technical testing. A self-assessment makes either engagement shorter, because you arrive with a data map and a gap list. If you want the review run with you, see a guided gap assessment.

DPDP compliance self-assessment: frequently asked questions

What is a DPDP compliance self-assessment?

It is an internal, structured review of how your business handles personal data against the duties in the DPDP Act, 2023 and the DPDP Rules, 2025. It produces a gap list with owners and dates.

Is a DPDP self-assessment mandatory for every business?

No. Neither the Act nor the Rules require every business to run one. Only Significant Data Fiduciaries must carry out a yearly Data Protection Impact Assessment and data audit under section 10 and Rule 13. A self-assessment is a practical way to prepare.

Can a startup conduct a DPDP self-assessment on its own?

Yes, for a first pass. A founder or operations lead can run it with process owners. Take advice where applicability or interpretation is unclear, or where children's data or large volumes are involved.

How often should a business conduct a DPDP self-assessment?

The law sets no frequency for businesses that are not Significant Data Fiduciaries. A sensible rhythm is once before 13 May 2027, then every six to twelve months, and whenever you launch a product, add a major vendor or see a new official notification.

Is a DPDP self-assessment the same as a privacy audit?

No. A self-assessment is done by your own team and relies on your own answers. A privacy audit is carried out by an independent reviewer who tests controls against set criteria.

Does a small business need a Data Protection Officer?

Only a Significant Data Fiduciary must appoint a Data Protection Officer (section 10(2)(a)). Every Data Fiduciary must publish the business contact details of a person who can answer questions about its processing (section 8(9), Rule 9).

What is the difference between a data mapping assessment and a DPDP readiness assessment?

A data mapping assessment records what personal data you hold and where it flows. A readiness assessment uses that map to check each duty: notice, consent, security, breach, retention, rights and vendors. Mapping comes first.

How can a business assess data breach readiness?

Walk a realistic incident through your team. Check detection, escalation, ownership, the ability to identify affected people, draft intimations that match Rule 7, and a decision step for CERT-In reporting. Note every point of hesitation as a gap.

What is a DPDP vendor risk assessment?

It is a review of the vendors that process personal data for you: whether a valid contract exists, what security they apply, how they report breaches to you, how they delete data and whether they use sub-processors. Depth should match the risk of each vendor.

Can a self-assessment score establish DPDP compliance?

No. A score reflects your own answers on a given day. Compliance depends on controls that work and can be evidenced, and under the Act it is the Data Protection Board, after an inquiry, that determines whether a breach occurred.

What evidence should be maintained?

Keep the data inventory, notices and consent records, the retention schedule and deletion logs, security settings and access reviews, vendor contracts, the incident plan and incident log, rights and grievance registers, training records and the dated assessment itself.

When should a business seek professional help?

When your role or an exemption is unclear, when you process children's data or very large volumes, when data moves across borders under sector rules, after a serious incident, or when nobody internally can own the work.

Is the DPDP Act in force now?

Partly. The Board framework has been in force since 13 November 2025, and the Consent Manager provisions start on 13 November 2026. The main duties of Data Fiduciaries, and the penalty provisions, start on 13 May 2027 under G.S.R. 843(E).

Does the 72-hour rule apply to every breach report?

Not in that form. Under Rule 7, affected Data Principals and the Board must be informed without delay, and a detailed report goes to the Board within seventy-two hours of becoming aware, unless the Board allows longer. CERT-In's six-hour reporting of cyber incidents is a separate requirement under a different law.

What to do next

A DPDP compliance self-assessment is where preparation starts, not where it ends. It turns a long statute into a short list of things your business must build before 13 May 2027.

Three habits make it worth the effort. Ask for evidence behind every answer. Fix gaps in order of risk and lead time, with a named owner for each. Reassess, because the business and the official position will both change.

If you have not started, do three things this week: name an owner, list where personal data enters your business, and take the free DPDP readiness assessment for a first view. If your review surfaces questions you cannot settle internally, you can ask to be introduced to an implementation specialist.

Sources

  • Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023), India Code: sections 2, 3, 4 to 14, 16, 17, 33 and the Schedule.
  • Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), 13 November 2025, Gazette of India: Rules 1, 3, 6 to 10, 12 to 15 and the Third and Fourth Schedules; corrigendum G.S.R. 892(E), 10 December 2025.
  • Commencement notification G.S.R. 843(E), 13 November 2025, Gazette of India.
  • Digital Personal Data Protection (Removal of Difficulties) Order, 2026, S.O. 5458(E), 5 October 2026, Gazette of India.
  • Press Information Bureau backgrounder, "DPDP Rules, 2025 Notified", 17 November 2025.
  • MeitY circular F. No. 2(1)/2026-Pers.I on appointments to the Data Protection Board, 6 May 2026.
  • CERT-In Directions No. 20(3)/2022-CERT-In, 28 April 2022, under section 70B(6) of the Information Technology Act, 2000.

Last reviewed: 13 November 2026. This guide is general information from an independent education resource. DPDP Act India is not a government body, regulator, law firm or certification body, and nothing here is legal advice or a certificate of compliance. Where the Act or Rules leave a point open, this guide marks it as our reading.