Privacy
Privacy Notice
Last updated: August 3, 2026
This notice explains how Zro handles data for its regional open-source model inference service.
Who operates Zro
MoonMath operates Zro and is responsible for the processing described in this notice. For privacy questions or requests, email zro@moonmath.ai.
Data Processing Agreement
Our Data Processing Agreement describes the processor obligations, security measures, sub-processors, international transfer mechanisms, and data-subject rights assistance that apply when MoonMath processes personal data on your behalf as part of the service. It is mainly relevant for Teams and Enterprise customers who need formal processor terms, and it applies only when a copy has been executed with you.
Data we process
We process prompts, completions, web-search queries, account identifiers, email addresses, IP addresses, API-key metadata, selected inference regions, token and cost totals, billing records, security and reliability logs, referral or attribution sources, and website or product events.
Purposes and legal bases
We use this data to provide inference and tools, authenticate and secure the service, administer accounts, calculate usage, collect payment, prevent abuse, diagnose failures, and comply with legal obligations. We process service, account, and billing data as necessary to perform our contract with you; limited security, fraud-prevention, reliability, and operational data for our legitimate interests in operating and protecting Zro; and records we are required to keep to satisfy accounting, tax, or other legal obligations.
Where inference runs
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: a provider receives only the request content needed to generate a completion and returns it to our gateway, 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 selection applies to model inference only; it does not determine where account, billing, authentication, analytics, web-search, or other service-provider processing occurs.
International transfers
Beyond the inference regions you select, some service providers may process personal data outside your country. Where data-protection law requires a transfer mechanism, we rely on an applicable adequacy decision, contractual safeguards such as Standard Contractual Clauses, or another lawful mechanism.
Prompt and request retention
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: content exists only for as long as it takes to process the request and return your response. Content logging is disabled at the gateway itself. Infrastructure providers process request content transiently to execute the request; any operational logging on their own systems is governed by their terms. If we later offer a feature that stores request content, such as history, debugging, or exports, it will store content only if you turn it on, and we will update this notice before it becomes available.
Training use
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.
Service providers
We use Clerk for authentication, Dodo Payments for billing, PostHog EU and Google Analytics for analytics, Linkup for optional web search and URL fetch, and hosting, networking, and GPU infrastructure providers for the gateway, database, and model inference. They receive only the data needed for their role and process it under their own locations, contractual terms, and legal obligations. We select inference infrastructure providers that maintain independent, externally audited security certifications, such as SOC 2 Type II and ISO/IEC 27001, and that make GDPR-aligned data-processing terms available; a certification held by a provider describes that provider's own control environment and is not a certification of Zro.
Web search and URL fetch
When an agent invokes Zro web search, Zro sends the search query and the parameters needed to perform that search to the Linkup API. When an agent invokes URL fetch, Zro sends the requested URL to Linkup; Linkup retrieves the page and returns its content. We do not send the full conversation to Linkup. Linkup may process the query, URL, and related request metadata to provide these tools.
Account and billing data retention
We retain account identifiers, API-key metadata, billing status, token totals, and usage-event records while your account is active and afterward only as needed for security, dispute resolution, accounting, tax, or other legal requirements. Analytics events are retained according to our configured provider retention periods. We delete or anonymize data when it is no longer needed for these purposes.
Your choices and rights
Depending on applicable law, you may request access, correction, deletion, restriction, or portability of personal data, or object to certain processing. Where we rely on your consent, you may withdraw it at any time without affecting processing already carried out. You can block or delete analytics cookies through your browser settings, and Google offers a Google Analytics opt-out browser add-on. You may also complain to your local data-protection authority. To exercise a privacy right, email zro@moonmath.ai.
Changes to this notice
We update this notice when our processing changes, including when we add or change the categories of providers that serve inference or the features that handle your content. The date at the top of this page reflects the most recent change. Where a change materially affects how we handle your content, we will make that clear before it takes effect.