Terms
Terms of Service
Last updated: July 20, 2026
These terms govern access to and use of Zro.
Service
Zro provides API access to open-source model inference, account management, metered billing, and related operational tooling.
Acceptable use
You are responsible for the prompts, outputs, applications, and users connected to your account. Do not use the service for unlawful activity, abuse, credential sharing, attempts to disrupt infrastructure, or violations of applicable model, export, privacy, or safety requirements.
Data handling
We process request content to provide inference. Prompt and response retention is off by default, but a feature you expressly enable may store content and metadata according to its stated settings. We do not use customer requests, histories, or logs for training, fine-tuning, evaluations, analytics, or other secondary purposes unless you separately and explicitly agree.
Regional processing
Every inference request passes through Zro's EU gateway for authentication and routing. Each API key specifies whether model inference may run in Europe, the United States, or either region. By selecting United States and creating or using that key, you instruct Zro to transfer inference request content to US infrastructure for processing. Zro will not intentionally route inference to a region that the key does not allow; if no allowed deployment for the requested model is available, the request may fail instead.
Region scope
The API-key region setting applies only to model inference. Account management, authentication, billing, operational analytics, optional web search, networking, and other service-provider processing may occur separately as described in the Privacy Notice. You are responsible for determining whether your selections and use of Zro satisfy your legal, regulatory, contractual, residency, and compliance obligations.
Billing
Usage-based billing is calculated from token usage and related billing metadata. You agree to pay fees associated with usage under your account and to keep payment information current.
Availability
The service may change as models, infrastructure, dependencies, or compliance requirements evolve. We may suspend access to protect the platform, users, or third parties.