Privacy policy
What AI Inference collects, why we hold it, who else processes it, and what you can ask us to do with it.
1. Who is responsible for what
For your own account — your email address, your name, your billing record — we are the controller, and this policy explains what we do with it.
For the content of the prompts you send, you decide what goes into them. We process that content to serve the request, to meter it, to cache it for you and to show you your own history, and for nothing else. We do not train on it, we do not sell it, and we do not mix one account's traffic with another's.
2. What we hold
Your account
- Email address and, if you give them, your name and company.
- Your settings: your default model, your requests-per-minute limit and how long a cached response stays valid for you.
- Whether the account is an administrator, whether it is suspended, and whether it has been granted free use, together with when the account was created and last updated.
Your requests
- For each call: which catalog model served it, which of your keys was used, the input and output token counts, the latency, whether it was a cache hit, the price, the status, and any error message.
- A hash of the prompt, used as the cache key, and a short preview — the first 200 characters — of both the prompt and the response, so that your request history is readable. That preview is part of the request record and outlives the cache entry.
- The full response text, in a cache held in memory, for as long as the cache window on your account allows and no longer. Set that window to zero and nothing is cached.
- Metered usage events and daily usage totals derived from the above.
Your keys and your session
- For each API key: its name, its first few characters, its last four, and a SHA-256 hash of the key itself. Not the key. The full value is shown once when it is created and is not recoverable afterwards, by us or by anyone.
- A signed session cookie, and a short-lived record for a password reset you have requested.
Payment
- The amount, currency, status and timing of your billing cycles, and the processor's reference for them.
- Not your card number. Card details go directly to our payment processor and never reach our servers or our database.
Security and administration
- An audit record of administrative actions — who did what, to which record, and when — including the IP address of the person who did it. This is the only place we keep an IP address, it is never readable from a browser, and it exists so that an action on your account can be accounted for.
We do not run advertising or third-party analytics trackers on this site, and we do not sell personal data or share it with data brokers.
3. Why we hold it
- To provide the service you asked for — performance of our contract with you.
- To meter and bill usage, and to keep the accounting and tax records we are required to keep — contract and legal obligation.
- To keep accounts secure and to investigate misuse, including the audit record and the per-account rate limit — legitimate interests.
- To answer you when you contact us.
4. Cookies
We set the cookies needed to keep you signed in and to protect the sign-in flow. They are strictly necessary for the service to function; there are no advertising, profiling or cross-site tracking cookies. Clearing them signs you out.
5. Who else processes it
We use a small number of sub-processors, each for one job:
- a hosting and application platform, which runs the service;
- a managed database and authentication provider, which stores your records and your credentials;
- a payment processor, which takes the payment and holds the card details we never see;
- one or more upstream model providers, which receive the text of the prompt you send and return the response. Which one receives a given request depends on the model that serves it, and each operates under its own data policy, surfaced in the model detail view.
Each is bound by a data-processing agreement, may process personal data only on our instruction, and may not use it for its own purposes. For the current named list, write to omnichannel200@gmail.com and we will send it to you. We publish the functions rather than the names because the names change and a list in a page goes stale; the list you are sent is the current one.
We will also disclose data where we are legally required to, and in a merger or acquisition, in which case we will tell you before your data moves and this policy continues to apply to it.
6. Where it is processed
Our sub-processors may process data outside your country, including in the United States. Where personal data moves out of the European Economic Area or the United Kingdom, that transfer is made under the European Commission's standard contractual clauses, with the UK addendum where the UK GDPR applies.
7. How long we keep it
- Cached responses: for the cache window set on your account, after which the entry is no longer served. The cache is held in memory and is also bounded in size, so an entry can be evicted sooner.
- Account, request and usage records: while your account exists. Deletion is handled on request rather than from the console today: ask us and we delete the account and these records, except where we must keep something longer.
- Billing and accounting records: for as long as tax and accounting law requires, which is typically seven years.
- Audit records: retained for security and accountability, and kept separately from your request history.
8. Your rights
Depending on where you live, you can ask us to give you a copy of your personal data, correct it, delete it, restrict or object to how we use it, or send it to someone else in a portable form. You can also complain to your data protection authority.
Write to omnichannel200@gmail.com. We answer within one month and ask for nothing beyond what we need to confirm it is really you.
If you put someone else's personal data into a prompt, you are the one who decided to do that, and a request from that person about it has to be answered by you. Tell us and we will support you in answering it.
9. Security
Records are scoped to the owning account, and the prompt cache is keyed per account, so one account cannot be served another account's response. API keys are stored only as a hash. Credentials are handled by our authentication provider and we never see your password. Access to production data is limited to the people who need it, and administrative actions are recorded.
We claim no security certification or audit attestation. If you need our security documentation for a diligence process, ask and we will send what we have.
10. Children
The service is for businesses. It is not directed at children, and we do not knowingly collect personal data from anyone under 16. If you believe we have, tell us and we will delete it.
11. Changes and contact
If we change this policy materially we will give notice before the change takes effect. The date at the top of this page is the current revision.
Privacy questions, or a request about your data: omnichannel200@gmail.com. See also our terms of service.