PRIVACY
effective May 8, 2026Privacy Policy.
This page explains what Agent Machines stores, where it lives, and which third-party services may process it. Tiny goblin footnote: the machine is durable, so delete what you do not want preserved.
data collected
- Account data from Clerk, such as user id, email, and session state.
- UserConfig data, including provider status, machine refs, active machine id, draft setup choices, and redacted public status.
- Provider credentials and gateway bearers stored in Clerk private metadata.
- Machine data stored under /home/machine, including chats, artifacts, agent runtime files, sessions, logs, skills, and crons.
where data lives
Clerk stores auth data and private metadata. Vercel hosts the web app. Dedalus hosts live provider machines today. Cloudflare may carry preview tunnel traffic. Cursor processes delegated code tasks only when you configure CURSOR_API_KEY and call cursor-bridge.
Inside the machine, ~/.agent-machines stores product data. ~/.hermes stores Hermes runtime data. /home/machine/hermes-machines stores the git checkout used for reloads.
how data is used
- Authenticate you and route you to your dashboard.
- Provision, wake, sleep, inspect, and select machines.
- Proxy chat requests without exposing gateway bearers to browser JavaScript.
- Display artifacts, sessions, logs, skills, MCP tools, and machine status back to you.
sharing
Agent Machines does not sell personal data. Data is shared with service providers only as needed to run the product, host machines, authenticate users, route requests, or execute tools you invoke.
Model providers and tool providers may receive prompts, files, screenshots, or metadata when your agent calls them. Their terms and policies apply.
retention
Clerk metadata remains until removed or your account is deleted. Machine data remains on the selected provider machine until you delete files, archive the machine, or destroy the machine.
control
- Delete artifacts and files from the machine when you no longer need them.
- Remove provider keys from setup when you stop using a provider.
- Destroy provider machines when you want their disks removed by that provider.
- Open a GitHub issue for account-level deletion requests.
security
The dashboard keeps provider credentials server-side. Gateway bearers are proxied by API routes and are not shipped as NEXT_PUBLIC values. No system is perfect; do not store secrets on a machine unless the selected provider is acceptable for that use.
contact
Questions or corrections should go through the GitHub repository.