Trust Centre · Retention
Retention & deletion
What AxForge keeps, for how long, and what is never stored at all. This schedule is the published policy for every class of data the service handles.
Schedule
Retention schedule
| Data | Retention |
|---|---|
| Prompt/completion bodies | Memory-only; discarded when the request completes. |
| Temporary request buffers | Seconds. Cleared at request completion, never written to disk. |
| Dedicated GPU rental: machine contents | For the rental period. When the rental ends, the machine and all data on it are deleted. |
| Request identifiers & API metadata | 90 days operational, then deleted or aggregated. |
| Usage measurements (billing aggregates), bookings & balance ledger | 24 months. |
| Security/access logs | 12 months. |
| Website visit records (first-party analytics) | 12 months, then deleted or aggregated. See cookies for what is recorded. |
| Site Guide (website chat) conversations | 24 months, as support records. |
| Account profile | Account lifetime + 90 days after closure. |
| Support records | 24 months. |
| Payment records held by Stripe | Held by Stripe Payments Europe, Limited under its own retention terms; AxForge keeps booking and ledger references with the billing aggregates above. |
| Invoices/accounting evidence | The statutory accounting period. |
| Backups (metadata stores only) | 35-day rotation; prompt/completion bodies and rented-machine contents are never present in backups. |
- The statutory accounting period 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, any active rental is ended and its machine deleted, and 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, so 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 1.0 · Effective 2026-09-04 · Last reviewed 2026-09-04
- 2026-09-04, version 1.0: rows added for dedicated GPU rental contents, bookings and balance ledger, website visit records, Site Guide conversations and Stripe payment records.
- 2026-08-26: first published version of this page.