DPDPA vs GDPR: Key Differences Explained
DPDPA vs GDPR compared: lawful grounds, sensitive data, children, rights, breach notice, transfers, DPOs, penalties and reach, and what carries over.
17 min readBy Sachin Shirish, Director
Reviewed by Pragya Dwivedi, Associate Director, CISM (ISACA), eWPTX (INE Security)
The DPDPA vs GDPR question comes up whenever a company already compliant with one law starts serving people under the other. The two share a skeleton: purpose limitation, security, rights and breach reporting. They differ in the details that decide your workload. India's Act rests on consent and a short list of legitimate uses, has no special categories of data, treats everyone under eighteen as a child and reports every breach. A GDPR programme is a strong start, not a finished one.
At a Glance
- The laws: the EU's General Data Protection Regulation (EU) 2016/679 and India's Digital Personal Data Protection Act, 2023, with the DPDP Rules, 2025.
- Grounds for processing: the GDPR gives six lawful bases. The DPDP Act gives two routes: consent, or one of the "certain legitimate uses" listed in section 7.
- Sensitive data: the GDPR has special categories. The DPDP Act has none.
- Children: under the GDPR, information society services need parental consent below 16, or a lower national age of at least 13. Under the DPDP Act a child is anyone under 18.
- Breaches: the GDPR notifies a regulator when there is a risk. The DPDP Act and Rules require intimation of every personal data breach to the Board and to each affected person.
- Transfers: the GDPR restricts transfers unless a Chapter V tool applies. The DPDP Act allows them unless the Central Government restricts a country by notification.
- Penalties: up to €20 million or 4% of worldwide annual turnover under the GDPR; up to ₹250 crore for the most serious category (failing to take reasonable security safeguards) under the DPDP Act, with lower ceilings for other breaches.
Same Skeleton, Different Vocabulary
Start with the words.
The GDPR's controller is the DPDP Act's Data Fiduciary: the party that decides the purpose and means of processing. The processor is a Data Processor in both. The data subject becomes the Data Principal, and for a child or a person with a disability who has a lawful guardian, the Act's definition of Data Principal includes the parent or guardian. The supervisory authority becomes a single national regulator, the Data Protection Board of India.
Two scope differences matter early. The DPDP Act covers digital personal data only: data collected in digital form, or collected on paper and digitised later. The GDPR also covers manual records in a filing system. And the Act's notion of a Significant Data Fiduciary, which the Central Government notifies, has no direct GDPR equivalent; the GDPR scales duties by risk and by activity instead.
The Comparison Table
| Topic | GDPR | DPDP Act and Rules |
|---|---|---|
| Grounds for processing | Six lawful bases in Article 6, including contract and legitimate interests | Consent, or a legitimate use listed in section 7; no general legitimate-interests ground |
| Sensitive data | Special categories in Article 9 with extra conditions | No special categories in the Act |
| Children | Parental consent below 16 for information society services; member states may lower it to 13 | Child means under 18; verifiable parental consent; no tracking, behavioural monitoring or targeted advertising directed at children; Rule 12 exemptions apply |
| Individual rights | Access, rectification, erasure, restriction, portability, objection, and rights on automated decisions | Information, correction, completion, updating and erasure, grievance redressal, and nomination |
| Breach notification | To the supervisory authority within 72 hours where feasible, unless unlikely to result in a risk; to individuals when high risk | Every breach to the Board without delay, a detailed report within 72 hours, and to each affected Data Principal |
| Cross-border transfer | Allowed only under Chapter V: adequacy, appropriate safeguards or a derogation | Allowed unless the Central Government restricts a notified country; sectoral laws may go further |
| Data Protection Officer | Required for public authorities and for certain large-scale core activities | Required for Significant Data Fiduciaries, and must be based in India |
| Maximum penalty | €20 million or 4% of worldwide annual turnover, whichever is higher | Up to ₹250 crore for failing to take reasonable security safeguards |
| Territorial reach | Offering goods or services to, or monitoring the behaviour of, people in the EU | Processing outside India connected with offering goods or services to Data Principals in India |
Lawful Bases Against Consent and Legitimate Uses
This is the difference with the largest operational cost.
Under Article 6 of the GDPR, processing is lawful on any one of six bases: consent, contract, legal obligation, vital interests, public task and legitimate interests. Most commercial processing in a GDPR programme runs on contract or legitimate interests, with consent kept for marketing and cookies.
Section 4 of the DPDP Act allows processing only for a lawful purpose, and only with the Data Principal's consent or for "certain legitimate uses". Section 7 lists those uses. The first is the closest to a contract basis: data the person voluntarily provided for a specified purpose, where she has not said she does not consent. The others are narrower and mostly public or legal in nature: state functions, compliance with law or court orders, medical emergencies, disasters and certain employment purposes.
There is no general legitimate-interests ground. Processing you justified in Europe with a balancing test, such as analytics, fraud models or product improvement on customer data, needs a fresh look in India. If it does not fit a listed use, it needs consent.
Consent itself is demanding. Section 6 requires it to be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the data necessary for the purpose. Section 5 requires a notice describing the personal data and the purpose, with the option to read it in English or any language in the Eighth Schedule to the Constitution. A GDPR privacy notice is a useful draft, but it is not written to that specification.
Sensitive Data
The GDPR singles out special categories, among them health, biometric and genetic data, racial or ethnic origin, religious beliefs and sexual orientation, and Article 9 prohibits processing them unless a specific condition applies.
The DPDP Act has no such list. All personal data gets the same basic treatment. That does not mean health or financial data can be handled casually: sectoral rules still apply, and the volume and sensitivity of data processed are among the factors the Central Government can weigh when notifying a Significant Data Fiduciary under section 10.
Children's Data
The gap here is large. Under the GDPR, where an information society service relies on consent for a child, parental consent is needed below 16, and member states may set a lower age of no less than 13.
Under the DPDP Act, a child is anyone who has not completed eighteen years. Section 9 requires verifiable consent of the parent before processing a child's personal data, prohibits processing likely to cause a detrimental effect on a child's well-being, and bars tracking, behavioural monitoring and targeted advertising directed at children, subject to exemptions the Rules grant to certain classes of Data Fiduciary and purposes (Rule 12 and the Fourth Schedule). Rule 10 of the DPDP Rules sets out how a Data Fiduciary verifies that the person consenting is an identifiable adult. A consumer product that set its age gate at 13 or 16 for Europe has to treat sixteen- and seventeen-year-olds as children in India, with a parental consent flow and no behavioural advertising, unless exempt.
Data Principal Rights
The GDPR's rights are broader. Articles 15 to 22 cover access, rectification, erasure, restriction, data portability, the right to object and rights around automated individual decision-making, including profiling.
The DPDP Act gives Data Principals a right to information about processing (section 11), to correction, completion, updating and erasure (section 12), to grievance redressal (section 13) and to nominate another person to exercise their rights on death or incapacity (section 14). There is no portability right and no general right to object. The right to information runs against a fiduciary the person consented to, including under the first legitimate use in section 7, so check section 11 against your request workflow.
Two items are new for GDPR teams. Nomination has no GDPR counterpart. And grievance redressal is a formal duty: section 8(10) requires an effective mechanism, and the Rules require a Data Fiduciary to publish the period within which it will respond to grievances, which may not exceed ninety days.
Breach Notification
Under Article 33 of the GDPR, a controller notifies the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to individuals. Article 34 adds communication to individuals where the risk is high.
The DPDP Act has no risk threshold. Section 8(6) requires a Data Fiduciary to intimate every personal data breach to the Board and to each affected Data Principal. Rule 7 sets the form: a description to the Board without delay, a detailed report within seventy-two hours (or a longer period the Board allows on written request), and a plain-language notice to each affected person covering what happened, the likely consequences, what you are doing and what they can do.
In practice your GDPR incident runbook needs a new rule: in India, the "do we need to notify?" step always answers yes. Our guide to DPDP Act breach notification walks through the sequence, and sector regulators may impose their own, shorter reporting duties on top.
Cross-Border Transfer
The approaches run in opposite directions. Chapter V of the GDPR permits a transfer outside the EU only on an adequacy decision, appropriate safeguards such as standard contractual clauses, or a listed derogation. India does not have an adequacy decision, which is why European customers ask Indian vendors to sign standard contractual clauses.
Section 16 of the DPDP Act works as a negative list. Transfers are allowed unless the Central Government, by notification, restricts transfer to a country or territory. Section 16(2) preserves any other Indian law that sets a higher degree of protection or restriction, so sectoral data localisation rules continue to apply. Rule 15 adds that transfers are subject to any requirements the Central Government specifies about making personal data available to a foreign State or entities under its control.
For an Indian company serving EU customers, both rules apply to different data. Keep your SCCs for EU data, and keep a register of where Indian personal data goes so you can respond if a restriction is notified.
DPOs and Significant Data Fiduciaries
Under Article 37 of the GDPR, a data protection officer is required for public authorities and where core activities involve regular and systematic monitoring of individuals on a large scale, or large-scale processing of special category or criminal offence data.
Under the DPDP Act, the duty attaches to status, not activity. Only a Data Fiduciary notified by the Central Government as a Significant Data Fiduciary must appoint a Data Protection Officer, and that officer must be based in India, be responsible to the board of directors or similar governing body, and be the point of contact for grievance redressal. The same section requires an independent data auditor and periodic Data Protection Impact Assessments.
Penalties
Article 83(5) of the GDPR sets the upper tier at €20 million or 4% of total worldwide annual turnover of the preceding financial year, whichever is higher.
The DPDP Act's Schedule sets fixed ceilings per type of breach, imposed by the Board after an inquiry:
- up to ₹250 crore for failing to take reasonable security safeguards to prevent a personal data breach;
- up to ₹200 crore for failing to notify the Board or affected Data Principals of a breach;
- up to ₹200 crore for breaching the additional obligations on children's data;
- up to ₹150 crore for breaching the additional obligations of a Significant Data Fiduciary;
- up to ₹50 crore for breach of any other provision of the Act or Rules.
The DPDP Act has no turnover percentage, so for a large group the GDPR ceiling is higher; for a mid-sized Indian company, the fixed DPDP ceilings are the bigger number.
Extraterritorial Reach
Both laws follow the customer. Article 3(2) of the GDPR applies to a controller or processor outside the EU that offers goods or services to people in the Union or monitors their behaviour there. Our guide to GDPR readiness for SaaS works through that test.
Section 3 of the DPDP Act applies to processing of digital personal data within India, and to processing outside India if it is in connection with any activity related to offering goods or services to Data Principals within India. There is no separate monitoring limb, so a European company selling into India is in scope through its offering, not its tracking.
What a GDPR Programme Carries Over
You will reuse more than you rebuild. Records of processing become the data map for India. Security controls, access reviews and logging carry over, though the Rules require logs to be kept for at least one year. Processor contracts need DPDP terms added, not new contracts. The incident runbook needs the notify-every-breach rule and the Board as a recipient.
What you build new: consent notices to the Act's specification, a review of every purpose that relied on legitimate interests, an under-18 children's data flow, nomination and grievance handling with a published response period, and, if notified as a Significant Data Fiduciary, a DPO in India and an independent data audit.
Timing matters. Rule 1 of the DPDP Rules brings most Data Fiduciary duties into force eighteen months after publication on 13 November 2025, which is 13 May 2027 unless the Rules are amended.
How SecureRoot Helps
SecureRoot runs both programmes. Our DPDPA compliance service covers data mapping, gap assessment, notice and consent design, rights and grievance workflows and breach procedures. Our GDPR service covers lawful basis registers, records of processing, rights processes, impact assessments and breach readiness. When a client needs both, we map one inventory to two laws.
Two limits. SecureRoot is not a law firm, so legal interpretation of either law belongs with your counsel. And no DPDP certificate exists: no body is authorised to certify compliance with the Act, and we do not claim to.
Frequently Asked Questions
If we are GDPR compliant, are we compliant with the DPDP Act?
No, although you are well ahead of a company starting from nothing. The two laws share structure: a data map, security safeguards, processor contracts, rights handling and breach response. Those carry over with adjustments. What does not carry over is the legal footing for much of your processing. The DPDP Act has no general legitimate-interests ground, so purposes that rely on it in Europe need consent or a listed legitimate use in India. Children are everyone under eighteen, not sixteen or thirteen. Every breach goes to the Data Protection Board and to each affected person, with no risk threshold. And nomination and grievance redressal are rights GDPR teams have not built for. Treat your GDPR programme as the base layer and run a DPDP gap assessment against it, purpose by purpose, before 13 May 2027, when most Data Fiduciary duties come into force under the Rules.
Does the DPDP Act have special categories of personal data like the GDPR?
No. The GDPR's Article 9 lists special categories, such as health, biometric and genetic data, religious beliefs and sexual orientation, and sets extra conditions before they can be processed. The DPDP Act has no equivalent list, so all digital personal data receives the same baseline protection under the Act itself. That is not a licence to treat sensitive data lightly. Sectoral rules for health, banking, insurance and telecom still apply alongside the Act. The Central Government can also weigh the volume and sensitivity of personal data processed when it decides to notify a Data Fiduciary as a Significant Data Fiduciary under section 10, which brings a Data Protection Officer in India, an independent data auditor and periodic impact assessments. For a team coming from the GDPR, the sensible course is to keep your special category safeguards as good practice while recognising that the Indian legal trigger is different.
Can we rely on legitimate interests under the DPDP Act?
Not in the GDPR sense. Section 4 of the DPDP Act allows processing only with consent or for "certain legitimate uses", and section 7 lists those uses exhaustively. The nearest to everyday commercial processing is the first: personal data a person voluntarily gave you for a specified purpose, where she has not said she does not consent to that use. The other uses cover matters such as state functions, legal obligations, court orders, medical emergencies, disasters and certain employment purposes. There is no open balancing test. In practice, list every purpose you run on legitimate interests in Europe, such as product analytics, fraud scoring, marketing to existing customers or model training, and test each one against section 7. Where none fits, you need a notice and consent that meet sections 5 and 6, or you stop that processing for Indian Data Principals. This review is usually the largest single piece of work for a GDPR team.
How does breach notification differ between the GDPR and the DPDP Act?
The main difference is the threshold. Under Article 33 of the GDPR, a controller notifies its supervisory authority without undue delay and, where feasible, within 72 hours, unless the breach is unlikely to result in a risk to individuals; individuals are told only where the risk is high. Under section 8(6) of the DPDP Act, every personal data breach is intimated to the Data Protection Board and to each affected Data Principal, with no risk filter. Rule 7 of the DPDP Rules then sets the content and timing: a description to the Board without delay, a detailed report within seventy-two hours unless the Board allows longer on written request, and a plain-language notice to each affected person. Failing to notify the Board or affected Data Principals carries a penalty of up to ₹200 crore under the Schedule. Sector regulators can add their own reporting duties alongside these.
Is the DPDP Act stricter than the GDPR on cross-border data transfers?
Generally it is looser. The GDPR starts from restriction: under Chapter V, personal data leaves the EU only on an adequacy decision, an appropriate safeguard such as standard contractual clauses, or a narrow derogation. India has no adequacy decision, so EU customers ask Indian vendors to sign clauses. The DPDP Act starts from permission. Section 16 allows transfers out of India unless the Central Government, by notification, restricts transfer to a particular country or territory. Rule 15 adds that a Data Fiduciary must meet any requirements the government specifies about making personal data available to a foreign State or entities it controls. The caution is section 16(2): any other Indian law that sets stricter protection or localisation, such as sectoral rules in financial services, continues to apply. So check your sector before assuming Indian data can move freely, and keep a register of where it goes.
Where to Start
Take your GDPR records of processing and add one column: the DPDP ground for each purpose, consent or a section 7 use. The blanks in that column are your work plan. If you want it done against your own systems, request an assessment and we will map both laws from the same inventory.
Free Checklist
Get the DPDP Act Checklist
Our DPDP Act checklist: the controls, evidence and decisions the programme turns on, marked up for your scope. Tell us where to send it.
One form, the same notice as every enquiry on this site.
Have a Question About This?
If this raised something specific to your environment, a scoping call is the fastest way to get a direct answer.
We reply within one business day.
See Every Published Price Band