Security
How Eaon Desktop protects your work.
Eaon Desktop runs on your computer with your own AI provider keys. This page lists what it does to protect your data today, for security reviewers and IT teams. The deployment guide has the details.
Your data
Your data stays with you.
Bring your own key
Prompts and responses go directly from your computer to the AI providers you choose. They don’t pass through Eaon’s servers.
No telemetry
Eaon has no telemetry or analytics. Crash reports stay on your device and are never uploaded.
Open source
The code is public on GitHub under the GPL-3.0 license, so anyone can inspect it.
On the device
Protected on your computer.
Keys in the system keychain
API keys are encrypted with the operating system’s keychain: the macOS Keychain, Windows DPAPI, or libsecret on Linux.
Private app data
Eaon’s app data is readable only by your user account.
A sandboxed interface
The app’s interface runs in Chromium’s sandbox, isolated from the rest of the system.
Signed and notarized on macOS
macOS builds are signed with an Apple Developer ID, notarized by Apple, and use the hardened runtime.
AI agents
Agents that ask first.
Approval by default
Agents ask before making changes. Irreversible actions, such as real-money trades or destructive operations, always wait for your approval, whatever the approval mode.
Credentials are off limits
Agents’ file tools refuse credential stores, such as SSH keys, cloud credentials and password keychains, and Eaon’s own data. A command that names one always asks you first.
No redirects into your network
When an agent fetches a web page, the page can’t redirect it into your local network or to cloud metadata services.
For IT and security teams
Manage it across your organization.
A managed policy
Deploy a policy through MDM (Jamf, Kandji, Intune) or GPO. It can turn features off, cap how much autonomy agents get, limit which AI providers people can use, and restrict which MCP servers can run. Users can see the policy in Eaon’s settings. Deployed where only administrators can write, it can’t be changed by users.
A tamper-evident audit log
Every record is hash-chained, so an edited or deleted record is detected. The log covers key changes, failed authentication, policy and setting changes, and agent actions. It never contains API keys or message text, and you can forward it to your SIEM, such as Splunk, Elastic or Datadog.
Built to support your SOC 2 program
The deployment guide maps Eaon’s controls to the AICPA Trust Services Criteria, with the evidence each one produces.
Responsible disclosure
Found a vulnerability?
Please report it privately through GitHub Security Advisories rather than in a public issue.
Roadmap
What we’re working on.
These are plans, and none of them has a date yet.
- SOC 2 Type II auditPlanned
- Code signing for Windows buildsPlanned
- Encrypted connections for Remote devicesPlanned