Effective August 1, 2026
This Privacy Policy explains how Viro Climate Action, Inc. ("Viro," "we," "us," or "our") collects, uses, discloses, and protects personal information when you use:
collectively, the "Service."
This Privacy Policy applies to developers, account administrators, representatives of customers, and other people who interact directly with Viro.
It also explains how Viro processes information submitted through the API on behalf of customers. However, if you are an end user of an application built by a Viro customer, that customer's privacy policy governs its collection and use of your information. You should generally direct privacy requests concerning that application to the customer operating it.
Our legal role depends on the type of information involved.
Viro generally determines how and why account information, billing records, security logs, support communications, and Service usage metadata are processed. For this information, Viro acts as a controller, business, or similar responsible entity under applicable privacy law.
Customers determine what information they submit through the API and why they process it. When Customer Content contains personal information, Viro generally processes that information on the customer's behalf to provide the requested Service.
For this information, the customer generally acts as the controller or business, and Viro generally acts as its processor or service provider.
This Privacy Policy does not replace any data processing agreement between Viro and a customer.
Viro does not persistently store the content of API prompts, messages, uploaded files, tool inputs, or model responses in the Viro application database.
Our per-request usage records contain operational information such as:
These usage records are designed not to contain prompt, file, or response content.
Request content is processed in memory for the time reasonably necessary to:
Viro does not use Customer Content or model responses to train foundation models. We also do not use that content for advertising or marketing profiles.
This Viro-level commitment does not automatically mean that every underlying model Provider offers zero-data-retention processing. Provider retention, abuse monitoring, and data-use practices can differ by Provider, model, endpoint, region, and commercial agreement.
Customers that require zero-retention or other specific processing terms should review the applicable model documentation or contact Viro before selecting a model or router.
When you create or administer an account, we may collect:
If you sign in through Google, we receive the authentication and profile information authorized through the sign-in process, such as your email address and Google account identifier. We do not receive your Google password.
Payments are processed by Stripe.
Viro does not receive or store your complete payment-card number or card security code. We may receive limited transaction information from Stripe, such as:
We use this information to add purchased Credits to your account, maintain billing records, investigate payment issues, prevent fraud, and satisfy accounting and legal obligations.
Stripe processes payment information under its own terms and privacy policy.
For each request, we may collect operational metadata including:
Usage metadata does not intentionally contain prompt or response content.
Viro does not store complete API keys in plaintext after they are created.
A full API key is displayed to you when it is generated. Viro retains:
Because Viro does not retain the complete key in recoverable form, a lost API key must be replaced rather than recovered.
"Customer Content" includes prompts, messages, instructions, files, images, URLs, function arguments, tool inputs, and other content submitted through the API.
Customer Content may contain personal information selected and controlled by the customer.
Viro processes Customer Content transiently to provide the Service. We do not persistently store it in our application database or include it in ordinary usage records.
Customer Content is transmitted to the model Provider or other service provider required to perform the customer's request.
When you access the Service, Viro and its infrastructure providers may automatically process:
Viro's systems are designed not to place prompt or response content into ordinary infrastructure logs. However, technical logs may contain limited fragments of request information if necessary to diagnose an unexpected error or if information is voluntarily submitted as part of a support request.
Infrastructure providers may retain technical logs according to their own contractual and operational retention schedules.
If you contact us, we may collect:
Do not send prompt or response content to support unless it is necessary to resolve your issue and you are authorized to disclose it.
Content voluntarily included in a support request is not covered by the ordinary API zero-content-retention design. We retain and process it as part of the support communication.
The developer console may use cookies, local storage, and similar technologies necessary to:
Where applicable law requires consent for a non-essential cookie or similar technology, we will request consent before using it.
We use personal information to:
We may aggregate or de-identify operational information so that it cannot reasonably be associated with a person or customer. We may use and disclose properly aggregated or de-identified information for analytics, capacity planning, environmental reporting, reliability improvements, and other legitimate business purposes.
We will not attempt to reidentify information that we maintain as de-identified, except to test whether our de-identification measures are effective or as otherwise permitted by law.
Where European, United Kingdom, or similar privacy laws apply, Viro relies on one or more of the following legal bases:
We process information where necessary to:
We may process information where necessary for legitimate interests such as:
We consider the nature of the information and the potential impact on individuals when relying on legitimate interests.
We process information when necessary to comply with applicable tax, accounting, sanctions, regulatory, law-enforcement, and other legal obligations.
We may rely on consent where required, such as for certain optional cookies or communications. You may withdraw consent at any time, although withdrawal does not affect processing that occurred before it was withdrawn.
We do not sell personal information.
We do not share personal information for cross-context behavioral advertising or use Customer Content to create advertising profiles.
We disclose information only as described below.
We transmit Customer Content and required request information to the model Provider selected by you or selected by a Viro router.
Current Providers may include:
Providers receive the request information needed to generate and return the requested result. Depending on the Provider, this may include:
The Provider returns model Output and usage information to Viro.
Provider availability may change. Viro may add, replace, or remove Providers as the Service evolves. Current model and Provider information is available through our documentation and developer console.
A Provider's processing may be governed by both its agreement with Viro and its own published privacy and service terms. Viro selects and configures Providers but cannot promise a particular Provider retention practice unless that practice is expressly identified for the applicable model or service configuration.
When you explicitly enable a tool such as viro:web_search, Viro sends the search query and related parameters to the applicable search provider.
Brave Search may receive search queries when the Brave-backed search feature is used.
When you use a web-retrieval tool, the operator of the destination website may receive standard network information associated with the retrieval request, such as the requested URL, request time, and the IP address of Viro's retrieval infrastructure.
Search and retrieval information is shared only when the relevant tool is enabled or invoked.
Stripe receives and processes payment, billing, and transaction information needed to complete Credit purchases and handle refunds, disputes, and fraud prevention.
We use service providers to operate the Service, including:
These providers may process account, transaction, usage, authentication, and technical information only as necessary to provide their services to Viro.
We may disclose information to lawyers, accountants, auditors, insurers, consultants, and other professional advisers where reasonably necessary for their services and subject to appropriate confidentiality obligations.
We may preserve or disclose information when we reasonably believe doing so is necessary to:
Where legally permitted and reasonably practical, we will seek to notify an affected customer before disclosing its information in response to legal process.
If Viro is involved in a merger, acquisition, financing, reorganization, bankruptcy, sale of assets, or similar transaction, information may be reviewed, transferred, or disclosed as part of that transaction.
Any recipient will be required to handle personal information consistently with applicable law and the commitments in this Privacy Policy unless you are notified of a change.
Viro's own zero-content-retention design does not necessarily apply to every model Provider.
A Provider may process or temporarily retain request content for purposes such as:
Whether a Provider uses request content for model improvement or training depends on Viro's agreement with that Provider, the endpoint used, the account configuration, and the Provider's applicable policies.
Viro seeks to use commercial API services and configurations that do not use customer API content to train public foundation models. However, customers should not assume that every model offers identical retention or data-use terms.
Where a specific model or route is represented as offering zero-data-retention processing, that representation applies only to the documented configuration and may be subject to limited exceptions required for security or legal compliance.
Contact nick@viro.app if you need current information about the processing configuration for a specific model or Provider.
Customers are responsible for determining whether they may lawfully submit personal information through the Service.
Customers must:
Unless Viro has expressly agreed otherwise in writing, customers should not submit information that requires specialized legal or contractual safeguards, such as:
If an End User contacts Viro about information controlled by a customer, we may direct the person to that customer. Where appropriate, we will assist the customer with a verified request as required by applicable law or a data processing agreement.
We retain different categories of information for different periods.
Viro does not persistently store API prompt, file, tool-input, or response content in its application database.
Customer Content is retained in active memory only for the time reasonably necessary to process and return the request, subject to transient buffering, network transmission, security controls, and Provider processing.
Content voluntarily submitted through support channels is retained as a support communication rather than as ordinary API content.
Account information is generally retained while your account remains active and for a reasonable period afterward to:
Billing, payment, Credit-ledger, invoice, tax, and transaction records may be retained for the period required by tax, accounting, financial, and other applicable laws.
Closing an account does not require Viro to delete records that we are legally required to maintain.
Usage metadata is retained as reasonably necessary to:
Usage metadata does not intentionally contain Customer Content.
Technical and security logs are generally retained for shorter operational periods determined by security, debugging, abuse-prevention, and infrastructure requirements.
Some logs may be retained longer when associated with an active security investigation, legal obligation, billing dispute, or enforcement action.
Support records may be retained for as long as reasonably necessary to resolve the request, maintain customer-service history, improve support operations, and establish or defend legal claims.
Deleted information may remain temporarily in encrypted backups or disaster-recovery systems until those backups are overwritten under ordinary retention cycles. We do not restore deleted information from backups except where necessary for disaster recovery, security, or legal compliance.
Viro uses administrative, technical, and organizational safeguards designed to protect personal information.
These safeguards include, where appropriate:
Access to production information is limited to personnel and service providers who need access to operate, secure, support, or maintain the Service.
No method of transmission or storage is completely secure. We cannot guarantee that unauthorized parties will never defeat our safeguards.
If you believe you have identified a vulnerability, contact nick@viro.app before publicly disclosing it.
Viro is based in the United States. Our Providers and service providers operate in the United States and other countries.
As a result, personal information may be processed in jurisdictions whose privacy laws differ from those in your place of residence.
Where required by applicable law, Viro will use an appropriate legal mechanism for an international transfer, which may include:
Customers are responsible for determining whether their submission of personal information through a particular model, Provider, or region satisfies their own data-location and international-transfer requirements.
Depending on where you live and subject to applicable exceptions, you may have the right to:
Viro does not sell personal information or share it for cross-context behavioral advertising. We therefore do not currently provide an opt-out mechanism for those activities.
To exercise a privacy right, contact: nick@viro.app
Please describe:
We may request additional information to verify your identity and authority. We will use verification information only to process the request.
You may use an authorized agent where applicable law permits. We may require evidence that the agent has authority to act for you and may verify your identity directly.
We will respond within the period required by applicable law. If we deny a request, we will explain the reason where required and provide information about any available appeal process.
You will not receive discriminatory treatment for exercising an applicable privacy right.
If your information was submitted through an application operated by a Viro customer, contact that customer first.
Viro may not be able to identify or retrieve your information because API Customer Content is not persistently stored in Viro's application database and may not be associated with your identity in Viro's systems.
When a customer asks Viro to assist with a valid End-User request, we will provide reasonable assistance as required by applicable law and our agreement with that customer.
You may contact us first so that we can attempt to resolve your concern.
Where applicable, you may also complain to the data-protection or privacy authority responsible for your jurisdiction.
This section applies only to the extent an applicable U.S. state privacy law covers Viro and the relevant information.
During the preceding 12 months, Viro may have collected the following categories of personal information:
We collect, use, retain, and disclose these categories for the purposes described in this Privacy Policy.
We may disclose them to:
We do not sell these categories of personal information or share them for cross-context behavioral advertising.
We do not knowingly use or disclose sensitive personal information for purposes other than providing the Service, maintaining security, preventing fraud, and other purposes permitted by applicable law.
The Service is intended for developers, businesses, and other users who are at least 18 years old.
We do not knowingly collect personal information directly from anyone under 18 through account registration.
Customers must not permit a person under 18 to create or control a Viro developer account.
Customer Applications may have their own permitted audiences. Customers are responsible for determining whether their applications may lawfully submit information relating to children and for complying with applicable parental-consent, notice, age-assurance, and children's-privacy requirements.
If you believe a person under 18 has created a Viro account or submitted personal information directly to Viro, contact nick@viro.app.
The Service may contain links to or retrieve content from third-party services and websites.
This Privacy Policy does not govern the independent privacy practices of those third parties. Review their privacy policies before providing information to them or relying on their services.
Enabling a tool or instructing a model to interact with an external service may cause information to be transmitted to that service.
We may update this Privacy Policy as the Service, Providers, or applicable laws change.
When we update it, we will revise the effective date at the top.
If a change materially affects how we collect, use, or disclose personal information, we will provide reasonable notice through email, the developer console, or another appropriate method before the change takes effect, where required.
Your continued use of the Service after an updated policy takes effect is subject to the updated policy. Where applicable law requires consent for a change, we will request it separately.
Questions, concerns, security reports, and privacy requests may be sent to:
Viro Climate Action, Inc.
Email: nick@viro.app