Guardian consent must be explicit
The flow needs to identify who approved the check and for what purpose.
Solution - Guardian Consent
Under-18 checks need guardian consent.
DPDP-mandated guardian consent built into sensitive verification flows.
0+
guardian consent events modeled
Microsoft 365MSG91WhatsApp BusinessAWS IndiaOpenAPIRazorpayMicrosoft 365MSG91WhatsApp BusinessAWS IndiaOpenAPIRazorpay
DPDP Section 6Consent receipt built inAudit-ready evidence
Minor-related verification needs extra care. PRAMAAN treats under-18 flows as a specific consent pattern, not a checkbox added later. The route is designed for schools, clubs, residential communities, and service contexts where guardian approval is required.
Retention needs extra care
Operators should avoid keeping minor-related data beyond the required purpose.
Families need a support path
Correction, dispute, and grievance routes must be visible.
Request to Verify to Audit
One workflow language for every verification decision.
1Identify
Confirm the guardian and purpose
The request clearly states who is asking and why.
2Approve
Guardian gives consent before processing
Consent is captured as an evidence event.
3Limit
Result is purpose-limited and reviewable
Operators see only what the workflow needs.
Platform capabilities
Six product blocks built around the buyer's daily work.
intake
Purpose-specific intake
Start every under-18 with guardian consent flow with a named requester, purpose, and consent step.
status
Status-first operations
Show verified, pending, expired, revoked, or review-needed state instead of raw documents.
roles
Role-aware access
Give residents, guards, admins, reviewers, and operators only the view they need.
timeline
Expiry and renewal
Prevent stale verification from silently becoming permanent trust.
audit
Audit packet export
Bundle request, consent, result, timestamp, and reviewer context for later proof.
api
API and dashboard handoff
Operate from the PRAMAAN dashboard first, then connect approved systems through API or webhooks.
DPDP assurance is part of the workflow, not a footer.
Each industry template keeps purpose, consent, masking, residency, and incident posture visible to buyers.
- ✓Guardian consent before processing
- ✓Purpose-limited consent before processing
- ✓Masked identity display for operational views
- ✓India-region processing posture
- ✓DSR, correction, and grievance routes linked
Under-18 consent pattern
100%
guardian approval required before checks
Minor-related checks need a different posture, not a standard adult flow with a label changed.
Trust operations
PRAMAAN
Read full case studyIntegration-ready rails
Text marks used where logo licensing is unclear.OpenAPIWebhooksMSG91RazorpayWhatsApp BusinessMicrosoft 365AWS IndiaDashboard exportOpenAPIWebhooksMSG91RazorpayWhatsApp BusinessMicrosoft 365AWS IndiaDashboard export
0%
guardian approval before under-18 checks
0h
breach communication posture
0+
family support routes linked
Under-18 with Guardian Consent FAQ
Related surfaces
Ready to modernise under-18 with guardian consent workflows?
Start with one high-friction workflow, prove the audit trail, then expand across roles.