Legal
Privacy
Last updated 2026-10-19 · Draft, pending legal review
/v1 API and the daemon mesh. The venom CLI and a self-hosted orchestrator send nothing to us.Request and response content
For security and audit, the cloud stores the content of every inference request that passes through it, for every organisation: the request body and the response bytes as they were sent.
- Sealed. Each body is encrypted with AES-256-GCM under a key for your organisation before it is written. Up to 1 MiB of each side is kept; anything longer is cut and the record is marked truncated.
- Kept 30 days by default. Owners and admins of your organisation can set the retention from 1 to 90 days under Settings, Data & logging. A body is deleted automatically when its retention ends. Shortening the retention applies to new bodies; stored ones are deleted at the expiry they were stored with.
- Every read is audited. Reading a body needs the content:read permission (owners, admins and developers by default). Each read writes a
content.viewedrow to your organisation's audit log, with who read it and when. - Only the operator can turn it off. Your organisation can see the setting and change the retention, but switching capture off for an organisation is done by us, the operator. A deployment without an encryption key stores no content at all.
- Direct requests. In direct mode your client sends the request straight to a daemon and the body does not pass through the cloud. When your organisation's content logging is enforced, the daemon sends the cloud a copy of the request and the response, which is sealed, kept and audited the same way.
Request metadata
For every request the cloud records who sent it (the API key's name and key group), when, the model asked for and the one served, where it went (your daemon, a public node or a provider), the status and any error code, tokens, cost and timings. This is what the Requests page, usage, budgets and billing are built from. It holds no prompt or response text. It is kept 90 days by default.
The public status page is computed from this metadata as totals across all organisations. It shows no organisation, key, model or content.
Your account and organisation
- Sign-in: your email address and the identifier from the sign-in provider you use (GitHub, or our sign-in provider Clerk).
- Your organisations, key groups, roles and invitations, and when you were last active in the console.
- API keys: stored as a hash. The full key is shown to you once, when it is created.
- Provider keys you add: sealed with AES-256-GCM under your organisation's key and opened only to serve a request. The console shows the last four characters.
- Daemons you connect: name, version, the models and hardware they report, their endpoints and heartbeats, and a location if you set one.
- An audit log of changes and reads in your organisation (keys, members, settings, content views).
- Billing, when your plan is paid: seats and usage. Payments go through Stripe; we do not see or store card numbers.
Who else processes data
- Hosting and database: Vercel runs the service and Neon hosts its Postgres database.
- Sign-in: GitHub or Clerk, depending on how you sign in. Clerk's script loads only on the Clerk sign-in pages.
- Payments: Stripe, for paid plans.
- Model providers: when a request is served by a provider (on Venom's keys or your organisation's own), that provider receives the request and processes it under its own terms.
- Daemons: your own daemons process the requests routed to them. If your organisation allows trusted or managed routing, a request can go to a public node run by someone else.
Cookies and tracking
The site loads no analytics, advertising or tracking scripts. The console sets only cookies it needs: the sign-in session (12 hours), short-lived sign-in and onboarding tickets, the operator's organisation filter, your time zone for the log explorer, and whether you hid the setup checklist. Your light or dark theme is kept in your browser's local storage.
Retention at a glance
| Request and response content | 30 days by default, 1 to 90 days as your organisation sets it |
|---|---|
| Request metadata | 90 days by default |
| Finished jobs (routing state, no content) | 7 days |
| Account, organisation, audit log | [retention after an account or organisation is closed] |
Your rights and choices
Owners and admins can change the content retention, revoke keys and remove members in the console. To ask for a copy of your data, a correction or deletion, write to joel@elishah.biz. [the rights that apply under the governing law, and how and how fast requests are answered].
Where data is stored
[hosting regions, international transfers and the safeguards that cover them].
Changes
When this page changes, the date at the top changes. [how account holders are told about material changes].