Effective date: October 19, 2026
Verb Compute is an AI inference service operated by Verb Compute (“we”, “us”). We run open-weight language models on our own hardware and serve responses to requests routed to us through API platforms and marketplaces such as OpenRouter, and through our own API endpoint. This policy explains what data Verb Compute processes, what we keep, and for how long. It applies to the inference service only.
1. What we receive
When a request is routed to our endpoint, we receive the prompt, request parameters, and an API credential that identifies the platform or customer sending the request. We do not receive the identity of the end user behind a platform request.
2. What we store
We do not store prompt content or generated responses.
For each request we retain metadata only: timestamp, model name, token counts (input, cached input, output), response status, latency, and error type if the request failed. We use this metadata for billing reconciliation, service monitoring, and capacity planning.
During processing, prompt and response data exist temporarily in server memory, including a short-lived cache used to speed up repeated prompt prefixes. This cache is held in volatile memory only, is not written to disk, and is cleared automatically.
3. Training and secondary use
We do not use prompts, responses, or any request data to train, fine-tune, or evaluate models. We do not sell or share request data with third parties, except as required to operate the service (see section 5) or as required by law.
4. Retention
Request metadata is retained for 12 months from the date of the request to support invoicing, dispute resolution, and service audits, and is then deleted. Aggregated statistics that do not identify individual requests may be kept longer.
5. Where data is processed
Inference runs on servers located in the United States, operated for us by a hosting provider under contract. Metadata is stored on infrastructure we control. Our hosting provider does not access request content in the ordinary course of operation.
6. Security
Our endpoint is served over HTTPS only. Access to servers is restricted to authorized personnel using key-based authentication. Metadata is encrypted in transit and accessible only from our own systems.
7. Changes
We may update this policy as the service changes. The effective date at the top of this page reflects the latest revision.
8. Contact
For questions about this policy or data handling: privacy@verb.com