Consent OS
Every yes. Every no. Every withdrawal. Provable.
The DPDP Act wants consent that is free, specific, informed, unambiguous and as easy to withdraw as to give (Section 6). Consent OS asks for it everywhere your business meets people. It keeps proof of every choice, and it makes sure a “no” reaches every system that uses the data.
Every channel
Website, counter, QR code, link, WhatsApp share and your mobile app: one set of purposes and one record.
Proof that holds
Each choice gets a receipt and sits in a hash-chained log, so an edit or a deletion shows.
Withdrawal that sticks
One click stops it everywhere: your vendors are told, your systems are told, and the next check says no.
ID numbers handled right
Aadhaar, PAN and other ID purposes are asked on their own, and the number is never stored.
Children and guardians
Parents and lawful guardians give consent, with no tracking or targeted ads for children.
Wired into your systems
Signed webhooks and a live consent check, so your CRM and app always know the current answer.
Website banner and cookie scanner
Paste one script tag. Tracking waits until the visitor says yes.
- The cookie scanner shows what your site sets before anyone agrees.
- Scripts you tag wait for consent to their purpose.
- Google Consent Mode v2 signals follow the visitor's choice.
- Accept and Reject are equally easy, and nothing is pre-ticked (Section 6(1)).
- A "Privacy choices" link on every page changes or withdraws consent (Section 6(4)).
- Banner text in English and any of the 22 scheduled Indian languages.
Counter, QR code, link and app
For clinics, schools, stores, events and forms: the same choices, wherever people are.
- A hosted consent page with a QR code and a printable poster.
- Short links tagged by where you shared them, and shared on WhatsApp in one step.
- The same purposes, languages and records inside your mobile app (React Native or Flutter).
- People choose in their own language and get a receipt.
Proof of every choice
Show what someone agreed to, under which notice, and when (Section 6(10)).
- Purpose, notice version, language, channel and time, under a random person ID: no name, no IP address.
- Hash-chained records, so any edit or deletion shows.
- Look up any receipt a person shows you.
- Import records from a consent tool you already use, and take in records from registered Consent Managers (Rule 4).
Withdrawal that reaches everyone
Withdrawing has to stop the processing everywhere, including at your vendors (Section 6(6)).
- A preference page: with any receipt, a person sees every choice they made with you, on any channel, and can withdraw it all.
- Your processors are listed, with a ready-made stop notice and the date each was told.
- Each choice is sent to your CRM or marketing tool as a signed webhook, with proof it was delivered.
- A live consent check, so your systems ask "does this person agree right now?" before using the data.
Aadhaar, PAN and other ID numbers
Purposes that use an ID number get extra care, because the risk is higher.
- Covers Aadhaar, PAN, passport, voter ID, driving licence and bank account numbers.
- Each ID purpose is asked on its own: "Accept all" never includes it.
- GRC-Flow records that consent was given for the ID type, never the number itself.
- If a law requires the ID, consent isn't the basis: Consent OS points you to record it as a legal requirement (Section 7).
Children and persons with disability
A child's data, or that of a person with disability who has a lawful guardian, needs a parent's or guardian's consent (Section 9, Rule 10).
- An age question before consent, and a parent and guardian form.
- Each request is logged with a reference, and you check it before relying on it.
- No tracking, behavioural monitoring or targeted ads for children (Section 9(3)).
- Coming soon: the parent verifies with DigiLocker. DigiLocker confirms only that they are 18 or older, and GRC-Flow keeps only that result and the date, never their name, birth date or Aadhaar details.
Built for your developers
Consent OS fits into the systems you already run.
- One script tag for the website, and a web view for apps.
- Signed webhooks for every choice.
- A consent status API with its own key (shown once, revocable), limited to 600 checks a minute.
- Answers by a random person ID or receipt: never a name, phone number or email.
Consent over WhatsApp, with GreenTick
Ask for consent in the chat people already use, and check before every message, with GreenTick, our WhatsApp marketing platform.
- Share your consent link in a WhatsApp chat in one step; every answer gets a receipt and proof.
- A live "may I message this person?" check that GreenTick, or any messaging tool, asks before sending.
- When someone withdraws, the check says no, so the next message doesn't go.

Works with GreenTick
GreenTick is our WhatsApp marketing platform, built on the official WhatsApp Cloud API: broadcasts, a shared inbox, chatbots and automations for growing businesses.
Visit GreenTick- Ask on WhatsApp. Share your consent link in the chat, and every answer lands in Consent OS with a receipt and proof.
- Check before you send. Consent OS answers “may I message this person?” live, so GreenTick can check before a broadcast goes out.
- A no means no. When someone withdraws on any channel, the check says no, so the next message to them doesn't go.
What Consent OS is not
We say this plainly, so you know exactly what you are buying.
- Not KYC. It doesn't verify anyone's identity for banking, lending or onboarding. The DigiLocker check confirms a parent is an adult, nothing more.
- Not a registered Consent Manager. Those register with the Data Protection Board (Rule 4). Consent OS is your own consent system, and it works with them.
- Not a certificate. The DPDP Act has no certificate. What you get is proof: every choice, on record, ready when it's asked for.