About the product
What PIEDAP Consent is, how it relates to the DPDP Act, what it leaves to your business and who uses it.
Short answers about what the product is and what stays with you. Each one links to the page that explains it.
About the product#
What is PIEDAP Consent?#
It is a tool for asking people for consent, recording what they answered and proving it later. It shows a notice on your website and gives your app the notice to show. It keeps a record of every answer and tracks rights requests against a deadline. It tells your other systems when someone changes their mind.
More: What is PIEDAP Consent.
Is it the same as DPConsent?#
Yes. The product appears as DPConsent in the PIEDAP platform menu and on the India site. These pages call it PIEDAP Consent. Both names mean the same product.
More: What is PIEDAP Consent.
Is PIEDAP Consent a Consent Manager?#
It does a different job. In the DPDP Act, a Consent Manager is a company registered with the Data Protection Board of India. It lets people manage their consents across many businesses in one place. Registration for that role opens on 13 November 2026, under Rule 4 of the DPDP Rules, 2025.
PIEDAP Consent serves you, the Data Fiduciary. It can accept consent and withdrawals people send you through a registered Consent Manager, sealed into your records like any other.
More: Accept consent from a Consent Manager.
Does using it make us compliant with the DPDP Act?#
No tool can do that alone. The product helps with the parts a tool can do. It shows a notice with the items the Act lists, keeps records that can serve as proof, and tracks rights requests against their deadline.
You still decide your purposes and their legal basis. You act on withdrawals in your own systems, and you send the messages the Act asks you to send. Ask your counsel how the Act applies to you.
More: DPDP duties for notice and consent.
Is it only for India?#
No. A region rule decides which form each country sees and under which law. The same property, a site or an app, can serve a DPDP notice in India and a GDPR banner in Europe.
More: Choose regions.
Does it work in mobile apps?#
Yes. In an iOS or Android app, your own screen shows the wording you published, and the SDK records the answer.
More: Record consent in a mobile app.
What it leaves to you#
Does it give legal advice?#
No. You decide your purposes, the legal basis for each and the wording, with your own counsel. The checks in the product cover only what it can see.
More: Run the DPDP check.
Does it send email or SMS to our customers?#
No. You send these yourself:
- the confirmation link for a rights request
- the double opt-in email
- a breach notice
- a warning before erasure after inactivity
- the links of a notice campaign
The product gives you the link, the draft text or the date. For a notice campaign it gives you one link per person, as a file or through a webhook, and your own mailer or SMS gateway sends them.
More: Send a notice to existing customers.
Does it stop processing in our other systems?#
Not by itself. Your systems ask the consent check before they process, or act on the consent.withdrawn webhook.
When a person known by an email, phone number, user id or device id withdraws, that webhook lists instructions to stop. There is one, with a due date, for each registered Data Processor the person had allowed. An erasure lists instructions to erase. You pass them on, and the Processors page tracks what each processor reported.
More: Check consent before you process and Pass instructions to processors.
Can we import consent from a spreadsheet?#
Yes. In Records, Import CSV reads a file of up to 100,000 rows in your browser, checks every row first, then writes the records. Your server can also send each row with its date. An import never replaces a newer answer, a withdrawal or an erasure.
More: Import consent from a file.
Does it correct personal data we hold?#
No. A correction request is tracked in the console with its deadline. Your team makes the correction in your own systems, then closes the request with Mark completed.
More: Handle a request.
Who uses it#
Who in our company needs to be involved?#
Usually a privacy lead or Data Protection Officer, a marketing or content lead, a developer, a support agent, and IT or operations. In a small company one person may hold several of them.
More: Reading lists by role.
Can we limit what each person may do in the console?#
Not inside a project. Access is given per project. Anyone who can open a project can use every function of the console in it, including publishing, export, erasure and keys.
Ask your platform administrator to give a project only to the people who need it. Every change made in the console is written to the audit log, with who made it and when.
More: Access and roles.
Can we send the audit log to our SIEM?#
Yes. A collector pulls the log with a key that holds audit:read. On your own deployment, each entry is also a JSON line on standard output, and you can download any range of days. The log is append-only in the database. It is not a connector, and failed sign-ins are logged by PIEDAP IAM.
More: Send the audit log to your SIEM.
Can a second person approve what we publish?#
Yes. Turn on Require a second person to publish forms in Project settings. Each publication then waits until another person approves it. The person who asked cannot approve their own request.
More: Approve a publication.