Privacy Policy

Last updated: November 6, 2026

Overview

Codync is an independent open-source project by leepokai ("we", "us"). It lets you message the AI agents that run on your own computer. It is built so that your files, conversations and credentials stay on your devices.

What stays on your devices

  • Bots and conversations are stored by the Codync host on your computer (in ~/.codync). Your phone keeps a cache so the app opens instantly.
  • Your phone talks to your computer directly over your local network or Tailscale, or, away from home, through our relay, which only forwards end-to-end encrypted data it can't read. A message you send while your computer is offline waits in the relay, still encrypted for your computer, for up to 24 hours, and is deleted once delivered. If you point a computer at a relay you run yourself, its traffic goes through that relay instead of ours and we receive none of it; its notifications still go through our push relay.
  • Agents run with your own logins (Claude Code, Codex, Cursor and others). Codync never sees or stores their credentials.
  • Usage limits are read on your computer, only for the agents your bots run and the ones you turn on. Your phone gets the limits as percentages, plus any balance or credits an agent reports as text.

Push notifications

To notify you when a bot needs you or finishes, your computer sends a short alert (the bot's name and a one-line preview) through our push relay, a Cloudflare Worker that forwards it to Apple Push Notification service (iPhone) or Firebase Cloud Messaging (Android). The alert is encrypted for your phone, so the relay and those services carry only generic text, and the relay does not store notifications. Your device token is encrypted into a ticket that only the relay can read; your computer never sees the raw token.

Routine webhooks

A routine can start when another service sends it a webhook at its public address on our relay. These deliveries are not end-to-end encrypted: the relay receives them over HTTPS, can read their content, and keeps each one until your computer collects it, for up to 72 hours. It also stores the routine's key to check signatures. With “Reach from anywhere” off, deliveries no longer reach your computer, but the relay still accepts them at the old public address and keeps them, readable, for up to 72 hours; they run if you turn it back on within that time. To stop them, remove the address from the sender, or delete the routine or replace its key while “Reach from anywhere” is on.

Cloud assistants

If you turn cloud assistants on at a computer and add the Codync connector to ChatGPT, Claude or another assistant, that assistant's requests to your bots and the bots' replies are not end-to-end encrypted: they pass through our relay over HTTPS, which can read them but doesn't store them, and the assistant's provider sees them as part of your conversation there, under its own privacy policy. Cloud assistants are off on every computer until you turn them on at that computer, and the relay passes on only requests from your own Codync account.

Codync account

You can sign in to the Codync apps with Apple, Google or GitHub, so your phones can find your computers and reach them through our relay. You can also use them without an account, over Wi-Fi or Tailscale only; a computer in no account then advertises its computer ID and private network addresses on your local network, so your phones can find it there. Your account keeps your email address, an account ID, and the names of the phones and computers you connect with it. You can delete it at any time: see Delete your Codync account below.

Data we collect

Usage analytics; the registration of each computer that uses our relay (its name, platform, device type, Codync version, public keys and when it was last online), with the public keys of the devices allowed to use it; and the account data described under Codync account. Analytics are on by default (the Windows installer asks first); turn them off on each phone and each computer in Settings (Share usage analytics), and that device stops sending right away.

  • What we record: which features you use, such as opening the app and its screens, setting up and pairing a device (and whether you allow notifications), creating or deleting a bot, sending a message (with the number of attachments, not the files), starting a routine or a voice call, and installing a connector from the catalog. Each event carries the app version, the platform and the agent and model a bot uses.
  • On codync.dev: page views, how long a page stays open and how far it's scrolled, how fast it loads, and clicks on download and outbound links, counted without cookies; counting them stores nothing on your device.
  • Crash and error reports: when an app crashes or hits an unexpected error, or an agent fails to answer, we record what kind of error it was and where in Codync's own code it happened (type, function names and line numbers). The error's message is never sent, and file paths are cut down to Codync's own files.
  • What we never record: your messages, prompts, code, files, file names or paths, bot names, credentials or anything your agents produce. We don't store your IP address: it is only used to look up your approximate location (country and city), which is kept with the events.
  • Who it's linked to: your Codync account when you're signed in; otherwise a random ID created on that device.
  • Why: to spot bugs sooner and serve you better, by seeing which features work and where people get stuck. It is never sold, never shared for advertising and never used to track you across other apps or websites.

Codync has no advertising identifiers.

Third-party services

  • Apple Push Notification service: delivers notifications and Live Activity updates on iPhone.
  • Google Firebase Cloud Messaging: delivers notifications and live updates on Android.
  • Cloudflare Workers: runs the push relay (nothing stored), the relay between your phone and your computer (computer registrations, messages waiting for an offline computer, webhook deliveries) and the Codync account service; its TURN service forwards a remote screen session's encrypted video when there's no direct path.
  • Clerk: runs sign-in for the Codync account, including the sign-in an assistant you connect to Codync uses.
  • n0 (iroh public relays): only if you connect your computers with codync-network using the default connector. When two of your computers can't connect directly, their encrypted traffic goes through iroh's public relays, and they find each other through n0's address lookup; these see the computers' IP addresses and connection metadata, not what they say. With your own relay or the private connector, none of it reaches n0.
  • PostHog (US): stores the usage analytics described above, unless you turned them off.
  • Vercel: hosts codync.dev and forwards the site's analytics to PostHog.
  • The AI agents you choose: they run on your computer under their own terms and privacy policies.
  • OpenAI or Google (optional, voice): only if you add your own OpenAI or Gemini API key for calls or dictation. In a realtime call, your voice goes from your phone or computer directly to that provider, together with the bot's name and description and the chat messages it asks for during the call. In a call's speech mode, and when you dictate a message with the provider, your recording goes to your computer, which sends it to the provider to be transcribed, together with the names of the bots on that computer as spelling hints, and sends the bot's replies to the provider to be read aloud. All of it is under your account and the provider's privacy policy. The key is stored encrypted on your computer and sent only to that provider, never to our relay or services; a realtime call gets a short-lived credential made from it. Without a key, voice uses your device's own speech recognition.

This policy covers Codync as we publish it. Codync services run by third parties (for example a hosted host or relay) handle your data under their own privacy policies; we don't operate them and receive none of that data.

Data retention

Your bots and conversations live on your devices. Our services keep only these: your account; each computer's registration, the devices allowed to use it and its routines' webhook keys, while the computer is registered; a log of account and access changes (30 days); messages waiting for an offline computer (up to 24 hours); and webhook deliveries waiting for it (up to 72 hours). Delete a bot to remove its conversation; uninstall the host and delete ~/.codync to remove all of it. Deleting the phone app removes its cache. Turning analytics off stops new events from being sent.

Delete your Codync account

Delete it in the app: on iPhone and Android, tap the account button on the Bots tab, then Delete account; in the desktop app, open the account menu and choose Delete account. Without the app, email kevin@codync.dev from the address you sign in with, with the subject “Delete my Codync account”: we delete it, and the usage analytics linked to it, within 30 days and reply when it's done. The steps are also on Delete your account.

  • Deleted: your sign-in and email address, your account's list of computers, and every device's access through the account.
  • Kept: a record that the account was deleted, with the revoked devices' names and keys, so those devices can't be used with it again; the log of account and access changes (30 days); and, when you delete it in the app, the usage analytics linked to it, until you email us to delete them too. Bots and conversations stay on your computer until you delete them there (see Data retention).

Children's privacy

Codync is not directed at children under the age of 13.

Changes

We may update this policy. Changes will be posted on this page with a new date.

Contact

Questions? Email kevin@codync.dev or open an issue at github.com/leepokai/Codync/issues.