Know what’s on your site before a plaintiff’s firm does
A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.
Most multinationals that reach Indian customers already run a privacy program built for the GDPR and a growing patchwork of US state laws. India’s Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 will not let them simply copy that program across, but they will not force a rebuild either. A large share of the work, from notices to vendor contracts to breach playbooks, carries over with adjustments. The rest is genuinely Indian: a consent-first model with no legitimate-interest basis, breach notices to every affected person, parental consent for everyone under 18 and a regulator with power to impose penalties of up to ₹250 crore. With the main obligations starting on 13 May 2027, the next six months are the practical window to map one program onto the other.
TL;DR
- Most duties for businesses under India’s DPDP Act and Rules apply from 13 May 2027, eighteen months after the Rules were notified on 13 November 2025.
- Security, processor contracts, rights handling and breach response from a GDPR or US state program can be reused, but they need Indian timelines, notice content and record-keeping added.
- India has no legitimate-interest basis, requires breach notice to the Board and every affected individual, treats everyone under 18 as a child and has no “monitoring” trigger for foreign companies.

The vocabulary, translated
The DPDP Act uses its own terms, and most of them have a close GDPR cousin. Getting the translation right early prevents a lot of confusion in policy documents and contracts.
- Data fiduciary is the person that, alone or with others, decides the purpose and means of processing. Read it as “controller,” with a name that signals a duty of trust.
- Data principal is the individual the data relates to. For a child it includes the parent or lawful guardian, and for a person with a disability it includes her lawful guardian.
- Data processor processes data on behalf of a fiduciary, much like a GDPR processor.
- Significant data fiduciary (SDF) is a fiduciary or class the central government notifies based on factors such as the volume and sensitivity of data, risk to individuals, and national interests. SDFs carry extra duties.
- Consent manager is a registered intermediary that lets individuals give, manage, review and withdraw consent across businesses. Using one is optional.
- Data Protection Board of India is the adjudicating body that handles breach intimations, complaints and penalties.
Two scope points stand out for GDPR teams. The Act covers only digital personal data, whether collected digitally or digitised later, and it excludes data a person has made publicly available herself. It also has no separate category of sensitive or special category data. Every piece of personal data is treated the same way, with children’s data the notable exception. For a fuller primer, see our overview of the DPDP Act.
Does the law reach you? Three common set-ups
Section 3 applies the Act to digital personal data processed within India and to processing outside India “in connection with any activity related to offering of goods or services” to people in India. How that plays out depends on how a company is present in the country.
- A website that people in India can simply reach. If processing happens outside India and the company is not offering goods or services to people in India, the text of Section 3 does not bring it into scope. Unlike Article 3(2)(b) of the GDPR, the Act has no separate trigger for monitoring behaviour, so analytics on stray Indian visitors alone is not an obvious hook. Companies should still check whether pricing in rupees, Indian shipping or local-language pages point to offering services.
- A company offering goods or services to people in India from abroad. The Act applies to the processing connected with that offering, wherever it takes place. There is no requirement to appoint a local representative of the kind a GDPR EU representative provides, though an SDF must appoint a data protection officer based in India.
- A company with an Indian subsidiary. The subsidiary processes data within India, so its processing is in scope in full, including employee data. Section 17(1)(d) exempts most obligations where a company based in India processes data of people outside India under a contract with a foreign party, which matters for shared service centres. The security duty in Section 8(5) still applies to that work.
What carries over from your GDPR and US programs
The parts of a mature program that tend to transfer with modest edits:
- Security controls. Rule 6 lists minimum safeguards such as encryption, masking or tokenisation, access control, logging and monitoring, backups and contract clauses with processors. A program built on GDPR Article 32 or the security duties in US state laws will cover most of this. The Indian addition is keeping relevant logs and personal data for one year to support detection and investigation.
- Processor contracts. Section 8(2) allows a fiduciary to use a processor only under a valid contract, and the fiduciary stays responsible for what the processor does. Existing data processing agreements can be extended with Indian security, erasure and breach-cooperation terms.
- Rights handling. Indian individuals get rights to a summary of data and processing, the identities of other fiduciaries and processors that received their data, correction, completion, updating and erasure, grievance redressal and nomination. A GDPR rights workflow handles most of these; nomination, which lets a person name someone to act for her on death or incapacity, needs a new path.
- Breach response. Incident detection, triage and forensic processes carry over. What changes is who you notify and when.
- Accountability. Records of processing, retention schedules and governance committees are not mandated in GDPR form, but they are the easiest way to show the “technical and organisational measures” Section 8(4) requires.
What is India-specific
- Consent first, narrow exceptions. Section 4 allows processing only with consent or for “certain legitimate uses” listed in Section 7. Those cover situations such as data a person voluntarily provides for a specified purpose, legal obligations, medical emergencies, disasters and employment. There is no equivalent of GDPR contract necessity as a general basis and no balancing test like legitimate interests. Fraud analytics, product improvement and many marketing uses will need consent or a clear fit within Section 7.
- Notice content. Rule 3 requires a standalone notice in plain language with an itemised description of the data, the specified purposes, and links for withdrawing consent, exercising rights and complaining to the Board. Withdrawal must be as easy as giving consent.
- Breach notice to everyone affected. Section 8(6) and Rule 7 require notice to the Board and to each affected individual, without delay, with no harm threshold. The Board gets an initial description and a detailed report within 72 hours. GDPR, by contrast, asks for notice to individuals only when there is a high risk to them.
- Children under 18. Section 9 and Rule 10 require verifiable consent of a parent before processing any child’s data, with checks that the parent is an identifiable adult, and ban tracking, behavioural monitoring and targeted advertising directed at children. GDPR lets member states set the age between 13 and 16, and COPPA’s parental consent rule covers children under 13.
- Response timelines. Rule 14 sets a maximum of 90 days for responding to grievances, which must be published. Rule 9 requires contact details for the DPO or a responsible person in every rights response.
- Erasure and retention. Rule 8 sets three-year inactivity periods after which large e-commerce, online gaming and social media platforms must erase data and requires a 48-hour warning before erasure. Separately, processing logs must be kept for at least a year.
- SDF duties. Notified SDFs need an India-based DPO, an independent data auditor, an annual DPIA and audit reported to the Board, due diligence on algorithmic software and compliance with any data localisation list the government sets.
- Penalties. The Schedule to the Act allows penalties of up to ₹250 crore for failing to take reasonable security safeguards, up to ₹200 crore for breach-notice or children’s-data failures, up to ₹150 crore for SDF failures and up to ₹50 crore for other breaches.
Transfers abroad are permitted unless the government restricts a destination by notification, subject to any sectoral law with stricter rules. Our analysis of cross-border transfer impacts covers that area in more depth.
A six-step adaptation plan
- Confirm scope by entity. List each legal entity, website and app that touches people in India and classify it under the three set-ups above.
- Re-paper the lawful basis. For every Indian processing activity currently justified by legitimate interests or contract necessity, decide whether it fits a Section 7 legitimate use or needs consent.
- Write Indian notices. Build Rule 3 notices that stand on their own rather than pointing to a global privacy policy, with itemised data and purpose descriptions.
- Tune the breach playbook. Add a Board notification track with a 72-hour detailed report and a mandatory notice to all affected individuals through their account or registered contact.
- Rebuild age gating. Products that allow users aged 13 to 17 need a parental consent flow and must switch off tracking and targeted ads for them.
- Extend contracts and logs. Update processor agreements, set one-year log retention and publish grievance and DPO contact details.
Frequently asked questions
Does GDPR certification or an adequacy finding help in India?
No formal recognition exists. GDPR compliance is useful evidence of good practice, but the Board will judge conduct against Indian requirements.
Do we need consent from employees?
Section 7(i) covers processing for employment purposes and for protecting the employer from loss or liability, so many HR uses can rely on that legitimate use rather than consent.
Is the old IT Act regime still in force?
Yes, for now. Section 43A of the Information Technology Act, 2000 stays in force until the provision of the DPDP Act that removes it starts on 13 May 2027.
What happens if consent is challenged?
Section 6(10) puts the burden on the fiduciary to prove that notice was given and consent obtained properly, so consent records need to be kept and easy to retrieve.
Reuse the engine, rewire the controls
A GDPR program gives a company most of the machinery India expects: inventories, contracts, security and a rights desk. What it does not supply is India’s logic, which starts from consent, notifies everyone when things go wrong and protects every teenager as a child. Teams that treat India as a configuration of their existing program, rather than an afterthought or a fresh build, will reach May 2027 with fewer surprises.
Put this into practice
Turn privacy guidance into working controls.
Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.