- Use DSR, DPO, or grievance routes instead of chat for data-rights requests.
- Deletion may be limited by legal, audit, fraud-prevention, billing, or dispute reasons.
- If a business or society holds its own copy, you may also need to contact that data fiduciary.
- Do not submit raw identity secrets through support chat.
Overview
Access
Request a copy or explanation of personal data linked to your verified identity.
Correction
Ask PRAMAAN to review incorrect, stale, or disputed data.
Erasure
Request deletion where retention, audit, billing, fraud-prevention, or dispute needs do not require keeping records.
Nomination
Use formal routes when an authorized representative or nominee is involved.
Grievance
Escalate dissatisfaction through the published grievance path.
Consent withdrawal
Withdraw consent for future processing in scope; this is related to deletion but not always identical.
Which request do you need?
I want a copy of my data
Start an access request through DSR.
I found incorrect data
Start a correction request and include the disputed field reference, not raw documents in chat.
I want data deleted
Start an erasure request and PRAMAAN will review retention limits.
I want to withdraw consent
Use DSR or consent controls where available; withdrawal affects future processing in scope.
I want to raise a grievance
Use the grievance route if you are not satisfied with handling.
I am a representative
Be ready for authority and identity checks before PRAMAAN can act.
Deletion workflow timeline
- 1Submit DSR request.
- 2Complete identity or authority check.
- 3Confirm request scope.
- 4Review retention, legal hold, billing, fraud-prevention, and dispute limits.
- 5Take action where permitted.
- 6Send confirmation or escalation route.
Important limitations
- Some records may be retained for legal, audit, fraud-prevention, billing, or dispute reasons.
- Deletion and consent withdrawal are related but not always identical.
- Enterprise or society-held copies may require a separate request to that data fiduciary.
- Support chat should receive ticket or reference IDs, not raw identity secrets.
Frequently asked questions
How do I delete my data?›
Start a formal DSR erasure request. PRAMAAN will verify identity or authority, confirm scope, and review retention limits before acting.
Can I withdraw consent?›
Yes. Consent withdrawal stops future processing in scope, but it may not erase records that must be retained for valid reasons.
Can PRAMAAN delete every record immediately?›
Not always. Some records may need to be kept for audit, fraud-prevention, billing, legal, or dispute reasons.
What if a business or society requested my verification?›
PRAMAAN can handle records it controls. The business or society may also have its own data-fiduciary obligations and copies.
Can someone file on my behalf?›
A representative may need to prove authority before PRAMAAN can process the request.
What if I am not satisfied?›
Use the published grievance route so the issue is tracked formally.
Glossary terms
When to talk to a human
Use formal DSR and grievance routes for access, correction, erasure, nomination, and privacy complaints.
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.