Privacy policy
Last updated: 8 October 2026
This policy explains what information Cordbay handles, where it goes and what Cordbay (“we”, “us”) does with the little of it that reaches us. It covers the Cordbay desktop app, the cordbay command-line tool and the cordbay-tui terminal UI (together, “the app”), the website at cordbay.com, and the services behind it at api.cordbay.com and downloads.cordbay.com.
The short version
- The app keeps its data on your computer.
- Your skills and agents sync through a git repository that you own. We do not run a sync server, and your skills and agents are never sent to us.
- To activate a licence and check it about once a day, the app sends our licence service, Sealcord, the licence key and a few details about the computer: a random id, its name in Cordbay, its operating system and the app version.
- The desktop app asks downloads.cordbay.com whether there is a new version when it starts, every 6 hours while it runs, and when you ask it to.
- The app calls GitHub and skills.sh to find, install and update skills.
- The app sends content to TypeSafe AI only if you add your own Jev API key, and only for three things: the text of a skill, to score that skill; both versions of a file in a sync conflict, to suggest how to settle it, when you ask for a suggestion or turn conflict suggestions on; and the new version of a skill’s
SKILL.md, read from GitHub, before the desktop app installs that skill update by itself. - The app contains no analytics, advertising or tracking, and the website sets no cookies.
- Payments are taken by Polar, which sells Cordbay to you as merchant of record. We receive your email address and what you bought, never your card details.
- If you ask for launch news on cordbay.com, your email address is kept with our email provider, Resend, so we can send you one email when Cordbay launches. That email has an unsubscribe link.
Who is responsible
Cordbay is the controller of the personal data described in “What reaches us” below. Contact: support@cordbay.com.
Polar is the merchant of record for purchases (see “Buying a licence”) and handles the payment data it collects as a controller in its own right, under its privacy policy.
For everything the app stores on your own computer or sends to your own git repository, you are in control and we have no access.
What the app stores on your computer
| Data | Where | Purpose |
|---|---|---|
| Settings: the coding agents you manage, the URL and local folder of your sync repository, the folders you watch for git repositories, and desktop preferences such as whether to show notifications | config.toml in ~/.config/cordbay (on Windows, in your user config folder) |
To run the app as you set it up |
| Machine identity: a random id and a label, which starts as your computer’s hostname | machine.json in the same folder |
To tell your machines apart |
| Sync bookkeeping, and a record of the agent files the app wrote for each coding agent | applied.json, sync.lock and agent-files.json in the same folder |
To know what has been synced and written |
| The last results of the skill update check | skill-updates.json in the app’s state folder |
To show updates without asking GitHub again |
| Licence state: the licence key (which contains your email address), when the trial started, and the licence service’s last signed answer | licence.json in the config folder, readable only by your user |
To know whether the app is licensed, also while offline |
| A random id for this installation, made by the updater | The updater’s folder: ~/Library/Caches/velopack on macOS, /var/tmp/velopack on Linux |
Sent with update checks (see “Update checks”) |
| A clone of your sync repository | The app’s data folder | To sync while offline |
| API keys and tokens you add (a Jev API key, a GitHub token) | Your operating system’s keychain (macOS Keychain, the Linux Secret Service), or a file only your user can read where no keychain is available | To call the service the key belongs to |
| Your skills and agents | ~/.agents/skills, ~/.agents/agents and the skill and agent folders of the coding agents you manage |
They are your files; the app reads and writes them at your request |
Only if you run cordbay mcp install: an entry that starts cordbay mcp |
The configuration file of the coding agent you named | So that coding agent can ask Cordbay about your machines |
| Only if you turn the agent mesh on: the machine’s private mesh keys | Your operating system’s keychain, or the file used where there is none | To sign and decrypt tasks between your machines |
| Only if you turn the agent mesh on: the machines you trust and their public keys, the tasks sent from and to this machine (prompts and answers), and a log of what happened | The app’s config and data folders, readable only by your user | To run tasks between your machines and show you what happened |
None of this is sent to us, except what licence activation and update checks send (see “What reaches us”). API keys, tokens, the licence key and private mesh keys are never written to the sync repository.
What the app sends to your git repository
When you sync, the app commits and pushes to the private git repository you configured, using the git program and the credentials already on your computer:
- your skills and agents;
- an optional
cordbay.tomlfile with per-machine rules; - on a separate
statebranch, one file per machine with: the machine’s id and label (your hostname by default), its operating system, the names and sources of its installed skills, the names of its agents, and, for each git repository under the folders you chose to watch, its local path, current branch, whether it has uncommitted changes, how far it is ahead of or behind its upstream, when it was last fetched, and the address of its remote with any user name, password or token removed; which coding-agent programs are installed and their versions; and, only while the agent mesh is on, the machine’s public mesh keys; - only if you turn the agent mesh on, on a separate
cordbay-mailboxbranch: tasks sent between your machines and their answers, each encrypted so that only the receiving machine can read it. Your git host can see which machine sent a message to which, when, and its size, but not its contents. Messages are removed once delivered.
This goes to the git host you chose (for example GitHub, GitLab or your own server) and is governed by your agreement with that host. Cordbay never receives it and has no access to your repository.
Outside services the app calls
The app contacts these services directly from your computer. As with any internet request, each service sees your IP address. We do not receive copies of these requests.
| Service | When | What is sent |
|---|---|---|
| Your git host | When you set up sync or sync | The contents described in the section above, through git |
GitHub (api.github.com) |
When you check skills for updates | The owner and name of each GitHub repository your skills were installed from. If you added a GitHub token, it is sent with these requests; if you did not, but the GitHub CLI (gh) is installed and signed in, its token is sent instead. A token only raises GitHub’s rate limit. |
GitHub (github.com) |
When you install or update a skill | A git clone of the repository that holds the skill, using your own git credentials if the repository is private |
| skills.sh, run by Vercel (privacy policy) | When you search for skills | Your search text and the number of results asked for |
TypeSafe AI (api.typesafe.ai), the Jev service (privacy policy) |
Only if you have added a Jev API key, and only when a skill is scored, Jev is asked about a sync conflict, or before a skill update installs by itself (see below) | To score a skill: the text of that skill’s SKILL.md file, the scoring question, and your Jev API key. To suggest how to settle a sync conflict: both versions of the one file in conflict (at most 96 KiB together), what kind of file it is, fixed questions about which version to keep and whether either version could make a coding agent act unsafely, and your Jev API key. Before a skill update installs by itself: the new version’s SKILL.md as published on GitHub (at most 96 KiB), a fixed question about whether it could make a coding agent act unsafely, and your Jev API key. Not the file’s path, the skill’s name or source, the names of your machines or any other file. |
| A coding-agent command-line tool on your computer (Claude Code or Codex) | Only when you ask the app to generate an agent | The name, one-line description and skill names you typed. That tool then contacts its own provider (Anthropic or OpenAI) under your account with them |
Each of these services handles what it receives under its own terms and privacy policy. If you never add a Jev API key, the app sends nothing to TypeSafe AI.
A sync conflict is sent to TypeSafe AI only when you click Ask Jev on it, run cordbay sync conflicts --ask-jev, or turn on Suggest conflict resolutions with Jev in the desktop app’s Settings. That setting is off until you turn it on, and it lets the desktop app ask about each conflict that comparing the two versions on your computer does not settle. A conflict that this comparison settles, one where a machine deleted the file, and one whose two versions together are longer than 96 KiB are never sent. The request goes from your computer with your key, under your own account with TypeSafe AI, as scoring does; we receive nothing. Jev’s answer is only a suggestion: nothing is resolved until you choose a version. Turning the setting off stops the desktop app asking by itself; deleting your Jev API key stops every request to TypeSafe AI.
With a Jev API key saved, the desktop app also asks Jev about each skill update it is about to install by itself, which it does unless you turn off Install skill updates automatically in its Settings. It sends only the new version’s SKILL.md, the public file from the skill’s GitHub repository, and installs the update unless Jev finds that file may make a coding agent act unsafely, or can’t check it; then the update waits for you. Jev reads only that file, not the skill’s other files. Without a key nothing is sent and every update installs.
What reaches us
We receive personal data only in these cases.
- Buying a licence. Polar (polar.sh), run by Polar Software, Inc. in the United States, sells Cordbay to you as merchant of record. Polar takes the payment, handles sales tax and refunds, and collects your name, email address, billing details and payment details under its own privacy policy. We receive the order details Polar shares with sellers: your email address, the name and country you gave at checkout, what you bought, what you paid and whether it was refunded. We never see your full card number.
- Your licence key. When Polar tells our API that an order is paid, the API asks our licence service, Sealcord, to issue a licence for the email address on the order. It emails you the key through Resend, and shows it on cordbay.com/purchase/ to whoever holds the link Polar’s checkout sent you to, for 7 days. The API itself stores nothing: it reads the order from Polar and the licence from Sealcord each time.
- Licence activation. When you activate a licence key, about once a day while one is activated, and when you deactivate it, the app sends Sealcord (
api.sealcord.com): the licence key, which contains the email address it was sold to; the computer’s random id frommachine.json; and, when activating, the computer’s name in Cordbay (your hostname unless you renamed it), its operating system (for examplemacos) and the app’s version. Sealcord keeps the licence (its id, the email address, its status) and a record of each computer it is activated on, with when it was last seen, so a licence stays within the computers it covers (up to 3) and you can free one to use another. Like any web service it also sees the IP address of each request, which it uses to limit how often it can be called. - Update checks. The desktop app, when installed with its installer, asks downloads.cordbay.com whether there is a new version when it starts, every 6 hours while it runs, and when you choose to check. Every check sends the same request, which names the app, the version you have and a random id for this installation, made by the updater and not linked to your licence, your email address or your machine id. The
cordbayandcordbay-tuiprograms do not check for updates. - Finding a lost key. If you enter your email address on cordbay.com/licence/, our API asks Sealcord for the licences sold to that address and, if there are any, emails their keys to that address through Resend. To limit abuse, the API counts in its memory how often each address and each network has asked: at most 3 emails per address a day and 5 requests per network in ten minutes. These counts are not written anywhere and are lost when the API restarts.
- Launch news. If you enter your email address in the form on cordbay.com, see “Launch news by email” below.
- Support. If you email support@cordbay.com, we receive your email address and whatever you include in the message. Our email is hosted by Google Workspace.
- The website and our services. cordbay.com, api.cordbay.com and downloads.cordbay.com are served by bunny.net (BunnyWay d.o.o., Slovenia). Its network keeps a log of each request (time, address requested, browser type, country and IP address) for 3 days; for cordbay.com, api.cordbay.com and downloads.cordbay.com the last part of the IP address is removed before it is logged. Our API also writes its own log of each request (an id, the method, the path, the status and how long it took), with no IP address, no request body, and every email address shortened to its first letter and domain (
s***@example.com); bunny.net keeps those logs for the period it sets. The domain’s DNS is answered by Cloudflare, which does not see the pages you visit. The website sets no cookies and loads no analytics or advertising scripts. It stores one value in your browser’s local storage, your light or dark theme choice, which never leaves your browser. Search in the documentation runs inside your browser.
Launch news by email
Before Cordbay goes on sale, the home page at cordbay.com has a form for one email when it launches.
- What we keep. The email address you enter, and when you entered it. Nothing else is asked for.
- Where. The form sends your address to our API, which adds it to a contact list held by Resend (resend.com), the service we use to send email. The API keeps nothing itself. It sees your IP address, as any web request does, and uses it only to limit how many times one network can submit the form in ten minutes, counting in memory; it does not store it.
- Why. To tell you when Cordbay launches. We use the address for nothing else, do not share it with anyone but Resend, and do not add it to any other list.
- No tracking. Our emails carry no open or click tracking.
- Unsubscribing. Every launch-news email has an unsubscribe link, which stops all further email at once. You can also write to support@cordbay.com and we will delete your address.
- How long. Until you unsubscribe or ask us to delete it, and in any case we delete the list within 30 days after the launch email is sent.
Why we use it and on what basis
| Purpose | Data | Legal basis (GDPR and UK GDPR) |
|---|---|---|
| Selling you a licence, delivering the key and keeping the licence valid on your computers | Order, licence and activation data; licence emails | Performance of a contract |
| Sending a lost key to the address it was sold to | Email address, licence data | Performance of a contract |
| Offering updates | Update check requests | Performance of a contract |
| Tax and accounting records | Order data | Legal obligation (kept by Polar as merchant of record) |
| Sending launch news you asked for | Email address | Consent, which you can withdraw by unsubscribing |
| Answering support requests | Support messages | Legitimate interests (helping you), or performance of a contract when it is about your licence |
| Keeping the website and services running, secure and free of abuse | Request logs, rate-limit counts | Legitimate interests |
We do not sell or share personal data for advertising, use it for profiling, or use your skills, agents or any other content to train AI models. We never have your content in the first place.
Who we share it with
Only with the service providers that act for us, each for the purpose above:
| Provider | What for | Where its data is kept |
|---|---|---|
| Polar (Polar Software, Inc.) | Checkout, payment, tax and refunds, as merchant of record | United States |
| Sealcord | Issuing licence keys and counting the computers each one is activated on | Germany (servers on bunny.net, database on Neon in AWS Frankfurt) |
| Resend | Sending licence, lost-key and launch-news emails; holding the launch-news list | United States |
| bunny.net (BunnyWay d.o.o.) | Hosting the website, the API and the downloads | The API runs in Germany; pages and downloads are served from bunny.net’s network worldwide |
| Cloudflare | Answering DNS lookups for cordbay.com | Worldwide |
| Google (Google Workspace) | The support mailbox | Google’s data centres |
We also disclose data where the law requires it.
International transfers
Some of these providers keep data in the United States or serve it from other countries outside the European Economic Area and the United Kingdom. Where they do, the transfer relies on the safeguards in each provider’s data processing terms, such as the European Commission’s standard contractual clauses or the EU-US Data Privacy Framework where the provider is certified. Sealcord and our API keep their data in Germany.
How long we keep it
- Purchase records: kept by Polar for as long as tax and accounting law requires; Polar sets the period.
- Licences and activations: a Cordbay licence does not expire, so Sealcord keeps it, and the list of computers it is active on, for as long as the licence exists. That is what lets you activate it again or have the key sent again years later. Deactivating a computer frees its place. A refunded licence is revoked, not deleted. Sealcord’s database keeps backups for 7 days.
- Emails we send (licence and lost-key emails): Resend keeps a record of each email sent for the period its service sets.
- Launch news addresses: until you unsubscribe or ask us to delete yours, and in any case no more than 30 days after the launch email is sent.
- Support messages: for as long as we need them to help you, and no more than 2 years after your last message, unless the law requires longer.
- Request logs: 3 days for bunny.net’s network logs; our API’s own logs (with no IP address) for the period bunny.net sets.
- Rate-limit counts: in memory only, for at most a day.
Data on your computer and in your git repository stays until you delete it. Removing the app does not delete your skills, agents or sync repository.
Your rights
Depending on where you live, you may have the right to see, correct, delete, restrict or receive a copy of the personal data we hold about you, to object to its use, to withdraw consent at any time, and to complain to your data protection authority. If you live in California or another US state with a privacy law, you have the right to know what we collect, to have it deleted and corrected, and not to be treated differently for using these rights; we do not sell or share personal information as those laws define it.
To use any of these rights, write to support@cordbay.com from the address in question, or tell us your Polar order number, so we can confirm the data is yours. We answer within one month.
If you ask us to delete the data tied to a licence, we revoke the licence and remove what we can. A revoked licence record that Sealcord cannot delete is kept only as a record that the licence existed and is no longer valid, and is used for nothing else. Polar keeps its purchase records under its own legal obligations.
Security
The licence key, API keys and tokens on your computer are kept in your operating system’s keychain or in files only your user account can read. The app reaches your git host with your existing git credentials and never stores them. Our API holds no database, logs no keys, tokens or full email addresses, and keeps its service keys out of every log and error message. No system is perfectly secure; keep your computer, your git host account and your keys protected.
Children
Cordbay is a tool for software developers and is not directed at children under 16. We do not knowingly collect personal data from them.
Changes to this policy
We will post changes on this page and change the date at the top. If a change affects how we use data we already hold about you, we will tell customers by email, at the address their licence was sold to, before it applies.
Contact
Cordbay, support@cordbay.com.