Privacy Policy

Last updated: October 8, 2026

Summary

AiiWare offers two distinct product lines and the data practices differ between them. Local products run on your device. Telemetry-capable Aii CLI releases offer limited usage analytics as described below; the local VSCode and Chrome extensions do not send these usage analytics. Aii Cloud (the hosted service at cloud.aiiware.com) necessarily collects account and usage data to provide the service. This page describes both.

Local Products — Your Content and Credentials

Local products do not send your content or credentials to AiiWare as usage analytics. These exclusions apply when using your own provider keys or a locally hosted Aii Server:

Your inputs (prompts, commands) are processed locally and may be sent to third-party AI providers only when you configure and authorize that.

Aii CLI — Optional Usage Analytics

In telemetry-capable releases, usage analytics is enabled by default for eligible use after the CLI displays a short notice with this policy, the terms, and disable controls. The notice is shown before any usage analytics request. Releases without this feature do not send these signals, and upgrading does not upload historical usage. Following a release default is not recorded as an explicit agreement; an explicit ON setting is distinguished from the default.

Signals describe CLI launches, setup outcomes, and completed requests. They contain random installation and event identifiers, event timestamps, CLI version, broad operating system and architecture, interactive or one-shot mode, backend class, preference state, and notice version. Outcomes, duration buckets, and predefined error categories are included where relevant. These identifiers are pseudonymous, not anonymous or hardware fingerprints. We use the signals to understand observed installations, successful activation, reliability, and product use; they do not establish a count of individual people.

Requests go to telemetry.aiiware.com. The receiving network necessarily processes a source IP address. The telemetry service may use it transiently for approximate country inference and abuse limits; raw IP addresses are not stored in telemetry records. Country may be unknown. We do not collect city location or precise location through CLI usage analytics.

We use Cloudflare to secure and route telemetry requests. Cloudflare processes network and security metadata, including source IP addresses, under its applicable retention policies. These provider records are separate from our product analytics, which do not retain raw IP addresses. Our telemetry policy prohibits logging payloads or credentials and exporting network logs for product analysis. See Cloudflare’s Privacy Policy and analytics retention documentation.

Turn analytics off with aii telemetry off, or set AII_TELEMETRY=off before launching the CLI. The environment setting overrides a local ON preference. Inspect your setting with aii telemetry status, and choose ON with aii telemetry on. Collection is suppressed in recognized automation, when the notice cannot be delivered, or when the platform cannot provide the required controls. Windows collection remains disabled in the initial implementation.

Turning an enabled installation OFF through the command saves OFF before any new usage request is dispatched and may attempt one minimal preference receipt for that transition. It contains only the state disabled_explicitly, notice version, a random per-action receipt identifier, and a coarse UTC-day timestamp. It contains no installation or account identifier, country, or usage details. Repeating OFF, an already disabled installation, environment OFF, and recognized automation send no receipt. Receipts have no persistent retry or replay on later launches. Requests transmitted before OFF cannot be recalled and may still arrive afterward. OFF does not erase previously received data; its retention limits still apply.

Raw telemetry events and preference receipts expire within 90 days. Installation lifecycle records expire after 180 inactive days. Detailed aggregates and their pseudonymous membership records expire within 13 calendar months of their reporting window ending. Reviewed coarse totals that omit installation identifiers and detailed dimensions may be retained longer. Detailed reports are restricted to authorized operators and suppress sparse groups. Usage analytics is optional background work: delivery failures are silent and do not prevent CLI work.

Aii Cloud (cloud.aiiware.com) — Data We Collect

When you sign in to Aii Cloud and use the hosted service, we collect and store, for as long as needed to provide the service: account identity received from your chosen sign-in provider (Google or GitHub — we receive your email, display name, profile picture URL, and provider-issued user ID); API keys we issue you (stored hashed; plaintext shown only once at creation); per-request usage records (date/time, model, token counts, credit cost); your credit balance and onboarding-survey response; and session cookies scoped to cloud.aiiware.com. We do not collect third-party LLM provider keys you might use elsewhere.

When you send a chat message, your prompt is forwarded to the upstream LLM provider that fulfils the request (Anthropic, OpenAI, OpenRouter, DeepInfra, or others — their own privacy policies govern what they do with the prompt).

Free-tier conversations (prompts you send and responses you receive on the free tier) may be retained by AiiWare and used to evaluate, improve, fine-tune, or train AiiWare's own AI models, and for abuse detection. If you don't want your messages used this way, don't send them through the free tier. Future paid tiers will have a different policy published before any paid plan launches.

You can request access to or deletion of your account data by emailing support.

Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our products, services, or practices. When we make changes, we will revise the “Last updated” date at the top of this page. CLI telemetry notices are versioned separately; a release default is not treated as an affirmative consent action.

Contact

Questions about this policy? Email [email protected]