PracticeStacks
All guides
DPDP ComplianceComplianceSettings

DPDP compliance

Keep a record of why you hold each client's personal data, ask for consent where it is needed, and record withdrawals.

Open DPDP Compliance2 min readChecked 8 Nov 2026

India's data protection law expects you to say, for every piece of a client's personal data you hold, why you hold it and on what legal footing. This screen keeps that record and builds most of it for you from your signed proposals.

How it works

  1. Let it fill itself. When a client approves a proposal, the purposes it introduced are recorded, dated from the signing. An approved amendment that adds a service adds a new purpose, dated from when the amendment was sent. The client sees what their data will be used for on the same page where they approve.
  2. Read the register. Open the Legal Basis Register tab. Each row is one purpose for one client and its legal footing. Counters above show entries recorded, notices issued, consents granted and consents withdrawn.
  3. Add an entry by hand for anything the system did not create, such as a mailing list you keep: pick the client, write the purpose in plain words and choose the basis it rests on.
  4. Ask for consent where it is needed. Filing returns, payroll and audit records rest on legal obligation and need no consent. Optional purposes such as marketing, referrals or publishing a testimonial do: click Ask for Consent on that row. The client confirms on a link, and the time and device details are stored as evidence.
  5. Record a withdrawal. A client may withdraw consent at any time. Record it and stop the processing it covered. It shows in the counters and in the Consent History tab, next to the original consent.
The DPDP legal basis register. Rows for filings rest on Sec 7(c) Legal Obligation and need no consent; rows for marketing messages need Sec 6 Consent, each with an Ask for Consent button (one marked).

Tips

  • Consent must be a real choice: the client still gets the service if they decline. Keep the consent tick box on a proposal optional.
  • Consent cannot be asked on a purpose that rests on legal obligation; the system refuses it.
  • A consent request needs a client contact with an email or phone number.

Common questions

Do I have to fill this in?

Most of it fills itself from signed proposals. Add entries by hand only for processing outside your engagements.

A client asked what data we hold on them. Where do I look?

Filter the register to that client. It lists every purpose recorded, with dates.

Record the withdrawal and stop using their testimonial. The register keeps both the consent and the withdrawal, which proves you acted on it.

More guides

Every other part of the product, the same way.

See all