Request Erasure

​

Endpoint

POST /v1/dpdp/data-principals/:principalId/erasure

​

Authentication

​

Request Headers

​

Path Parameters

​

Example Request

curl -X POST https://api.grantex.dev/v1/dpdp/data-principals/user_abc123/erasure \
  -H "Authorization: Bearer gx_..."

​

Response — 201 Created

{
  "requestId": "ER-2026-01J9Z6ZC4Q8F2V1K3M5N7P9R0S",
  "dataPrincipalId": "user_abc123",
  "status": "completed",
  "recordsErased": 3,
  "grantsRevoked": 2,
  "delegatedGrantsRevoked": 0,
  "grievancesRedacted": 0,
  "exportsDeleted": 0,
  "retained": [
    { "category": "consent_records", "count": 3, "reason": "Kept and marked erased, not deleted: ..." },
    { "category": "audit_log", "reason": "Audit entries are neither modified nor deleted: ..." },
    { "category": "grievances", "count": 1, "reason": "Kept unchanged, description and evidence included, ... Expanded erasure is not enabled on this deployment (DPDP_ERASURE_EXPANDED), so they were not redacted." },
    { "category": "stored_exports", "count": 1, "reason": "Stored compliance exports about the data principal are kept until they expire ... so they were not deleted." },
    { "category": "fiduciary_data", "reason": "Grantex holds no personal data the Data Fiduciary processed ..." }
  ],
  "submittedAt": "2026-04-05T14:00:00.000Z",
  "completedAt": "2026-04-05T14:00:00.120Z",
  "expectedCompletionBy": "2026-04-05T14:00:00.120Z"
}

​

Response Fields

​

What Happens on Erasure

1. The grants of the principal’s consent records that are still active are revoked, with revokedAt, the revocation cache and a grant.revoked event each. By default only those grants are revoked, as this endpoint always did; with DPDP_REVOCATION_CASCADE=true the grants delegated from them, their credentials and wallet reservations are revoked through the grant cascade too.
2. The principal’s consent records are set to status: 'erased' with erasedAt; they are retained, not deleted.
3. With DPDP_ERASURE_EXPANDED=true only: the principal’s grievances keep their reference, type, status and dates, and their description and evidence are replaced by a fixed marker.
4. With DPDP_ERASURE_EXPANDED=true only: stored exports filtered to the principal, or containing the principal id, are deleted.
5. The request is stored and recorded on the audit chain as grantex.dpdp.erasure_completed, and a dpdp.erasure.completed event is emitted.

• Consent records are kept, marked erased, because the Data Fiduciary bears the burden of proving consent (DPDP Act s.6(10)) and DPDP Rules 2025 r.8(3) require processing logs and associated data to be retained for at least one year.
• Audit entries are neither modified nor deleted: DPDP Rules 2025 r.6(1)(e) and r.8(3) require logs to be retained for at least one year, and the entries form a tamper-evident hash chain.
• Grievances are kept as the record of grievance handling: redacted with DPDP_ERASURE_EXPANDED=true, otherwise unchanged, and the reason says expanded erasure is not enabled.
• Stored exports (stored_exports, only without DPDP_ERASURE_EXPANDED=true) about the principal are kept until they expire, seven days after creation, and the reason says expanded erasure is not enabled.
• The fiduciary’s processed data is not held by Grantex; erasing it in the fiduciary’s own systems and its processors’ (DPDP Act s.8(7)) is the fiduciary’s step.

​

Error Responses

​

SDK Examples

import { Grantex } from '@grantex/sdk';

const grantex = new Grantex({ apiKey: 'gx_...' });

const result = await grantex.dpdp.requestErasure('user_abc123');
// result.recordsErased → 3
// result.grantsRevoked → 2

from grantex import Grantex

grantex = Grantex(api_key="gx_...")

result = grantex.dpdp.request_erasure("user_abc123")
print(f"Erased {result.records_erased} records, revoked {result.grants_revoked} grants")

​

Ownership