Guardian Consent Desk
Records a parent's consent for each use of a student's data, and when consent is withdrawn, deletes the student from every connected system and issues a signed certificate.
500 synthetic students, each with a guardian check and a consent for each use
The parent's page, here in Telugu: each use is separate, in plain words
One withdrawal, four systems confirmed, certificate ready
Anyone can check the certificate's signature
The whole demo as a video, with captions and chapters
Demo built on synthetic data.
1 of 5: The students
The problem
Consent sits on paper forms and in five tools that don't talk to each other. When a parent asks you to delete their child's data, the LMS forgets them, the marketing list doesn't, and you can't show what happened.
What it does
It verifies the parent or guardian before a student under 18 is enrolled into anything that uses their data.
It records consent per purpose — learning analytics, communications, photos — with the exact notice the parent saw.
On withdrawal, it deletes from every connected system and shows each one's confirmation.
It issues a signed certificate anyone can check.
It scans for data left behind after a deletion.
Try to break it
On the call we'll trigger these, live:
- The marketing tool doesn't confirm a deletion. It stays open on the list and isn't counted as done.
- A student opens the consent link instead of the parent. Verification stops it.
- Old records turn up in the analytics database. The scan finds them.
Where it runs
Your own cloud account or a server on campus.
Who else does something like this
SuperAwesome Kids Web Services provides verifiable parental consent for apps and games used by children.
The Consent Desk is built for Indian institutes under the DPDP Act, and it proves deletion across your own systems.
The rules it respects
Built for the DPDP Act 2023 and Rules 2025 — verifiable parental consent for anyone under 18.
What our tests measured
How we test- Run on 4 October 2026
- Model: none (deterministic)
- 500 examples
For your engineers
- Engines
- Consent Spine, Proof Console
- Sealed mode
- Test passed: with sealed mode on, it refuses every outbound connection except to the model you've approved.
Data flow



