Free trial
Colour

The privacy request log and due dates

Log each export, erasure or correction request, set its due date and see which are overdue.

For
OwnerAdministrator
Hosting
Any hosting
Devices
Web browserServer
Business
All businesses

Checked against Pop Dispatch 0.1.0

The request log keeps one row for each request a person makes about their data: export, erasure or correction. You set the due date for each, so you can show that you answered in time.

Before you start #

  • You need the owner or manager role.
  • The time you have to answer depends on the law that applies to you. Check it with your adviser and set the due dates to match.

Steps #

  1. Open the person on the Person data tab. Under Log a request choose the kind (Export, Erasure or Correction), say how it arrived, set the Due date and add a note. If you leave the date empty, the default number of days applies.
  2. Open Request log. Open requests show first, soonest due at the top. A request past its date shows Overdue.
  3. Change a due date straight in the table.
  4. For a correction, change the record on its own screen, then choose Mark done. Choose Mark refused when you decline a request, and write the reason in the note.
  5. Under Default days to answer a request, set the number of days used when you leave the date empty. It starts at 30. You can set 1 to 365.

Running an export or an erasure from the person's panel closes its request for you. When no request was logged first, Pop Dispatch adds one and marks it done. After an erasure, the person's name and contact are removed from their log rows.

Technical details

GET /privacy/requests, POST /privacy/requests, PATCH /privacy/requests/:id and GET/PATCH /privacy/settings (due_days). Rows hold the kind, the person kind and number, the received and due dates, the status and a result summary with counts only.