Security & privacy
What leaves your machine
AWO runs on your computer and talks to whatever you point it at. This page lists every case where something leaves, because "we take privacy seriously" is not a claim anybody can check.
What AWO sends
The calls in your workflow
A step that asks a model sends your prompt to the model you chose. A step that posts to Discord sends the message to Discord. That is the workflow doing its job, and it is the only network traffic AWO originates.
your machine→the endpoint you configured
Nothing else. Ever.
No telemetry, no usage counts, no crash reports, no check-in on startup. Not for licensing either — see below. If you unplug the network, AWO keeps working apart from the steps that need the internet by definition.
your machine→nowhere
The licence never phones home
A key is a signed statement, not a lookup. AWO carries only a public key, which can verify a licence and cannot mint one — so checking your licence is arithmetic on your own machine, not a request to a server.
Why it is built that way: a licence check that phones home fails on a plane, behind a corporate proxy, and on the day the licence server has an outage. Each of those punishes a paying customer for something that is not their fault.
If a subscription lapses, AWO keeps running at the paid tier for 14 days and says so on screen, rather than stopping mid-workflow at midnight.
Dangerous things are off until you turn them on
Four capabilities can affect your machine rather than just read from it. Each needs a separate, explicit opt-in, and a workflow file can never enable one on its own — otherwise a workflow shared with you could turn them on.
Shell commands
Off by default, and allow-listed by command when on.
Filesystem access
Off by default. Scoped to directories you name.
Git writes
Off by default. Branch and push are separate permissions.
Code-writing agents
Off by default. Runs in a sandbox and opens a pull request rather than pushing to your default branch.
Your secrets stay secrets
- Bot tokens, API keys and webhook URLs are read from your environment, not stored in the workflow file — so a workflow can be committed to a repository or sent to a colleague without carrying credentials.
- Workflows are plain YAML on your disk. You can read them, diff them and keep them in version control.
- Run history is stored locally. Nothing about a run is uploaded.
This website
The site holds itself to the same standard as the product, because a privacy page served by a tracking script would be self-refuting.
- No third-party scripts. No analytics vendor, no ad network, no font CDN — the fonts are served from this domain.
- No IP addresses stored. Visits are counted through a hash of address, browser and date, salted with a server secret. It cannot be reversed, and yesterday's value for the same person is a different value.
- No account needed to download or run AWO. An account exists only so you can read back a licence key you bought.
Check it yourself
Run it with the network watched. The only requests are the ones your workflow makes.