DPO Radio

A privacy team handling rights requests at volume — fifty a month, several hundred a quarter for consumer-facing services — cannot draft every first response from scratch. Each request needs acknowledging inside a statutory window, routing to whoever holds the records, and a written reply that does not accidentally concede or refuse more than the law requires. The acknowledgement is the part that is both time-critical and highly repetitive, and it is the part that slips first when the queue grows.
The DSR batch workflow takes a CSV of pending requests and drafts the acknowledgement for every row in one pass. Each draft is written against the frameworks the organisation actually has installed, carries its citations, and is reviewed by the DPO row by row before anything is sent. Alongside each draft the workflow queues a verification task, so the substantive question — which records are genuinely in scope for this requester — is assigned to a human rather than assumed by the model.
This is a deliberate boundary. Forseti drafts the response that acknowledges the request and states the applicable deadline. It does not decide whether a request should be fulfilled, partially fulfilled, or refused. Those are determinations with legal consequence, they depend on facts the CSV does not contain, and they stay with the privacy team. What the workflow removes is the typing, not the judgement.
The upload takes three required columns — request identifier, requester email, and request type — plus an optional deadline and free-text notes. The page parses the file and reports how many rows it read before anything runs, so a malformed export is caught at upload rather than halfway through a batch. Rows that fail validation are surfaced individually; the rest proceed.
Each row produces a short acknowledgement body — one to three paragraphs — drafted against the request type and the frameworks installed for that organisation. The draft acknowledges receipt, states the applicable regulatory deadline, and asks for clarification where the request as written is ambiguous. It commits to nothing beyond the regulatory minimum, by design.
Citations are attached to the persisted draft rather than woven into the prose, so the reviewer can see the grounding without the requester receiving a letter full of bracketed references. Where no regulatory excerpt can be retrieved for a row, the draft falls back to a deterministic template and says so rather than inventing an anchor.
Before drafting, the workflow looks for prior requests from the same requester and for related processing-activity records. A repeat requester is a materially different situation from a first-time one, and the draft reflects that.
Every row queues its own verification task — confirm the in-scope records, then approve before send. The task inherits the row's deadline and is raised in priority for deletion and objection requests, which carry the tighter consequences. Tasks carry a suggested owner role; a human picks the assignee.
The DPO walks the row list and accepts or rejects each draft independently. A rejection is recorded with its operator and timestamp; the request stays in the queue for manual handling. Nothing is sent by the workflow itself.
Each row emits the same three-event trail as every Forseti workflow: run started, draft produced, draft resolved. The events are stitched by a per-row draft identifier, so an auditor can walk the batch end to end and see which drafts were accepted, which were rejected, and by whom.



Every draft is grounded before it is written. The workflow retrieves regulatory excerpts for the request type against the organisation's installed frameworks, and where it cannot, it falls back to a deterministic template rather than producing an unanchored legal claim.

Nothing sends. The workflow drafts and queues; the DPO accepts or rejects each row; a separate verification task confirms scope before a response goes out. There is no configuration in which a rights-request response leaves the platform without a human action behind it.

The audit trail records per-row outcomes stitched by draft identifier, so a regulator asking what the assistant contributed to a specific request gets a precise answer rather than a general assurance.
| Framework | How DSR Batch Processing Supports It |
|---|---|
| Vietnam Personal Data Protection Law | Drafts the acknowledgement for each row against the PDPL rights-request provisions applicable to the request type, with citations attached to the draft. |
| EU GDPR | Drafts the acknowledgement for each row against the GDPR data subject rights provisions applicable to the request type, with citations attached to the draft. |

The batch workflow prepares acknowledgements from the uploaded queue. Use the individual rights-response review for an existing case. See Privacy Workflows.
Ready to see a fifty-row rights-request queue acknowledged in one pass, with a verification task raised against every row? Request a personalised demo.


Run DSR batch processing against your active rights-request queue for 30 days. Measure how much of the acknowledgement backlog clears and how consistently the statutory clock is met.

Talk to our team about how the DSR batch workflow fits alongside your existing rights-request intake and fulfilment process.
A single batch accepts up to two hundred rows. Larger queues are processed as successive batches. No Forseti token allowance limits a batch: each run's requests go to the AI provider your organisation has configured, which bills your organisation for them, and the Usage page reports what the batches consumed.
No, and this is deliberate. Forseti drafts the acknowledgement — confirming receipt, stating the deadline, requesting clarification where needed. Whether a request is fulfilled, fulfilled in part, or refused is a determination with legal consequence that depends on facts outside the intake file, so it stays with the privacy team. Each row raises a verification task for exactly that decision.
No. The workflow produces drafts and queues tasks; it has no send capability. A response reaches a requester only after a person has reviewed the draft, confirmed the in-scope records through the verification task, and sent it themselves.
One verification task per row, titled against that request, carrying the deadline supplied in the CSV and raised to high priority for deletion and objection requests. The task asks a human to confirm which records are in scope and to approve before the response is sent. Tasks carry a suggested owner role; the operator picks the assignee.
The rejection is written to the audit trail with the operator and the time, and the request stays in the queue for manual handling or a later re-run. A rejected draft never partially applies — nothing from it reaches the request record.