Decide the purposes and the legal basis for each
VachanSetu records your decision. It cannot tell you whether a purpose rests on consent or on a Section 7 use.
The DPDP Rules were notified on 13 November 2025. The consent, notice and rights obligations apply to Data Fiduciaries from 13 May 2027.
This page is our reading of the Act and the Rules. It is not legal advice. Please confirm it with your counsel.
Rows marked planned are not in the first release. Section numbers refer to the Act and rule numbers to the Rules.
| Obligation | Source | How VachanSetu serves it | Status |
|---|---|---|---|
| Itemised notice: the data, the purposes, how to withdraw, the person's rights, how to complain to the Board | Section 5, Rule 3 | The notice builder holds the Rule 3 parts as structured fields, so a notice cannot be published without them. Notices | In the first release |
| Notice in English or any Eighth Schedule language | Section 5(3) | Notices and the preference center in English, Hindi, Tamil, Telugu and Kannada. Other languages are planned. Notices | In the first release for 5 languages. The rest are planned |
| Consent that is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action | Section 6(1) | The collection widget and API show one unticked box for each purpose and an explicit button. Refusals are recorded too. Collection | In the first release |
| Withdrawal as easy as giving consent, and processing stops | Section 6(4) to 6(6) | The preference center takes two steps, the same as giving consent. The decision API then answers deny, and signed webhooks reach each system and processor. Preference center | In the first release |
| The fiduciary must be able to prove notice and consent | Section 6(10) | A signed ledger, receipts with inclusion proofs, and an evidence pack an auditor can verify offline. Ledger | In the first release |
| Processing without consent for certain legitimate uses | Section 7 | The purpose inventory records the legal basis. Section 7 purposes are shown for information and consent is not asked. Purpose inventory | In the first release |
| Erasure once the purpose is served or consent is withdrawn | Section 8(7), Rule 8 | An erasure request is recorded and announced to your systems as an event. Automated retention and erasure jobs are planned. Rights and grievance | Partly in the first release. Automated jobs are planned |
| Logs and records kept for at least one year | Rules 6 and 8 | The ledger and the decision log hold the record of each consent and each check. Decisions | In the first release |
| Verifiable parental consent, and guardians | Section 9, Rules 10 and 11 | Planned. The record format already reserves a guardian reference. | Planned |
| Access, correction, erasure, grievance and nomination | Sections 11 to 14, Rule 14 | A rights and grievance queue. A person raises a request from the preference center or you enter one through the API. Rights and grievance | In the first release, in a basic form |
| Grievance answered within 90 days | Rule 14 | Every request carries a clock, with a lower target that you can set. Rights and grievance | In the first release |
| Breach report to the Board | Section 8(6), Rule 7 | Not part of VachanSetu today. | Planned |
| Impact assessment and audit for Significant Data Fiduciaries | Section 10, Rule 13 | Not part of VachanSetu today. | Planned |
The product records your decisions and applies them. Making them is still your job.
VachanSetu records your decision. It cannot tell you whether a purpose rests on consent or on a Section 7 use.
The notice builder requires every part of Rule 3. The words about your data and your purposes are yours, and they must be true.
A deny changes nothing until your systems ask for a decision and obey it. Webhooks and the decision API give you the means. Wiring them in is your engineering work.
The queue tracks each request and its clock. Your grievance officer decides the answer and sends it.
VachanSetu is a consent management platform. It is not a registered Consent Manager under Section 6 of the Act.
No part of the Government, the Ministry of Electronics and Information Technology or the Data Protection Board has approved or certified it. Nothing on this site says otherwise.
Whether your use of it satisfies the Act is a question for you and your counsel. The platform page describes each feature so that counsel can judge it.
For readers who know privacy law but are new to this Act's vocabulary.
The sandbox is free and runs in test mode. Build your purpose inventory, publish a notice and record a first consent before you speak to anyone.