Data subject request operations
The first request is rarely the problem. The problem is the third one arriving while the second is still being searched for, in a system nobody has looked at since it was installed, with a legal clock running.
The short version
A data-subject request is a person asking an organization what it holds about them, or asking it to correct, delete, export or stop using that data, under a privacy law. The work here makes the answer routine: a single place requests arrive, a way to check who is asking, a known list of where to search, and a log that shows the deadline was met.
Deadlines differ by law
Deadlines are set by each law and differ by request type. 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. The GDPR and UK GDPR period is the shorter of the two.
Sources: the ICO’s guide to subject access and Article 12 of the GDPR on EUR-Lex; the California Privacy Protection Agency’s FAQ. Deadlines also vary by request type and are amended, so the current text is confirmed with your counsel before a process is fixed to it.
How one request moves
Each request follows five steps: it is received, the requester is verified, the systems are searched, a response is sent, and the outcome is logged.
What you get
- An intake route. One address or form, accepted wherever a request lands, including a request sent to a salesperson.
- Identity verification. Identity checks should be proportionate: enough to be sure the requester is the person concerned, without collecting more personal data than the check needs.
- A search guide. Which systems to search for which kind of request, taken from the data map.
- Response templates and exceptions. Drafts for each outcome, with the points that need counsel marked.
- A deadline tracker and a log. The clock for each law that applies and the record that the response was made.
Doing it for you, or building it with you
Either. We can design the process and train your people to run it, or handle intake, search and drafting on your behalf, while the decision to disclose or refuse stays with you and your counsel. Where request volume justifies software, selection is covered in privacy tool selection and implementation.
Deletion requests meet the retention schedule, which is why records management and retention and the request process are best designed together. Website opt-out signals are handled on website consent and cookie review.
Who it is for
Organizations with customers, users or employees in more than one jurisdiction, software companies whose enterprise customers forward requests, and anyone who has just received their first request.
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 what it holds about them, or asking it to correct, delete, export or stop using that data, under a privacy law.
How long do we have to respond?
Deadlines are set by each law and differ by request type. 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.
How should we verify who is asking?
Identity checks should be proportionate: enough to be sure the requester is the person concerned, without collecting more personal data than the check needs.
Can you handle requests for us?
Either. We can design the process and train your people to run it, or handle intake, search and drafting on your behalf, while the decision to disclose or refuse stays with you and your counsel.
Tell us how requests arrive today
Background reading: data subject requests across jurisdictions. Say which laws you think apply, roughly how many requests you receive and where they land. The reply says what a process would cover. See also all privacy services.