Dsar Processing

Processing Data Subject Access Requests

Overview

A Data Subject Access Request (DSAR) is the right of an individual under GDPR Article 15 to obtain confirmation of whether their personal data is being processed, and if so, to access that data along with supplementary information. This skill provides a complete operational workflow for receiving, validating, processing, and responding to DSARs within the legally mandated timeframe.

Legal Foundation

GDPR Article 15 — Right of Access by the Data Subject

1. Art. 15(1) — The data subject has the right to obtain from the controller confirmation as to whether personal data concerning them is being processed, and where that is the case, access to the personal data and the following information:

   • (a) the purposes of the processing
   • (b) the categories of personal data concerned
   • (c) the recipients or categories of recipient to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations
   • (d) where possible, the envisaged period for which the personal data will be stored, or if not possible, the criteria used to determine that period
   • (e) the existence of the right to request rectification, erasure, restriction, or to object to processing
   • (f) the right to lodge a complaint with a supervisory authority
   • (g) where the personal data are not collected from the data subject, any available information as to their source
   • (h) the existence of automated decision-making, including profiling, referred to in Art. 22(1) and (4), and meaningful information about the logic involved, significance, and envisaged consequences

2. Art. 15(3) — The controller shall provide a copy of the personal data undergoing processing. For additional copies, the controller may charge a reasonable fee based on administrative costs.

3. Art. 15(4) — The right to obtain a copy shall not adversely affect the rights and freedoms of others.

GDPR Article 12 — Transparent Communication

• Art. 12(3) — Response deadline: without undue delay and in any event within one month of receipt. That period may be extended by two further months where necessary, taking into account the complexity and number of requests. The controller shall inform the data subject of any such extension within one month of receipt, together with the reasons for the delay.
• Art. 12(5) — Where requests are manifestly unfounded or excessive (particularly due to repetitive character), the controller may either charge a reasonable fee or refuse to act. The controller bears the burden of demonstrating the manifestly unfounded or excessive character.

DSAR Processing Workflow

Step 1: Receive and Log the Request

1. Record the request in the DSAR tracking register with a unique reference number (format: DSAR-YYYY-NNNN).
2. Capture the channel of receipt (email, web form, postal mail, telephone, in-person).
3. Timestamp the receipt to the minute using UTC.
4. Assign the request to the designated DSAR processing team member.
5. Send an acknowledgement to the data subject within 3 business days confirming receipt and reference number.

Step 2: Verify the Identity of the Requester

1. Low-risk verification (request received from a verified account, e.g., logged-in customer portal): Confirm account ownership via existing authentication.
2. Medium-risk verification (request received via email matching records): Request two of the following — date of birth, account number, postal code associated with the account, last four digits of payment method.
3. High-risk verification (request from unrecognised channel or on behalf of another person): Require government-issued photo ID plus one additional identifier. For third-party requests (e.g., solicitor acting on behalf), require written authorisation signed by the data subject plus proof of identity for both the representative and the data subject.
4. If identity cannot be verified, inform the requester within 10 business days that additional proof is required. The 30-day response clock pauses until verification is complete per EDPB Guidelines 01/2022 paragraph 64.

Step 3: Assess the Request Scope

1. Determine whether the request covers all personal data or a specific subset.
2. Identify all data processing systems where the subject's data may reside:
   • CRM systems (e.g., Salesforce, HubSpot)
   • HR/payroll systems (for employee DSARs)
   • Marketing automation platforms
   • Customer support ticket systems
   • Analytics and logging platforms
   • Backup and archival systems
   • Third-party processor systems
3. Document any data that falls under exemptions (see Step 5).
4. Where the controller processes a large quantity of data, request that the data subject specify the information or processing activities to which the request relates, per Recital 63.

Step 4: Calculate the Response Deadline

1. Standard deadline: 30 calendar days from the day after receipt of the request (or from the day after identity verification is completed, if verification was required).
2. Extension: Where the request is complex or where there are numerous requests, extend by up to two additional months (total maximum: 90 calendar days). Notify the data subject of the extension and reasons within the initial 30-day period.
3. Weekend/holiday rule: If the deadline falls on a weekend or public holiday in the controller's jurisdiction, the deadline moves to the next business day per Regulation (EEC, Euratom) No 1182/71.