Data retention
Generated files are kept indefinitely, log rows for a year, the financial record forever. Here are the exact rules, so you know what you need to take with you.
Generated files: indefinitely
Providers hand back images on links that expire fast — typically within a day, download links sooner still. So we never return an upstream link to you: the result is immediately re-hosted into our own storage and you get a permanent URL like https://api.altrouter.ai/media/….
These links do not expire and are not deleted on a schedule. You can store them in your database, show them to users and serve them directly. They are public: anyone with the URL sees the file — so do not put into prompts anything that must not leak via a guessed link.
Log rows: 12 months
Each row in Logs — request parameters, model, provider, tokens, cost — is kept for a year and then deleted. A year covers any accounting reconciliation, and neither of us needs the raw per-request log kept forever.
Note that deleting a log row does not delete the file. The CDN link keeps working — what disappears is the record of which request produced the file. If the prompt-to-result link matters to you, store it on your side.
The financial record: forever
Balance movements — top-ups, holds, captures, releases — form an append-only ledger that is never pruned. It is the ledger, not the request log, that answers “where did the money go” for any period.
What to take with you
- Prompts and parameters, if you need them beyond a year.
- The mapping from our file URL to your own entity — we do not know it.
- The files themselves, if your policy requires them inside your own perimeter.
Deletion on request
Specific files, or an account’s entire history, can be deleted ahead of schedule — on request from the account owner, handled manually. There is no self-serve button for this yet. The financial ledger is retained either way: it is needed for accounting and holds no request content.
NextReliability →