Retention and export
Owners and admins see both in Settings → Data.
How long data is kept
Section titled “How long data is kept”| Data | Kept |
|---|---|
| Sessions: messages, plans, code and attachments | Until you delete the session |
| Files | Until you delete them in Files |
| Memory and lessons | Until you delete or retire them |
| Command output inside sessions | 7 days |
| Traces your application sends | 14 days |
| Model responses kept so that a retried step is not charged twice | 30 days; the usage numbers stay |
| Evaluation output | 90 days; each case’s result stays |
| Access history | 365 days |
| Exports | 7 days |
| Previews of your app | 30 minutes at most; the link stops working when the preview ends |
| Credits and usage numbers | For billing reconciliation; they hold no content |
| Deletion records | Kept without any content, so a restored backup cannot bring deleted data back |
WeHarness applies this policy once a day and records each run, so retention is checked rather than assumed. The Data page shows when the policy was last applied. Deleting a session ends access to its data straight away, whatever the period (see Deleting a project).
Exporting a workspace
Section titled “Exporting a workspace”An owner or admin can prepare an export in the WeHarness web app. API tokens and MCP cannot ask for one.
The export is prepared in the background as a tracked run. It is one ZIP archive with one JSON file for each kind of data:
- sessions, with their messages;
- plans;
- the memory shared in the workspace (personal items stay with the person who saved them);
- lessons;
- scenario cases;
- the credit ledger.
Files you uploaded are not in the archive; download them from Files.
Each Download opens a link that works for 10 minutes and is recorded in the access history. The archive is kept for 7 days, then deleted.