DriverDevelopers

Zero data retention

One flag and nothing the execution sees is stored. Events stream to your client and die there.

const { Driver } = require('@crtrs/driver');

const driver = new Driver({ apiKey: 'dr_••••••••' });

// Sugar: one zero-data-retention run.
const done = await driver.runZdr('summarize this confidential brief');
console.log(done.result);

// Same thing as a per-run option.
await driver.run('summarize this confidential brief', { zdr: true });

// Whole instance: every run is ZDR unless a run says otherwise.
const vault = new Driver({ apiKey: 'dr_••••••••', zdr: true });
await vault.run('routine task', { zdr: false }); // explicit opt-out wins

Three shapes, one behavior: runZdr is the sugar for one-off calls, { zdr: true } the per-run option, and setting it in the constructor makes the whole instance ZDR so every run inherits it. An explicit zdr: false on a run always wins over the instance default.

Exactly what is stored

The receipt survives; the content never exists. Per run:

Prompt
No
Blanked before the run record is first written.
Event log
No
Plan, steps, tool calls, results, final answer: never written.
Intermediate outputs
No
The working files an execution spills are deleted when it ends.
Tool usage
No
Neither tool names nor how many ran.
Run id + status
Yes
The receipt: the run existed and how it ended.
Timestamps
Yes
Started / ended. Billing evidence.
Key (masked) + account
Yes
Attribution of the spend to your account.
Quota consumption
Yes
One accepted run = one execution from your plan.

In the dashboard a ZDR run shows the mark, status and timestamps, nothing else. The choice is per run, so the same key can mix retained and ZDR executions. ZDR covers CREATORS infrastructure end to end; retention by the AI providers a run talks to is outside this scope.