PramaanDPDP Live
Log inGet Verified
Help CenterWorker Badges

Badge Dispute FAQ for PRAMAAN Worker Badges

Plain-language PRAMAAN help for badge dispute across worker badges, with consent-first verification, DPDP guardrails, and support escalation guidance.

Start by confirming the purpose of the check and the person whose data will be processed. PRAMAAN routes sensitive information only through consented verification flows.
Use the dashboard, hosted verification flow, or API surface that matches your tier. Keep raw Aadhaar, PAN, OTPs, and documents out of chat and free-text fields.
Read the result as a source-backed signal, not as a guarantee. Escalate unclear, legal, enterprise, or account-specific cases to human handoff.
For DPDP requests, use the DSR route so access, correction, erasure, nomination, and grievance clocks are tracked formally.

Frequently asked questions

What should I know about badge dispute in PRAMAAN?

PRAMAAN treats badge dispute as a consented verification workflow. The requester must state the purpose, the data principal must understand the flow, and the result should be used with documented context.

Does badge dispute expose raw personal data?

No. Public screens and badges avoid exposing raw documents. Sensitive fields are routed through controlled partner, dashboard, or DSR flows and are redacted before support or AI use.

When should I ask support about badge dispute?

Ask support when the case is legal, enterprise-specific, billing-sensitive, or unclear after the dashboard explains the result. PRAMAAN support will ask for the ticket or verification reference, not raw identity secrets.

Next step

Open the relevant PRAMAAN dashboard or start a Rs 99 verification only after you have consent. For unclear cases, use human handoff from the help center.