VachanSetu

One record of consent, used by every system.

VachanSetu™ holds a Data Fiduciary's purposes, notices, consents, rights requests and evidence in one place. This page walks through each part, in the order a consent travels.

Start with a list of purposes.

Each purpose names the data it needs, the legal basis, the retention in plain words, any processor that receives the data, and the person who owns it.

The legal basis is either consent or a use under Section 7 of the Act. A Section 7 purpose is shown to the person for information. Consent is not asked for it.

The notice, the widget and every later decision are built from this list. A purpose that is not in it cannot be asked for.

Purpose inventory

3 purposes

PurposeBasisDataProcessor
Account statements by emailConsentEmail addressMail provider
Offers from partner insurersConsentName, phone numberInsurer partner
Tax reporting required by lawSection 7 usePAN, transactionsNone

Illustration with sample data

Privacy notice

Version 3, published

  • English
  • हिन्दी
  • தமிழ்
  • తెలుగు
  • ಕನ್ನಡ
  1. 1What we use your data for
  2. 2The data we use
  3. 3How to withdraw your consent
  4. 4Your rights
  5. 5How to complain to the Data Protection Board

Edited by Compliance. Approved by a second person.

Illustration with sample data

A notice that cannot leave out a required part.

The parts the DPDP Rules ask for are separate fields: data items, purposes, how to withdraw, the person's rights and how to complain to the Board. A fixed template renders them, so a notice with a missing part does not publish.

A published version never changes. Editing starts a new version, and a second person holding the approval privilege must approve it. The last editor cannot approve their own work.

Each version carries English, Hindi, Tamil, Telugu and Kannada. Changing a purpose forces a new version and lists the people who agreed to the old one.

Collection through the widget or your own server.

The widget is a script you add to your page. The API takes the same consent from your backend. Both record a grant or a refusal for each purpose.

  1. Step 1

    Notice shown

    Version 3, in the language the person chose.

  2. Step 2

    Affirmative action

    The person ticks each purpose they agree to. Nothing is ticked in advance.

  3. Step 3

    Record signed

    Your server or the widget sends the choice. The artefact is signed with your organisation's key.

  4. Step 4

    Receipt returned

    A receipt id comes back at once. The same request sent twice records one consent.

Browsers use a publishable key bound to the origins you list. That key can show a notice and record a grant or a withdrawal, and nothing else. Servers use an OAuth client and receive a token that lasts fifteen minutes. Example code is provided in Node and Java.

Read the developer guide

The ledger seals each consent into a block.

A consent is signed the moment it is recorded. Within a minute it joins a block, and the block is chained to the one before it.

Events are canonical JSON, hashed with SHA-256 and signed with an Ed25519 key that belongs to your organisation. Blocks are Merkle trees, so a single receipt can be checked against its block without opening the others.

Once an hour an independent timestamp authority signs a root that covers every block sealed in that hour. Our servers cannot back-date a block past that point.

The database refuses updates and deletes on ledger tables. A scheduled job recomputes the chain and the timestamps, and raises an alert if anything drifts.

How verification works

The layers that protect it

Block explorer

Example Finance

BlockConsentsStateTimestamp
141238SealedAnchored 14:00
141341SealedAnchored 14:00
141412SealedWaiting for the hourly anchor

Illustration with sample data

Systems ask before they process, and hear when a person withdraws.

Two interfaces keep your other systems in line with the ledger.

Decision API

Before using personal data for a purpose, a system asks whether it may. The answer reflects the person's latest choice. One call can carry up to 500 checks.

Every check is logged and kept for at least one year, so you can show which system asked and what it was told.

Decision log

Sample checks

PersonPurposeAnswerReason
ref 7Q2…K9Order updatesAllowGranted on notice version 3
ref 7Q2…K9Partner offersDenyWithdrawn today, 10:42
ref C41…0XPartner offersDenyNever granted

Illustration with sample data

Webhooks

You register endpoints and choose the events each one receives. Every body is signed with HMAC-SHA256 over a timestamp and the body, so a receiver can reject a forgery or a replay.

A failed delivery is retried with increasing gaps for 24 hours, then marked dead and shown to you. An endpoint marked as a processor lets you report that a withdrawal reached that processor.

Deliveries for one withdrawal

Sample

EndpointResultTime
Mailing systemAcknowledged10:42
Insurer partner (processor)Acknowledged10:42
Analytics warehouseRetrying, attempt 310:58

Illustration with sample data

A customer reads her phone at a bank desk while an officer waits.

A preference center under your name

Each organisation gets a preference center carrying its name and colours. A person gets in with a one-time code sent to their email, or through a short-lived link your own backend issues.

They see each purpose they agreed to and the notice version that applied. They can withdraw in no more steps than it took to agree, download a receipt with its proof, raise a rights request and name a nominee.

The page is served from this site's host. Custom subdomains are planned.

Rights requests arrive in one queue, with a clock on each.

Access, correction, erasure, nomination and grievance requests arrive from the preference center or the API. Each starts a clock.

Rights queue

90 days under Rule 14, or a shorter target you set

TypeReceived fromDays leftAssigned toState
AccessPreference center74 daysGrievance officerIn progress
CorrectionAPI61 daysGrievance officerAwaiting information
ErasurePreference center88 daysUnassignedNew
NominationPreference center30 daysComplianceIn progress
GrievancePreference center12 daysGrievance officerIn progress

Illustration with sample data

The grievance officer assigns each request, answers from templates and closes it with a message that names the person's right to escalate to the Data Protection Board. An erasure request creates a record and sends an erasure.requested event to your systems. Carrying out the erasure is still your job in this release.

Evidence an auditor can check offline.

Compliance and the Auditor role export an evidence pack for any date range. A command line verifier, published with the docs, checks a receipt, a range of blocks or a whole pack against your public keys and the timestamp receipts.

The Home screen shows what needs attention: notices awaiting approval, requests by days left, failing webhooks and the result of the last scheduled verification.

Verify a sample receipt in your browser

Evidence pack

One zip, one PDF

  • Consent events, with pseudonyms in place of names
  • Sealed blocks and the independent timestamp receipts
  • The organisation's public keys, with their validity windows
  • Every published notice version, with its translations
  • A README that says how to verify the pack
  • A PDF summary for the committee

Illustration with sample data

Who does what in the product

The organisation administrator handles users and billing. These roles handle consent.

RoleWhat it does
Data Protection OfficerOwns the purpose inventory. Approves notices.
ComplianceEdits notices. Exports evidence.
Product ownerMaintains purposes. Reads opt-in reports.
DeveloperCreates API clients and keys. Manages webhooks. Reads the decision log and uses the sandbox.
Grievance officerWorks the rights queue and sends the closing message.
AuditorReads everything. Exports evidence. Changes nothing.

Every staff role signs in with two-step verification. Each organisation's data is isolated from the others in the database itself. Access in detail

What is planned and not yet built.

These are not in the first release. We list them so you can plan around them.

ItemStatusWhat exists today
Children and guardiansPlannedThe record already has a place for a guardian reference.
Retention and erasure jobsPlannedPhase 1 records the erasure request and sends the event. A job to carry it out is planned.
Re-consent campaignsPlannedPhase 1 lists the people affected by a purpose change.
Connectors to business systemsPlannedWebhooks work today.
Mobile SDKsPlannedThe web widget and the API work today.
Assisted channelsPlannedAgent app, QR, WhatsApp and phone.
All 22 scheduled languagesPlannedFive are in the first release.
Tenant subdomainsPlannedThe preference center is served on the shared host.
Bring your own keyPlannedKeys are held by the application service.
On-premise installationPlanned

VachanSetu is not a registered Consent Manager under Section 6 of the Act. It is a tool that a Data Fiduciary runs for its own consents.

Start in the sandbox.

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.