How Aiola handles security and your data

Aiola reports provider and server failures automatically to help find bugs. You do not need to report each failed turn manually. Reports are anonymous, redacted, and grouped by provider and error type.

You can disable desktop reporting under Settings → General → Privacy. This setting is separate from the App Logs integration in a product you ship.

A coding CLI may stop responding during a thread. Grouped failure reports help Aiola find repeated provider problems. You can inspect the thread error and choose whether to retry.

App Logs receives errors from your own application through its SDK or HTTP endpoint. It needs Pro or an active trial. Review its event payload and integration settings separately.

Other services handle model-provider requests, accounts, billing, and optional phone notifications. The data boundaries below explain what each service receives.

Aiola is one desktop app for macOS and Windows. Coding agents work next to the problems they fix. Review Analytics, App Logs, Feedback, GitHub, and Tasks beside those agents.

Use Notebook for Plan, Notes, and Todo, plus Automations, Terminals, Agents, Skills & MCP, and Central. The phone companion is on the iPhone App Store and Android Google Play.

Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity run on your machine. You use your own provider subscriptions, with no token markup.

This page explains disk access, installers, updates, and data sent from your computer. We list only certifications we have earned and protections the app has today.

This is our reference for security questions. The same facts appear in our data ownership page, docs, and summaries for agents. If the app behaves differently, please email us so we can correct it.

Download Aiola from GitHub Releases through our download page. Each platform build is packaged and signed before release.

macOS. Aiola ships a universal disk image, with separate Apple Silicon and Intel builds. Builds use Apple’s hardened runtime and pass Apple’s notarization process before release. Apple scans the binary for known malware signatures. A stapled notarization ticket lets Gatekeeper check it on first open. You may need to confirm opening the app after downloading it from the web. This is normal for developer-signed apps outside the Mac App Store.

Windows. The Windows installer is an NSIS package (.exe) signed with a code-signing certificate. Signing identifies the publisher and helps SmartScreen build trust over time. A fresh Windows machine may show an “unrecognized app” prompt until the certificate has enough installs. See our install guide for the steps.

GitHub release files show download URLs, version history, and checksums. The in-app updater uses the same release channel.

The desktop app uses electron-updater to check GitHub Releases for new versions. It downloads updates in the background and asks you to restart when ready. It checks again about every six hours, including when the app stays open.

macOS. Updates pass the same notarization process as first installs. Hardened runtime permissions stay the same unless release notes explain a change.

Windows. Updates use signed NSIS installers from the same GitHub Releases channel. You can also install from the download page whenever you choose.

Aiola registers the aiola:// deep-link protocol. Checkout and setup can return you to the desktop app after browser steps. Use our official download links or the in-app updater.

Your code and repos stay on your machine. Agent prompts and file context go only to your chosen AI provider.

Use your own subscription with Anthropic (Claude Code), OpenAI (Codex), Cursor, xAI (Grok CLI), or Google (Antigravity). OpenCode uses whichever provider you choose. Aiola never proxies, stores, or resells your code or model traffic.

Threads, tasks, notes, and automations stay local, in SQLite and plain files in your repo. Automations run while your desktop is on.

Optional Analytics, App Logs, and Feedback from shipped products use Aiola’s cloud, through Supabase and Tinybird. These hosted features need Pro or an active trial. Hosted MCP and Setup Health also need Pro or an active trial.

Aiola uses account and billing services. Redacted diagnostic reports help find failures. You can disable desktop diagnostic reporting in Privacy settings.

Optional phone notifications use Expo, APNs, or FCM. They can contain thread titles, reply previews, or approval details.

The local agent workspace works offline. Running agents needs provider access. GUI Lifetime keeps the local app opening even when Aiola’s servers are unreachable.

Read our own your data page for more detail. Local workspace data stays on disk; optional hosted product data passes through Aiola’s cloud.

On your machine: Aiola reads workspace settings, thread and task state, agent personas, and skills you define. Thread and task data use local SQLite and plain files. Aiola also reads Git metadata for projects you open and terminal output within the app. This data stays on disk unless you enable a connected feature.

With hosted features enabled: Aiola receives analytics events, error logs, and user feedback from your web apps. These come from the Aiola snippet or SDK you install. Supabase and Tinybird receive this data so you can query it in the desktop app. Hosted Analytics, App Logs, and Feedback need Pro or an active trial.

Outside that access: Aiola cannot read private repos you have not opened in a workspace. It cannot see provider conversations beyond local thread history. Your provider API keys and CLI session tokens stay in each vendor’s credential store. Aiola cannot see other applications outside the workspaces you attach.

Your AI providers: Providers receive prompts, file context, and tool output you send through your chosen coding agent. This applies to Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity. Your provider’s privacy policy applies. Aiola does not proxy or resell that traffic. Aiola does not read your repositories for training or resale.

Aiola accounts use Google OAuth or email one-time passcodes (OTP). There is no Aiola-specific password to leak. Sessions link to your subscription, trial, or GUI Lifetime license through Aiola’s central access service in Supabase. Sign-in supports licensing and account management.

Signing in to Aiola is separate from signing in to coding agents. Connect each CLI on your machine after opening the app. Examples include claude login, codex login, cursor-agent login, and grok agent --reauth. Credentials stay with the vendor’s tools; Aiola runs binaries you have already signed in to.

If you find a security flaw in Aiola, email [email protected] with:

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

Please give us time to review the issue and ship a fix before public disclosure. We aim to acknowledge reports within a few business days. We do not offer a paid bug bounty program. We credit researchers who help improve the app when they wish to be named.

For product help, visit our support page or email us.