Data subject requests across jurisdictions: deadlines, identity checks and what goes wrong
One request is easy. The trouble is that the same person’s request can arrive by email, by phone and through a salesperson, in more than one country, with a different clock under each law.
Key points
- A data subject request is a person asking an organization to give them their personal data, or to correct, delete, restrict or stop using it, under a privacy law.
- The clocks differ: the GDPR and UK GDPR give one month, extendable by two further months for complex or numerous requests; California gives 45 calendar days, extendable once by 45; and Canada’s PIPEDA gives 30 calendar days, extendable by up to 30 more in listed cases.
- A request is valid whatever form it takes: the ICO says there are no formal requirements, a verbal request counts, and any staff member or social media channel may receive one.
- The requests that go wrong are the ones that arrive in the wrong place, the ones that need a search nobody has done before, and the ones that mix the requester’s data with other people’s.
As of November 2026 these are the periods in the sources linked below. Laws are amended and deadlines differ by request type, so your counsel confirms the current text before a process is fixed to it.
The deadlines side by side
The clocks differ: the GDPR and UK GDPR give one month, extendable by two further months for complex or numerous requests; California gives 45 calendar days, extendable once by 45; and Canada’s PIPEDA gives 30 calendar days, extendable by up to 30 more in listed cases.
| Regime | Standard period | Extension |
|---|---|---|
| GDPR and UK GDPR | One month | Two further months, complex or numerous requests |
| California | 45 calendar days | One extension of 45 days, with notice |
| Canada, PIPEDA | 30 calendar days | Up to 30 more days in listed cases, notified within the first 30 |
Sources: Article 12 of the GDPR on EUR-Lex and the ICO’s guide to subject access; the California Privacy Protection Agency’s FAQ; the Office of the Privacy Commissioner of Canada’s page on access requests to businesses. Other regimes, including Brazil’s LGPD and India’s Digital Personal Data Protection Act, 2023, have their own periods that we do not state here; if you have people there, ask your counsel for the current text.
The practical consequence: do not build one clock. Build the process around the shortest period that can apply to the requester, record which law you treated as governing, and tell the person when you rely on an extension.
What counts as a request
A request is valid whatever form it takes: the ICO says there are no formal requirements, a verbal request counts, and any staff member or social media channel may receive one. Staff who answer phones, run social accounts or manage customers are all a request channel, which is why training them to forward, not answer, is the cheapest control available.
Start the clock from the date the request arrives wherever it landed, unless the law you rely on says otherwise. A log that records the date received, the channel, the law applied and every later step is the evidence that the deadline was met.
Identity checks that are proportionate
Verify identity in proportion to the risk, asking for no more than is needed to be sure of who is asking, and never collect new identity documents that you will then have to protect.
In practice that means matching what the person tells you against what you already hold. A customer who writes from the email address on the account, and can answer a question only the account holder could, usually needs no more. A request that arrives from an unrecognized address asking for a large amount of data needs more, but the extra check should be the least that settles the question. A request made through an agent or a relative needs the authority to act, checked in the same proportion.
Handing data to the wrong person is itself a breach, so the check is not optional, and it should not become a reason to delay without end. Say what you need and when the clock resumes, if the law you rely on provides for that.
The requests that go wrong
The requests that go wrong are the ones that arrive in the wrong place, the ones that need a search nobody has done before, and the ones that mix the requester’s data with other people’s. A short decision flow keeps the common cases from becoming complaints.
Where the time is lost
- Wrong place. A request sent to a salesperson sits in an inbox for ten days. The fix is training and one route.
- The unknown system. The search finds the CRM and misses the support tool, the exports and the backups. The fix is a search guide from the record of processing and the findings of discovery.
- Other people’s data. An email thread names three colleagues and a customer. Disclosing it unredacted creates a second problem. A reviewer who knows the exceptions, with counsel for the borderline cases, is the control.
- Deletion that is not deletion. The primary record is removed and the copy in the analytics warehouse is not. Deletion meets the retention schedule, and anything you must keep is explained to the person, not silently ignored.
- Multiple laws. The same person is covered by two. Where you cannot tell which governs, ask your counsel, and note the answer in the log.
Measure it
Four numbers, reported quarterly, show whether the process works: requests received by channel, median days to respond, requests that used an extension, and requests that arrived anywhere but the intake route. The last one is the most useful; it measures training. The full service is described on data subject request operations. Where volume justifies software, see choosing a privacy platform.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What is a data subject request?
A data subject request is a person asking an organization to give them their personal data, or to correct, delete, restrict or stop using it, under a privacy law.
What are the response deadlines?
The clocks differ: the GDPR and UK GDPR give one month, extendable by two further months for complex or numerous requests; California gives 45 calendar days, extendable once by 45; and Canada’s PIPEDA gives 30 calendar days, extendable by up to 30 more in listed cases.
What counts as a valid request?
A request is valid whatever form it takes: the ICO says there are no formal requirements, a verbal request counts, and any staff member or social media channel may receive one.
How should we verify identity?
Verify identity in proportion to the risk, asking for no more than is needed to be sure of who is asking, and never collect new identity documents that you will then have to protect.
Which requests go wrong most often?
The requests that go wrong are the ones that arrive in the wrong place, the ones that need a search nobody has done before, and the ones that mix the requester’s data with other people’s.
Make the next request routine
Tell us which countries your requesters are in and where requests land today. The reply says what a process would cover. The service is data subject request operations; Canadian detail is in the Canadian privacy law map.