Skip to content
TrustOS

Free tool

Request deadline planner

A customer emails on a Friday asking you to delete their data. When must you reply, and when should you? Enter the date and the kind of request, set the targets your team works to, and see the dates side by side with the outer limit in the Rules.

Free tool1 min

Answers
Enter the date a request arrived and its type. See your own targets and the 90 day outer limit for grievances under Rule 14.
Based on
The DPDP Act and Rules as notified
Privacy
Calculated in your browser. Nothing is sent unless you choose to send it

Your own targets, in calendar days

Prefilled with example targets. Set them to what your team commits to.

Erase data no longer needed for the purpose, unless a law requires you to keep it, and record the reason for anything kept. Processors must erase too.

Your plan for this request

Day 0Day 30Day 60Day 90
  1. Day 2 · your target

    Acknowledge and check identity

    Enter a date above

    ...

  2. Day 30 · your target

    Complete the action and reply

    Enter a date above

    ...

  3. Day 90 · the Rules

    Outer limit if it becomes a grievance

    Enter a date above

    ...

The Act and Rules do not set a single fixed period for this kind of request. You publish how requests are made and work to your own period. If the person is not satisfied, a grievance follows, and that has a 90 day outer limit under Rule 14. Answering the request properly in the first place is the easier path.

Indicative only and not legal advice. It is worked out from what you enter and the DPDP Act and Rules as notified. The duties apply from around 13 May 2027 as notified, unless amended. Read the rights guide.

Send me this and talk to someone

We send your result to the TrustOS team, and someone who knows the Act and the product replies with a view on your next steps.

How this works

What the tool is based on

The outer limit

Rule 14 asks for a grievance redressal system that responds within a reasonable period not exceeding 90 days.

Your own targets

For access, correction, erasure and nomination, you publish how requests are made and the period you work to. The planner shows the dates for the targets you set.

Calendar days

Dates are counted in calendar days from the day the request arrived. If your policy counts working days, set your targets to match.

Erasure, everywhere it lives

One request out, a confirmation back from each system

The erasure plan comes from the data inventory. Connectors act where they can, processors confirm, people close manual tasks, and anything kept under a legal duty is recorded with its reason.

ERASURE REQUESTREQ-2026-0418Ritika ShahIdentity checkedReceived 10 Oct · due 14 OctErasureplanfrom the data inventoryLoan appConnector · erasedCRMConnector · erasedData warehouseConnector · erasedEmail platformProcessor · confirmedCall recordingsTask · IT ops, doneKYC archiveKept · legal duty to retain5 erased, 1 kept with its reason · reply sent to Ritika · request closed

See it with your data

Show us where your personal data lives. We will show you TrustOS running on it.

A 30 minute walkthrough on Google Meet with someone who knows the Act and the product. You leave with a view of your first phase, the owners and the effort.

Or get a rollout proposal in two minutes
  1. Step 1A 30 minute demo on Google MeetWith someone who knows the Act and the product.
  2. Step 2Your systems and purposesWe walk one product's personal data through TrustOS.
  3. Step 3A first phase you can planModules, owners and effort, written down for you to keep.