← All news and guides
Data protection

DPDP vs GDPR for SaaS: Where Your GDPR Programme Covers You and Where It Doesn't

Does a GDPR programme cover India's DPDP Act? What carries over, what does not, and the system changes SaaS teams need before the 13 May 2027 start.

Mono Team ·

Two railway tracks of different gauge running side by side into a quiet station at dusk, with an empty platform and warm lights, shallow depth of field.

Short answer: a working GDPR programme gets you a long way towards the DPDP Act, but the gaps it leaves are the ones that break systems. Notices, consent records, processor contracts, security controls and rights handling carry over with edits. Four things do not carry over. DPDP has no legitimate-interests basis and no general contract basis. Every personal data breach must be reported to the Board and to each affected person, with no risk threshold. A child is anyone under 18, parental consent comes before any processing, and tracking and targeted ads aimed at children are barred. And a GDPR transfer toolkit does not map to DPDP's much lighter transfer rules. The core DPDP duties start on 13 May 2027.

This guide is for SaaS teams that already run GDPR controls and now serve Indian customers or users. Where a point needs a legal reading, take it to counsel. GDPR changes proposed in the EU's Digital Omnibus are not in force, so this compares the law as it stands.

Does a GDPR programme cover the DPDP Act?

Two different plug types, a European two-pin and an Indian three-pin, lying beside a universal travel adapter on a pale wooden desk in soft window light.

Partly. The two laws share a core: a notice before you collect, valid consent where you rely on it, a way to withdraw, safeguards, processor contracts, rights requests and breach handling. If built well for GDPR, reuse the structure and change the details.

ControlGDPRDPDP Act and RulesWhat to do
Notice before collectionGDPR: Arts 13 and 14DPDP Act and Rules: s.5; Rule 3 (standalone notice with an itemised description of the data, purposes and services)What to do: Reuse the content. Add links for withdrawal, rights and the Board complaint route. Offer English or an Eighth Schedule language (s.5(3)).
Consent qualityGDPR: Free, specific, informed, unambiguous (Art 4(11))DPDP Act and Rules: Free, specific, informed, unconditional and unambiguous, by clear affirmative action, limited to necessary data (s.6(1))What to do: Remove bundled consents. Consent must be limited to the data necessary for the stated purpose.
Withdrawal and proofGDPR: As easy as giving (Art 7(3)); consent demonstrable (Art 7(1))DPDP Act and Rules: As easy as giving (s.6(4)); processors stop too (s.6(6)); fiduciary must prove notice and consent (s.6(10))What to do: Reuse your consent log. Record the notice version, and check withdrawal reaches every processor.
Processor contractsGDPR: Art 28DPDP Act and Rules: Valid contract needed (s.8(2)); fiduciary stays responsible (s.8(1))What to do: Reuse your DPA. Add DPDP clauses (see below).
SecurityGDPR: Art 32DPDP Act and Rules: Reasonable safeguards (s.8(5)); Rule 6 minimumsWhat to do: Map your controls to Rule 6. Add one-year log retention (Rule 6(1)(e)).
Access, correction, erasureGDPR: Arts 15 to 17DPDP Act and Rules: ss.11 and 12; erasure also on withdrawal or when the purpose ends (s.8(7))What to do: Reuse the workflow. Add the fiduciary and processor sharing list that s.11(1)(b) requires.

Our gap assessment runs this comparison against your own systems. For the consent record itself, see DPDP consent logs. The rest of this guide covers where GDPR habits give the wrong answer.

Which GDPR lawful bases do not exist under DPDP?

GDPR Article 6(1) gives six bases, and SaaS companies lean on contract performance (b) and legitimate interests (f) for much processing. DPDP section 4 allows only two routes: consent, or one of the "legitimate uses" in section 7. There is no legitimate-interests basis and no general contract basis.

The section 7 list is closed:

  • voluntary provision of data for a specified purpose, where the person has not said they do not consent (s.7(a))
  • State functions, benefits and legal disclosures to the State (s.7(b) to (d))
  • compliance with a court judgment, decree or order (s.7(e))
  • medical emergencies, epidemics, disasters and breakdowns of public order (s.7(f) to (h))
  • employment, including safeguarding the employer from loss or liability (s.7(i))

For a SaaS company, the nearest thing to contract performance is s.7(a). It covers data a person gave you voluntarily for a purpose, and it ends once they tell you they do not consent. Whether it fits a given feature is a question for counsel. The safe default is to treat anything outside that list as needing consent.

Product analytics, A/B testing, fraud scoring, model training on customer data and marketing are the purposes to review first. Under DPDP they need either consent or a clear fit in section 7.

What to change:

  • Add a `lawful_basis` field to your data map, with only `consent`, `s7_voluntary`, `s7_employment`, `s7_legal` and similar values. Block a new processing purpose from shipping with the value empty.
  • List every purpose currently on legitimate interests. Decide for each: ask for consent, redesign so it fits s.7, or stop.
  • Keep GDPR and DPDP bases as separate fields. The same purpose can be lawful in the EU and need consent in India.
  • Separate the consent for necessary data from the consent for optional data.

Consent given before the Act's commencement is treated more kindly, and counsel can confirm which records that covers. Under s.5(2) you may keep processing until the person withdraws, but you must send a notice as soon as reasonably practicable. So you need a notice campaign, not necessarily a re-consent one.

How do breach duties differ?

GDPR runs on a risk test. Article 33 requires notice to the authority within 72 hours unless the breach is unlikely to result in a risk to people. Article 34 requires notice to individuals only when the risk is high.

DPDP has no such filter. Under section 8(6) and Rule 7, every personal data breach goes to the Board and to each affected Data Principal. The Rules say:

  • to each affected person, without delay: what happened, the likely consequences for her, the mitigation steps, safety steps she can take, and a contact (Rule 7(1))
  • to the Board, without delay: a description of the breach, including nature, extent, timing, location and likely impact (Rule 7(2)(a))
  • to the Board, within 72 hours, or a longer period the Board allows on written request: updated detail, the broad facts and reasons, mitigation, findings on the person responsible, remedial measures and a report on the notices given to people (Rule 7(2)(b))

The penalty for failing to give breach notice is up to ₹200 crore (Schedule, item 2). Build the process now, even though reports say the Board's members are not yet appointed.

What to change: drop the "is this reportable?" gate for Indian data principals. Your breach runbook needs a path that tags affected records by country, drafts a plain-language notice per person, and sends it through the channel registered with the user. The same incident can still need CERT-In reporting within 6 hours. Our breach runbook guide sets out both clocks together.

Why is children's data treated so differently?

An empty school classroom with rows of small wooden desks and chairs, afternoon sunlight falling across the floor from tall windows, no people.

GDPR Article 8 sets a parental consent age of 16, which member states may lower to 13. It applies when you rely on consent for an online service offered directly to a child. DPDP is stricter in three ways.

  • The age is 18. A child is anyone under 18 (s.2(f)). There is no lower tier. A GDPR age gate set at 13 or 16 leaves a gap for 13 to 17 year olds in India.
  • Consent comes first, for any processing. Section 9(1) requires verifiable consent of a parent or guardian before processing a child's data.
  • Tracking is barred. Section 9(3) prohibits tracking, behavioural monitoring and targeted advertising directed at children. The penalty is up to ₹200 crore.

Rule 10 asks the fiduciary to check, with due diligence, that the person giving consent is an identifiable adult. It can do so using identity and age details it already holds, or details the person gives voluntarily, directly or through a virtual token from an authorised entity, including DigiLocker. The Rules name no single method, so treat these as ways to meet Rule 10 and keep the evidence.

The Fourth Schedule exempts some uses from s.9(1) and (3), subject to conditions. Part A covers healthcare professionals for health services, educational institutions for educational activities or safety, crèches, and school transport. Part B covers purposes such as an email-only account, real-time location for safety, blocking harmful content and ads, and confirming that a user is not a child. That last item means an age gate is itself permitted.

Two cautions for SaaS teams. First, we found no confirmation that an edtech platform counts as an "educational institution". Edtech firms should not assume the exemption applies. Second, the Act does not define behavioural monitoring. An AI tutor that personalises content from a pupil's answers may count as it. We would not call it banned, or assume it is safe.

What to change: add an age signal at sign-up, route under-18 users into a parental consent flow, and switch off analytics SDKs, ad identifiers and personalisation for those accounts by default (auditing mobile SDKs covers the app side). Our guide to verifiable parental consent covers the flow. As of November 2026 we found no age notification under s.9(5) issued by the government.

How do cross-border transfers compare?

GDPR Chapter V is restrictive by default. You need an adequacy decision (Art 45), safeguards such as standard contractual clauses or binding corporate rules (Art 46), or a narrow derogation (Art 49). DPDP is permissive by default. Section 16(1) lets the government restrict transfers to notified countries, and none is notified as of November 2026.

Rule 15 is not that negative list. It says a fiduciary that transfers data abroad must meet any government order on making data available to a foreign State, or to entities that State controls. The negative list is s.16(1). Section 16(2) keeps stricter sector laws in place.

QuestionAnswer
Do you need SCCs to send Indian users' data to your US or EU servers under DPDP?Answer: No DPDP mechanism requires them as of 20 November 2026. The Act applies wherever the data is processed if you serve people in India (s.3(b)).
Do you need SCCs to move EU users' data to India?Answer: Usually. India has no EU adequacy decision (European Commission adequacy page, checked 20 November 2026), so you need an Art 46 safeguard such as SCCs, or a narrow Art 49 derogation.
Can a regulator require data to stay in India?Answer: Yes, through sector rules. RBI's circular RBI/2017-18/153 of 6 April 2018 requires the entire data relating to payment systems to be stored only in India. Its FAQ allows processing abroad if the data is deleted there and brought back within one business day or 24 hours, whichever is earlier.

What to change: keep your GDPR transfer paperwork for EU data, and add a region field per tenant. Hosting Indian customer data in an Indian region can avoid future s.16 restrictions and sector rules. DPDP does not require it. For AI features that send prompts to a model vendor, see cross-border AI APIs under DPDP.

How do rights and response times compare?

DPDP gives four rights: access (s.11), correction, completion, updating and erasure (s.12), grievance redressal (s.13) and nomination (s.14). GDPR adds portability (Art 20), objection (Art 21), restriction (Art 18) and limits on automated decisions (Art 22). DPDP has no portability and no general right to object. You can keep those GDPR features for EU users only.

The access right is also narrower in form. Under s.11 the person gets a summary of the data and processing, and the identities of other fiduciaries and processors it was shared with. Under GDPR Article 15 she gets a copy of the data.

Deadlines differ. GDPR Article 12(3) sets one month, extendable by two. For DPDP, Rule 14(3) requires a published grievance process that responds within a reasonable period not exceeding 90 days. We found no separate statutory deadline for access or erasure requests. Publish the means to make a request and any identifier needed (Rule 14(1)). Under s.13(3) a person must try your grievance route before going to the Board.

What about DPOs, DPIAs and records of processing?

GDPR Article 37 requires a DPO in several situations, Article 35 requires DPIAs for high-risk processing, and Article 30 requires records of processing. DPDP is lighter for most firms.

ItemGDPRDPDP
DPOGDPR: Required in the cases in Art 37DPDP: Mandatory only for Significant Data Fiduciaries, and must be based in India (s.10(2)(a)). Others publish a contact (s.8(9)).
DPIAGDPR: High-risk processing (Art 35)DPDP: SDFs only: annual DPIA and audit reported to the Board (Rule 13(1) and (2)).
Records of processingGDPR: Art 30DPDP: No equivalent. Keep a data map anyway, because you need it for notices, rights and breach scope.
Special categoriesGDPR: Art 9 sets stricter rulesDPDP: No separate sensitive category. Same rules for all personal data.

No SDF has been notified as of November 2026. If your customer base or data volumes might put you in that class, read our note on SDF readiness.

How do the fines compare?

GDPR fines scale with turnover. Article 83 allows up to €10 million or 2% of worldwide annual turnover, and up to €20 million or 4%, whichever is higher, depending on the breach. DPDP uses fixed maximums in its Schedule:

DPDP breachMaximum penalty
Reasonable security safeguards (s.8(5))Maximum penalty: ₹250 crore
Breach notice (s.8(6)) or children's obligations (s.9)Maximum penalty: ₹200 crore each
Significant Data Fiduciary duties (s.10)Maximum penalty: ₹150 crore
Any other provisionMaximum penalty: ₹50 crore

These are ceilings, and the Board sets the amount case by case. No penalties have been reported as of November 2026.

Who is in scope if you sell to India from outside?

Section 3(b) applies DPDP to processing outside India if it is connected with offering goods or services to people in India. GDPR Article 3(2) reaches offering to people in the EU and also monitoring their behaviour. DPDP's text has only the offering limb. A SaaS company that serves people in India should assume it is in scope, and take counsel's view on borderline cases.

Most B2B SaaS companies are Data Processors for their customers. The Act puts its main duties on the Data Fiduciary, but your customers will push them to you by contract. Our guide on whether your SaaS is a Data Processor covers the contract asks. Expect clauses on breach timing, erasure on withdrawal, sub-processors and log retention.

What should an engineering team change first?

  • Tag Indian data principals in your data map and event pipeline, so rules can differ by country.
  • Add a DPDP basis field per purpose and block purposes with none.
  • Rebuild the breach runbook so there is no risk gate, and every affected Indian user gets a notice.
  • Add an age signal and a parental consent path for under-18 users. Suppress tracking SDKs for them.
  • Extend log retention to cover Rule 6(1)(e) and Rule 8(3), at least one year.
  • Update processor contracts with DPDP clauses and a sub-processor list.
  • Offer notices in English or an Eighth Schedule language for users in India.
  • Plan a region option for Indian tenants, if banks or fintechs are in your pipeline.

Start with items 1 to 3. Our implementation service covers the build. The legal reading goes to your counsel.

Sources: Digital Personal Data Protection Act, 2023, ss.2(f), 3, 4, 5, 6, 7, 8, 9, 10, 11 to 14 and 16 and the Schedule (meity.gov.in). Digital Personal Data Protection Rules, 2025, Rules 3, 6, 7, 8, 10, 13, 14 and 15 and the Fourth Schedule (dpbi.gov.in). Removal of Difficulties Order, 2026 (S.O. 5458(E), 5 October 2026). Regulation (EU) 2016/679, Arts 3, 6, 7, 8, 12, 33, 34, 35, 37 and 83 (gdpr-info.eu). European Commission, adequacy decisions page. RBI circular RBI/2017-18/153, 6 April 2018, and RBI FAQ on storage of payment system data. Last reviewed 20 November 2026.

FAQ

Is DPDP the same as GDPR?

No. They share a core of notice, consent, rights, security and breach handling, but DPDP has no legitimate-interests basis, treats everyone under 18 as a child, requires breach notice to every affected person with no risk threshold, and has far lighter transfer rules. A GDPR programme needs edits, not just a re-label.

Does DPDP have legitimate interests like GDPR?

No. Section 4 of the DPDP Act allows processing only with consent or for a closed list of legitimate uses in section 7. There is no general legitimate-interests basis and no general contract-performance basis, so purposes that rely on those under GDPR need consent or a fit within section 7 for Indian data principals.

Do I need SCCs for Indian data under DPDP?

No DPDP mechanism requires SCCs. DPDP allows transfers abroad unless the destination is notified under section 16(1), and none is notified as of November 2026. Sector rules can still require local storage, such as the RBI rule for payment data. GDPR transfer tools still apply to EU data moved to India, which has no EU adequacy decision.

What is the age of consent under DPDP compared with GDPR?

DPDP treats anyone under 18 as a child and requires verifiable parental or guardian consent before processing, with no lower tier. GDPR Article 8 sets 16, which member states may lower to 13, and applies to consent for online services offered directly to a child.

Do I have to report every data breach under DPDP?

Yes. Section 8(6) and Rule 7 require notice to the Data Protection Board and to each affected Data Principal for any personal data breach, with no risk threshold. The Board also gets a detailed report within 72 hours, or a longer period it allows on written request. GDPR notifies individuals only for high-risk breaches.

When do the DPDP duties apply to my SaaS company?

The core duties, including notice, consent, rights, breach notification, retention and erasure, start on 13 May 2027. If you offer goods or services to people in India, the Act applies even if you process data outside India. Start with a data map and the lawful-basis, breach and children's changes.

Find where your GDPR controls fall short of DPDP.