VachanSetu

Consent management for the DPDP Act

Proof that your customer said yes.

VachanSetu™ keeps a signed record of every consent your customers give, in a ledger that anyone can check. When a customer changes their mind, every system using their data is told.

The sandbox is free and runs in test mode.

Example Finance

Sample receipt

Consent receipt, 20 Nov 2026

Newsletter
Granted
Order updates
Refused
Notice shown
Version 1, English
Artefact
0b1c2d3e-0000-4000-8000-000000000001
Verified by VachanSetu

Each span is a sealed block of consents, chained to the block before it. Sample data.

You should not have to take our word for it.

A consent record only counts as evidence if someone outside your business can test it. So every record here can be tested by anyone, without asking us.

A record anyone can verify

Each consent is signed with your organisation's key and sealed into a block within a minute. The blocks are chained, and an independent authority timestamps them every hour. An auditor can check a receipt without asking us.

How verification works

A withdrawal that stops the processing

Once a person withdraws, the next decision check answers deny. Each connected system and processor receives a signed message, and you can see which of them has acknowledged it.

Decisions and webhooks

Consent records kept in India

The database, its backups and the archive are hosted in India. The ledger holds a pseudonym for each person. Names and contact details sit in a separate vault, encrypted with a key per person.

Security and residency

Obligations apply from

13 May 2027

The DPDP Rules were notified on 13 November 2025. Eighteen months later, a Data Fiduciary must give an itemised notice, take consent by a clear affirmative action, make withdrawal as easy as giving it, and be able to prove both.

This is our reading of the Act and the Rules. Please confirm it with your counsel.

See each obligation and the part of the product that serves it

How a consent is recorded and honoured

Each step is a screen or an API call in the product. Choose a step to see it.

Purpose inventory

3 purposes

PurposeLegal basisData used
Account statements by emailConsentEmail address
Offers from partner insurersConsentName, phone number
Tax reporting required by lawSection 7 usePAN, transactions

A purpose that rests on a Section 7 use is shown to the person for information. Consent is not asked for it.

Illustration with sample data

Withdrawing is as easy as agreeing.

A person sees every purpose they agreed to, in the language they read it in, and can change their mind in two taps. The business sees the effect at once.

The preference center carries your name and your colours. Each change produces a receipt the person can keep.

A shopkeeper stands behind his counter, reading his phone.

Example Finance

Your consents

  • Account statements by email

    Agreed on 12 Nov 2026. Notice version 3, shown in English.

  • Offers from partner insurers

    Agreed on 12 Nov 2026. Notice version 3, shown in English.

Powered by VachanSetu

Try it: withdraw a consent. Sample data, nothing is sent.

The next decision check

POST /api/v1/decisions

Before a system uses the data, it asks. This is the answer for “Offers from partner insurers”.

Decision

Allow

Reason

granted

Logged

Every check, kept at least a year

Systems that are told

webhooks
  • Customer records

    Your system

    Waiting for a change
  • Email service

    Your system

    Waiting for a change
  • Partner insurer

    Processor

    Waiting for a change

Check a receipt yourself.

This is the worked example from our public specification. Your browser runs the four checks an auditor's own code would run. Then edit the record and run them again.

Read how verification works

Consent receipt

Sample from the public specification
Event
Consent given, 20 Nov 2026
Newsletter
Granted
Order updates
Refused
Notice shown
Privacy notice, version 1, English
Artefact hash
a0996e9ee8c9d9cc…bf5ba7b2
Signing key
vs-Zm9ydHk0Mm5vdGFSZWFsS2V5-1
Sealed in
Block 1, with two other consents

What your browser checks

  1. The record matches the hash on the receipt

    The record is written out in one fixed form and hashed with SHA-256.

  2. The organisation signed exactly this record

    An Ed25519 signature, checked against the organisation's published key.

  3. The record is part of the sealed block

    Two hashes from the receipt lead from this record to the block's root.

  4. The block is signed and names that root

    Each block also names the hash of the block before it.

Who uses it, and for what

Two colleagues review a printed document at a desk.

Data Protection Officers and compliance heads

Own the purpose inventory, approve each notice before it is published, and export an evidence pack that an auditor can verify offline.

See the platform

Developers

Add the widget or call the API, then ask the decision endpoint before processing. Each change arrives as a signed webhook, with every delivery attempt on screen.

Read the developer guide

Grievance officers

Work access, correction, erasure, nomination and grievance requests from one queue. Each request shows the days left to answer it.

Rights and grievance

An old stone bridge of many arches crosses a still river in morning mist.

Why it is called VachanSetu

Vachan वचन
One's word. A promise.
Setu सेतु
A bridge.

A business gives its word about how it will use someone's data. VachanSetu is how it keeps that word, and how it shows that it did.

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.