What it does
Versioned purpose notices, consent and withdrawal receipts that are added and never overwritten, rights requests with response deadlines, retention rules with a dry run, a breach register with notification clocks, a residency allow list and a readiness report. The records support an operator's own compliance work. They are not a legal certification.
How it works
Administrators publish a notice for each purpose and version. Activating a new version retires the previous active one, and the content of a version cannot change. A data principal who is signed in as a platform account records a consent, or its withdrawal, against an active notice version. Each is stored as a new receipt and nothing is overwritten. Principals list their receipts under /v1/privacy/consents and submit access, correction, erasure, grievance or nomination requests under /v1/privacy/rights-requests. Each request gets a response deadline and moves through received, in progress, completed or rejected.
Retention rules, scoped to a project, state how long a kind of data is kept for a purpose. GET /admin/compliance/dpdp/retention-rules/dry-run evaluates them and lists what would be eligible for deletion, without deleting anything. The breach register records a breach with its 72-hour board-notification deadline and later notification times. The readiness report summarises which controls have data behind them, and the document at /.well-known/dpdp names the Act, the controls and the duties that stay with the operator.
An erasure rights request cannot be completed, and cascade erasure cannot run, while a legal hold covers the principal.
Where you reach it
- HTTP
GET /v1/privacy/notices, GET|POST /v1/privacy/consents, GET|POST /v1/privacy/rights-requests - HTTP
GET /admin/compliance/dpdp/readiness, GET|POST /admin/compliance/dpdp/notices - HTTP
GET|POST /admin/compliance/dpdp/consents, GET /admin/compliance/dpdp/rights-requests, POST /admin/compliance/dpdp/rights-requests/:id/status - HTTP
GET|POST /admin/compliance/dpdp/retention-rules, GET /admin/compliance/dpdp/retention-rules/dry-run - HTTP
GET|POST /admin/compliance/dpdp/breaches, POST /admin/compliance/dpdp/breaches/:id/notifications, GET|PUT /admin/compliance/dpdp/residency - HTTP
GET /.well-known/dpdp
Example
# Needs an active notice for this purpose and version
curl -s -X POST "$KYNETRA_URL/v1/privacy/consents" \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"purpose_id":"order-fulfilment","notice_version":1,"status":"granted","source":"checkout-form"}'
# returns {"receipt": {...}}; withdrawing sends status "withdrawn" and adds a new receiptLimits
- Retention execution is switched off. The execute route returns 501 and deletes nothing, because deletion over HTTP waits on legal-hold and concurrency controls that are not wired to it. The dry run works. Deleting expired data is carried out by the operator.
- Legal holds exist as records and are honoured by erasure, but there is no route to place or release one in this release.
- Notices, consents, rights requests and breach records are held at deployment level, not per project. Retention rules are the one record type scoped to a project.
- The principal-facing routes need a platform account token and are not available to project end-user tokens. An application with its own end users records consent for them through an administrator route.
- This is operational record-keeping. It does not certify compliance with the Act or its rules, and notifying the board and affected principals of a breach stays the operator's duty.
Evidence
- On this siteSecurity overview
- Tests33 DPDP tests in the compliance crate (notice versions, consent receipts that are never overwritten, deadlines, the 72-hour breach clock, retention dry run and tenant isolation, legal holds) and 7 mounted retention-route tests
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to talk through the limits above against your own workload.