AION

Security

Access checks on the server, a tool policy for agents and a history of every run — by default on every plan.

Access is checked on the server

Every request is tied to an authenticated user. Project data is isolated by membership, and hiding an element in the interface is never treated as a security boundary.

Control over agents

A tool policy separates reading, writing and privileged actions. Sensitive steps wait for a server-issued approval from an authorized person, and each run keeps its events and results.

Secrets

Provider keys and connection tokens stay on the server and are not sent to the browser. The desktop app keeps device and MCP credentials in the operating system's protected storage and refuses to save them if that protection is unavailable.

Desktop runtime

Local models get only the prompt you send. Folder grants select approved working directories. The app does not upload diagnostic reports automatically and checks for updates only when you ask.

Reporting a vulnerability

If you find a security issue, email our support team with the details and steps to reproduce. Please do not publish it before we have had a chance to fix it.

Updated 24 October 2026