Data requests

Who this covers

The people who raise requests. Your agents are staff; the person who wrote in may be a colleague, a customer or a member of the public, and their address and their words sit on the request. That is the personal data Helpora holds about them.

1 · Subject access — export everything held

Requester alex@example.com (5 requests) bea@example.com (5 requests) chris@example.com (5 requests) dana@example.com (5 requests) demo@example.com (1 request) eli@example.com (4 requests) fran@example.com (4 requests) gus@example.com (4 requests) hana@example.com (4 requests) happy@example.com (1 request) ivo@example.com (4 requests) jo@example.com (4 requests) patient@example.com (1 request) silent@example.com (1 request) stillwaiting@example.com (1 request) waiting@example.com (1 request)

Download their data (JSON)

2 · Erasure — remove someone's data

On every request they raised, their address, the subject line, the details they wrote, the resolution written back to them, their "did it help?" comment, every message in the thread and the notes in the request log are replaced with [removed], and the photos they attached are deleted from disk.

The requests themselves stay. The reference, the queue, the status and both clocks with their stamps are the evidence of how the desk performed; once the words are gone they name nobody.

Helpora refuses while any of their requests is still open, because the desk may still owe them an answer.

Requester alex@example.com bea@example.com chris@example.com dana@example.com demo@example.com eli@example.com fran@example.com gus@example.com hana@example.com happy@example.com ivo@example.com jo@example.com patient@example.com silent@example.com stillwaiting@example.com waiting@example.com

Erase their data