Acceptable Use Policy

This Acceptable Use Policy applies to the Verixos SaaS, APIs, SDKs, CLI tools, MCP integrations, webhooks, demo environments, support channels, documentation, and self-host license workflows. It is incorporated into the Verixos Terms of Service and any agreement that references it.

Users may not probe, scan, attack, overload, disrupt, or bypass Verixos systems, customer deployments, authentication controls, authorization checks, SSO/SAML flows, rate limits, API limits, plan limits, license checks, audit logs, or security controls.

Users may not upload malware, exploit code, credential dumps, phishing content, unauthorized secrets, or code intended to compromise Verixos, customers, subprocessors, or third-party systems.

Users may not upload classified information, export-controlled technical data, ITAR technical data, CUI requiring a dedicated authorized environment, sensitive government data, third-party proprietary files, personal data, or regulated data into any deployment not approved for that data category.

Users may not use Verixos to evade export controls, sanctions, procurement rules, agency security requirements, classification rules, or contractual data-handling obligations.

Users may not represent Verixos outputs as flight approval, safety certification, regulatory approval, agency acceptance, or final engineering sign-off unless a separate written agreement and customer validation process expressly support that statement.

Users may not remove context, warnings, validation limits, or provenance from Engineering Output in a way that is misleading for downstream reviewers.

Automation must use authorized accounts, API keys, tokens, webhook endpoints, and customer-approved workflows. Users may not share, publish, embed, or commit live credentials.

Users may not use automation to scrape restricted data, create abusive load, exfiltrate customer data, bypass billing limits, bypass license limits, or trigger unauthorized third-party systems.

Users may not use Verixos for unlawful activity, infringement, harassment, privacy violations, fraud, sanctions violations, deceptive conduct, or interference with other users.

Users may not upload or process content unless they have the rights and permissions needed to do so.

Users may not reverse engineer protected Verixos code, models, services, license mechanisms, or non-public APIs except where law prohibits that restriction.

Users may not use non-public Verixos materials, beta access, benchmarks, roadmap information, or support communications to build or benchmark a competing service without written permission.

Verixos may suspend accounts, revoke API keys, disable webhooks, restrict projects, remove content, require remediation, notify organization administrators, or terminate access when it reasonably believes this policy has been violated or a security, legal, or operational risk exists.