Trust centre · Retention
Retention & deletion
What AxForge keeps, for how long, and what is never stored at all. This schedule is a policy decision we publish for review before commercial launch, and we present it as exactly that: a launch draft.
Schedule
Retention schedule — launch draft v0.1
| Data | Retention |
|---|---|
| Prompt/completion bodies | Memory-only; discarded when the request completes. |
| Temporary request buffers | Seconds — cleared at request completion, never written to disk. |
| Request identifiers & API metadata | 90 days operational, then deleted or aggregated. |
| Usage measurements (billing aggregates) | 24 months. |
| Security/access logs | 12 months. |
| Account profile | Account lifetime + 90 days after closure. |
| Support records | 24 months. |
| Invoices/accounting evidence | Swedish statutory accounting period (Bokföringslagen). |
| Backups (metadata stores only) | 35-day rotation; prompt/completion bodies are never present in backups. |
- The Swedish statutory accounting period (Bokföringslagen) applies only to qualifying accounting records — invoices and accounting evidence — not to general account metadata, which follows the shorter rows above.
- Records kept for legal-hold or accounting reasons remain erasable where the law requires erasure to prevail: legally required erasure takes precedence over any retention or immutability rule on this page.
Account closure
Deletion when you leave
When an account is closed, the account profile is deleted 90 days after closure. Every other record follows the schedule above and expires on its own row's clock. Prompt and completion bodies were never stored in the first place — there is nothing to delete and nothing left behind in backups. How prompts are handled in flight is on the data residency page; the full policy is in the privacy policy.
Related
Nearby in the trust centre
Version 0.1 (launch draft) · Effective 2026-08-26
- 2026-08-26 — first published version of this page.