Stated data retention

The idea

Settings shows what is kept and for how long from the constants in force; full model inputs are kept 7 days and only the requester can read or delete them.

The problem
Customers cannot tell what is stored about their work.
Why it matters
Retention is visible and held to the running code by a test.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Redaction on write and the credential vault

    Secret-shaped values are removed before events, steps, tool results and model context are stored, and customer credentials are sealed with AES-256-GCM bound to org and credential.

  • Erasure by tombstone, log untouched

    Owner-only calls erase an organization or a person in one transaction; the person becomes a tombstone and audit rows point at it, so the log is never edited.

  • Append-only, hash-chained audit log

    Every event is appended to a per-org hash chain that a database trigger keeps from change or deletion, with secrets redacted first.

  • Forget reaches derived copies

    When a person forgets a note, the platform also rewrites the copies that work made from it: briefs, plans, findings, logs and outputs. It also cancels approvals and holds outreach that quote the note.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.