DPDP Act vs GDPR: the short answer
Quick answer
The DPDP Act is consent-centred and narrower: it covers digital personal data, offers a short list of "legitimate uses" instead of six lawful bases, and has no category of special sensitive data. GDPR is broader and stricter on individual rights, with data portability, objection and fines of up to 4% of global turnover. If you serve both Indian and EU users, you need to satisfy both.
Side-by-side comparison
| Area | DPDP Act, 2023 (India) | GDPR (EU / UK) |
|---|---|---|
| Data covered | Digital personal data, and non-digital data that is later digitised | All personal data, digital or on paper in a filing system |
| Territorial scope | Processing in India, and outside India when offering goods or services to people in India | Establishment in the EU, or offering goods and services to or monitoring people in the EU |
| Lawful basis | Consent, or a listed legitimate use (Section 7) | Six bases: consent, contract, legal obligation, vital interests, public task, legitimate interests |
| Sensitive data | No special category. Significant Data Fiduciaries are decided by volume and risk | Special categories such as health, biometrics and religion get extra protection |
| Children | Under 18. Verifiable parental consent; no tracking or targeted ads | Default age 16, member states may lower to 13 |
| Regulator | Data Protection Board of India (appeals to TDSAT) | National supervisory authorities in each member state |
| DPO | Mandatory only for Significant Data Fiduciaries, and must be India-based | Mandatory for public bodies and for large-scale systematic monitoring or special-category processing |
| Fines | Fixed caps per breach, up to ₹250 crore | Up to €20 million or 4% of global annual turnover |
Lawful bases vs consent
GDPR lets you process data on six different grounds, so many activities never need consent. Under the DPDP Act, consent is the main ground. The other route is "certain legitimate uses" in Section 7, such as a person voluntarily providing data for a specific purpose, compliance with law, medical emergencies, and employment-related purposes.
The practical effect: Indian companies must build clear, granular consent and notice flows, and keep proof of each consent. A GDPR-style "legitimate interests" argument does not exist in the DPDP Act.
Rights of individuals
| Right | DPDP Act | GDPR |
|---|---|---|
| Access / information | Yes (Section 11) | Yes |
| Correction and erasure | Yes (Section 12) | Yes |
| Grievance redressal | Yes, with the Data Fiduciary first (Section 13) | Complaint to the regulator |
| Nominate another person | Yes (Section 14) | No |
| Data portability | No | Yes |
| Object to processing / restrict | No (consent can be withdrawn) | Yes |
| Automated decision-making safeguards | Not specified | Yes |
The DPDP Act also places duties on individuals (Section 15), which GDPR does not.
Breach reporting and cross-border transfers
Breaches. GDPR requires notice to the regulator within 72 hours when a breach is likely to harm individuals. The DPDP Act requires every personal data breach to be reported to the Data Protection Board and to each affected individual, and the Rules set prompt intimation plus a detailed report within 72 hours.
Transfers. GDPR restricts transfers outside the EU unless an adequacy decision or safeguard such as Standard Contractual Clauses applies. The DPDP Act is more open: transfers are allowed except to countries the Central Government restricts by notification, and stricter sector laws still apply, for example RBI rules for payment data.
Penalties compared
GDPR scales fines to turnover. The DPDP Act uses fixed caps: up to ₹250 crore for security safeguard failures, ₹200 crore for failing to notify a breach or breaching children's data rules, ₹150 crore for Significant Data Fiduciary duties, and ₹50 crore for other breaches. Estimate yours with the DPDP penalty calculator.
Do Indian companies need to comply with both?
If you sell to or monitor people in the EU or UK, yes. A single privacy programme can cover both. Build one data inventory, one consent and notice layer, one rights-request workflow and one breach runbook, then add the law-specific items: Standard Contractual Clauses and a DPO decision for GDPR, and verifiable parental consent, Indian-language notices and Board reporting for the DPDP Act.
Not sure where you stand? Take the free DPDP readiness quiz or read what the DPDP Act requires.
Frequently asked questions
Is the DPDP Act the same as GDPR?
No. Both protect personal data, but the DPDP Act is narrower in scope, centres on consent and a short list of legitimate uses, and has no special category of sensitive data. GDPR has six lawful bases, wider data subject rights and percentage-of-turnover fines.
If I comply with GDPR, am I compliant with the DPDP Act?
Not automatically. GDPR compliance gives you a strong base, but the DPDP Act adds Indian-specific points such as verifiable parental consent up to age 18, notices in the 22 scheduled languages on request, Consent Managers, and breach reporting to the Data Protection Board.
Does GDPR apply to Indian companies?
Yes, if you offer goods or services to people in the EU or UK, or monitor their behaviour, even when you have no office there. An Indian BPO, SaaS or e-commerce company with EU customers is covered by both laws.
Which law has the bigger fines?
GDPR fines go up to €20 million or 4% of global annual turnover, whichever is higher. The DPDP Act sets fixed caps per breach, up to ₹250 crore for failing to take reasonable security safeguards.
This guide is general information, not legal advice. Check the Act, the DPDP Rules 2025 and official MeitY notifications, or speak to a qualified advocate, before acting on any point here.
