Consent withdrawal (S.6(4))
- Reference
- DSR-2026-004847
- Status
- Received
- Data Principal
- Simran Ahluwalia
- Contact
- si••••••@rediffmail.com · ••••••5363
- Received
- 02 Jul 2026, 09:30
- Channel
- Language
- HI
- Identity
- Not verified
Runs from receipt. The organisation publishes this period, which makes it binding.
- Due
- 09 Jul 2026, 09:30
- Assigned to
- Progress
- 0 of 4 steps complete
Fulfilment steps
Each step is a system that must actually do something. A response issued before these complete is a response that will generate a grievance.
- In progressRecord the withdrawal against the artefactConsent Manager · Rohit Verma
- Propagate to downstream systemsData Discovery
- Queue erasure where no other basis appliesRetention Manager
- Confirm to the Data PrincipalRights portal
History
Events marked as visible are also shown to the Data Principal when they track the request.
- Request submittedlast month
Received through the Data Principal portal.
02 Jul 2026, 09:30Data PrincipalVisible to the Data Principal
Data map (8 elements)
Assembled automatically from Discovery. This is what makes a Section 11 response complete rather than best-effort — and it is only as good as discovery coverage.
Covering approximately 2.02 Cr records across 7 systems.
Response
Templates are bilingual and pre-populated. Section 11(b) requires the identities of other Data Fiduciaries the data was shared with to be disclosed, so the access template always lists recipients.