Hivecode — privacy

What never reaches us at all

icr-merge and git-clash run 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 .gitignore excludes are never synced, and neither are .env files, 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, seat 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 account 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 and stays on the relay

A room's participants exchange document updates through the relay over an encrypted connection (wss://). On standard open rooms (room-…), the room link itself is the capability: anyone who holds the link can read and write that room's synced files and chat. On secured rooms (hs_…), access is gated by signed tokens and folder-scoped invitations ensure an out-of-scope file is never sent to that participant at all.

On the hosted relay, snapshots of a room's synced files, chat, tasks and claims are written to the container's local disk (.hive-relay-data) so a room remains accessible from the browser Control Room when editors close and survives a relay process restart. The hosted relay runs on a plan whose container disk is wiped on a redeploy or container replacement, and there is no self-serve room-delete command yet: when a redeploy wipes the container, synced files come back from participants' own folders if they rejoin, and chat and tasks return only if a still-running client reconnects.

Hivecode's application logs record connection and channel events: the room id, when a participant joined and left, how long they stayed, how many participants were in the room, sample synced relative file paths (up to three per multiplexed burst, or per file when full audit logging is enabled), and the display name sent on connect. Hivecode's own application logs never record file contents or client IP addresses (Render's edge proxy terminates TLS under Render's standard platform request handling).

In the VS Code extension, sharing your display name with the relay can be switched off under Settings → Hivecode → Share Name With Relay (with it off, the extension connects anonymously). Agents connecting through hivecode-mcp send their room display name so activity and limits remain attributable per agent. Names are self-declared on open rooms — the relay has no user account system.

If none of that is acceptable for your code, run the relay yourself (npx hivecode-relay) and pin your machine to it with HIVE_RELAY_PIN or HIVE_PRIVATE=1. 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