Exporting data
The export feature downloads a JSON snapshot of records available in your active organisation context. It is intended for audit review, portability, support investigation, and controlled internal analysis.
Start an export from Organisation Settings, Data. The browser downloads tow-export.json.
What the export contains
The export can include:
| Dataset | Examples |
|---|---|
| Raw events | Captured inputs, source metadata, timestamps, and content hashes. |
| Docs | Pages, revisions, chunks, references, tags, and metadata. |
| Memory | Memory type, title, body, status, confidence, source references, validity dates, and review flags. |
| Snapshots | Company or project snapshot content, type, status, sources, and validity dates. |
| Tickets | Issue key, type, title, description, status, priority, labels, due dates, assignees, hierarchy, progress, estimates, and source references. |
| Ticket history | Comments, activity, and links. |
| Operating records | Commitments, daily sessions, AI summaries, memory basis, and operating proposals. |
| Decisions and risks | Context, decisions, alternatives, consequences, severity, likelihood, mitigation, and status. |
The export is JSON, not a formatted report. It is best opened in approved analysis tools, secure data stores, or support tooling.
Scope
Exports are tied to the signed-in user and active organisation.
Some records are user-owned, such as a user's raw events, docs, doc revisions, snapshots, commitments, daily sessions, and proposals. Shared records such as memory, decisions, risks, and tickets are exported according to the user's readable organisation, group, user, and project scope.
Exports are not a replacement for infrastructure backup. They do not guarantee a complete tenant restore by themselves.
The export can contain confidential business information, private strategy, customer details, uploaded-file references, AI-generated summaries, and security-relevant metadata. Store exports only in approved systems and delete temporary copies after use.
Handling guidance
Before exporting:
- Confirm you are in the intended active organisation.
- Confirm your project scope and access are appropriate for the review.
- Use a trusted device.
- Avoid exporting during a screen share unless everyone is authorized to see the data.
After exporting:
- Move the file to an approved secure location.
- Apply your organisation's retention policy.
- Do not send raw exports over unmanaged email or chat.
- Redact sensitive fields before sharing with external support unless a data processing agreement covers the transfer.
Backups and legal holds
Use database and volume backups for disaster recovery. Use JSON export for user-accessible review and investigation.
For legal hold, compliance review, or incident response, coordinate with the server administrator so database records, upload volume contents, logs, and relevant configuration are preserved together.