How Aiola handles security and your data

Aiola is a local-first desktop app for macOS and Windows that orchestrates Claude Code, Codex, Cursor, Grok CLI, and OpenCode on your machine. Security here means being precise about what the app does on your disk, how installers and updates are delivered, what leaves your computer, and how to reach us if something looks wrong. We do not claim certifications we have not earned, and we do not describe protections that are not in the product today.

This page is the canonical reference for trust questions — the same facts appear in our data ownership page, docs, and agent-facing summaries. If something here conflicts with behavior you observe in the app, please email us so we can correct it.

You download Aiola from GitHub Releases via links on our download page. Each platform build is packaged and signed before it is published.

macOS. Aiola ships as a universal disk image with separate Apple Silicon and Intel builds. Builds use Apple's hardened runtime and go through Apple's notarization process before release. Notarization means Apple has scanned the binary for known malware signatures and stapled a ticket that Gatekeeper checks on first open. You may still need to confirm opening an app downloaded from the web the first time — that is normal macOS behavior for any developer-signed app outside the Mac App Store.

Windows. The Windows installer is an NSIS package (.exe) signed with a code-signing certificate. A signed installer identifies the publisher and helps SmartScreen build reputation over time. On a fresh Windows machine you may see an "unrecognized app" prompt until the certificate accumulates enough installs — see our install guide for the honest walkthrough.

We publish release artifacts on GitHub so the download URL, version history, and checksums are visible. The in-app updater pulls from the same release channel.

The desktop app includes electron-updater, which checks GitHub Releases for newer versions, downloads them in the background, and prompts you to restart when an update is ready. The app also rechecks on a schedule (approximately every six hours) so long-running installs do not stay on old builds silently.

macOS. Updated builds go through the same notarization pipeline as initial installs. Hardened runtime entitlements stay consistent across versions unless a release note calls out a deliberate change.

Windows. Updates arrive as signed NSIS installers from the same GitHub Releases channel. You can always install manually from the download page if you prefer to control timing yourself.

Aiola also registers a deep-link protocol (aiola://) so checkout and onboarding flows can return you to the desktop app after browser steps. Only install Aiola from our official download links or the in-app updater.

Your code and repos stay on your machine. Agent prompts and file context are sent only to the AI provider you choose — Anthropic (Claude Code), OpenAI (Codex), Cursor, xAI (Grok CLI), or whichever provider you configure in OpenCode — under your own subscription. Aiola never proxies, stores, or resells your code or model traffic. Threads, tasks, notes, and automations are stored locally (SQLite + plain files in your repo). If you use the optional analytics/logs/feedback layer for your shipped products, that telemetry is ingested via Aiola's cloud (Supabase/Tinybird). Offline: agent orchestration UI works offline; running agents requires provider access; GUI Lifetime keeps the local app opening even if Aiola's servers are unreachable.

Read more about what stays local in our own your data page. The short version: orchestration data lives on your machine; optional ops-layer telemetry for products you ship transits Aiola's cloud.

Aiola can see (on your machine): workspace configuration, thread and task state stored in local SQLite and plain files, agent personas and skills you define, git metadata for projects you open, and terminal output within the app. This data stays on disk unless you explicitly enable a cloud-connected feature.

Aiola can see (if you enable ops features): analytics events, error logs, and end-user feedback from web apps where you install Aiola's snippet or SDK. That telemetry is ingested through Aiola's cloud (Supabase/Tinybird) so you can query it inside the desktop app.

Aiola cannot see: your private repositories unless you open them in a workspace; your conversations with AI providers except what is stored locally in thread history; your provider API keys or CLI session tokens (those live in each vendor's own credential store); or other applications on your computer outside the workspaces you attach.

Your AI providers can see: prompts, file context, and tool output you send through Claude Code, Codex, Cursor, Grok CLI, or OpenCode — under the privacy policy of whichever provider you chose. Aiola does not proxy or resell that traffic.

Aiola accounts authenticate with Google OAuth or email one-time passcodes. There is no Aiola-specific password to leak. Sessions tie to your subscription, trial, or GUI Lifetime license state stored in Aiola's central entitlement service (Supabase).

Signing in to Aiola is separate from signing in to your coding agents. After you open the app, you connect each CLI on your machine — for example claude login, codex login, cursor-agent login, or grok agent --reauth. Those credentials stay with the vendor's tooling; Aiola invokes the binaries you have already authenticated.

If you believe you have found a security vulnerability in Aiola, please report it responsibly. Email [email protected] with:

• A clear description of the issue and its potential impact
• Steps to reproduce, including Aiola version and operating system
• Any proof-of-concept you are comfortable sharing
• Your preferred contact for follow-up

We ask that you give us reasonable time to investigate and ship a fix before public disclosure. We do not currently offer a paid bug-bounty program, but we do acknowledge researchers who help us improve the product when they wish to be credited.

For general product support (not security), visit our support page or Discord.