Breachvaultops • Updated November 2026
📝 Compliance • 9 min read

India's DPDP Rules Are Phasing In: Compliance Costs, Obligations and the 2027 Deadline

India's DPDP obligations carrying the largest penalties are expected to apply from around May 2027. Here's a six-month work plan, indicative budgets and the gaps a GDPR program won't cover.

SPONSORED CONTEXTUAL PLACEMENT
💼
Evaluating Enterprise Deployments in 2026?

Request our confidential total cost of ownership matrix and vendor RFP templates.

Launch Calculator →

What the DPDP Rules 2025 switch on, and when

India's Digital Personal Data Protection Act, 2023 did very little until the Ministry of Electronics and Information Technology (MeitY) notified the DPDP Rules 2025 in November 2025. The Rules set a phased timeline. Most obligations that matter to a data fiduciary are expected to apply about 18 months after notification, around mid-May 2027. If you're planning DPDP Act compliance now, you have roughly six months. That's enough for a focused program. It isn't enough if you still have to discover where your Indian users' data lives.

PhaseApproximate effective dateWhat appliesWho needs to act
On notificationNovember 2025Data Protection Board set up, definitions, Board proceduresLegal and compliance teams: monitoring only
12 monthsNovember 2026Registration framework for consent managersFirms applying to become consent managers, plus fiduciaries planning to integrate with them
18 monthsAround May 2027Notices, consent, security safeguards, breach notification, retention and erasure, children's data, rights handling, significant data fiduciary dutiesEvery organization in scope

Have counsel confirm the exact dates against the Gazette notification. The government can amend the Rules or exempt classes of fiduciaries by notification, and some provisions depend on further notifications.

Advertisement
RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

Who is in scope, including foreign firms and significant data fiduciaries

The Act covers digital personal data processed in India. It also covers processing outside India when that processing is connected to offering goods or services to people in India. There's no revenue threshold and no general exemption for small businesses. The government can exempt specific classes, such as certain startups, but don't plan around an exemption that hasn't been notified.

For foreign companies, the first question is your role. Say you're a UK payroll SaaS processing employee data for Indian clients. You're probably a data processor. The statutory duties fall on your client, the data fiduciary, who will pass them to you by contract: security controls, breach alerts, deletion on instruction. Now say you're a Singapore e-commerce brand selling directly to Indian consumers. You're a fiduciary and carry the full set of obligations, even with no Indian entity.

Significant data fiduciary obligations

The government designates significant data fiduciaries (SDFs) by notification. It looks at the volume and sensitivity of the data, the risk to data principals, and wider concerns such as sovereignty and public order. Large consumer platforms, fintechs, health-data processors and big telecom or e-commerce operators should assume they could be designated. The extra obligations are:

  • A Data Protection Officer based in India who reports to the board or an equivalent governing body
  • An independent data auditor
  • A data protection impact assessment and an audit every year, with key findings reported to the Board
  • Due diligence showing that algorithmic software used on personal data doesn't put data principals' rights at risk
  • Possible restrictions on moving specified categories of personal data out of India, based on a government committee's recommendations

That last item is a real architecture risk for multinationals that serve Indian users from global regions.

Where a GDPR program carries over and where it falls short

If you already run a GDPR program, you can reuse a large share of it: the data inventory, vendor contracts, security controls and incident response. The gaps are the ones that cause trouble, because teams assume equivalence and don't check.

AreaGDPR positionDPDP positionReuse verdict
Lawful basisSix bases, including legitimate interestsConsent, or a short list of "certain legitimate uses." There is no general legitimate-interest basisFalls short. Revisit every processing purpose that relies on legitimate interests
Breach notificationNotify the regulator within 72 hours if there's a risk; notify individuals only if the risk is highNotify the Board without delay, with a detailed report within 72 hours, and notify affected individuals with no risk thresholdPartial. Runbooks need a step for notifying individuals in every case
ChildrenMember states set the age between 13 and 16Under 18; verifiable parental consent; limits on tracking and targeted advertisingFalls short for consumer products
NoticesPlain languageStandalone and itemized, available in English or any of the 22 languages in India's Eighth SchedulePartial. Budget for translation
Records and inventoryArticle 30 recordsNo identical requirement, but you can't comply without oneReusable
Cross-border transfersAdequacy decisions, SCCs, BCRsAllowed unless the destination is restricted by notification; SDFs may face localizationMostly simpler, but watch for restriction notices
LoggingNot prescribedKeep logs and related personal data for at least one yearNew. This affects storage costs

The lawful-basis gap does the most damage. Analytics, fraud scoring and marketing that rely on legitimate interests in Europe will usually need consent in India. That pushes the work into product and UX, not just policy.

DPDP compliance cost: indicative budgets by company profile

The figures below are typical 2026 market ranges in USD for first-year spend. They vary widely by contract, vendor and whether you buy from Indian or global firms. Indian advisory firms are often noticeably cheaper than global firms for comparable work. Get quotes before you commit to a budget.

ProfileTypical first-year spendMain cost drivers
Foreign B2B SaaS with modest Indian usage and an existing GDPR program$15,000 to $60,000Gap assessment, contract updates, breach runbook changes
Indian SME (20 to 200 staff) with no prior privacy program$25,000 to $100,000Data mapping, notices, consent capture, security baseline, external counsel
Mid-size consumer-facing company (Indian or multinational)$100,000 to $400,000Consent management platform, erasure workflows across legacy systems, translations, rights-request tooling
Likely significant data fiduciary$500,000 to $2 million or moreIndia-based DPO, independent auditor, annual DPIA, algorithmic reviews, possible localization changes

After the first year, ongoing costs usually settle at a fraction of first-year spend, mostly platform licenses, audits and staff time.

Worked example (hypothetical)

Say a 120-person e-commerce company based in Dubai has about 400,000 Indian customers and a basic GDPR-style program. A rough build might be: data mapping, $15,000 to $25,000; consent management platform, $12,000 to $40,000 a year; notices translated into Hindi and two regional languages, $3,000 to $8,000; legal review of purposes and contracts, $20,000 to $40,000; breach runbook plus a tabletop exercise, $8,000 to $15,000; erasure automation across the order system and CRM, $15,000 to $35,000. That adds up to roughly $73,000 to $163,000. Erasure is the line most companies underestimate.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

A six-month work plan to the May 2027 deadline

Work backward from mid-May 2027 and leave a four-week buffer for testing. This sequence fits most mid-size organizations:

  1. December to January: scope and inventory. List every system, vendor and data flow that touches personal data of people in India. Decide whether you're a fiduciary or a processor for each flow. Mark children's data and any processing that relies on legitimate interests.
  2. January: legal basis decisions. For each purpose, choose consent or one of the legitimate uses. Retire purposes you can't justify. This step causes the most product changes, so do it early.
  3. February: notices and consent. Draft standalone, itemized notices. Build consent capture so withdrawing is as easy as giving consent. Choose translation languages based on your actual user base.
  4. February to March: security safeguards. Confirm encryption, masking or tokenization, access controls, and log retention of at least one year. Make sure processor contracts require the same.
  5. March: breach response. Add steps for the Board report and for notifying individuals. Pre-draft those notices. Run one tabletop exercise on a realistic scenario, such as a compromised vendor API.
  6. March to April: rights and retention. Stand up handling for access, correction, erasure and grievances, with responses to grievances within 90 days. Set retention schedules. If you're a large e-commerce, gaming or social media platform covered by the Rules' inactivity-erasure provisions, build the three-year deletion trigger and the 48-hour advance warning to users.
  7. April to May: test, evidence and sign-off. Run test rights requests, record your decisions, and brief the board.

Likely SDFs should add DPO appointment, auditor selection and the first DPIA to the January to March window. Independent auditor capacity may be tight in early 2027, so shortlist early.

Consent managers in India, tooling choices and red flags

Two things get confused. A consent manager in India is a specific regulated entity: an Indian company registered with the Data Protection Board, subject to a minimum net-worth requirement and duties of interoperability and neutrality. Individuals use it to give, manage and withdraw consent across many fiduciaries. A consent management platform (CMP) is software you license for your own website and apps. Examples include OneTrust, Securiti, TrustArc and Usercentrics, along with several India-focused vendors.

You don't have to integrate with a registered consent manager. You do have to honor consent and withdrawals that arrive through one. For most companies, the practical answer for 2027 is a CMP that can receive consent signals from consent managers through APIs. In sectors where account-aggregator-style interoperability is already common, such as financial services, expect integrations to become standard.

Red flags when evaluating vendors

  • The vendor calls the product "DPDP certified." No such certification exists.
  • The notice templates are GDPR notices with the regulator's name swapped, with no itemized purposes and no language options.
  • There's no audit trail of consent and withdrawal you could produce for the Board.
  • Data residency choices are vague, which is risky if you could be designated an SDF.
  • Pricing is per domain or per user and climbs sharply as Indian traffic grows. Model three-year cost at two to three times current volume.

Penalties, insurance and the decision to make this quarter

The Act's schedule sets maximum penalties. The largest, up to INR 250 crore (roughly USD 28 to 30 million at recent exchange rates), is for failing to take reasonable security safeguards. Failing to notify a breach, and breaching the obligations on children's data, each carry up to INR 200 crore. The Board weighs severity, duration, repetition and mitigation, so a documented good-faith program matters.

On insurance: cyber policies sold in India, the UK, Singapore and elsewhere usually cover breach response, notification and forensic costs. Whether they cover regulatory penalties depends on the policy wording and on whether the penalty is legally insurable where the policy is issued. Practice differs between jurisdictions, and Indian practice under the DPDP Act is untested. Ask your broker in writing whether DPDP fines and the cost of notifying individuals are covered, and whether any sublimit applies. Have a licensed insurance professional and Indian counsel review the answer.

Here's the decision rule. If you process personal data of people in India and have no complete data inventory, start one this month with a named owner and a budget. If you already have an inventory from a GDPR program, give yourself two weeks to scope fixes for the lawful-basis and breach-notification gaps. Those two drive the largest exposure and take the longest to fix.

Quick Answers

Does the DPDP Act apply to a foreign company with no office in India? +
Can we rely on our GDPR legitimate-interest assessments in India? +
Do we need to appoint a Data Protection Officer? +
What is a realistic DPDP compliance cost for a mid-size company? +
BR
Breachvaultops Editorial Team
Independent research desk
Guides on Breachvaultops are produced by our editorial team. Pricing, features and regulations change often - confirm details with the vendor or a licensed professional before making decisions.
SPONSORED 2026 Vendor Pricing Benchmarks: Model exact seat pricing, setup fees, and ROI across our verified database.
Launch Calculator →