DPDP Act 2023Updated 22 November 202613 min read

DPDP Act vs GDPR: Side-by-Side Comparison for Tech Teams

A row-by-row comparison of India's DPDP Act 2023 and Rules 2025 with the EU GDPR: scope, lawful bases, children, rights, breach timelines, DPOs, transfers and penalties.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

India law
Digital Personal Data Protection Act, 2023 (Act 22 of 2023) and DPDP Rules, 2025
EU law
Regulation (EU) 2016/679 (GDPR)
DPDP core obligations apply from
13 May 2027
DPDP breach reporting
Every breach; detailed Board report within 72 hours (Rule 7(2)(b))
GDPR breach reporting
72 hours to the authority where there is risk (Art. 33)
DPDP maximum penalty
Up to ₹250 crore per instance (security safeguards)
GDPR maximum fine
€20m or 4% of worldwide turnover
Age of a child under DPDP
Under 18

Quick answer

The DPDP Act is narrower and more prescriptive than the GDPR. It covers only digital personal data, allows processing on consent or listed legitimate uses (no legitimate-interests basis), has no sensitive-data category, treats everyone under 18 as a child, and requires every breach to be reported. Fines are capped at fixed amounts up to ₹250 crore per instance, not a percentage of turnover.

  • GDPR compliance is a strong head start for DPDP, but it does not satisfy the Indian law on its own.
  • DPDP has no legitimate-interests or contract basis; outside the section 7 legitimate uses, you need consent.
  • Every personal data breach is reportable to the Board and to affected individuals under Rule 7, with no risk threshold.
  • Children are under 18 under DPDP, and verifiable parental consent is mandatory under section 9 and Rule 10.
  • DPDP penalties are fixed rupee caps per instance up to ₹250 crore; GDPR's top tier is €20m or 4% of worldwide turnover.
  • Core DPDP fiduciary obligations apply from 13 May 2027, so the gap analysis should be done now.

Who this is for: CTOs and engineering leads running EU and India products, Privacy and compliance teams with an existing GDPR programme, Indian SaaS and IT services companies with EU customers, Global companies offering services to users in India, Data Protection Officers

How does the DPDP Act differ from the GDPR in one paragraph?

Both laws regulate how organisations collect and use personal data, use a controller-like role (the Data Fiduciary in India, the controller in the EU) and give individuals enforceable rights. The differences are structural, not cosmetic:

  • Narrower lawful grounds. DPDP permits processing on consent (section 6) or a closed list of certain legitimate uses (section 7). There is no general legitimate-interests basis and no standalone contract basis.
  • No special categories. DPDP has no separate sensitive-data regime. Sensitivity matters instead when the Government designates a Significant Data Fiduciary and when the Board sets a penalty.
  • Stricter on children and breaches. Everyone under 18 is a child, and every personal data breach is reportable.
  • Lighter on documentation. There is no general DPO, DPIA or records-of-processing duty for ordinary fiduciaries. Those duties fall on Significant Data Fiduciaries.
  • Fixed-amount penalties. The Board imposes penalties up to fixed rupee caps per instance, not a share of turnover.

For a team already running a GDPR programme, the practical message is this. Reuse your data maps, vendor contracts and security controls. Then rebuild consent, children's flows, breach playbooks and retention around India's specific rules before 13 May 2027.

DPDP vs GDPR comparison table

TopicDPDP Act 2023 + Rules 2025GDPR
Material scopeDigital personal data, and non-digital data later digitised (s.3)Personal data processed wholly or partly by automated means, and in filing systems
Territorial reachProcessing in India; outside India if connected to offering goods or services to Data Principals in India (s.3)EU establishments; non-EU organisations offering goods/services to, or monitoring, people in the EU (Art. 3(2))
Lawful basesConsent (s.6) or listed legitimate uses (s.7)Several bases, including consent, contract and legitimate interests
Sensitive dataNo separate categorySpecial categories with extra conditions
ChildrenUnder 18; verifiable parental consent; no tracking, behavioural monitoring or targeted ads (s.9, Rule 10)Lower age of digital consent, which member states may vary; check the GDPR text
Individual rightsAccess, correction/completion/updating/erasure, grievance redressal, nomination (ss.11–14)Wider set, including portability, objection and restriction
Breach to regulatorEvery breach: Board told without delay, detailed report within 72 hours (Rule 7(2))Within 72 hours where there is risk to individuals (Art. 33)
Breach to individualsEvery affected Data Principal, without delay (Rule 7(1))Where there is high risk (Art. 34)
DPOOnly Significant Data Fiduciaries, based in India; others publish a contact (Rule 9)Required for certain controllers and processors
DPIASignificant Data Fiduciaries, every 12 months (Rule 13)Where processing is likely to be high risk (Art. 35)
Cross-borderAllowed unless a country is restricted (s.16), subject to Rule 15 ordersAdequacy, SCCs or other Chapter V tools (Art. 44–49)
Local representativeNot requiredEU representative for many non-EU organisations (Art. 27)
PenaltiesUp to ₹250 crore per instance (Schedule)Up to €20m or 4% of worldwide turnover
RegulatorData Protection Board of India; appeals to TDSATSupervisory authorities in each member state

Lawful bases: why legitimate interests does not exist in India

This is the single biggest re-engineering item for GDPR-first teams. Under the GDPR, product analytics, fraud scoring and many B2B processing flows rest on legitimate interests or on contractual necessity. DPDP offers neither.

What DPDP offers instead

  • Consent (section 6): free, specific, informed, unconditional and unambiguous, given by clear affirmative action, limited to the data necessary for the purpose. Withdrawal must be as easy as giving it. Details are in DPDP consent requirements.
  • Legitimate uses (section 7): data voluntarily provided for a specified purpose where the person has not objected; State subsidies, benefits and licences; State functions; legal obligations; court orders; medical emergencies; epidemics; disasters; and employment purposes. See DPDP legitimate uses.

How to map your GDPR register

  1. Export your record of processing and the lawful basis column.
  2. For every contract row, test whether it fits section 7(a) (voluntary provision for a specified purpose). Delivery of an ordered product usually does. Upselling usually does not.
  3. For every legitimate interests row, either find a section 7 ground or move it to consent with a Rule 3 notice.
  4. Mark employment processing separately. Section 7 covers employment purposes, including protecting trade secrets and providing benefits.

Expect marketing, cross-product profiling and much analytics to land on consent in India, even where the EU flow does not.

Children's data and sensitive data

Children

DPDP defines a child as an individual under 18. Section 9 requires verifiable parental consent before any processing of a child's data. It bans processing likely to cause a detrimental effect on the child's well-being, and bans tracking, behavioural monitoring and targeted advertising directed at children.

Rule 10 says how to verify that the person consenting is an identifiable adult. You can rely on reliable identity and age details you already hold, on details the individual provides voluntarily, or on a virtual token from an authorised entity, including a Digital Locker service provider.

The Fourth Schedule exempts listed classes and purposes from section 9(1) and 9(3). Examples are healthcare providers, educational institutions, crèches, child transport, email-only accounts and confirming that a user is not a child. The bar on detrimental processing in section 9(2) is never exempted. See verifiable parental consent.

GDPR teams used to a lower age threshold for online services will need age assurance flows covering a much wider teen population in India.

Sensitive data

GDPR's special categories, such as health, biometrics and religion, have no DPDP equivalent. Health or financial data is ordinary personal data under the Act. Two things still make sensitivity matter in India:

  • The Central Government considers the volume and sensitivity of data when notifying a Significant Data Fiduciary (section 10).
  • The Board weighs the type and nature of personal data when fixing a penalty (section 33(2)).

Keep your GDPR special-category controls. They are good security practice and will reduce penalty exposure, even though DPDP does not mandate them separately.

Rights and breach notification compared

Rights

DPDP gives four core rights:

  • Access: a summary of the data and its processing, plus the identities of other fiduciaries and processors it was shared with (s.11).
  • Correction and erasure: correction, completion, updating and erasure (s.12).
  • Grievance redressal: this must be exhausted before going to the Board (s.13).
  • Nomination: naming someone to exercise rights on death or incapacity (s.14).

There is no portability right and no general right to object. The nomination right has no GDPR counterpart.

Rule 14 adds operational detail. You must publish how to make requests and which identifiers you need. You must also publish a grievance response period of no more than 90 days. See Data Principal rights.

Breach notification

GDPR filters notifications by risk. DPDP does not. Under Rule 7, on becoming aware of any personal data breach, a fiduciary must:

  1. Tell each affected Data Principal without delay, through her user account or registered contact. The notice must cover the nature, extent and timing, likely consequences, mitigation, safety steps she can take, and a contact person.
  2. Give the Board a description without delay.
  3. Within 72 hours, or longer if the Board allows on written request, send the Board a detailed report. It must include facts and reasons, mitigation, findings on who caused the breach, remedial measures and a report on the intimations sent.

India may also require a separate CERT-In report within 6 hours for specified cyber incidents. One incident can therefore trigger three clocks: CERT-In, the Board and, if EU data is involved, GDPR. See the 72-hour breach guide.

DPOs, DPIAs, processors and cross-border transfers

Governance roles

Only a Significant Data Fiduciary (none has been designated yet; obligations apply once notified) must appoint a DPO based in India and responsible to its board. It must also appoint an independent data auditor and run an annual DPIA and audit under Rule 13.

Every other fiduciary must publish the business contact of a person who can answer questions about processing, both on its website or app and in every rights response (Rule 9). You do not need an India DPO by default, but you do need a named contact route.

Processors

GDPR Article 28 lists mandatory processor contract terms. DPDP section 8 is shorter. A fiduciary may use a processor only under a valid contract, stays responsible for the processor's processing, and must cause the processor to stop or erase data when required.

Rule 6(1)(f) requires security clauses in processor contracts. Rule 8(3) means the processor must also retain processing logs for at least a year. Your GDPR data processing agreement template is a good base, but add these India clauses.

Cross-border transfers

GDPR starts from restriction. Transfers to India need SCCs (Decision (EU) 2021/914) or another Chapter V tool, because India has no adequacy decision (see GDPR adequacy and India).

DPDP starts from permission. Section 16 allows transfers except to countries the Central Government restricts by notification, and stricter sectoral rules, such as RBI payment data storage, prevail. Rule 15 adds any requirements the Government sets by order about making data available to foreign States. Rule 13(4) may localise specified data for Significant Data Fiduciaries.

In practice, India to the EU is easy under DPDP. EU to India still needs full GDPR transfer paperwork. See cross-border transfer.

Penalties, regulators and enforcement

GDPR fines scale with global turnover. DPDP penalties are fixed maximum amounts per instance, set out in the Schedule to the Act:

  • Failure to take reasonable security safeguards: up to ₹250 crore.
  • Failure to notify a breach: up to ₹200 crore.
  • Breach of children's obligations: up to ₹200 crore.
  • Breach of Significant Data Fiduciary obligations: up to ₹150 crore.
  • Any other breach: up to ₹50 crore.
  • Breach of a Data Principal's own duties: up to ₹10,000.

The Data Protection Board decides penalties after an inquiry. It weighs factors such as gravity, duration, type of data, repetition, gains made and mitigation. Penalties go to the Consolidated Fund of India. See DPDP penalties explained.

Who enforces

India has one national regulator, the Data Protection Board of India. It runs as a digital office, and appeals go to TDSAT within 60 days.

In the EU, each member state has its own supervisory authority. Individuals can complain to their local authority, and fines can be challenged in national courts.

Practical implication

Because DPDP caps are per instance, one incident can touch several heads. A breach caused by weak controls and then reported late could engage both the ₹250 crore and ₹200 crore entries. The Act has no turnover link. That makes the exposure relatively larger for mid-sized Indian companies than for large multinationals.

Turning a GDPR programme into DPDP compliance before 13 May 2027

Use your GDPR artefacts as inputs and close the India-specific gaps in this order.

  1. Scope. Confirm which systems process digital personal data of people in India. Include offshore systems that serve Indian users. See territorial scope.
  2. Lawful basis remap. Move legitimate-interests and contract flows to consent or a section 7 ground.
  3. Notices. Rewrite privacy notices into standalone Rule 3 notices: an itemised data list, specified purposes, and links to withdraw, exercise rights and complain to the Board.
  4. Children. Add age gating and verifiable parental consent for under-18s. Remove targeted advertising and behavioural monitoring for them.
  5. Breach runbook. Drop the risk threshold for India. Pre-draft Rule 7 notices for individuals and the Board, and align them with the CERT-In 6-hour clock.
  6. Retention. Add the Rule 8(3) one-year minimum retention for personal data, traffic data and processing logs. Then check the Third Schedule three-year erasure rule if you are a large e-commerce, gaming or social media platform.
  7. Rights operations. Publish request channels, identifiers and a grievance period of 90 days or less. Add nomination.
  8. Contracts. Add India security and retention clauses to processor agreements.

The work you can reuse unchanged includes your data inventory, encryption and access controls, vendor due diligence and incident logging. Treat that as your starting asset, not your finish line.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Remap every lawful basis

    Replace legitimate-interests and contract bases for Indian data with consent or a specific section 7 legitimate use.

    DPDP Act s.6, s.7

  2. Rewrite notices to Rule 3

    Create standalone notices with an itemised list of personal data, specified purposes, and links to withdraw consent, exercise rights and complain to the Board.

    Rule 3

  3. Remove the breach risk threshold for India

    Treat every personal data breach as reportable to the Board and each affected Data Principal, with a detailed report within 72 hours.

    Rule 7

  4. Extend child protections to under-18s

    Implement verifiable parental consent and switch off tracking, behavioural monitoring and targeted ads for Indian users under 18.

    DPDP Act s.9; Rule 10

  5. Add India clauses to processor contracts

    Add reasonable security safeguard obligations and one-year log retention to existing GDPR data processing agreements.

    Rule 6(1)(f); Rule 8(3)

  6. Publish a privacy contact

    Publish the business contact of a DPO or responsible person on the website or app and in every rights response.

    Rule 9

  7. Set a grievance SLA of 90 days or less

    Publish the response period and instrument ticketing so that responses stay within it.

    Rule 14(3)

  8. Check sectoral localisation

    Confirm whether RBI or other sector rules restrict where Indian data can be stored, even though DPDP itself allows transfers.

    DPDP Act s.16

Key dates

  1. DPDP Act receives Presidential assent

  2. DPDP Rules notified; Board provisions in force

  3. Consent Manager registration (Rule 4) in force

  4. Core fiduciary obligations, rights, breach and penalty provisions apply

Answers

Frequently asked questions

Is a GDPR-compliant company automatically compliant with the DPDP Act?

No. GDPR compliance covers much of the security, vendor and data mapping work, but DPDP has no legitimate-interests basis, treats everyone under 18 as a child, requires every breach to be reported, and sets India-specific notice, retention and grievance rules. A focused gap analysis is still needed before 13 May 2027.

Does the DPDP Act have a legitimate interests basis like the GDPR?

No. DPDP allows processing only on consent under section 6 or on the closed list of legitimate uses in section 7. Those cover voluntarily provided data for a specified purpose, State functions, legal obligations, emergencies and employment purposes. Anything else needs consent.

Is breach notification stricter under DPDP than under GDPR?

In scope, yes. GDPR requires notifying the regulator only where there is risk to individuals, and individuals only where risk is high. DPDP Rule 7 requires notifying the Board and every affected Data Principal for any personal data breach. The detailed Board report is due within 72 hours.

Do I need a Data Protection Officer in India like under GDPR?

Only if your organisation is notified as a Significant Data Fiduciary, which must appoint a DPO based in India. Other fiduciaries must publish the business contact details of a person who can answer questions about processing, under Rule 9.

Can personal data be transferred from India to the EU?

Yes. Section 16 of the DPDP Act permits transfers except to countries the Central Government restricts by notification. Rule 15 adds any requirements the Government sets by order about foreign State access. Transfers from the EU to India still need a GDPR Chapter V mechanism such as SCCs, because India has no adequacy decision.

Are DPDP penalties higher than GDPR fines?

They work differently. DPDP penalties are fixed caps per instance, up to ₹250 crore for security failures, with no link to turnover. GDPR's top tier is €20 million or 4% of worldwide turnover. For mid-sized Indian companies the DPDP caps can be the larger relative exposure.

Does DPDP have a right to data portability?

No. The DPDP Act gives rights of access, correction and erasure, grievance redressal and nomination, but no portability right like the GDPR's. Consent Managers registered under Rule 4 must give Data Principals machine-readable copies of their consent records, but that is a narrower duty.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rules 3, 6, 7, 10, 13, 14 and 15 (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 3, 6, 7, 9, 10, 16 and the Schedule (official text)
  • General Data Protection Regulation — Articles 3, 27, 28, 30, 32, 33, 34, 35 and Chapter V (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.