4

Withdrawal of consent for service notifications

Please treat this as a formal request under the Digital Personal Data Protection Act, 2023.

DischargesS.6S.8(7)
Request

Consent withdrawal (S.6(4))

Reference
DSR-2026-004832
Status
Awaiting Data Principal
Data Principal
Farhan Nair
Contact
fa••••••@outlook.com · ••••••1486
Received
18 Apr 2026, 09:30
Channel
email
Language
HI
Identity
Verified(otp email)
Statutory deadline

Runs from receipt. The organisation publishes this period, which makes it binding.

--:--:--
Due
25 Apr 2026, 09:30
Assigned to
Progress
1 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.

  • Record the withdrawal against the artefact
    Consent Manager · Ananya Reddy · 21 Apr 2026
  • Propagate to downstream systems
    Data Discovery · Priya Nair
    In progress
  • Queue erasure where no other basis applies
    Retention Manager
  • Confirm to the Data Principal
    Rights portal

History

Events marked as visible are also shown to the Data Principal when they track the request.

  1. Request submitted4 months ago

    Received through the Data Principal portal.

    18 Apr 2026, 09:30Data Principal
    Visible to the Data Principal
  2. Acknowledgement sent4 months ago

    Reference number issued; response due within 30 days.

    18 Apr 2026, 10:30System
    Visible to the Data Principal
  3. Identity verified4 months ago

    One-time code confirmed against the registered mobile number.

    19 Apr 2026, 09:30System
    Visible to the Data Principal
  4. Data map assembled4 months ago

    Personal data located across connected sources and attached to the request.

    20 Apr 2026, 09:30Data Discovery

Data map (11 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.

staging.beneficiary.biometric_ref_hash
Family ID Core Registry
Biometric referenceactiveCritical2
archive.claim.device_fingerprint
Family ID Core Registry
Device identifierexpiredLow3
welfare.profile.full_name
Pension Disbursement Ledger
NameactiveMedium3
hr.applicant.grievance_text
Scheme Beneficiary Warehouse
Grievance historyactiveHigh1
welfare.extract.date_of_birth
Grievance Case Management
Date of birthactiveHigh3
/records/grievance_2025.pdf
Departmental Email (Exchange)
Date of birthexpiredCritical2
/scans/grievance_2020.csv
Collaboration Workspace
Namelegitimate useCritical6
/scans/document_2023.csv
Collaboration Workspace
Bank accountnoneMedium3
/archive/document_2026.xlsx
Document Object Store
Biometric referenceactiveCritical1
core.applicant.family_id
Vendor Portal Database
Family IDwithdrawnHigh2
1–10 of 11
1 / 2

Covering approximately 1.85 Cr records across 9 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.

S.6S.8(7)