Data Usage.
Local-first by default — and honest about the rest. Your work stays on your machine; you control what leaves and when.
Last Updated · 24 July 2026
The Principle
AIEOS is built local-first. Your work lives on your machine, and AIEOS only reaches out to another service when a workflow you configured tells it to. We do not claim “nothing ever leaves your computer” — that would be untrue, because AIEOS is designed to work with GitHub, your model providers, LLM Vault and other integrations. The honest promise is different: you control what leaves, and it is never silent.
Local-First Storage
Your projects, evidence and the decision journal are stored on your own machine (under ~/.aieos) — not in our cloud. AIEOS does not require uploading your codebase to us to function.
Credentials Are Never Seen
The official provider CLIs own their own sign-in. API keys are actively stripped from the execution path, so work runs on your subscriptions and accounts. AIEOS is not a place you paste secrets for us to hold.
On-Device Voice
Speech-to-text and text-to-speech run on your device. Your voice is captured and transcribed locally — it is not shipped to a cloud voice service to make the feature work.
Governed Integrations — What Does Leave
When you connect an integration, data moves to that service because you enabled it:
- GitHub — reading and writing to the repositories you point AIEOS at.
- Your AI model providers — the prompts and context a task needs to run go to the provider you configured, on your account.
- LLM Vault — where you route work through it for capacity or key management.
Every one of these calls is deliberate and recorded — initiated by a workflow you set up, not a silent background transfer. Disabling an integration stops its data flow.
What The Advisor Layer Works With
The advisor “C-Suite” is designed to coordinate work from structured summaries, labels and status rather than raw file contents. You control the context routed to it. It is a coordination layer over your work, not a copy of it sent elsewhere.
Telemetry
As a controlled-pilot build, AIEOS keeps operational diagnostics minimal and does not sell data. Any figures shown on this website (for example, example test counts or chain numbers) are illustrative of how the product works, not readings from your machine.
Your Control
You decide which integrations to enable, which providers to use, and which context to route. Turning an integration off ends the flows it enabled.