Retention, export and deletion

Set how long each kind of data is kept, read the purge reports, export your data, delete it end to end, and run a backup restore drill.

Retention

A retention rule keeps one class of data for a number of days. Records older than that are purged on schedule and every purge leaves a report.

Class	What it covers
`memory`	Memory items, with their observers and code links.
`derived_data`	Derived text and vectors. Rows whose memory item is gone are swept in the same run.
`agent_conversations`	Assistant conversations.
`ci_artifacts`	CI artifact records.
`run_logs`	Run logs.

The audit log is not a class: dropping its oldest rows would break the chain, so it is exported, never purged by age.

overlane enterprise retention set --rule memory=365 --rule run_logs=90
overlane enterprise retention show
overlane enterprise retention purge --dry-run

retention purge runs a purge now, and each report lists, per class and store, the cutoff and how many records were removed. A second purge in the same minute removes nothing more. Retention is included from the Business plan up.

Export your data

overlane enterprise data export --out export.ndjson
overlane enterprise data export --scope project --subject prj-1

The file holds one JSON record per line: memory, derived text, vector metadata (not the raw vectors), conversations, CI records, logs and, for a whole-team export, the audit log. A project or user scope exports only that project’s or user’s records. Export is open to every plan.

Delete your data

overlane enterprise data delete --scope project --subject prj-1 --dry-run

Deletion removes the scope’s records from every store: indexes, derived rows, vectors, logs and, for a whole team, the backup snapshots Overlane wrote. The report lists the rows removed per store. Database point-in-time copies cannot be edited; they age out within 30 days, and the report states that date. The audit log keeps identifiers only, including the deletion itself, so the record of what was deleted and by whom stays. Deleting needs --force without a terminal, is in the deletion class of autonomy, and is open to every plan.

Backup restore drill

The drill takes a snapshot of a team’s data, reads it back from storage, restores it into a scratch target and compares the record count of every table with the source. The restored audit rows must also still verify as a chain. The report states each table’s expected and restored counts and passes only if all match. Snapshots expire after 30 days.