Security and data
What the platform keeps, what it does not, and what backs each guarantee. Every claim on this page links to the page that states it.
- Two serving tiers, stated
- Keys stored as a hash
- No certification claimed
01 / Zero retention
What zero retention means
Two kinds of supply serve requests, and the platform states which is which instead of averaging them into one claim. A key or a request can require the zero-retention tier; the rented tier is labelled transient.
Partner routes, under agreement
Partner routes are admitted only under a written zero-retention agreement, and a request that requires zero retention never falls back to a route without one: the key switch "zero-retention routes only", or the :zdr suffix on a model id, makes the router fail closed with 503 zdr_unavailable instead.
The rented tier is transient
Rented GPU machines serve the same models from capacity the platform rents. The platform stores nothing there either, but the machine operator holds root and can see a request while it is processed, so the tier is disclosed as transient and no zero-retention request reaches it.
What is not stored
The gateway keeps no copy of a request or an answer. A request leaves a usage line with its id, the account, the key, the model, the token counts, the latency, the cost, the status and the time. The body is not in it.
The three places text can rest
Text rests only where a key asked for it: the memory vault until you delete a note, the response cache for ten minutes, and the idempotency replay for 24 hours so a retry is answered once.
The provider side is a contract
On the partner tier, a provider’s commitment not to keep a prompt or an answer is a written agreement, not a request option. The agreements are held per provider and available on request before a regulated workload.
02 / Encryption
What is encrypted, and what is not
This section names the surfaces and the limits, including the two things that are not encrypted at rest today.
In transit
The site and the API answer over encrypted connections only. Plain http is redirected, and a strict transport security policy covers the site for two years.
At rest
Backups are encrypted at rest. The secrets the gateway must keep are sealed with authenticated encryption under a server key, so the database never holds them in the clear.
Passwords and sign-in
A password is kept only as an argon2id hash, never in clear. A second factor can be an authenticator app or a passkey.
What is not encrypted
The memory vault note text rests in the service database without encryption at rest, and the host disk is not encrypted. The protection there is access control on the host and the database, and the retention page says so in the same words.
03 / Keys
How a key is held
A key is shown once
The gateway stores a hash of an API key and a short prefix used to name it in support, never the key itself. A key that is lost cannot be recovered, only revoked and replaced.
Revoked means refused
Revoking a key in the dashboard refuses it on its next request. An account’s key export carries names, models, limits and routing policy, and never a secret or a hash.
04 / Agent machines
Erasure for agent machines
A managed agent runs on a machine the platform operates. Disposing it destroys the key to its disk, and the erasure is proved rather than asserted.
The disk key is destroyed
The machine runs on a disk encrypted with a key kept outside the guest. Disposing the machine destroys that key, so every copy of the ciphertext becomes unreadable, including a copy taken before the disposal.
The limits of that claim
A host compromised while the key is present still has it, and a backup that included both the machine’s files and the hypervisor’s key store would undo an erasure. No such backup exists, and a machine created before the feature keeps a plaintext disk until it is rebuilt.
05 / Test money
Test money stays test money
A sandbox credit is marked, not mistaken
Sandbox deposits exercise the payment path without a chain transfer. The switch ships off and is owner-only, a sandbox credit is marked on the payment, on the receiving address and in the transaction id, and the reconciliation that checks the payments excludes it.
06 / Reporting
Report a vulnerability
Write to support@rackduck.com and mark the subject as a security report. The same address handles support, data protection and legal notices, so there is no separate security mailbox.
Say what you did, what you expected and what happened. A request id or a dashboard record makes a report easier to follow up, and testing against another account’s data is out of bounds.
No response time is published for a security report, and the terms provide the service without guaranteed service levels. Two times are committed in writing: a request about your data is answered within one month, and a complaint within 30 days.