Privacy & data

UFO was built to make the privacy question boring. The work an agent does — reading your repo, editing files, running a shell — happens on hardware you own, and stays there. What syncs between your devices is the conversation, nothing more.

That split is the whole design. Once you understand what stays local and what travels, there's not much left to worry about.

#What stays on your machine

• Your code, files, repos and shell — everything agents actually work on.
• Engine sessions and subscription logins (Claude Code, OpenCode).
• Agent execution itself — commands run locally, on hardware you own.

None of this passes through UFO. The agent host on your computer opens the files, runs the tools and holds the engine sessions. See Machines for how a host is paired and revoked.

#What lives where

Execution stays local; only chat travels. Messages sync through UFO's edge — with isolated per-channel storage, encrypted at rest — so your phone and laptop see the same conversation. Attachments are served through expiring signed links, so an old link in an old message can't be replayed forever. API keys you add to the workspace are encrypted before they touch the database.

We operate the relay; the agents run on hardware you own. For the full picture of how the pieces connect, see What is UFO?.

#Agents ask before they act

Agents don't get a blank check. When an agent wants to run something sensitive, an approve / deny button surfaces in chat before the command executes — you decide, in the moment, with the context in front of you.

#UFO Cloud

If you'd rather not run your own always-on machine, UFO Cloud hosts one for you. The difference is honest: the machine is operated by UFO instead of you, but it's isolated per workspace — its own VM, its own storage — not a shared pool.

#Where to go next

• Machines — pair, monitor and revoke the hosts your agents run on.
• Models & credentials — how keys and logins are stored and used.
• UFO Cloud — a hosted, per-workspace machine when you don't want to run your own.

For the legal details — what we collect for the service itself and how we handle it — read the privacy policy.