- The worker controls badge sharing where the product supports it.
- Public badge screens should avoid raw documents.
- Requesters see permitted source-backed status signals.
- A badge is not an employment guarantee or permanent clearance.
Overview
Worker-owned
The badge belongs to the worker, not one employer or society.
Portable
Workers can reuse the trust signal across legitimate requesters.
QR shareable
A QR or link can show permitted status signals.
Consent-controlled
Sharing and fresh checks should follow consented flows.
Renewal supported
Badges can be refreshed where the product and policy support renewal.
Corrections supported
Wrong or stale signals should route through correction or DSR paths.
Dummy badge preview
| Field | Example |
|---|---|
| Name | R**** K**** |
| Role | Domestic worker |
| City | Bengaluru |
| Verification status | Verified signal available |
| Validity | Valid until renewal date |
| QR | Masked QR placeholder |
| Consent status | Shared by worker |
Worker privacy
- Public badge screens avoid raw documents.
- Sensitive fields should be minimized.
- Requesters should see source-backed status signals, not private records.
- DSR and correction paths remain available.
Frequently asked questions
What is a worker badge?›
A worker badge is a portable PRAMAAN trust signal with QR or link sharing for permitted verification status.
Who owns the badge?›
The worker owns the badge. It should not be locked to one employer, household, or society.
Who can scan it?›
Anyone the worker shares it with can scan the public link, but they should see only permitted signals.
Can I renew it?›
Renewal is supported where the product flow and badge validity rules allow it.
Can I correct a wrong signal?›
Yes. Use correction, support, or DSR routes for wrong, stale, or disputed data.
Can an employer force me to share?›
PRAMAAN cannot make employment-law promises here. Workers should understand what is being shared and use human support for coercive or unclear cases.
Can I revoke access?›
Revocation depends on the product flow and previous audit/contract records. Use support or DSR if unclear.
Glossary terms
When to talk to a human
Use human handoff for badge misuse, correction, revocation, coercion, 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.