Privacy

Codync keeps your work on your computer. The phone and desktop apps are windows onto the host running there. This page lists what stays on your devices, what passes through Codync's services and what they can see, and the usage analytics Codync collects. The Privacy Policy is the formal statement.

What stays on your computer

  • Bots, conversations, routines and memory are kept by the host in ~/.codync on your computer. Your phone keeps a cache so the app opens quickly.
  • Agents run with their own logins. Claude Code, Codex and the other agents use the sign-ins you set up on the computer. Your prompts go from the agent to its provider, as they would without Codync.
  • Secrets are encrypted. Connector credentials, voice API keys and other keys you enter in Codync are stored encrypted on the computer. The encryption key is held by the system's credential store (Keychain on macOS, Secret Service on Linux, Credential Manager on Windows). They're never sent to Codync's cloud. Codync Cloud computers work differently: see Codync Cloud below.
  • Usage limits are read on your computer, and only for the agents your bots run and the ones you turn on in the Usage screen. An agent you don't use is never started, and its saved sign-in is never read. Claude Code uses its usage command and status line, and the Codex CLI a read-only current-account query; each account you added to either as a login profile is read the same way. oh-my-pi, Amp, Hermes Agent, Auggie, Kilo, Kiro, Kimi, OpenCode, Mistral Vibe and Junie report through their own command, a local database or an IDE file. GitHub Copilot (account.getQuota), Grok Build (x.ai/billing) and Antigravity (/usage, or its running app) are read by starting the agent's own server on your computer, which asks its provider with the agent's login; the host never handles that login. None of these starts a conversation or model turn. Cursor is the exception. It has no such report, so the host reads the sign-in Cursor saved and asks Cursor's dashboard service for unified-plan usage, or cursor.com for a legacy-plan summary. That token is not logged, and Codync does not call any other provider's API with an agent's login. To read Claude Code's limits, codync-host install routes its status line through codync-host statusline; a status line you already had keeps working and is restored when you uninstall.

Codync Cloud

If you start a cloud computer, your bots, conversations, agent sign-ins and code live on a machine in your own account with the provider (Boat or InstaBox), not on your computer.

  • Your provider key is kept by Codync's account service, encrypted, and shown back only by its last four characters. The service opens it to create your cloud computers, put them to sleep, wake them, back them up and delete them. A Boat key reaches only its codync environment; an InstaBox key reaches every machine in its workspace and can run commands on them.
  • The cloud computer's vault key, which unlocks the secrets you save there, is kept by the same service, encrypted. With the access above, whoever controls that service could open those secrets.
  • The provider runs the hardware and can in principle read a running machine's memory and files. Boat documents no encryption at rest, and its snapshots may be stored outside the EU.
  • Your apps still reach the cloud computer end to end encrypted, through the relay.

The relay

When your phone isn't on the same network as your computer, the connection goes through the Codync relay on Cloudflare. Everything inside it is end-to-end encrypted between your phone and your computer. See Remote access for how that works and how to turn the relay off.

If you point a computer at a relay you run yourself, that relay takes the Codync relay's place for it: whoever runs that server sees what's listed below, and Codync's relay sees none of it. It can't read the encrypted connection either. Sign-in, public routine webhooks and remote screen through the relay aren't available there, and push notifications still go through Codync's push service.

The relay can't read your messages, files, bot output, approvals, terminals or anything else you send through the encrypted connection.

The relay does see:

  • that your computer is registered, with its name, platform, device type, Codync version and public keys;
  • when your computer and your devices connect, how often, and how much data passes;
  • messages you send from the iPhone while the computer is offline, which wait there, encrypted, for up to 24 hours until the computer picks them up;
  • your account's email address, the names and platforms of your signed-in devices, and which of them may use which computer. Sign-in itself is handled by Clerk, the sign-in service Codync uses. You can delete your account in the apps; see Deleting your account.

The relay can't add a device to your computer. A new device needs either a pairing code shown on the computer or your approval there. The one exception is the setting Skip the 6-digit check, which lets any device signed in to your account in without that check.

Public routine webhooks are the exception to end-to-end encryption. A service that calls a routine's public URL sends its data to the relay over HTTPS. The relay can read it and keeps the routine's key to check signatures. If you don't want that, use the routine's local URL instead.

Cloud assistants are the other exception. If you turn them on at a computer and add the Codync connector to ChatGPT, Claude or another assistant, the assistant's requests to your bots and the bots' replies pass through the relay over HTTPS, and the relay can read them (it doesn't store them). They're off until you turn them on at the computer, and the relay passes on only requests from your own account. See Cloud assistants.

Remote screen sessions are encrypted between your phone or desktop app and the computer you're viewing. When there's no direct path, the video goes through a Cloudflare relay that can't see what's on your screen. The desktop app uses that relay only for computers in your account (a cloud computer, for one); a computer it reaches over SSH always connects directly.

Local network advertising. A computer in no account has no relay to tell a phone its new address, so it advertises its computer ID and private network addresses on the local network over mDNS. Anyone on that network can read them; Tailscale names and addresses are left out, and nothing is advertised once the computer is in an account. They go nowhere beyond the network.

codync-network, your computers' network (bots on your other computers) doesn't use the Codync relay. Your computers connect to each other directly, encrypted end to end. When two can't, the default connector sends their encrypted traffic through iroh's public relays, run by n0, and they find each other through n0's address lookup; these see your computers' IP addresses and when they connect, not what they say. With your own iroh-relay or the private connector, nothing reaches n0.

Push notifications

On the iPhone, a bot can notify you when it needs you, when it's done, or when it failed. Your computer encrypts each notification's text (the bot's name and a short preview) to a key that only your iPhone holds. Codync's push service, a separate Cloudflare Worker, forwards it to Apple's push service with only a generic text such as "Your task is complete. Open Codync to read the result." Your iPhone decrypts the real text on the device. If it can't (for example before you first unlock the phone after a restart), you see the generic text.

  • The push service and Apple see the generic text, the encrypted text, and identifiers that say which computer and bot the alert is for (not their names).
  • Your phone's push token is wrapped in a ticket that only the push service can open. Your computer never sees the raw token. The push service doesn't store notifications.
  • Live Activities on the Lock Screen and in the Dynamic Island get only the bot's status from the computer, never message text.
  • No notification is sent while the iPhone app is connected to the computer. Muted and hidden bots don't notify.

To turn notifications off on an iPhone, tap the connection status at the top of the Bots tab (such as 1 connected), choose Manage computers, and turn off Push notifications on that computer. Each bot's settings have their own notification options.

Voice

What leaves your device in a voice call or during dictation depends on the engine you pick. Details: Voice.

EngineWhere your voice goes
On device (the default)Recognized on your iPhone or Mac with Apple speech, or on your Android phone. Apple's servers may be used when on-device recognition isn't available for your language. On Android, dictation uses the phone's speech service when the phone can't recognize your language itself, and that service may use its provider's servers (Google's on most phones). Only the recognized text goes to your computer, as an ordinary message.
OpenAI or Gemini, Realtime modeStraight from your device to the provider. Your computer gives the device a short-lived credential made from your key. Before the call, the provider also gets the background your computer writes for the voice: the date and time, what your bots remember about you (shared memory and the names of its notes), this bot's settings, routines and memory, the project's git branch, changed files and recent commits, what the bot is working on, the recent messages and calls in the chat, your other bots, and the names of files shared in the chat. When a call reconnects or you switch engine mid-call, it also gets what was said on the call so far. During the call it gets the messages and results the voice reads. Your computer keeps the call's written transcript, in the chat.
OpenAI or Gemini, Speech mode, and dictation with a providerYour recording goes to your computer over the encrypted connection, and your computer sends it to the provider with your key and the names of the bots on the computer as spelling hints. The provider's spoken replies come back the same way. If you set a server of your own for the OpenAI engine, your computer sends them to that server instead of OpenAI.

Your provider key stays on your computer, encrypted. It's never sent to the relay or Codync's cloud. Calls with your own key run under your provider account and its privacy policy.

Usage analytics

Codync records which features you use, to spot bugs sooner and see where people get stuck. Analytics are on by default. The Windows installer asks first; nothing else does. They go to PostHog (US).

What's recorded: opening the app and its screens, setting up and pairing (and whether you allow notifications), creating or deleting a bot, sending a message (with the number of attachments, never the files), running a routine or a voice call, and installing a connector. Each event carries the app version, the platform, and the agent and model the bot uses.

Crashes and errors: the kind of error and where in Codync's own code it happened. Never the error's message; file paths are cut down to Codync's own files.

Never recorded: your messages, prompts, code, files, file names or paths, bot names, credentials, or anything your agents produce.

Location: your IP address is used to look up an approximate location (country and city). The IP address itself isn't stored.

Who it's linked to: your Codync account when you're signed in; otherwise a random ID made on that device.

Codync Cloud computers: Codync's cloud also records when it wakes one of your Codync Cloud computers, why (a device connected, a message, an access request or a routine), and how long until it was back. This is linked to your account, carries no location, and is sent only while that computer's own switch is on.

Analytics are never sold, never used for ads and never used to track you across other apps and websites. The website, codync.dev, counts page views, time on page, scrolling, load speed, and clicks on download and outbound links, without cookies. Vercel, which hosts the site, forwards these counts to PostHog.

Turning analytics off

Each phone and each computer has its own switch, Share usage analytics. Turning it off stops sending right away and drops anything not sent yet.

  • iPhone: the Settings tab, Share usage analytics.
  • Desktop app: Settings → General, under Privacy. This switch belongs to the computer's host, so it also covers the terminal UI on that computer.
  • Terminal UI: press ^k and choose Share usage analytics.
  • Windows installer: it asks whether to share usage analytics from the computer (not when Codync updates itself). No turns off the same switch the desktop app shows.
  • Command line: codync-host analytics off (on turns it back on).

The info button next to the switch (About usage analytics… in the terminal UI) lists the same details. What you do from the phone on a computer, such as sending a message, is recorded by that computer. To stop all of it, turn the switch off on both.

Removing your data

Delete a bot to remove its conversation. To remove everything from a computer, see "Uninstalling" in Updates. On the iPhone, Start over on the Settings tab signs out and forgets every computer; your computers keep their bots and chats. Deleting the iPhone app removes its cache.

Rating invitations

Codync may invite you to rate it when you've sent your fifth message from your iPhone or Android phone. It does not ask when you open the app, and voice calls don't count. Invitations are at least 120 days apart, with at most two requests in a year. Apple (on Android, Google Play) decides whether to show its rating window. You can also choose Rate on the App Store (on Android, Rate on Google Play) on the Settings tab at any time. Report an issue opens a separate feedback link, regardless of whether you choose to rate the app.

The timing history stays on your phone. If Share usage analytics is on, Codync records requests and taps on the rating link, with the number of messages sent. It does not send conversation content or know whether you rated it.