Language

🇬🇧English🇩🇰Dansk🇸🇪Svenska🇩🇪Deutsch

Requests for Insight

A request arrives. The clock starts.

Every data subject right has a deadline attached to it. Requests for Insight turns each one into a case with an owner and a countdown, sitting on top of the only thing that makes it answerable: knowing where that person's data actually is.

Try now for freeSee the platform

Article 15

30

days, from the request arriving to the answer going out

  1. ClassifyDecide what the data actually is.
  2. Verify (this page)Let the person who owns it confirm.
  3. ActBlock, strip, relabel or remove.

Requests for Insight

Awaiting capture

The requests list with status, type, assignee, days left and deadline columns

public/product/insight-requests-list.webp

Every open case, who owns it and how many days are left.

Workflow

From the form to the answer

The part most organisations do in a shared mailbox and a spreadsheet.

1

It arrives

Through a form you publish and configure, or added by hand when it came by post or over the phone. Either way it gets a request ID, a received date and a deadline.

2

It gets an owner and a type

Access, erasure, rectification, portability, restriction or objection, under the regulation that applies, assigned to a named person. Unassigned and overdue are both visible at a glance.

3

It is answered from the data

Open the data subject and see every document holding their data, or open a redaction project to take other people out of the documents before they are handed over.

4

It is closed and counted

Finished or rejected, with the full history kept. Totals, open, overdue, finished, rejected and average days to close, plus created and closed per week.

Requests for Insight

Awaiting capture

The public request form settings

public/product/insight-requests-form.webp

The form data subjects fill in, which opens a case automatically.

Capability

What makes it survivable

01

Rights

All six request types

Access, erasure, rectification, portability, restriction and objection, each with the regulation it falls under, rather than one generic request bucket.

02

Deadlines

Days left, and days overdue

Every case carries its deadline and its remaining days. Overdue is a filter, not a discovery you make later.

03

Ownership

Assignees and assigned to me

Cases belong to people. Filter by assignee, by assigned to me, by status, by type or by regulation.

04

Connected

One click to the data

Open data subject goes straight to everything held about that person. Open redaction project goes straight to taking third parties out of it.

05

Intake

A form you control

Publish a request form with the fields and wording you want, so requests arrive structured instead of as free text in an inbox.

06

Reporting

Numbers for the annual report

Total, open, overdue, finished, rejected and average days to close, with requests created and closed over time.

Questions about requests

What makes answering a request hard?+
Not the case management. It is finding every place the person appears. That is why this sits on top of Data Subject rather than being a standalone ticketing tool.
Can we handle requests that did not come through the form?+
Yes. A request can be added manually with the date it was received, so the deadline is calculated from the real date.
How do we avoid disclosing other people's data?+
Open a redaction project from the case. See Redaction for how the content is removed from the file itself.

Stop running requests from a mailbox

See how a request looks when the data behind it is already mapped.