Privacy Policy.

• 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.

Clerk stores auth data and private metadata. Vercel hosts the web app. Your selected sandbox provider—Daytona, E2B, Sprites, or Vercel—hosts your Worker compute and workspace files. 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 all agent state -- runtime data, app data, skills, sessions, crons, and config. /home/machine/agent-machines stores the git checkout used for reloads.

• Authenticate you and send 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.

Agent Machines does not sell personal data. Data is shared with service providers only as needed to run the product, host machines, authenticate users, send requests, or run 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.

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.

• Delete artifacts and files from the machine when you no longer need them.
• Remove saved provider and model credentials in Settings when you stop using them. This removes your account’s saved copy, not deployment-provided defaults or copies already installed in Workers or profiles. It does not revoke the vendor key or stop sandboxes; revoke keys separately with the vendor when needed.
• Destroy provider machines when you want their disks removed by that provider.
• Open a GitHub issue for account-level deletion requests.

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.

Questions or corrections should go through the GitHub repository.