Privacy

How long do you have to respond to a DSAR?

Direct answer

Under GDPR Article 12(3), a controller must respond to a data subject access request without undue delay and within one month of receiving it. The period can be extended by two further months for complex or numerous requests, giving a three-month maximum, provided you notify the individual within the first month and explain the reasons.

The legal unit is one month, not 30 days; a month is calculated by the calendar.

When does the one-month clock start, and how is it counted?

The EDPB’s Guidelines 01/2022 on the right of access say the period starts when the request reaches the controller through one of its official channels. Nobody has to have read it yet. The person may use the channels the controller provides or any official contact point, and the request needs no particular format; only a request sent to a completely random or apparently incorrect address can be left aside.

The EDPB counts the month under Regulation No 1182/71 on periods, dates and time limits:

  • A request received on 5 March must be answered by 5 April at the latest.
  • A request received on 31 August, where the next month has no 31st, must be answered by 30 September.
  • If the last day falls on a weekend or a public holiday, the controller has until the next working day.

The clock can pause. Where the controller has reasonable doubts about the requester’s identity and asks for more information without undue delay, time is suspended until it has what it needs. The same applies when a controller holding a large quantity of data asks the person to specify which processing the request relates to. The EDPB recommends confirming receipt in writing and stating the dates the period runs from and to.

When can you extend the deadline, or refuse the request?

The two-month extension in Article 12(3) is an exception, not a routine. The EDPB lists factors that can make a request complex: the amount of data processed, data that is hard to retrieve because it sits with different units, the need to redact information about other people or trade secrets, and data that needs further work to be intelligible. A large effort alone does not make a request complex, and neither does a big company receiving many requests. A temporary surge, for example after extraordinary publicity, can justify it.

Refusal is narrower still. Under Article 12(5), a controller can refuse, or charge a reasonable fee, only where a request is manifestly unfounded or excessive, in particular because it is repetitive, and it bears the burden of showing that. If you do not act on a request, Article 12(4) requires you to tell the person without delay, and at the latest within one month, why, and that they can complain to a supervisory authority and seek a judicial remedy.

The rights of others under Article 15(4) do not justify refusing outright. They lead to leaving out or making illegible the parts that would harm other people.

What must the response contain?

Article 15 has three parts: confirmation of whether you process the person’s data, access to the data itself, and information about the processing. That information covers the purposes, the categories of data, the recipients (in particular in third countries), the retention period or the criteria for it, the rights to rectification, erasure, restriction and objection, the right to complain to a supervisory authority, the source of the data where it was not collected from the person, and any automated decision-making, including profiling. Where data goes to a third country, the person is also told about the Article 46 safeguards.

The first copy of the data is free. A reasonable fee based on administrative costs is allowed only for further copies (Article 15(3)). A request made electronically is answered in a commonly used electronic form unless the person asks otherwise.

The EDPB expects the search to cover all IT systems and non-IT filing systems, and the answer to reflect the data as it stood when the request was received, including data that may be incorrect or unlawfully processed. The general information can start from your record of processing activities and privacy notice, tailored to the person asking.

How does the Swiss FADP deadline differ?

Under Article 25(7) of the revised FADP, access information is in general provided within 30 days. Article 18 of the Data Protection Ordinance sets it at 30 days from receipt of the request. If that is not possible, the controller must tell the person and say how long it will take. A decision to refuse, restrict or defer access must be communicated within the same 30 days.

The ordinance also sets the form: the request is made in writing, or verbally if the controller agrees, and can be made and answered electronically (Article 16). Access is free of charge. Where providing it involves a disproportionate effort, the controller may ask for a capped contribution to costs, but must announce the amount first; if the person does not confirm within ten days, the request is treated as withdrawn, and the 30 days start when that reflection period ends (Article 19). A processor that holds the data helps the controller answer (Article 17(2)). See the FADP compliance checklist.

How Acuna GRC handles it

Data Privacy in Acuna GRC tracks each request against a due date with a colour-coded badge, allows one extension, and links the request to the processing activities that hold the subject's data.

Sources

  1. EDPB Guidelines 01/2022 on data subject rights, right of access, version 2.1
  2. Regulation (EU) 2016/679 (GDPR), Articles 12, 15 and 83(5)
  3. Federal Act on Data Protection (FADP), Article 25
  4. Data Protection Ordinance (DPO), Articles 16 to 19

This page explains the rules in general terms and is not legal advice.

Frequently asked

Does the person have to say why they want their data?

No. The EDPB states that data subjects do not have to give reasons for an access request or justify it, and that it is not for the controller to analyse whether the request will actually help them check the lawfulness of the processing.

Can we ask for a copy of an ID card before answering?

Only where it is necessary and proportionate. The EDPB considers it disproportionate to require an identity document when the person is already authenticated, for example through their account login, and warns that ID copies create their own security risk.

What fine applies to an access request answered late or not at all?

Infringements of the data subject rights in Articles 12 to 22 fall under Article 83(5)(b): fines of up to EUR 20 000 000 or, for an undertaking, up to 4 % of total worldwide annual turnover of the preceding financial year, whichever is higher.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US