Cynos Terms of Use and Acceptable Use Policy
Last updated: November 19, 2026
1. About these Terms
These Cynos Terms of Use (the "Terms") are a binding agreement between Averlon, Inc., a Delaware corporation with offices in Redmond, Washington ("Averlon," "we," "us"), and the customer that accesses or uses Cynos ("Customer" or "you"). The Acceptable Use Policy in Section 6 is part of these Terms.
You accept these Terms by clicking to accept, by creating an account, or by using Cynos, whichever happens first (the "Start Date"). If you sign up with a work email address or on behalf of an organization, that organization is the Customer and you confirm you have authority to bind it.
If you and Averlon have signed a separate agreement for Cynos (such as a master services agreement or order form), that agreement controls where it conflicts with these Terms.
Cynos is a business service for security practitioners. It is not offered to consumers.
2. Definitions and the Service
2.1 Definitions.
- "Cynos" or the "Service" means Averlon's inference platform for security workflows, including its API, routing engine, Cynos Judge, Cynos models, dashboard, and Documentation.
- "Model" means any large language model or other AI model reachable through the Service.
- "Third-Party Model" means a Model made available by a third party (a "Model Provider"), whether called through that provider's API or hosted by Averlon or its inference partners.
- "Cynos Model" means a Model built, fine-tuned, or operated by Averlon, including Cynos Task Expert models.
- "Model Terms" means the terms, usage policies, and licenses that a Model Provider applies to its Model, as listed in the Documentation.
- "Inputs" means prompts, files, code, logs, and other content you or your Users submit to the Service. "Outputs" means content the Service returns. Inputs and Outputs together are "Customer Content."
- "Customer Data" means Customer Content plus account information you provide.
- "Usage Data" means metadata and telemetry about use of the Service, such as request counts, token counts, latency, model selected, judge scores, and error rates. Usage Data does not include the text of Inputs or Outputs.
- "Users" means your employees, contractors, and end users whom you allow to use the Service under your account.
- "Customer Application" means a product, service, or workflow you build or operate that calls the Service.
- "Documentation" means the Cynos documentation we make available, as updated from time to time.
2.2 How Cynos works. For each request, Cynos selects a Model from a group of Models it judges suitable for the task, generally preferring the lowest-cost Model expected to produce a correct result. The Cynos Judge may evaluate an Output and ask the same or another Model to revise it one or more times.
2.3 What this means for you. A single request may be processed by more than one Model and more than one Model Provider. Fees for a request cover all routing, Model calls, and judge steps for that request, as described in the Documentation.
2.4 Changes to Models. We may add, remove, or replace Models and Model Providers at any time. Where practical we will give advance notice of removals that affect a Model you have selected as a Fallback Model or pinned in your configuration.
3. Accounts and Access
3.1 Eligibility. To use Cynos you must be at least 18, use it for business purposes, and not have been suspended from Cynos or from any Model Provider's service. You may not use Cynos if you are located in, organized under the laws of, or owned or controlled by a party in a country or region subject to comprehensive U.S. sanctions, or if you appear on a U.S. or other applicable restricted party list.
3.2 Right to use. Subject to these Terms and payment of fees, we grant you a non-exclusive, non-transferable right during the term to access and use the Service, and to allow your Users to do so, in line with the Documentation.
3.3 Account information. You will give accurate account information and keep it current. Organization accounts are managed by one or more administrators who control Users, API keys, routing settings, Fallback Model selection, provider allowlists, and logging settings.
3.4 API keys and credentials. You are responsible for keeping your API keys and passwords secure and for all activity and charges under them, except where caused by our breach of these Terms. Do not embed API keys in client-side code or public repositories. Tell us promptly at security@averlon.io if you believe a key or account has been compromised. We may suspend, rotate, or revoke credentials when needed to protect you, the Service, or a Model Provider.
3.5 Building on Cynos. You may use Cynos to power Customer Applications that you offer to your own customers, including security products, penetration testing tools, agent harnesses, and managed security services. When you do:
- You are responsible for your end users' use of the Service and for their compliance with Section 6 and applicable Model Terms.
- You will have terms with your end users that are at least as protective of Averlon and Model Providers as Sections 4 and 6.
- Your Customer Application must add meaningful functionality beyond access to the Service.
3.6 What you may not do with access. Without our written consent, you may not resell, sublicense, or white-label raw access to the Cynos API, offer the Service as a general-purpose model routing or inference service, or share API keys across separate organizations. You may enter your own Cynos API key into a third-party tool, such as an open source or commercial security harness, so that the tool calls Cynos on your behalf. Requests made through that tool with your key are your use of the Service under these Terms. The tool's provider is not a party to these Terms, and Averlon is not responsible for that tool. Any other arrangement in which a third party offers Cynos to its users requires a separate partner agreement with Averlon.
3.7 Managed service providers. If you are a managed service provider, you may use the Service to deliver services to your clients. Each client's data must be processed only for that client. You remain responsible for your clients' use as if it were your own.
4. Models and Model Providers
4.1 Model Terms apply. Your use of each Third-Party Model is also subject to that Model's Model Terms. You will comply with them and make sure your Users do. Model Providers may change their terms, and continued use of a Model after a change means you accept it. If you do not accept a change, remove that Model from your configuration.
4.2 Controlling where requests go. You can restrict routing to specific Models, Model Providers, or hosting regions using provider allowlists in your settings. If you have workloads that a Model Provider's terms do not permit, you are responsible for configuring Cynos so those workloads are not sent to that provider. Cynos offers a security-workload mode that routes requests only to Cynos Models and open-weight Models hosted under Averlon's control. Approved Offensive Testing runs in this mode.
4.3 Availability. Models are provided on an as-available basis. We do not guarantee that any particular Model will remain available, keep the same behavior, or respond within a given time. If a Model is unavailable, Cynos may route to another eligible Model or to your Fallback Model.
4.4 Provider actions. A Model Provider may restrict or end access to its Model, including at its own discretion or because it suspects a violation. We may restrict your access to a Model when a Model Provider asks us to or when we reasonably suspect a violation of its Model Terms. We are not liable for actions a Model Provider takes.
4.5 Restricted Models. Some Model Providers bar access from certain organizations, countries, or regions. You may not access a restricted Model through Cynos, including through VPNs, proxies, or any other means of hiding your location or identity.
4.6 Cynos Models. Cynos Models are governed by these Terms alone. No separate Model Terms apply to Cynos Models unless we tell you otherwise in the Documentation.
5. Customer Data
5.1 Ownership. As between you and Averlon, you own your Inputs. You own Outputs from Cynos Models, and we assign to you any rights we have in them. Ownership of Outputs from Third-Party Models is governed by the applicable Model Terms. Outputs may not be unique, and other customers may receive similar Outputs.
5.2 Our use of Customer Data. You grant us a non-exclusive, worldwide license during the term to host, process, transmit, and display Customer Data only as needed to provide, secure, and support the Service, including sending Inputs to the Models that Cynos selects for a request. We do not sell Customer Data.
5.3 No training on your data. We do not use Customer Content to train, fine-tune, or evaluate Cynos Models or any other models, and we do not share it for those purposes, unless you opt in in writing for a specific project (for example, a custom fine-tune built for you). Data used in an opted-in project is used only for you and kept isolated from other customers.
5.4 Retention. By default, Cynos runs with zero data retention: we do not store Inputs or Outputs after a request completes. We keep request metadata and Usage Data. If an administrator turns on request logging, we store Inputs and Outputs for the retention period you select, and you can view and delete them in the dashboard.
5.5 Model Provider data practices. When a request is sent to a Third-Party Model through that provider's API, the provider receives the Inputs. Every Third-Party Model available through Cynos runs under zero data retention terms with its Model Provider, so providers do not store Inputs or Outputs after processing a request or use them for training. All Model processing for Cynos takes place in the United States. We list our Model Providers in the Documentation and keep that list current. You can use provider allowlists to exclude any provider you do not want to receive your data.
5.6 Usage Data. We own Usage Data and may use it to operate and improve the Service, including the routing engine and Cynos Judge, and to produce aggregated statistics that do not identify you or your Users.
5.7 Security. We maintain administrative, technical, and physical safeguards designed to protect Customer Data. We will notify you without undue delay, and in any case within 72 hours, after becoming aware of a security incident affecting your Customer Data.
5.8 Personal data. Security data often contains personal data such as usernames, IP addresses, and email addresses. To the extent we process personal data on your behalf, our Data Processing Addendum applies and is part of these Terms. You are responsible for having a lawful basis to submit personal data and for not submitting special categories of personal data, protected health information, or payment card data unless we have agreed in writing.
5.9 Your responsibilities for Inputs. You represent that you have the rights and permissions needed to submit your Inputs, including any third-party code, logs, malware samples, or system data, and that your Inputs and your use of Outputs comply with law and Section 6.
5.10 Deletion. Within 30 days after the end of the term, or sooner on request, we will delete Customer Data we hold, except as required by law or kept in backups that are deleted on their normal cycle.
6. Acceptable Use Policy
Cynos is built for defenders. Security work often requires offensive techniques, and this policy permits them once Averlon has approved them and the owner of each target has authorized them. It prohibits using Cynos to harm systems, people, or organizations that have not agreed to be tested.
6.1 Permitted security work. Subject to the rest of this Section, you may use Cynos for:
- Vulnerability discovery, triage, prioritization, and root-cause analysis.
- Malware analysis, reverse engineering of samples, and threat intelligence work.
- Detection engineering, including writing detection rules and testing them against attack techniques.
- Misconfiguration triage, remediation, and generating infrastructure-as-code fixes.
- Security research, education, and capture-the-flag exercises.
- Offensive Testing, once approved under Section 6.2.
6.2 Offensive Testing requires approval. Penetration testing, red team operations, adversary emulation, exploit proof-of-concept development, phishing simulations, and any other use of Cynos to scan, probe, exploit, or actively test a system, network, application, or account ("Offensive Testing") are allowed only after Averlon approves your request for penetration testing access through the process described in the Documentation. We review each request case by case and may approve, limit, or decline it. Approval covers the scope described in your request, and we may withdraw it if your use goes beyond that scope or violates this Section. In addition, before any Offensive Testing you must have authorization from the owner of each target, and you must stay within the scope the owner agreed. You will keep records of that authorization and give them to us on request.
6.3 Prohibited security uses. You may not use Cynos to:
- Access, scan, exploit, or disrupt any system, network, or account without authorization from its owner.
- Develop, deploy, or distribute malware, ransomware, wipers, or botnets for use outside an authorized engagement, or for sale or distribution to others.
- Run denial-of-service attacks or attacks intended to degrade availability of systems you are not authorized to test.
- Target critical infrastructure, including power, water, healthcare, emergency services, and industrial control systems, outside an authorized engagement with the operator.
- Run phishing, social engineering, credential stuffing, or account takeover against people or organizations that have not authorized it.
- Steal, exfiltrate, or misuse credentials, personal data, or confidential information.
- Sell, broker, or supply exploits, vulnerabilities, or intrusion tooling to parties you know or should know will use them without authorization, or to any party subject to sanctions or export restrictions.
- Conduct surveillance, stalking, or tracking of individuals, or build tools for covert monitoring of people.
- Evade detection by law enforcement or hide the proceeds of crime.
6.4 Other prohibited uses. You may not use Cynos to:
- Violate any applicable law or regulation, including export control and sanctions laws, or any Model Terms.
- Create, distribute, or seek child sexual abuse material, or sexualize minors in any way. We report such material to the National Center for Missing and Exploited Children and to law enforcement.
- Develop or acquire chemical, biological, radiological, nuclear, or explosive weapons, or plan violence or terrorism.
- Harass, threaten, defame, or discriminate against any person.
- Commit fraud, impersonate any person or organization, or misrepresent your affiliation.
- Send spam or unsolicited bulk messages.
- Infringe or misappropriate intellectual property or privacy rights.
- Make automated decisions that have legal or similarly significant effects on individuals without appropriate human review.
6.5 Protecting the Service. You may not:
- Reverse engineer, decompile, or attempt to extract the source code, routing logic, Cynos Judge prompts or rubrics, or model weights of the Service, except where the law expressly allows it.
- Use the Service or its Outputs to build a competing model routing, judging, or inference service, including by systematically extracting routing decisions or judge evaluations.
- Circumvent rate limits, usage caps, security controls, or billing, including by creating multiple accounts or using another customer's credentials.
- Scrape the Cynos website or dashboard, or use automated means to access the Service other than through the API as documented.
- Load test or stress test the Service without our written approval.
- Interfere with or disrupt the Service, its infrastructure, or other customers.
6.6 Testing Cynos itself. You may test the robustness of your own Customer Applications and agents that use Cynos, including against prompt injection. You may not attempt to bypass the safety controls of Cynos or of any Model, or test the security of Cynos infrastructure, except under our vulnerability disclosure program or with our written approval. We welcome good-faith reports and will not pursue legal action against researchers who follow that program.
6.7 Benchmarking. You may benchmark Cynos for your own evaluation. You may publish benchmark results if you disclose the workflows, Models compared, Cynos configuration, and date of testing, and give us a reasonable chance to review the methodology before publication. Competitors of Averlon may not benchmark the Service without written consent.
6.8 Responsibility for actions and Outputs. Outputs can be wrong, incomplete, or unsafe to run. You are responsible for reviewing Outputs before relying on them and for any action taken by you, your Users, or your agents based on Outputs, including running code, changing configurations, or executing remediation in production. Use human approval for actions that could cause outages or data loss.
6.9 Monitoring and enforcement. We use automated systems to screen requests for abuse, which may process Inputs in transit even when logging is off. If we reasonably believe you have violated this Section, we may block requests, restrict Models, suspend or terminate your account, and report activity to law enforcement or affected parties where we believe it is required or appropriate. Where practical and lawful, we will notify you and give you a chance to respond first.
6.10 Reporting misuse. Report suspected misuse of Cynos to security@averlon.io.
7. Fees, Suspension, and Termination
7.1 Fees. You will pay the fees shown on our pricing page or in your order form. Self-serve accounts buy prepaid credits that are used up per request. Accounts on an order form are invoiced monthly in arrears, with payment due within 30 days. Fees exclude taxes, which you will pay except for taxes on our income.
7.2 Credits. Credits are not currency, have no cash value, cannot be transferred, and can be used only on Cynos. Unused credits expire one year after purchase. Purchases are non-refundable except where required by law. If you turn on auto-recharge, we will charge your payment method when your balance falls below the threshold you set, until you turn it off. Promotional credits can be changed or withdrawn at any time and have no value outside the promotion.
7.3 Price changes. We will give at least 30 days' notice of price increases for Cynos routing fees. Prices for Third-Party Models may change when Model Providers change their prices, and we will reflect those changes in the Documentation.
7.4 Rate limits. We may apply rate limits and usage caps described in the Documentation or your account settings.
7.5 Suspension. We may suspend your access, in whole or in part, if you fail to pay undisputed fees when due, if we reasonably believe you have violated Section 6, or if your use poses a security risk to the Service, a Model Provider, or others. We will give notice by email where practical and restore access once the issue is resolved.
7.6 Term and termination. These Terms start on the Start Date and continue until terminated. You may stop using Cynos and close your account at any time. We may terminate these Terms for convenience with 30 days' notice, or immediately if you materially breach these Terms, including Section 6, and the breach cannot be cured or is not cured within 10 days of notice.
7.7 Effect of termination. When these Terms end, your right to use the Service stops and you remain responsible for fees already incurred. If we terminate for convenience, we will refund unused prepaid credits within 30 days. If we terminate for your breach, unused credits are forfeited. Sections 5.6, 5.10, 6.8, 7.7, and 8 survive termination.
8. Legal Terms
8.1 Our intellectual property. Averlon owns the Service, Cynos Models, the routing engine, the Cynos Judge, the Documentation, and Usage Data, and all rights in them. We reserve all rights not expressly granted. The Cynos name and logo are Averlon trademarks.
8.2 Feedback. If you give us suggestions or feedback, we may use them without restriction or payment.
8.3 Confidentiality. Each party will protect the other's non-public information that is marked confidential or should reasonably be understood to be confidential, using at least reasonable care, and use it only to perform under these Terms. Your Customer Data is your confidential information. This does not apply to information that is public, already known, independently developed, or rightfully received from a third party. A party may disclose confidential information when required by law, after giving notice where lawful.
8.4 Disclaimers. The Service and all Models and Outputs are provided "as is" and "as available." To the fullest extent permitted by law, Averlon disclaims all warranties, express or implied, including merchantability, fitness for a particular purpose, title, and non-infringement. We do not warrant that the Service will be uninterrupted or error-free, that any Model will remain available, or that Outputs will be accurate, complete, secure, or free of vulnerabilities. Outputs are not a substitute for professional judgment, and Cynos does not guarantee that a system is secure.
8.5 Your indemnity. You will defend and indemnify Averlon and its affiliates against third-party claims arising from your Inputs, your Customer Applications, your or your Users' violation of Section 6 or of Model Terms, or your violation of law, and pay resulting damages and reasonable costs.
8.6 Limitation of liability. Neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, or data, even if advised of the possibility. Each party's total liability under these Terms is limited to the fees you paid to Averlon in the 12 months before the claim. For breach of Section 5.7 (Security), the limit is two times that amount. These limits do not apply to your payment obligations, a party's indemnity obligations, or liability that cannot be limited by law, including gross negligence or willful misconduct.
8.7 Export and sanctions. You will comply with U.S. and other applicable export control and sanctions laws. You will not use the Service, or export or re-export Outputs, in violation of those laws, including for prohibited end uses or by prohibited end users.
8.8 Changes to these Terms. We may update these Terms. We will give at least 30 days' notice of material changes by email or in the dashboard. Changes apply from the effective date stated in the notice. If you do not agree, stop using the Service before that date. Disputes are governed by the version in effect when the dispute arose.
8.9 Governing law and disputes. These Terms are governed by the laws of the State of Washington, without regard to conflict of laws rules. The parties will first try in good faith to resolve any dispute for 30 days after written notice. Any unresolved dispute will be decided in the state or federal courts in King County, Washington, and each party consents to their jurisdiction. Either party may seek injunctive relief in any court to protect its intellectual property or confidential information.
8.10 General. These Terms, with the Documentation, the Data Processing Addendum, and any order form, are the entire agreement on this subject. You may not assign these Terms without our consent. Either party may assign them without consent in a merger, acquisition, or sale of substantially all of its assets. If a provision is unenforceable, the rest remains in effect. Failure to enforce a provision is not a waiver. The parties are independent contractors. Neither party is liable for delays caused by events beyond its reasonable control. We may send notices by email to your account address. Send notices to us at legal@averlon.io. We will not name you as a Cynos customer or use your logo without your written permission.