法律
How BoostRail Handles Your Data
Last updated 2026-11-05. Controller: Boostly Limited, New Zealand.
本页以英文版本为准(the English version prevails)。
This page describes current practice in more detail than the Privacy Policy, which remains the governing document.
In short
- BoostRail does not store the content of text requests or responses. We keep the metadata needed for billing, usage reports and troubleshooting.
- Image and video jobs hold the prompt and reference image links only while the job is running. They are removed the moment the job ends.
- BoostRail does not store generated images or videos. Files are relayed from the provider, so they should be saved promptly.
- We do not sell request content or personal data, and we do not use request content to train models.
What we store
| Data | Stored by BoostRail | How long |
|---|---|---|
| Text prompts and responses | No. Passed to the model provider to serve the request | — |
| Image and video job prompts and reference image links | Only while the job is running, so it can be retried if a provider fails | Removed when the job succeeds, fails, is cancelled or expires |
| Generated images and videos | No. BoostRail keeps only the provider's download link and relays the file. Some image models return the image directly in the response, and it cannot be fetched again later | As long as the provider keeps the file. This varies by model and may be 24 hours or less |
| Request metadata: request ID, time, model, the provider that served it, token or unit counts, charge, status, error code, latency, API key and project | Yes | No set deletion date; kept for billing, usage reports and dispute resolution |
| Error text returned by a provider | Yes, for troubleshooting | Failed text requests: 90 days, then deleted automatically. Image and video jobs: kept with the job record |
| Server logs: IP address, time, path, status (no request content) | Yes, for security and troubleshooting | — |
| BoostRail API keys | A one-way hash and a short identifying prefix. The full key is shown once, at creation | Kept after deletion so past usage stays linked; a deleted key stops working immediately |
| Provider keys added under BYOK | Encrypted (AES-256-GCM); only the last four characters are ever shown | Deleted immediately when removed |
| Account, billing and support records | Yes, as described in the Privacy Policy | See the Privacy Policy |
Where requests go
Each request is forwarded to a provider that serves the requested model: the model developer's own API or a third-party inference provider. If that provider fails, the request may be sent to another provider of the same model. Providers handle requests under their own terms, may process them outside Singapore, and some keep request content or generated files for a period. With BYOK, requests are sent under the customer's own provider account, and that provider's terms apply.
Where data is stored
Our servers are in Singapore. Visitors from mainland China may connect through a relay in Hong Kong, which forwards encrypted traffic without decrypting it.
Daily database backups are kept on our server for 14 days. An encrypted copy is stored with a separate storage provider, which may hold it outside Singapore: daily copies for 30 days, and one copy per month with no set end date. Deletions apply to the live database; existing backups are not edited.
Who can access it
Production data is accessed by BoostRail staff who run the platform, for operations, billing and support. Sign-in to the BoostRail admin console requires two-step verification.
Controls available to customers
- Restrict which models each API key can call, and set daily or monthly spending limits per key.
- Export usage records as CSV from the console.
- Remove BYOK provider keys at any time.
- Request account deletion by writing to support@boostrail.com.
Advertising
We do not load the advertising tag for visitors from the EU/EEA, the UK or Switzerland.
Changes
When our practice changes, we update this page and the date at the top.