Privacy policy

Who this applies to

agmux is a macOS app for AI coding agents (Claude, Codex, Kimi, OpenCode, Grok, Cursor, on-device MLX, and related tools). This policy covers:

• The marketing site at agmux.dev
• The desktop app and its optional cloud features
• Phone remote at agmux.dev/remote and the remote relay
• Teams at teams.agmux.dev
• The optional beta program at agmux.dev/beta

When we say "we" or "agmux," we mean the people who operate these services. The desktop app is free to download. You do not need an agmux account for normal local use.

The short version

• Chats, code, and terminal history stay on your Mac for ordinary desktop use. Providers you connect (Anthropic, OpenAI, xAI, and others) have their own policies for what you send them.
• Remote moves session traffic between your Mac and your phone through our relay so you can control agents away from the desk. We store pairing and device credentials. We do not keep a permanent archive of your chat transcripts on the relay.
• Teams only uploads hourly usage counters and short labels if you opt in and join a team. It does not upload prompts, replies, diffs, or file contents. The full list is on the Teams disclosure page.
• We don't sell personal information and we don't run ads against your product data.

Desktop app (local by default)

The app stores project memory, thread state, settings, and related data under your user account on the Mac (for example under ~/.xanom/). Session logs for third-party agents often live in those tools' own folders (Claude, Codex, Grok, and so on). That data is on your disk. We don't receive it unless you turn on a feature that sends something specifically described below.

When you use cloud models, prompts and tool traffic go to that provider under their terms — not to agmux as a middleman that trains on your code. On-device MLX models run on your machine.

Auto-update checks may contact GitHub and, when a beta token is turned on, agmux.dev to see if a newer release exists. That is a normal update check, not a content upload.

Beta program

Applying at agmux.dev/beta is optional. We collect the email, name, and optional note you submit. If we approve you, we email a short-lived sign-in link and store a hash of a tester token (not the token itself, except briefly so we can show it to you once). Session cookies keep you signed in on the site. You can sign out or we can revoke access. Beta builds may be unstable.

Website (agmux.dev)

Visiting the site can generate ordinary web logs: IP address, user agent, pages requested, and roughly when. Hosting and CDN infrastructure (for example Cloudflare and the platform that deploys this site) may process those logs to keep the site up and block abuse.

If analytics are enabled for the site, we may use Google Analytics and/or Cloudflare Web Analytics to see aggregate traffic (which pages get hits, rough geography, referrers). Cloudflare Web Analytics is designed to be privacy-oriented; Google Analytics may use cookies or similar identifiers depending on configuration and your browser settings. You can block analytics scripts with browser tools or extensions. There are no ads on the site.

Download links point at public GitHub release assets. Clicking download goes to GitHub, which has its own privacy policy.

Phone remote

Remote is optional. You turn it on in the desktop app, pair a phone with a short code (or QR link) at agmux.dev/remote, and control sessions on your Mac from that phone.

What we store on the remote relay: device identifiers, pairing state, hashed phone tokens (and short prefixes so you can recognize devices in settings), optional device/Mac names, and similar connection metadata. Phone tokens expire; you can revoke a phone or all phones from the Mac. Turning remote off disconnects paired phones.

What passes through the relay: WebSocket messages needed to list sessions, stream conversation/terminal views, send messages, stop runs, and approve or deny tools. That traffic exists so your phone can control your Mac. The relay is built to fan messages between your paired devices; it is not a product feature for long-term chat storage. If both sides are online, content can be in memory or transit on the path between them. Treat remote like remote access: only pair phones you control, and revoke anything you don't recognize.

Remote does not require a separate agmux "user account." Pairing is the authentication model.

Teams (teams.agmux.dev)

Teams is a separate, optional product for org-level usage analytics. You choose to link a device, sign in, and join a team. Nothing about Teams runs until you opt in.

Account data. Sign-in uses GitHub or Google OAuth with basic profile scopes (identity, email, display name, avatar URL). We store enough to run membership, roles (owner / manager / employee), invites, and the dashboard. Device credentials for Teams live on your Mac under the app's Teams storage path.

Telemetry. The desktop uploads hourly aggregates only: token totals, estimated cost, active agent time, session/turn/tool counts, tool kinds, failure counts where available, file-change counts (not the files), provider/model names, project basenames or an opaque hash, coarse work-hour patterns, approval wait counts, and similar counters. Optional GitHub org leaderboard features use PR counts and size tiers from repositories your team owner selects — not pull request bodies or code.

What Teams never collects: prompt text, agent replies, chat history, diffs, file contents, absolute paths, terminal output, secrets, keystrokes, screenshots, or live "watch someone code" streams. Those are not in the product.

The same shared / never lists appear in the desktop join flow and on Teams. For the live checklist, open teams.agmux.dev privacy / disclosure.

Team owners and managers can see scoped dashboards for their team (employees see their own stats). Budgets, alerts, exports, and an audit log of admin actions (membership, roles, invites, budgets, exports — not prompt content) may be stored so the product works.

Third-party services

Depending on which features you use, data may be processed by:

• Cloudflare — website/CDN, Web Analytics (if enabled), Workers for remote relay and Teams
• Google Analytics — site traffic (if enabled)
• GitHub — release downloads, update metadata, Teams sign-in and optional leaderboard org data
• Vercel — website hosting and private beta file storage
• Resend — beta application and sign-in emails
• Google — Teams sign-in when you choose Google
• AI providers you configure (Anthropic, OpenAI, xAI, OpenRouter, local servers, and others) — whatever you send them from the agents you run

Those companies process data under their own policies. agmux is not responsible for how a third-party model provider uses prompts you send it.

Cookies and similar tech

The marketing site may set cookies or use local storage if analytics or similar tools are enabled. Teams sessions use the auth mechanism needed to keep you signed in (cookies or equivalent session storage). The beta program uses httpOnly session cookies after a magic-link sign-in. Remote pairing stores tokens on the phone and Mac so you don't re-pair every visit. You can clear site data in your browser; for remote, revoke devices in the desktop app.

How long we keep things

• Local desktop data — until you delete it or uninstall; we don't control your disk
• Remote pairing — until tokens expire, you revoke a device, or you reset remote identity
• Teams accounts and metrics — while your team/account is active; leave a team or delete the account to stop new uploads and remove access as the product allows
• Server logs — retained only as long as needed for operations, security, and debugging, then rotated away

Your choices

• Don't turn on Remote or Teams if you don't want those cloud paths
• Revoke phones and disable remote from the Mac at any time
• Leave a team or unlink Teams from settings
• Block analytics on the marketing site with your browser
• Delete local app data by removing the app data directories on disk (and uninstalling if you want a clean break)

If you need a copy of account data we hold on Teams, or want an account deleted and can't finish it in the product UI, contact us through the channels below. We'll respond in a reasonable time.

Security

Traffic to our sites and Workers uses HTTPS/TLS. Remote tokens are stored hashed on the relay where designed that way; Teams device credentials are kept on the Mac with restricted file permissions. No setup is perfect. If you find a vulnerability, report it privately via a GitHub security advisory or issue on the releases repository rather than posting exploit details in public.

Children

agmux is built for developers and teams. It is not directed at children under 13, and we don't knowingly collect personal information from them. If you think a child under 13 has given us personal data, contact us and we'll delete it.

International users

Services may be hosted in the United States or other regions where our providers operate. If you use the product from elsewhere, you understand that processing may happen outside your country, including places with different data-protection rules.

California and similar privacy laws

We do not sell personal information as that term is commonly used in California law, and we don't share it for cross-context behavioral advertising. Depending on your situation you may have rights to know, delete, or correct certain personal information we hold. Use the contact options below to make a request. We won't discriminate against you for exercising those rights.

Changes

If we change this policy, we'll update the date at the top. For material changes to how optional cloud features work, we'll try to surface a notice in the product or on the site when that's practical. Keep using the cloud features after a change means you accept the updated policy for those features.

Contact

Privacy questions and data requests: open an issue at github.com/neel-xanom/agmux-releases/issues. Teams-specific disclosure is at teams.agmux.dev/#/privacy. Related: Terms of service.