
How we keep our docs in sync with the code
Documentation
The GDPR-DSAR agent we run on Kortix — it verifies each incoming access or deletion request, locates the subject's data across our product database, compiles the report inside the SLA, and flags it for legal to review before anything goes out.
A GDPR data subject access request starts a clock. From the day we can verify who's asking, we have one calendar month to tell them what we hold on them, or to delete it — and that data is never in one place. It's spread across a users table, an orders table, a support history, an events table, a dozen joins a person has to know to write by hand. Miss the deadline or miss a table, and the exposure is the regulator's, not just the requester's.
We run a GDPR-DSAR agent on Kortix that reads each request out of our legal inbox, verifies it, locates the subject across the product database, and compiles the access-or-deletion report as a Google Doc — every day, well inside the SLA. It never deletes anything and never replies to the requester. It compiles and flags; legal decides and sends.
A DSAR arrives as an email, but the data it's asking about lives in a relational schema built for the product, not for privacy law. "Everything you have on me" means rows in the users table, orders, invoices, support tickets, login history, marketing consent, and whatever else joins off a customer ID — tables that were never designed to be read together, by someone who has one month to do it and get it right every time.
The common approaches don't hold up under repetition. A shared spreadsheet of "where subject data lives" goes stale the moment the schema changes. Assigning it to whoever's free that week means the verification step — confirming the requester actually is the subject, not someone phishing for their data — gets rushed or skipped. And a script that queries and deletes in the same run has no way to stop and ask a lawyer first.
On Kortix, a daily cron triggers an agent. It spawns a fresh session that checks our legal inbox in Gmail for new DSAR emails, verifies each requester against the identity details we already hold, then queries Postgres read-only across every table keyed to that subject — account, orders, support history, consent records — and compiles the findings into a Google Doc formatted as an access report (or a deletion inventory, if that's what was asked for). The doc, and a recommended action, get flagged to legal for review. The agent never runs a delete and never emails the subject back.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the dsar-fulfillment skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily GDPR data subject request agent in this workspace.
Create the agent agents/gdpr-dsar.md. Its job is to turn each data subject access or deletion request into a verified report for legal review. It may use the Gmail, PostgreSQL and Google Docs connectors and the legal review email channel.
Create the skill skills/dsar-fulfillment/SKILL.md with these rules:
Add a cron trigger daily-dsar-sweep to kortix.yaml. It runs the gdpr-dsar agent every day at 07:00 with the prompt "Load the dsar-fulfillment skill and run one complete DSAR sweep."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect Gmail, PostgreSQL and Google Docs, then connect the legal review inbox under Channels. Use a read-only database user for PostgreSQL. Credentials are brokered server-side and never enter the agent's machine.

Reads incoming requests and verifies each requester.
Finds the subject's records across tables, read-only.

Writes the access or deletion report for legal review.
Merge the change request, then start a session with the gdpr-dsar agent and send this prompt. Read the first report end to end before you let the schedule take over.
Run one DSAR sweep.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 07:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: daily-dsar-sweep name: Daily DSAR sweep on: cron: "0 0 7 * * *" run: agent: gdpr-dsar prompt: Load the dsar-fulfillment skill and run one complete DSAR sweep.Every database query is a read. Even an explicit erasure request ends as a recommendation in the report. The agent's only outbound message goes to the legal review channel. A lawyer approves the action, and a person runs any deletion and writes the reply to the requester.
Each request ends with one flag in the legal review channel. This is what a run looks like in the session:
Found 2 new requests. Verified 1 deletion request, located the subject in 6 tables and compiled the report, due in 30 days. Flagged 1 access request as unverified: the sender address matches no account.
Once it works, paste any of these into the same session.
Each run, list every compiled request with less than 7 days to its deadline and send that list to the legal review channel.
For each compiled access request, add a draft reply to the requester at the end of the report for legal to edit. Do not send it.
When a query finds subject data in a table the skill does not list, add that table to the skill in a change request for me to review.
A DSAR touches the most sensitive data we hold, so the agent's access is scoped and its authority stops well short of the parts that matter:
SELECT.A request that used to mean someone manually joining tables under deadline pressure now arrives in legal's queue as a compiled report, well inside the SLA, with the data located and the action recommended. The agent verifies and compiles; the people decide, delete, and reply.