Skip to main content
Rights Management

Every data request in one queue, with a due date on it

People raise access, correction, erasure, grievance and nomination requests from your Privacy Centre. Your team verifies, assigns and answers them in the Request Centre, and the full history is kept.

Requests arrive by email, and then they get lost

Sections 11 to 14 of the Digital Personal Data Protection Act, 2023 give every person the right to access their data, have it corrected or erased, raise a grievance and nominate someone to act for them. You must publish how they can do this and respond within the period the rules allow.

A shared inbox cannot tell you who the sender really is, who on your team owns the reply, or which requests are about to run late. One missed request is enough for a complaint to the Data Protection Board.

What the Rights Management module does

  • All five request types

    Access, Correction, Erasure, Grievance Redressal and Nomination, each raised from a form in your Privacy Centre.

  • Verified before it reaches you

    The requester confirms their email with a one-time code or a sign-in link before the request is created, so your team is not chasing anonymous messages.

  • Due dates you can see

    Each request gets a 30-day due date. The dashboard counts open, overdue and due-within-7-days requests, and highlights the late ones.

  • Assign to the right person

    Route a request to a team member. Invited members see only the requests assigned to them, with internal comments kept out of the requester's view.

  • Updates and replies by email

    Send the requester a status update or the final response, or ask an internal department for input. People can track their request and ask for an update themselves.

  • Nomination handled properly

    A nominee can act only after they verify themselves and upload a supporting document, and your team approves the claim.

How it works

  1. Share your Privacy Centre link

    Put the link in your privacy notice and website footer. It holds the Preference Centre and the Request Centre.

  2. A person raises a request

    They choose the right they want to use, describe the request and verify their email.

  3. Your team works the queue

    Assign the request, discuss it internally, and move it from review to a final answer before the due date.

  4. Close it with a record

    The response is emailed to the requester and the timeline of who did what is kept on the request.

Questions teams ask

Which rights can people use through Consently?

Access, correction, erasure, grievance redressal and nomination. Withdrawing consent is not a request: people do it themselves, instantly, in the Preference Centre.

How do you confirm who is asking?

The requester must verify their email address with a one-time code or a sign-in link before the request is created.

Does Consently delete the data from our systems?

No. Consently manages the request: verification, assignment, deadlines, replies and the record. Your team carries out the correction or erasure in your own systems and records the outcome on the request.

Can requests come from our own app or helpdesk?

Yes. Requests can be created through the Consently API, so a request raised in your app or support tool lands in the same queue.

Stop tracking requests in a spreadsheet

Book a demo and walk through a request from the form to the final reply.