How we handle GDPR data-subject requests on a deadline
Legal
The NDA agent we run on Kortix — every 15 minutes it reviews a new inbound NDA against our standard playbook, redlines the non-standard terms in the document, and drafts a flag summary for counsel. It never signs or sends; counsel does.
An NDA is the most standardized document a deal touches, and also the one most likely to sit in an inbox for two days waiting for someone with a law degree to open it. The deal doesn't move until it's signed, but the review itself is usually mechanical: the same eight or nine clauses, checked against the same standard positions, over and over.
We run an NDA-turnaround agent on Kortix that watches for inbound NDAs and gives each one its first pass within fifteen minutes of arriving. It redlines what deviates from our standard positions and drafts a flag summary for counsel. It never signs anything and never sends anything to the counterparty — counsel does both. This is how we keep NDAs from being the thing a deal waits on.
NDAs are high volume and low variance — most deals need one, and most of them follow the same handful of templates with the same handful of predictable deviations: a one-way instead of mutual, a perpetual confidentiality term, a non-solicit that reaches further than it should. None of that requires a first read from a lawyer. It just requires someone to check.
But "someone" means counsel, and counsel's queue is full of things that actually need judgment. An NDA that's 90% standard waits behind a contract renegotiation, and the deal it's gating waits with it. By the time it gets reviewed, the delay has nothing to do with the document's complexity and everything to do with queue position.
On Kortix, a cron fires every 15 minutes and checks a watched Gmail label for a new inbound NDA. Each firing spawns a fresh session — a cloud sandbox — that saves the attached document into a Drive folder, opens it in Docs, checks it clause by clause against our standard NDA playbook, redlines every deviation as a suggested edit in the document, and drafts — never sends — a flag summary on the original email thread addressed to counsel. Counsel opens the thread to a redline and a summary instead of a blank document.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the NDA playbook skill and the 15-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up an NDA turnaround agent in this workspace.
Create the agent agents/nda-turnaround.md. Its job is to give each new inbound NDA a first-pass review, a redline and a flag summary for counsel. It may use the Gmail, Google Drive and Google Docs connectors.
Create the skill skills/nda-playbook/SKILL.md with these rules:
Add a cron trigger nda-check to kortix.yaml. It runs the nda-turnaround agent every 15 minutes with the prompt "Load the nda-playbook skill and review the oldest unprocessed NDA under the NDAs label."
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 your email, your drive and your documents. Credentials are brokered server-side and never enter the agent's machine.

Picks up inbound NDAs from the watched label.

Saves each NDA and its redlines to the NDA folder.

Merge the change request, then start a session with the nda-turnaround agent and send this prompt. Read the suggested edits and the draft reply before you let the schedule take over.
Review the oldest unprocessed NDA under the NDAs label in Gmail.
The change request added this trigger to kortix.yaml. From now on the agent
runs every 15 minutes, 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: nda-check name: NDA turnaround check on: cron: "0 */15 * * * *" run: agent: nda-turnaround prompt: Load the nda-playbook skill and review the oldest unprocessed NDA under the NDAs label.The agent's only outputs are suggested edits in the Doc and a draft reply in Gmail. It never applies a suggestion, never sends the reply, and never signs, executes or messages the counterparty. Counsel reviews the redline and decides what goes back.
Each run ends with a redlined Doc and a draft reply for counsel. This is what a run looks like in the session:
Reviewed a one-way NDA with a 5-year confidentiality term. Flagged 3 clauses: the duration, a 24-month non-solicit that covers customers, and the governing law. Each has a suggested edit, and the summary for counsel is saved as a draft on the thread.
Once it works, paste any of these into the same session.
Every Monday, write a Google Doc in Legal/NDAs that lists last week's NDAs, their flagged clauses and whether counsel has replied.
When counsel rejects one of your suggested edits, propose a change to the nda-playbook skill that records the new position.
Before you review an NDA, look in Legal/NDAs for an earlier NDA with the same counterparty and note each clause that changed.
An agent that touches an unsigned legal document needs a hard line between drafting and executing:
NDAs stop being the paperwork a deal waits on. Counsel opens a thread to a redline already marked against our standard positions and a summary of exactly what's non-standard and why, instead of a cold document. The agent does the first pass; counsel still signs off on every word that goes back to the counterparty.