Terms & acceptable use

§1What the Service is

AIOS reviews software artifacts (code, configuration, schemas, infrastructure definitions, firmware, assets, and related files) against a set of typed governance critics, and returns verdicts (PASS / WARN / GATE) with findings. The governance critics run on AIOS's servers. The Client Tooling installed in your repository is a thin client: it reads files, sends them to the Service over an authenticated connection, writes results back into your repository's artifact files, and (optionally) installs a pre-commit hook so governance runs automatically.

§2Your API key

• An API key is issued to the email address you verify during signup. The verification link is single-use and expires 30 minutes after issuance.
• Beta keys are valid for 30 days from issuance ("free trial"). After that they auto-expire and stop working. You may request a replacement key by re-verifying your email; the old key is revoked when the new one is issued.
• Your key authenticates all calls to the Service and ties them to your account for usage tracking and abuse prevention.
• You are responsible for keeping your key confidential. Treat it like a password. Do not commit it to a public repository, embed it in client-side code, or share it. We display it once at issuance, so copy it then.
• We may revoke any key at any time if we detect abuse, terms violations, or a security concern. We will make a reasonable effort to notify you.
• Signup is rate-limited. Automated or bulk key acquisition is prohibited (see §4).

§3License to use the Client Tooling

We grant you a limited, non-exclusive, non-transferable, revocable license to install and use the Client Tooling solely to interact with the Service in your own repositories.

You may not:

• redistribute, resell, sublicense, or publish the Client Tooling or any part of it;
• use the Client Tooling to build, train, or improve a competing product;
• remove, obscure, or alter any proprietary notices.

This license terminates automatically if you violate these Terms, and immediately on expiry or revocation of your API key (you may keep the Client Tooling installed, but it will not function without a valid key).

§4Acceptable use

You may not:

• reverse-engineer, decompile, disassemble, or otherwise attempt to derive the governance critics, detection heuristics, rule definitions, or analysis logic of the Service, by any means including but not limited to systematic probing of the API with crafted inputs;
• attempt to circumvent rate limits, authentication, quotas, or other access controls;
• use the Service to process artifacts you do not have the right to process;
• use the Service in a manner that interferes with its operation or other users' access;
• acquire API keys through automated means, fake email addresses, or in excess of the beta cap;
• use the Service for any unlawful purpose.

Submitting a high volume of near-identical inputs differing in single tokens, in a pattern consistent with reverse-engineering the critics, is a violation of this section and may result in immediate key revocation.

A separate Acceptable Use Policy provides additional detail and is incorporated by reference (see below).

§5Your content

You retain all rights to the artifacts you submit for governance. By submitting them you grant us a limited license to process them solely to provide the Service (run critics, return findings, log the request for abuse prevention and the usage record). We do not use your submitted artifacts to train models or improve critics without your separate, explicit consent.

We log, per governance call: your account/tenant identifier, a content hash of the submitted artifact, the verdict, and a timestamp. We may retain these audit records for the period required for security, billing, and the integrity guarantees the Service makes. We do not retain the full content of your artifacts beyond what is needed to return the immediate result, unless you explicitly enable a feature that requires it.

During the beta we additionally collect aggregated, de-identified service metrics (verdict-type counts, which rule packs fired, severity mix, p50/p95 latency, agent identifiers, and artifact-size buckets) so we can tune what works. These metrics carry no source code, no diffs, no plaintext keys, and no per-user identifiers. They are retained for 24 months; account/IP fields are scrubbed within 90 days, and the full record is deleted within 30 days of account deletion. The full Privacy Policy describes the schema.

§6Beta status

The Service is in beta. It may change, break, or be discontinued. Verdicts are provided on an as-is basis and are not a substitute for your own review, testing, or professional security audit. AIOS critics are heuristic, they will have false positives and false negatives. A PASS verdict is not a guarantee that an artifact is safe, correct, or compliant. You remain responsible for what you ship.

During beta, the Service is provided free of charge. We reserve the right to introduce paid tiers, with notice, after the beta period.

§7Disclaimers and limitation of liability

§8Indemnification

You agree to indemnify and hold harmless AIOS and its operators from any claim arising out of your misuse of the Service, your violation of these Terms, or your violation of any law or third-party right in connection with your use of the Service.

§9Changes

We may update these Terms. Material changes will be reflected in an updated effective date and, where practical, communicated to the email on file. Continued use after a change constitutes acceptance.

§10Termination

You may stop using the Service at any time by uninstalling the Client Tooling (node aios-hook.js --uninstall-hooks .) and discarding your key. We may suspend or terminate your access for any violation of these Terms, for abuse, or for any security concern.

§11Governing law

These Terms are governed by the laws of the jurisdiction in which the Service operator is established, without regard to conflict-of-laws principles. Any dispute will be resolved in the courts of that jurisdiction.

§12Contact

For questions about these Terms, or to report abuse or a security issue, use the contact channel listed at the Service's signup page (email: ezra@visnryentertainment.com).

§1Permitted use

• Use your API key to submit artifacts from repositories you own or have the right to govern.
• Install the Client Tooling (CLI, pre-commit hook, MCP bridge) in your own repositories.
• Integrate AIOS governance into your own development workflow, CI, and AI-assisted coding tools.
• Reference AIOS findings in your own internal documentation and PR reviews.

§2Prohibited use

2.1   Reverse-engineering the Service

You may not attempt to derive, reconstruct, or approximate the governance critics, detection heuristics, rule definitions, scoring, or analysis logic of the Service. This includes, without limitation:

• decompiling, disassembling, or otherwise inspecting any server-side component;
• systematically probing the API with crafted, minimal-difference inputs to map critic behavior (a "differential probing" attack);
• submitting a high volume of near-identical artifacts that differ only in small token-level mutations;
• building a tool, dataset, or model that captures, mimics, or competes with AIOS's critic behavior using data derived from the Service.

The Client Tooling is plumbing: a file reader, an HTTP client, an artifact writer, and an instruction file. It contains no critic logic. Attempting to extract critic logic from the Client Tooling is futile and, if attempted via the API, is a violation of §2.1.

2.2   Abuse of access controls

You may not:

• circumvent or attempt to circumvent rate limits, quotas, authentication, or key expiry;
• acquire API keys through automation, disposable/fake email addresses, or in excess of any beta cap;
• share, resell, or sublicense your API key;
• use one key across an organization in a way designed to evade per-account limits.

2.3   Harmful or unlawful use

You may not use the Service to:

• process artifacts you do not have the legal right to process (including third-party proprietary code without authorization);
• facilitate any unlawful activity;
• interfere with the Service's operation or other users' access (including denial-of-service patterns);
• attempt to inject malicious payloads into the Service or use it as a vector against AIOS infrastructure.

2.4   Misrepresentation

You may not:

• misrepresent AIOS verdicts as a guarantee of safety, correctness, or compliance to third parties;
• claim AIOS endorsement, partnership, or certification that has not been granted;
• present AIOS-derived findings as your own product's analysis when reselling or white-labeling (white-labeling requires a separate agreement).

§3Rate limits and quotas

• Signup is rate-limited per IP (currently 5 attempts per minute).
• Beta API keys expire 30 days after issuance and must be re-verified to renew.
• Governance API calls may be rate-limited and quota-limited per account. Limits are enforced server-side; exceeding them returns 429 with a Retry-After indication.
• Sustained traffic patterns consistent with abuse or differential probing (see §2.1) will be throttled and may trigger key revocation.

§4Audit and logging

For every governance call we log: your account/tenant identifier, a content hash of the submitted artifact (not the content itself, unless a feature you enabled requires it), the verdict, the timestamp, and the calling IP. These records are used for security, abuse prevention, billing, and the audit-trail guarantees the Service makes. They are not shared with third parties except as required by law.

Any use of the AIOS_PREFLIGHT_BYPASS flag (in repositories that enable the intent-ledger forcing function) is recorded in the audit log. Bypasses are permitted for genuine emergencies but are visible.

Beta service metrics. In addition to the per-call audit record, during the beta we collect aggregated, de-identified service metrics (verdict counts by type, which rule packs fired, severity mix, p50/p95 latency, agent identifiers, and artifact-size buckets) to evaluate and improve the critics. These metrics carry no source code, no diffs, no plaintext keys, and no per-user identifiers; they are retained for 24 months. Account/IP fields in the per-call audit record are scrubbed within 90 days, and the full record is deleted within 30 days of account deletion.

Per-tenant health scoring. We may derive a per-account operational health score from your aggregate usage data (governance call volume, pass/gate ratios, and session cadence) for internal customer-success purposes, such as identifying accounts that may need support or are at risk of churn. This score is derived from the per-call audit records described above, is tied to your account identifier, and is not shared with third parties. You may request its deletion by contacting ezra@visnryentertainment.com.

§5Reporting violations

If you discover a security vulnerability in the Service, or observe abuse by another user, report it through the contact channel listed at the Service's signup page. Do not publicly disclose a vulnerability before we have had a reasonable opportunity to address it.

§6Enforcement

We may, at our discretion and without prior notice where the violation is severe:

• revoke the offending API key;
• suspend or terminate the offending account's access;
• block IP ranges associated with abuse;
• preserve relevant logs for legal purposes.

We will make a reasonable effort to notify you of enforcement actions, except where doing so would compromise an investigation or the security of the Service or other users.

§7Changes

We may update this AUP. Material changes will be reflected in an updated effective date. Continued use after a change constitutes acceptance.