Legal
Terms
Last updated 2026-10-19 · Draft, pending legal review
The service
Venom Cloud is one OpenAI-compatible endpoint that routes your requests to your own daemons, to public nodes your organisation allows, or to model providers on Venom's keys or your own, with keys, budgets, roles and request logs for your team.
Accounts and keys
- You sign in with GitHub or our sign-in provider. The person who creates an organisation is its owner and decides who else joins and with what role.
- API keys, join tokens and provider keys are credentials. Keep them secret; you are responsible for requests made with your organisation's keys. Revoke a key you think has leaked.
- You must be able to enter a contract to use the service. [minimum age and who may accept for an organisation].
Acceptable use
You agree not to:
- break the law, or the terms of a model provider your requests are sent to;
- try to reach another organisation's data, daemons or keys, or get around rate limits, budgets or plan limits;
- send a public node requests meant to harm it or its host, or, as a host, alter, record or misreport the requests your daemon serves;
- overload the service, or probe it for vulnerabilities without our written permission.
We may suspend a key, a daemon or an organisation that does, and will say why when we can.
Your content and its logging
You keep your rights in what you send and receive. For security and audit, the cloud stores request and response content, sealed, for a retention your organisation sets; every read is audited. The privacy page says exactly what is stored, for how long and who can read it.
Providers and public nodes
A request served by a model provider is also subject to that provider's terms. A request routed to a public node is served by a daemon someone else runs; your organisation chooses whether that can happen (its routing modes and trusted nodes).
Plans and payment
The plans, their limits and what counts as usage are on the pricing page. Paid plans are billed through Stripe per seat plus metered usage of Venom's keys and public nodes. [billing terms: billing cycle, taxes, refunds, late payment, price changes].
Availability
We publish availability and latency measured from the service's own logs on the status page. Those figures are information, not a promise. [service level commitment, if any, and its remedies].
Ending
You can stop using the service at any time. [how an organisation is closed, notice periods, what happens to its data].
Warranty and liability
[warranty disclaimer and limitation of liability].
Governing law
[governing law and courts].
Changes and contact
When these terms change, the date at the top changes. [how account holders are told about material changes]. Questions: joel@elishah.biz.