Your client withdraws from the rights link on their receipt. They choose Withdraw this consent and then Yes, withdraw. They give no reason, and you do not need to answer. The law says withdrawing must be as easy as giving consent (DPDP Act, section 6(4)). Our guide explains what your flow must allow.
What happens at once depends on the request:
| Your request | What happens when your client confirms |
|---|
| We hold the documents, and no law applies | Everything your client sent on that request is deleted. The key is destroyed and the file is removed. |
| A law and a period are named on the request, or you kept the documents under a law in the Retention queue | Nothing is deleted. See what happens when a law requires you to keep them. |
| You hold the documents yourself, because the request only records consent | There is nothing for us to delete. A row opens in your Retention queue with Confirm deleted. You delete the documents from your own records and then choose it. |
A withdrawal covers one consent. Your client's other requests stay as they are, and their name, phone and email stay on their record. An open renewal on that request ends. Any open request from your client under that consent is closed by the withdrawal.
You are told in the app and in the next daily summary, not by a separate email. The bell and the summary reach everyone whose role holds the Withdraw consent, end a relationship, erase a person switch, and admins always. The withdrawal also appears in the client's folder, in the Register tab of the Rights page as made by them through their rights link, and in your audit trail.
A withdrawal cannot be undone.
For example
Amaltas Deshmukh & Co sends Farhan Qureshi a request on 1 July 2027 with a two-year retention period and names no law. He uploads his documents the same day, so they would be kept until 30 June 2029. He withdraws on 1 September 2027. The documents are deleted at that moment instead. His folder then shows the consent as withdrawn on 1 September 2027, and the consent record stays.