← All solutions
Data Principal RightsSections 11, 12, 13

DSR & Rights Fulfilment

Logged, deadline-tracked workflow for access, correction, erasure, portability, and nomination requests.

The problem

When a customer emails you and says "delete my data," you have a statutory window to find every system that holds their data, perform the deletion, and respond. If you can't do that consistently — at scale, with audit evidence — every unfulfilled request is a Section 13 violation that the Data Protection Board can act on. Most organisations have no idea how many such requests they receive in a month, let alone how many they actually closed within SLA.

What you get

Capabilities, not feature toggles

Every capability below is a working part of the AutoCops application — not a roadmap promise.

01

Public intake portal

A branded web form where Data Principals can submit access, correction, erasure, portability, or nomination requests. Identity verification via email OTP. No login required.

02

SLA-tracked workflow

Every request gets a deadline based on the type and the 2025 Rules. The dashboard shows what's overdue, what's at risk, and what's on track. Slipping a deadline triggers an escalation.

03

Multi-system fan-out

Connectors to Postgres, MSSQL, Oracle, MongoDB, Elasticsearch, and any HTTP API. When a deletion request lands, AutoCops orchestrates the deletion across every connected system and records the result of each.

04

Identity verification

Email OTP, optional Aadhaar via DigiLocker, phone OTP. Configurable per request type (access requires lighter verification than erasure).

05

Response templates

Pre-written response templates for each request type, bilingual where needed, signed by your DPO or Grievance Officer. The Data Principal gets a clean PDF, not a cobbled-together email.

06

Auditor-grade evidence

For every request, you can show the regulator: when it was received, when it was acknowledged, what systems were searched, what was found, what was deleted, when the response was sent, and the verifiable identity of the requester.

How it works

From zero to live in days, not months

  1. 1

    Embed the intake form

    Add a link to your privacy notice or footer. Branded form, your colours, your language.

  2. 2

    Verify the requester

    AutoCops sends an OTP and confirms the requester's identity before the request is queued.

  3. 3

    Search every system

    Connectors fan out to every system you've registered. Results come back in seconds for connected systems and in minutes for HTTP APIs.

  4. 4

    Act and respond

    Your operator reviews the matches, executes the action (delete, correct, export), and the system auto-generates the response PDF and sends it to the Data Principal.

  5. 5

    Close the loop

    The full audit trail is sealed. If the request is later disputed, the entire history — search results, deletion confirmations, response email — is one click away.

Common questions

Things buyers ask in the demo

Can I add a custom system that isn't in your connector list?+

Yes. Any system that exposes a REST or GraphQL API can be wired in via the generic HTTP connector. If your system doesn't have an API, the request gets routed to a human operator with a checklist.

What about backups?+

AutoCops places a deletion marker on the record and tracks it through your backup rotation. The Data Principal gets an honest response: "erased from production, will be erased from the last backup on [date]." That's compliant under Section 8(7).

Ready to see it on your data?

Book a 30-minute walkthrough

Our compliance engineering team will show you dsr & rights fulfilment live on your environment, with your data, in your timezone.