What is a Purpose Registry in DPDP?

A Purpose Registry is one public list of every reason your business collects personal data, with the data you collect for each reason. Instead of one long privacy policy that mixes everything together, a registry gives each purpose its own clear entry, so people can see exactly what they are agreeing to and why.

Under India’s DPDP Act, consent follows the purpose, not the page. A registry is where those purposes live.

Why a registry matters

DPDP expects a business to tell people what data it collects, why it collects it, and how they can change their mind. It also expects consent to be specific. A person should be able to say yes to one purpose and no to another.

That only works if each purpose is written down clearly in one place. Without a registry, purposes get scattered across forms, banners and policy pages, and they drift out of sync.

What goes in a registry entry

Each entry answers a few plain questions:

• What is the purpose? A short name people understand, such as "Respond to your demo request".
• Why do you ask? One or two plain sentences.
• What data do you collect for it? Names of the data, such as email, name, company.
• What is the basis? Does the person opt in, or did they hand over the data for this one thing themselves?
• How do they withdraw? One clear way, and it works as easily as saying yes.

Example entries

Purpose	Data collected	Basis
Respond to your demo request	Name, work email, company	Given for this purpose (notice only)
Send product updates	Email	Opt-in consent
Understand how the site is used	Analytics cookie identifiers	Opt-in consent
Share with partners	Name, email	Opt-in consent

Each row is its own purpose with its own choice. Nothing is bundled.

Purpose Registry vs privacy policy

A privacy policy explains your overall approach. A Purpose Registry is the precise list behind it.

	Privacy policy	Purpose Registry
Format	Long document	Structured list, one entry per purpose
Answers	How we handle data in general	What exactly we collect, and why, per purpose
Linked from forms	Rarely	Yes, each consent has a "Why we ask" link
Changes	Edited as a whole	New version whenever a purpose changes

You still keep your policies. The registry makes the purpose-level detail easy to show and easy to keep current.

Versions and languages

A registry changes as your business does. A good one:

• Keeps versions. Each change creates a new version, so every consent can point to the exact version the person saw.
• Waits for approval. A new purpose or a wording change stays in draft until you publish it, so the public page never shows half-finished text.
• Speaks your customer’s language. Each version can be translated and approved language by language, with English always available.

How to build one in four steps

1. List your purposes. Go through your forms, banners and emails. Write down every reason you collect data.
2. Write each in plain words. What, why, which data.
3. Mark the basis. Opt-in consent, or given for this one purpose.
4. Publish and link. Put it on your trust page and link to it from every form and banner.

How pactbase handles the Purpose Registry

In pactbase, you define purposes once under Consent. They flow into a versioned Purpose Registry that you publish on your Trust Center. The registry has two sections: Cookies, for your banner categories, and Data we collect, for your consent purposes.

When you add or change a purpose, pactbase opens a new draft version. Nothing reaches the public page until you publish it. Each consent in the Consent ledger records the notice version the person saw.

Start free or book a demo to see it with your own purposes.

Frequently asked questions

What is a Purpose Registry?

It is a single, public list of every reason a business collects personal data, with the data collected for each purpose.

Is a Purpose Registry the same as a privacy policy?

No. A privacy policy explains your overall approach. A registry lists each purpose precisely, and consent links back to it.

Do I need one if I only use a cookie banner?

A cookie banner covers cookies. If you also collect data through forms, a registry keeps every purpose, cookie or not, in one place.

How often should I update it?

Whenever you add, remove or change a purpose. Each change becomes a new version.

Does it need to be in more than one language?

It helps. People should be able to read what they agree to in a language they know, and pactbase supports all 22 scheduled languages.