MemorySync
Enterprise / Data lifecycle

Retention & Export

The retention and data-movement controls available in the dashboard today: audit log retention, project exports, and recoverable deletion.

Audit trail

Audit log retention

Audit retention is configured in Settings → Audit, alongside the log view itself. Entries older than the configured window are removed by background enforcement, so there is nothing to run manually.

Set the window
Choose how long audit entries are kept. The current policy is shown next to the log view.
Enforcement is automatic
Expired entries are purged in the background rather than at request time.
Export before shortening
Reducing the window is destructive for entries already past the new limit. Export first if you may need them.
Forward for longer retention
If you need retention beyond what you keep here, forward entries to your own platform and let it own long-term storage.
Export

Exporting project data

Project exports are requested from Settings → Organization. An export is prepared in the background, and recent exports remain listed so they can be downloaded again without re-running the job.

What it contains
The project’s memories and their metadata, as a downloadable archive.
Prepared asynchronously
Large projects take time. The request returns immediately and the download appears when the job completes.
History is kept
Recent exports are listed with their status, so you can re-download rather than regenerate.
Treat it as sensitive
An export is a full copy of user content. Store and share it accordingly.

For per-user extraction rather than a whole project, use the export operation in the memory API, which returns only what the calling scope can read.

Deletion

Deletion, trash, and recovery

Where
Settings → Organization
Effect
Memories are removed from everyday use and held in trash, where they can be recovered for a limited window before being purged.
Reversible?
Recoverable during the retention window

Deleting individual memories from your application uses the forget operation in the memory API, which removes them from retrieval immediately. Whichever path you use, the audit trail keeps the record that the deletion happened — that record is what lets you show the action was carried out.