Does DPDPA apply to you?

Five questions. If you answer yes to any one of them, DPDPA applies to your organisation.

  1. Does your website have a contact form, enquiry form, appointment booking, or any form that collects a name, phone number, or email address? Yes → DPDPA applies
  2. Do you use Google Analytics, Facebook Pixel, or any third-party tracking tool on your website or app? Yes → DPDPA applies
  3. Do you collect Aadhaar, PAN, passport, driving licence, or any government ID from customers or employees? Yes → DPDPA applies
  4. Do you send marketing or communication messages to customers via email, SMS, or WhatsApp? Yes → DPDPA applies
  5. Do you employ people — permanent, contractual, or intern — in India? Yes → DPDPA applies

If you answered yes to even one question — and almost every Indian business does — your organisation is in scope for DPDPA. The guide below explains what that means and what you need to do.

DPDP Guide

The DPDP Act in plain language

India’s Digital Personal Data Protection Act, 2023 sets rules for how organisations handle digital personal data. This page is a short map of the ideas your product, ops, and legal teams use in the same conversation — not a substitute for professional advice.

Who the law speaks to

If your organisation decides why and how personal data is processed — and that processing happens digitally — you are usually in scope. There are statutory exceptions and nuances; your counsel confirms fit for your case.

  • Applies to processing of digital personal data where it relates to individuals in India (subject to how the Act and rules apply).
  • “Personal data” means data about an identifiable person — name, phone, email, IDs, and much more.

Two roles to remember

Almost every workflow boils down to the relationship between the person and the organisation that controls their data.

Data Principal and Data Fiduciary The person shares data with the organisation; the organisation must meet duties under the law. Data Principal The individual Data Fiduciary Your organisation

You owe that person clarity, lawful handling, and a way to exercise their rights.

Four things to operationalise

Teams move faster when they group work into four buckets (same framing as elsewhere on this site):

  • Tell Be transparent — notices, purposes, and who you share with.
  • Permission Where the law requires it, get valid consent and honour withdrawal.
  • Control Make rights requests (access, correction, erasure, grievance, etc.) workable and traceable.
  • Report Be ready for incidents and scrutiny — evidence, not panic.

Notice (being upfront)

Before or at collection, people should understand what you collect, why, how long you keep it, and how they can exercise rights. Notices should be easy to find — not buried in links nobody opens.

Rights of the individual

The Act recognises several rights in principle — such as access, correction, erasure, grievance redressal, and nomination — with details and limits in the statute and rules. Operationally: define who handles requests, how fast you respond, and how you prove what you did.

A minimal discipline loop for any rights channel.

Security & data breaches

You are expected to take reasonable security safeguards. If a breach hurts individuals, the law contemplates notification to the Data Protection Board of India and, in some situations, to affected people — timelines and content follow regulatory rules. Have a playbook before you need it.

Penalties & urgency

The Act allows for significant penalties for serious failures (including up to ₹250 crore per incident in the statute’s upper range for certain violations). Boards and regulators care whether you can show process and records, not only policy PDFs.

Industry talk often cites May 2027 as a milestone for fuller compliance readiness — verify what applies to your sector; this page does not set your legal deadline.

Disclaimer: Privigo is not a law firm. This guide summarises common talking points only. For obligations, contracts, and regulator engagement, work with qualified Indian legal counsel.

How Privigo helps you comply

DPDPA compliance has two layers. The public-facing layer — what your website and app collect — can be fixed in 7 days. The full-organisation layer — employees, third-party processors, internal systems — follows on your timeline.

DPDPA Ready

Public-facing compliance in 7 days

Cookie consent, AI privacy policy, compliant forms, and a Data Principal Portal — deployed across your website and mobile app in 7 working days. Plus a publicly verifiable DPDPA Ready badge your clients can check.

See what's included
DPDPA Compliant

Full organisation compliance in 6–8 weeks

Everything in DPDPA Ready plus employees, third-party processor agreements, system integrations, and a full organisation audit trail. For when RBI audits, enterprise RFPs, or DPDPA Compliant procurement requirements need deeper proof.

See what's included
Get free Gap Analysis

Your Gap Analysis report maps your gaps. A consultant call scopes the right tier and price for your organisation.