Teach students. Don’t expose them.
Enrollment, attendance, and assessment data vaulted at capture. Learning analytics runs on tokens — with heightened protection for children’s data under DPDPA.
Why this buyer hurts.
Minors’ data risk
Children’s records carry the strictest duties — and the worst breach headlines.
Analytics vs privacy
Personalized learning needs data; parents and regulators need guarantees.
Vendor sprawl
LMS, proctoring, and comms tools each become a copy of the student record.
Learn from tokens, protect the children.
cloakit vaults student records, applies stricter policies to minors’ data, and feeds analytics and personalization with stable token references instead of identities.
Pattern: age-aware policies, tokenized learning analytics, and consent- and purpose-scoped access.
The workflow, end to end.
Vault enrollment records
Admissions, attendance, and assessment data post SDK-to-vault at capture — vendors never need raw copies.
Apply age-aware policies
Minors’ records get stricter defaults automatically: tighter access, stronger minimization, review-ready trails.
Analyze on tokens
Personalization and reporting join on token references. Models learn patterns, never identities.
Asked by teams like yours.
How do you handle children’s data?
DPDPA Section 9 duties map to dedicated minor policies: verifiable-consent workflows, no behavioral tracking exposure, and full auditability.
What about parental access or deletion requests?
Lookup plus lifecycle deletion fulfills requests repeatably across every downstream copy — because copies hold tokens.
Do proctoring and LMS vendors get raw data?
No. Vendors receive scoped, revocable grants to tokens or redacted views — never the underlying records.
See it on your own workflow.
Bring one sensitive flow. We will map it to a vault schema live in 30 minutes.
Minors get the strictest path automatically.
Records are routed by age: minors’ data flows under verifiable-consent, no-tracking policies while standard records use purpose scoping — both feeding tokenized analytics.
record"] --> A{"Minor?"} A -- yes --> M["Strict policy
consent · no tracking"] A -- no --> S["Standard policy
purpose-scoped"] M --> T["Tokens to analytics"] S --> T T --> AU["Audit trail"]