- Verification cannot proceed without explicit consent.
- Consent should be specific to the purpose and data categories.
- Do not paste Aadhaar, PAN, OTPs, or documents into chat.
- This guide is plain-language information, not legal advice.
Overview
Stated purpose
The requester explains why the check is needed.
Clear notice
The subject sees data categories, result visibility, retention, and support routes.
Explicit action
Consent requires a clear action in the guided flow.
Scoped data use
Data collected for one purpose is not reused for an unrelated purpose.
Withdrawal path
The user sees where to withdraw consent or raise a request.
Consent artifact
PRAMAAN records the purpose, timestamp, actor, scope, and withdrawal path.
Consent flow
- 1Requester states purpose.
- 2Data principal sees notice.
- 3Consent is captured through a clear action.
- 4Verification runs through the guided flow.
- 5Result is generated as source-backed signals.
- 6DSR or withdrawal path remains available.
What good consent includes
- Who is requesting the check.
- Why the check is needed.
- What data categories may be used.
- How long relevant records may be retained.
- Who can see the result.
- How to withdraw or raise a data request.
What not to do
- Do not paste Aadhaar, PAN, OTPs, or raw documents into chat.
- Do not run secret checks.
- Do not reuse consent for unrelated purposes.
- Do not forward raw documents to committees, groups, or WhatsApp threads.
- Do not treat a verification result as an absolute guarantee.
Frequently asked questions
What is consent in PRAMAAN?›
Consent is the subject’s explicit approval for a stated verification purpose after seeing a clear notice.
Who gives consent?›
The person whose personal data will be processed gives consent, unless a verified representative route applies.
Can consent be withdrawn?›
Yes. Withdrawal should use the DSR or consent route and affects future processing in that scope.
What is a consent artifact?›
It is evidence of consent, including purpose, timestamp, actor, scope, source, and withdrawal path.
Can one consent cover multiple purposes?›
Avoid broad reuse. If the purpose changes materially, use a fresh consent path.
Can a society or employer verify without consent?›
PRAMAAN workflows are consent-first. Secret checks should not be run through PRAMAAN.
Glossary terms
When to talk to a human
Use human handoff or DSR routes for unclear consent, legal, account-specific, or grievance questions.
Use formal routes for data rights
Access, correction, erasure, nomination, consent withdrawal, and grievance requests should use DSR, DPO, or grievance pages so scope and handling are tracked.
Was this helpful?
Feedback helps PRAMAAN improve support answers without collecting raw identity data.
Move safely from answer to action
Use the route that matches the sensitivity of your case. Keep raw documents out of support messages unless a controlled workflow asks for them.