A Data Subject Access Request (DSAR) is a formal request from an individual exercising their rights under [GDPR art. 15–22] — to access their data, have it rectified or erased, restrict its processing, receive a portable copy, object to processing, or not be subject to solely automated individual decisions. Under [GDPR art. 12(3)], you must respond without undue delay and at the latest within one month of receipt. That period can be extended by two further months where necessary, taking into account the complexity and number of requests, provided you tell the requester about the extension, with the reasons, within the first month.
Logging a request
DSARs typically arrive by email to your privacy contact address. When one arrives:
- Open DSAR inbox in the dashboard sidebar.
- Click + New request.
- Enter the requester's email, the Date received and the subject line and text of the request (miniterms classifies the kind of request automatically). The date received is the day the request first reached you through any channel you offer (for example your general contact address), not only your privacy contact address, and not the day you log it. The 72-hour acknowledgement target and the one-month response deadline both run from that date.
- Click Create request. The request opens: check Kind and correct it if the automatic classification is wrong. The table below sets out what to do for each kind; if the request covers several rights, handle all of them.
Request kinds
| Kind | What you must do |
|---|---|
| Access | Confirm whether you process their data and, if so, give them a copy together with the information listed in GDPR art. 15 (purposes, recipients, retention period, source of the data, etc.) |
| Erasure | Erase their data where one of the grounds in GDPR art. 17(1) applies, unless an art. 17(3) exception applies (e.g. a legal obligation or the defence of legal claims). In Spain, data you must keep is blocked (art. 32 LOPDGDD) |
| Portability | Give them the data they provided to you in a structured, commonly used, machine-readable format, where the processing is based on consent or a contract and carried out by automated means |
| Restriction | Store the data without otherwise processing it (except with consent, for legal claims or the other GDPR art. 18(2) exceptions) while one of the art. 18(1) situations applies, e.g. while you verify its accuracy or an objection |
| Objection | If they object to direct marketing, stop processing their data for that purpose. If the processing is based on legitimate or public interest, stop unless you can show compelling legitimate grounds or need it for legal claims |
| Rectification | Correct inaccurate data and complete incomplete data |
| Automated decisions | Do not subject them to decisions based solely on automated processing that produce legal or similarly significant effects, unless a GDPR art. 22(2) exception applies; in those cases, ensure human intervention and their right to express their point of view and contest the decision |
Responding
Open the request from the inbox. You will see the request detail and remaining days. When you have prepared the response:
- Set Status to Fulfilled, or to Refused if you are lawfully declining the request.
- In Audit notes, record the response date and a brief note — what you sent, which data categories were included, any lawful exemptions applied. If you refuse, GDPR art. 12(4) requires you to tell the requester, within the same one-month period, the reasons and that they can lodge a complaint with a supervisory authority and seek a judicial remedy; record that you did.
- Click Save changes.
Keep this log accurate. It is part of your accountability record under [GDPR art. 5(2)] if a regulator asks for evidence of compliance.
Overdue and escalated requests
Requests with three or fewer days remaining turn amber. Requests past the deadline turn red. Missing a deadline can lead to a complaint to the competent supervisory authority (in Spain, the AEPD) and, where applicable, sanction proceedings.
If a request requires the two-month extension, notify the requester in writing within the original one-month window (giving the reason), then set Status to Escalated and record the extension and the new deadline date in Audit notes. The inbox keeps counting down to the original one-month deadline, so the request will turn red at that date even though the extension is valid.
72-hour acknowledgement alert (Dekimu Hub)
If you have not yet acknowledged a request with status New, Needs review or Escalated, and its 72-hour acknowledgement target (counted from the date received) is 24 hours or less away, or has passed, miniterms raises an alert in your Dekimu Hub inbox when you open the DSAR inbox in the dashboard, so it does not slip. To mark a request acknowledged, confirm receipt to the requester yourself (miniterms sends nothing), then set Status to Acknowledged and click Save changes. The GDPR sets no 72-hour deadline for acknowledging a request: this is a working target inside miniterms. The legal deadline is the one-month response period above. The alert only appears if you use Dekimu Hub.
miniterms tracks DSAR deadlines but does not automatically draft or send responses. Response content is your responsibility as data controller.