- Your badge should reduce repeated document requests.
- You should understand what is being shared.
- Sensitive data should be minimized.
- Use correction, DSR, or support routes for wrong or stale information.
Overview
Badge travels with worker
The badge is designed to be portable across legitimate requesters.
Worker controls sharing
Workers should understand and control where the badge is shared where product controls support it.
Corrections and renewal
Wrong or stale signals should use correction or renewal paths.
Source-backed signals
Requesters see verification status signals, not unrestricted private records.
Not a blank cheque
A badge is not permission to inspect every private record.
Support for misuse
Use human handoff if a badge is misused, coerced, or misunderstood.
What to do
- 1Start or renew your badge with consent.
- 2Share QR only with legitimate requesters.
- 3Use correction or DSR routes for wrong or stale data.
Worker dignity and privacy
- Verification should reduce repeated document requests.
- Workers should understand what is being shared.
- Sensitive data should be minimized.
- Workers should not be pressured into irrelevant disclosure.
Badge visibility matrix
| Viewer | Can see | Should not see by default |
|---|---|---|
| Public badge page | Masked profile and permitted status signals | Raw Aadhaar, PAN, OTPs, private documents |
| Household verifier | Status signals needed for the stated purpose | Unrelated private records |
| Society admin | Permitted worker or vendor workflow signals | Free-text identity document dumps |
| Business admin | Workspace-permitted signals and audit references | Secrets outside role or contract scope |
| PRAMAAN support | Reference IDs and redacted context | Raw identity secrets pasted into chat |
Frequently asked questions
What is a PRAMAAN worker badge?›
It is a portable trust profile that shows permitted verification status signals through a QR or link.
Who can scan my badge?›
Anyone you share it with can open the public badge page, but the page should avoid exposing raw documents.
What can they see?›
They should see permitted source-backed status signals, not unrestricted private records.
How do I renew or update my badge?›
Use the worker dashboard, badge flow, or support path where renewal is enabled.
Can I correct wrong data?›
Yes. Use correction, DSR, or support routes for wrong, stale, or disputed signals.
Can I revoke sharing?›
Revocation depends on the product flow and prior audit obligations. Use support or DSR if unclear.
Can my employer own my badge?›
No. The badge is positioned as worker-owned, not employer-owned.
What if I lose my phone?›
Use account recovery or support. Do not share OTPs or secrets in chat.
What if someone misuses my badge?›
Contact human support with the badge link or reference ID and a short summary. Avoid raw identity secrets.
Glossary terms
When to talk to a human
Use human support for misuse, coercion, lost phone, correction, renewal, or account-specific worker 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.