Aiz Research
Privacy
Aiz is private by design: local agent work stays on your Mac, while account, credits, and managed inference use the Aiz cloud only where necessary. This page describes the current product, not a future fully local-only mode.
What stays local
- Project files and folders you open
- Tool execution: shell, Git, browser automation, MCP, processes
- Chat history and memory (local SQLite on Desktop)
- BYOK provider API keys (macOS Keychain)
What can leave your device
- Aiz Managed: context selected for the current model turn is sent to the Aiz Gateway, then to OpenRouter and the chosen provider. Managed inference is not fully local.
- Portal sign-in, Desktop linking, and payment verification requests
- Wallet connection flows via Reown (your wallet signs; Aiz never receives your private key)
What Aiz cloud stores
- Account and wallet identity mapping (internal user id, not your wallet as primary id)
- Desktop session metadata and hashed refresh credentials
- Credit ledger, reservations, and payment verification records
- Inference usage metadata (model, tokens, cost, credits) — not full prompts or responses
What Aiz cloud does not store by design
- Copies of your project repository
- Complete Desktop chat history or local memory database
- Full inference prompts or model responses for billing or analytics
- Your wallet private key, seed phrase, or mnemonic
Telemetry
Aiz does not collect behavioral product telemetry by default (no PostHog, Amplitude, Segment, or Vercel Web Analytics in the app). Hosting, wallet, and payment infrastructure may still produce their own operational logs.
Upstream providers
Aiz controls its gateway storage policy. OpenRouter and individual model providers process inference content under their own terms. See OpenRouter for upstream policies.