The deadline runs from receipt, not from reading
One month or a shorter deadline per form type, with early warning and overrun as notifications. An extension of up to two months needs a reason in the request, just as Art. 12(3) demands.
The entry point Art. 12 GDPR requires, instead of an e-mail address in the privacy notice
Art. 12(2) GDPR requires the controller to facilitate the exercise of data subject rights, and paragraph 3 sets the response deadline at one month from receipt. The module turns that into an address that belongs in the privacy notice, on the website or as a QR code on a form. Every submission immediately becomes a data subject request with case number, running deadline and owner; the default handlers are notified, and the applicant receives an access code for the status page and follow-up questions. The form deliberately accepts no files: an anonymous endpoint with upload would be an open door. Evidence is requested via the return channel.
One month or a shorter deadline per form type, with early warning and overrun as notifications. An extension of up to two months needs a reason in the request, just as Art. 12(3) demands.
Where there are reasonable doubts, Art. 12(6) allows additional information. The switch "identity check required" starts the request in that state; evidence is requested via the return channel, never through the open form.
Name and e-mail are always requested, everything else is configurable. The form accepts no files, because there is neither virus scanning nor captcha and an anonymous upload endpoint would be exactly the attack surface a privacy form should not open.
A data subject finds the way, the deadline runs by itself, and the evidence that you facilitate the exercise of rights is the address itself.
Schedule a no-obligation demo – we will show you the module with your own use cases.