1.Who we are
Foundry runs usdf.fi and the API at api.usdf.fi and decides how the data below is used. Write to protocol@usdf.fi.
2.What we collect
When you sign in: your email address, X account or wallet address and the user id our sign-in provider gives you, and the wallets you link. For each request: the account and key it was made with, the model and the provider that served it, token or unit counts, cost, latency, status and time, and how it was routed. For payments, deposits and withdrawals: wallet addresses, amounts and transaction hashes. API keys are stored only as hashes. If you write to us, we keep the message. When you accept the Terms at sign-in, or the deposit terms before your first deposit, we record your account, your wallet, the boxes you ticked, the version you accepted, the time and the country your connection came from, never your IP address. That country is read from your IP address at the edge, to decide whether the service is available where you are, and is kept only as a two-letter country code, never the IP address. IP Geolocation by DB-IP (https://db-ip.com), CC BY 4.0.
3.Your prompts and responses
By default we keep no prompt, response or tool-call text: every API key starts in no-logs mode and stays in it unless you turn request logs on. If you turn them on, for your account or for one key, each chat and completions request of those keys is kept for 30 days so you can read, export or delete it: the prompt as it was sent to the model and the response (each up to 64 KB), with its model, provider, tokens, cost, latency and status. Private-tier keys, keys in no-logs mode, app keys, agent, organisation and platform keys, and any request run on attested hardware or asking for zero retention are never logged. For a key with request logs on, an internal report about a failed request can include part of it. Presets you save, a system prompt included, are kept until you delete them. A batch job's result stays with the model provider that ran it, not with us, for up to 7 days after the job ends; a generated video is held in memory until you fetch it, at most 30 minutes. The table under "How long we keep it" lists each record.
4.Public by design
A request's receipt (token counts, cost, price-sheet version and status, never its content) can be read by anyone who has its request id. Each request is also an entry in a usage log: its request id, model, provider, token counts, cost, status and time, and for a request paid per request its payment transaction; never its content, account or key. Anyone with a request id can read its entry and the proof that it is in the log. Settlement transactions record the log's root onchain, so an entry cannot be changed or removed later. Deposits, withdrawals and payments are transactions on a public blockchain.
5.How we use it
To run the service and bill requests, to show you your activity and statements, to secure the service and prevent abuse, to publish the reserve, status and usage proofs, and to meet legal obligations. We do not sell personal data, do not use it for advertising, and do not train models on your requests.
6.Who receives it
Model providers receive the content of your requests in order to answer them, under their own terms. Every model below its source price, and the cheapest provider wins every request. The source price is the maker's own price, the market's typical price, or the model's list price. That provider processes it under its own data policy, and you must follow the model provider's terms and acceptable-use rules. Models with a zero-retention route use it by default. A model marked 'provider may keep data' is served by a provider that may keep request data; choosing it is your choice. A private request (a :private model id, provider.private, or any request from a Private-tier key) runs only on attested hardware this gateway has verified, encrypted in transit and inside that hardware, and only for the models that have it (GET /v1/models marks them private); a private request for any other model is refused and nothing is charged. Our sign-in provider receives your email, X account or wallet address and IP address when you sign in, and its sign-in window may run a bot check. Our card payment partner receives what you give it in its window (see Card purchases). Our hosting and database providers process data on our behalf. A wallet connection service is used when you connect a wallet through it. Fonts are loaded from a font service, which receives your IP address. We share data with authorities only where the law requires.
7.Card purchases
If you buy by card, you pay in our card payment partner's window on this site. Your card details, and any identity check the partner asks for, go to the partner, not to us. The identity check may ask to use your camera; the site lets only that check use it, and only once you allow it in your browser. The partner tells us each purchase's status and amounts and the transaction that delivered it, matched to your account by an id we give it. We never see your card number or your identity documents. The partner's own privacy policy, shown in its window, covers what you give it.
9.How long we keep it
Account details are kept while your account is open. When you ask us to delete your account, we delete what we are not required to keep; entries in the usage log and onchain records cannot be deleted.
| Record | What it holds | Kept |
|---|---|---|
| Account | Email address, X account, wallets and the user id our sign-in provider gives you | While your account is open |
| Usage record | Each request's model, provider, token counts, cost, status and time; never its content | For billing and statements; its entry in the usage log is permanent |
| Request detail | How a request was routed and timed; never its content | 90 days |
| Request log | The prompt and the response, only for keys whose request logs you turned on | 30 days, or until you delete it |
| Preset | A saved request setup, a system prompt included | Until you delete it |
| Batch result | Held by the model provider that ran the job, not by us | Up to 7 days after the job ends |
| Generated video | Held in memory, never on disk | Until fetched, at most 30 minutes after it is ready |
| Payments | Deposits, withdrawals, payments and card purchases: amounts, wallets and transactions | As billing records; onchain transactions are permanent |
| Messages to us | What you wrote and our answer | As long as needed to answer and keep a record |
| Consent record | Each acceptance of the Terms or the deposit terms: account, wallet, the boxes accepted, the version, the time and the country, never the IP address | Kept as the record that you accepted, never changed |
10.Your choices and rights
You can revoke keys, turn request logs on or off and delete them, ask for a private request on any model that has an attested route (the private field of GET /v1/models) and withdraw your balance at any time from the dashboard. Depending on where you live, you can ask to see, correct, export or delete your personal data, or object to how it is used, and complain to your data-protection authority. To make a request, contact us as below.
11.Security
Traffic is encrypted, keys are stored as hashes, the site sends a strict Content-Security-Policy with every page, and access to production systems is limited. No system is perfectly secure; tell us at once if you believe your account or a key has been compromised.
12.Changes
We change this policy by updating this page with a new effective date.
13.Contact
Write to protocol@usdf.fi.