How long do you have to answer a right to erasure request? Under Article 12(3) of the EU GDPR, you must tell the person what you did “without undue delay and in any event within one month of receipt of the request”. You may extend that “by two further months where necessary, taking into account the complexity and number of the requests”, if you say so within the first month and give reasons. California’s CCPA rules give a covered business 45 calendar days, and up to 90 if necessary, with notice (texts read on 18 November 2026).

My view: the work is finding every copy before the month runs out.
In my view, an erasure request is a search job with a one-month deadline, and the CRM is only the first place to look.
Key numbers
| Item | Number |
|---|---|
| GDPR deadline to answer, Article 12(3) (at the latest, from receipt; without undue delay) | One month |
| GDPR extension for complex or numerous requests (where necessary; tell the person within the first month, with reasons) | Two further months |
| UK GDPR Article 12A applies to requests from (the month runs from the latest of receipt, identity information asked for, or any fee) | 5 February 2026 |
| Fixed period the ICO says may be helpful (UK) | 28 calendar days |
| CCPA receipt confirmation, 11 CCR 7021(a) (with how the business will process the request) | 10 business days |
| CCPA deadline to answer, 11 CCR 7021(b) (from receipt) | 45 calendar days |
| CCPA maximum, if necessary, with notice | 90 calendar days |
| GDPR grounds for erasure, Article 17(1) | 6 |
| GDPR exception purposes, Article 17(3) (only to the extent processing is necessary) | 5 |
| CCPA exceptions, section 1798.105(d) | 8 |
| EU GDPR fine cap for rights breaches, Article 83(5)(b) (for an undertaking, worldwide annual turnover, whichever is higher) | €20m or 4% of turnover |
| CCPA revenue threshold, section 1798.140 (annual gross revenues in the preceding calendar year, as adjusted; one of three alternative thresholds) | $25,000,000 |
Read on 18 November 2026 from the GDPR on EUR-Lex, the ICO’s right to erasure guidance, section 76 of the Data (Use and Access) Act 2025 and S.I. 2026/82 on legislation.gov.uk, California Civil Code 1798.105, 1798.130 and 1798.140, and 11 CCR 7021 and 7022 as published by Cornell LII. The ICO says its guidance is under review after the Data (Use and Access) Act.
Deleting the CRM record is one copy of many
The shortcut I would avoid is treating a request to delete as one click in the CRM. Article 19 says you “shall communicate any rectification or erasure” carried out under Article 17(1) to “each recipient to whom the personal data have been disclosed, unless this proves impossible or involves disproportionate effort”. On my reading, that takes in the sending tool you uploaded the list to and any agency you shared it with.
“They asked to be deleted, so we removed the contact from the CRM.” (illustrative)
On my reading, copies can remain in the sending tool, in exports and in backups.
My suggestion: list every system and recipient that holds the record, then erase or notify each one.
Article 19: tell “each recipient to whom the personal data have been disclosed”, unless impossible or disproportionate.
When Article 17 applies to a sales list
Article 17(1) lists six grounds. On my reading, four can come up for a sales list: the data are “no longer necessary” for their purpose; the person withdraws consent and there is no other legal ground; the person objects; or “the personal data have been unlawfully processed”. An objection to direct marketing under Article 21(2) is enough on its own; an objection under Article 21(1) counts only if there are “no overriding legitimate grounds for the processing”.
For the UK GDPR, the ICO, whose guidance is “under review” after the Data (Use and Access) Act, adds that a request can be made “verbally or in writing” and “does not have to include the phrase 'request for erasure' or Article 17 of the UK GDPR, as long as one of the conditions listed above apply”.
On my reading, California’s right is narrower in one respect and wider in another. Section 1798.105(a) needs no ground, but covers only information “which the business has collected from the consumer”. A “consumer” is “a natural person who is a California resident”, and the duty follows a “verifiable consumer request”. Only a “business” as section 1798.140 defines it must comply, for example one with annual gross revenues above $25,000,000 in the preceding calendar year, as adjusted. Whether a bought prospect record counts as collected from the consumer is a question for your lawyer; I found no answer in the section itself.
One month in the EU and UK, 45 days in California
| Law | Deadline | Extension |
|---|---|---|
| EU GDPR, Article 12(3) | Without undue delay, and within one month of receipt | Two further months where necessary for complex or numerous requests; tell the person within the first month, with reasons |
| UK GDPR, Article 12A (requests received from 5 February 2026) | One month from the “relevant time”: the latest of receipt, receipt of information you asked for to confirm identity, or payment of any fee charged | Two further months where necessary for complex or numerous requests, by notice with reasons within that month |
| California, 11 CCR 7021 | Confirm receipt and say how you will process it within 10 business days; answer within 45 calendar days of receipt | If necessary, up to 45 more days, “a maximum total of 90 calendar days”, with notice and an explanation given within the first 45 days |
The UK rule comes from section 76 of the Data (Use and Access) Act 2025, in force on 5 February 2026; requests received before that date keep the old rule. A California business may deny a request it “cannot verify” within the 45 days. The ICO says “it may be helpful to adopt a 28-day period”; my suggestion is to work to it. Both California regulations are quoted from Cornell LII, whose history notes end at amendments operative 29 March 2023; I did not check whether later rulemaking changed them.
When you can say no
Article 17(3) switches the right off only “to the extent that processing is necessary” for one of five purposes, among them a legal obligation and “the establishment, exercise or defence of legal claims”. For a sales team, on my reading, those two are the likely fit.
You can also refuse a request that is “manifestly unfounded or excessive”, but Article 12(5) says the controller “shall bear the burden of demonstrating” that. Under the EU text of Article 12(4), you must give your reasons “without delay and at the latest within one month of receipt of the request” and say the person can complain to a supervisory authority and seek a judicial remedy. California’s section 1798.105(d) lists eight exceptions of its own, including complying with a legal obligation.
For the UK, our email suppression list guide covers the ICO’s view on what to keep. Under the EU GDPR, Article 83(5)(b) makes breaches of “the data subjects' rights pursuant to Articles 12 to 22” subject to fines up to €20m or, for an undertaking, 4% of worldwide annual turnover, whichever is higher; see GDPR fines.
What happens to your backups
For the UK GDPR, the ICO says that “If a valid erasure request is received and no exemption applies then you will have to take steps to ensure erasure from backup systems as well as live systems.” Data may stay in a backup until it is overwritten, but “The key issue is to put the backup data ‘beyond use’”: held and not used “for any other purpose”. It also says: “You must be absolutely clear with individuals as to what will happen to their data”. I read no EU guidance on backups.
On my reading, California is looser. 11 CCR 7022(d) lets a business delay deleting data on “archived or backup systems” until that system “is restored to an active system or is next accessed or used for a sale, disclosure, or commercial purpose”.
What I would do this week
Log the date it arrived
The clock starts on receipt (in the UK, at the relevant time). My suggestion: route every deletion request to one inbox and set a 28-day due date.
Map every copy
My suggestion: list the CRM, the sending tool, exports, spreadsheets and anyone you shared the list with before you reply.
Notify every recipient
Article 19 covers each recipient; California’s section 1798.105(c)(1) covers service providers, contractors and third parties you sold or shared the data with. My suggestion: one notice template per tool.
Say what happens to backups
My suggestion: one sentence in every reply on what happens to backup copies, written to match what your systems really do.
My team’s record: 500+ projects delivered across 30 countries. Our email infrastructure page covers one-click unsubscribe, suppression and list validation; whether your process meets the law is for you and your lawyer to decide. For the sending side, see email hosting cost and what an email deliverability consultant costs.
The bottom line
Under the GDPR, answer an erasure request within one month; under the CCPA rules, within 45 calendar days. In my view, map your copies before the first request arrives. This is general information, not legal advice.