legal
Privacy
What we hold, why, and for how long. The short version: an email address and a licence record, and nothing else we could avoid.
Last updated 28 July 2026
What never reaches us at all
icr-mergeandgit-clashrun entirely on your machine. They make no network requests and send us nothing — including no telemetry, no usage counts and no error reports.- Your signing identity for provenance is a keypair generated on your machine. The private key never leaves it, and there is no account database it could be registered against — author identity is the public key's own fingerprint.
- Files your
.gitignoreexcludes are never synced, and neither are.envfiles, private keys, certificates or your local identity file, regardless of what your ignore rules say.
What we store
- Your email address and licence record — plan, committer allowance, status, and the Razorpay payment or subscription id — held in Supabase so the relay can check whether a key is valid. This is the only personal data we keep.
- Payment details are not ours. Razorpay processes the payment and we never see your card. What we receive back is an identifier and an amount.
We keep the licence record while your licence exists, and for as long afterwards as we need it for tax and accounting purposes. Ask us to delete it and we will, once it is no longer needed for those obligations.
What passes through the relay
A room's participants exchange incremental document updates through the relay over an
encrypted connection (wss://). The relay's job is to forward those updates
and to keep a room in sync while people are connected. It does not hold a canonical copy
of your repository, and folder-scoped invitations mean an out-of-scope file is never sent
to that participant at all.
The hosted relay writes a room's current state to disk so that a restart does not lose work in progress. That state is deleted when you end the room. Server logs record connection events: the room id, when a participant joined and left, how long they stayed, how many participants were in the room, and — if you chose to share it — the display name you set. Never file contents, never your IP address.
Sharing your display name with the relay is a separate choice from showing it to the people in your room, and you can switch it off: Settings → Hivecode → Share Name With Relay. With it off, the relay records your connection as anonymous. It is self-declared either way — the relay has no account system and never verifies who you say you are.
If none of that is acceptable for your code, run the relay yourself. It is the same program, it is public, and then nothing about your work touches our infrastructure.
Third parties we use
- Razorpay — payments.
- Supabase — the licence database.
- Vercel — this website and the licence API.
- Render — the hosted relay.
- Resend — sending your licence key, if email delivery is configured.
- Google Fonts — the two typefaces on this site, which means Google receives a request from your browser when you load it.
What we do not do
No advertising, no analytics, no tracking pixels, no cookies set by us, and no selling or sharing of your data with anyone not listed above. The website sets no cookies at all; the Control Room stores the name you type in your own browser's local storage so you do not have to retype it, and that never leaves your device.
Your rights
Ask us what we hold about you, ask us to correct it, or ask us to delete it: contact us and a person will answer. If we ever suffer a breach that affects your data, we will tell you.