Terms
Terms of Service
Last updated: August 3, 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 solely to provide inference. We do not retain prompts, responses, or request bodies, and the service provides no setting that enables retention. We do not use customer requests or logs for training, fine-tuning, evaluations, analytics, or other secondary purposes unless you separately and explicitly agree, and we do not authorize our providers to do so either. If we later offer a feature that stores request content, it will store content only if you turn it on, on the terms described in the Privacy Notice.
Inference capacity and providers
Zro fulfils inference requests using GPU capacity we operate and, where our own capacity is unavailable or saturated, capacity from third-party infrastructure providers engaged by Zro. We remain your counterparty and remain responsible for the service regardless of which capacity serves a given request. We select providers that maintain independent security certifications and offer GDPR-aligned data-processing terms, and we may add, change, or remove providers as capacity and compliance requirements evolve.
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. The region setting binds all inference capacity equally, including third-party providers: Zro will not intentionally route inference to a region that the key does not allow, and if no allowed deployment for the requested model is available from any source, the request may fail instead.
Region scope
The API-key region setting applies only to model inference, whether served by Zro or by an infrastructure provider. 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.