Quick answer
A data subject request (DSR) is a person's request to exercise a right over the personal data an organization holds about them: to access, correct, delete, restrict, move or object. A DSAR is the access-only kind. Finding the person's data across systems is usually the hardest part.
What is a data subject request?
A data subject request (DSR) is a request from a person, the data subject, to exercise a right over the personal data an organization holds about them: to see it, correct it, delete it, restrict its use, move it or object to its use. The most common kind is the data subject access request (DSAR), also called a subject access request (SAR), which asks what the organization holds and for a copy. Sources use DSR as the umbrella term and DSAR for the access request, though some use them interchangeably.
Two points from the UK Information Commissioner's Office apply well beyond the UK. A request has no formal requirements: it can be spoken or written, and it does not need to say "subject access request" or cite an article, as long as it is clear that the person is asking for their own personal information. And any employee can receive one, so a request may arrive in a support chat, a social media message or an email to a sales address.
This page explains the concept and cites the GDPR text; it is not legal advice, and deadlines and exemptions differ between laws.
The rights behind the request
Under the GDPR, a DSR usually falls into one of these rights.
| Request | GDPR article | What the person is asking for | What the organization must be able to do |
|---|---|---|---|
| Access | 15 | Confirmation of whether their data is processed, a copy, and supplementary information such as purposes, recipients and retention | Collect every record about the person into one readable copy |
| Rectification | 16 | Correct inaccurate data | Edit the value wherever it is stored |
| Erasure | 17 | Delete the data when a ground applies, for example it is no longer needed or consent is withdrawn | Delete across systems, and know the exceptions in 17(3) such as a legal obligation or legal claims |
| Restriction | 18 | Stop using the data for now, but keep it | Freeze processing without deleting |
| Portability | 20 | Receive the data they supplied in a structured, commonly used, machine-readable form | Export in a usable format |
| Objection | 21 | Stop a type of processing, such as direct marketing | Stop that processing |
Access is the request that tests an organization's records the hardest, because it needs everything, not one field.
The hard part: finding the person's data
The form is easy. The difficulty is that one person is stored under several keys in several places, and you can only search the key you were given.
Sample data: Maya writes to a software company from her email address. The company holds records about her in six places.
| System | Key it stores | Records about Maya | Found by email alone? | Found with an identity map? |
|---|---|---|---|---|
| Billing | 6 | Yes | Yes | |
| Product database | Login ID | 215 | No | Yes |
| Analytics, signed in | Login ID and two device IDs | 1,341 | No | Yes |
| Analytics, before sign-in | A rotating visitor ID only | 37 | No | No |
| Support chat | Email she typed in the chat | 3 | Yes | Yes |
| Email tool | 17 | Yes | Yes |
Total records: 6 + 215 + 1,341 + 37 + 3 + 17 = 1,619.
- Searching by email alone finds 26 records (6 + 3 + 17), which is 1.6% of the total and 3 of 6 systems.
- Searching by login ID alone finds 1,556 records (96.1%), but only 2 of 6 systems; billing, chat and the email tool are missed.
- With an identity map that links email, login ID and device IDs, you find 1,582 records (97.7%) in 5 of 6 systems.
- The remaining 37 records (2.3%) belong to browsing before she signed in. They carry no key she can give you.
The lesson is that you cannot answer an access request or perform an erasure faster than you can map identities, and no amount of form handling changes that. For the mapping itself, see identity resolution and data governance.
The GDPR addresses the last row directly. Article 11 says a controller is not obliged to collect extra data just to identify a person, and where it can demonstrate it cannot identify the person, Articles 15 to 20 do not apply unless the person supplies additional information that makes identification possible. Whether that applies to your anonymous data is for your counsel to decide. Article 12(6) is the companion rule: when there is reasonable doubt about who is asking, you may ask for more information to confirm identity.
How long you have
Article 12(3) requires a response without undue delay and in any event within one month of receiving the request. The period can be extended by two further months where requests are complex or numerous, and the person must be told of the extension, with reasons, within the first month. Responses are free of charge unless a request is manifestly unfounded or excessive (Article 12(5)). The ICO adds that the clock starts when you have the information needed to confirm identity, and pauses while you ask the person to clarify. Other laws set different periods; check the law that applies to you.
A handling sequence
- Log it when it arrives, whichever channel it came through, and note the date.
- Confirm who is asking, in a proportionate way. Ask for more only where you have reasonable doubt.
- List the identifiers you hold for this person (email, login ID, device IDs, customer number) and the systems each appears in.
- Search every system and record which ones you searched and what you found; a reasonable and proportionate search is the standard.
- Check the exceptions before acting on an erasure: a legal obligation to keep the data, or its use for legal claims, can apply (Article 17(3)).
- Act, then answer, with the copy, the confirmation of deletion or the reason for refusal, inside the deadline, and keep a record.
Common misunderstandings
- "It must come through our form." It does not. A clear request in any channel counts, including a chat message.
- "Stopping tracking is the same as deleting." An opt-out stops future collection. Rows already stored stay until retention expires or an erasure request removes them.
- "Erasure always means delete everything." The Article 17(3) exceptions can apply, and aggregated statistics that contain no personal data are not what the request is about.
- "One system is enough." Analytics is one place. Billing, support, email tools and backups hold their own copies.
- "The deadline is a fixed number of days." The GDPR text says one month, extendable by two further months in complex cases. Read the deadline in the law that applies to you rather than using a rule of thumb.
Data subject requests in TapCub
Take Maya's email: she asks what the company holds on her and wants it deleted. This is how the analytics part of the request goes in TapCub.
- Confirm who is asking before you create anything; that step is yours.
- Find her identifiers. On an identified project, All-platform analytics › Users › People shows her profile, and All-platform analytics › Users › Identity map lists how her login ID and devices are linked. A subject can be entered as a device ID, login ID, email or person ID; an email is matched after a server-side hash. Anonymous visitors have no profile, so there is nothing to find by email.
- Create the request in Configuration › Privacy center, under Data subject requests (DSAR). The types are access, erasure, restrict and portability. A key with the
privacy:writepermission can also create requests, and an external privacy platform can submit them through the OpenDSR path. - Know what runs when. Access and portability run immediately and the result can be downloaded. Erasure and restrict stop TapCub processing new events for that subject as soon as you submit them, then wait out a cooling-off period, 3 days by default and 7 in China mode, and you can cancel during it.
- Know what erasure covers. It deletes the subject's stored rows, including that visitor's replay recordings. Daily aggregates contain no personal data and are not rewritten. Live-chat conversations are not part of it: an owner or admin deletes a conversation from the inbox, which removes its messages and attachment files at once.
TapCub does not verify the requester, does not search your other systems, and does not decide whether an exception applies. See handle a data-subject request and data export and deletion. How the underlying principle limits collection is in data minimization, and for the law behind the rights see GDPR.
Sources
- EUR-Lex, Regulation (EU) 2016/679 (GDPR): Articles 11, 12, 15 to 18, 20 and 21.
- Information Commissioner's Office, A guide to subject access.
- Information Commissioner's Office, How do we recognise a subject access request (SAR)?
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Engineer
Writes about event design, data quality, and collection workflows, with verifiable implementation methods for reliable analytics.