HydraCode
How it worksServerAccountDownload ↓
← All policies and support

HydraCode / Privacy Policy

Privacy by architecture.

HydraCode is local-first. Your code, your conversations with your agents and your provider credentials stay on computers and servers you control. This policy explains the few things that do reach us, and what happens to them.

Effective date
October 8, 2026
Last updated
October 8, 2026

On this page

  1. 01Overview
  2. 02What stays on your machines
  3. 03The desktop app and the server
  4. 04Your account
  5. 05The iPhone and iPad app
  6. 06Notifications and Live Activities
  7. 07The relay
  8. 08Server history sync
  9. 09Synced settings and the vault
  10. 10Other parties
  11. 11How long we keep it
  12. 12Deleting your account
  13. 13Your choices and rights
  14. 14Children
  15. 15Changes to this policy
  16. 16Contact

01

Overview

HydraCode is made by Team Hydra, a small studio in Canada. In this policy "we" and "us" mean Team Hydra. It covers the HydraCode desktop app, the HydraCode server (hydra), the HydraCode app for iPhone and iPad, the optional HydraCode account and relay at code.hep.gg, and this website.

The short version:

  • We do not sell your data, show ads, or use analytics, tracking or crash reporting services.
  • You can use the desktop app and the server without an account. Signed out, and unless you link a machine to Hep.gg's Claude account pool (section 03), nothing about your work reaches us.
  • With an account we keep your email address, the devices and machines you sign in, your synced settings, and a copy of each linked headless server's thread history.
  • When your phone cannot reach one of your machines directly, its connection passes through our relay. We pass that traffic along without storing it.
  • You can delete your account at any time, in the app under Settings, Account, or on code.hep.gg/account.

02

What stays on your machines

Your projects, files, Git repositories and terminals, and the threads you run with Codex or Claude, are kept by the HydraCode server on the machine that runs it: the server built into the desktop app, or a headless server you installed. Your Codex and Claude sign-ins and API keys, SSH keys, and the access tokens of your devices stay on the device that holds them. They are never synced as plain account settings.

When you send a message, your server passes it to Codex or Claude, which process it under OpenAI's and Anthropic's own terms. That traffic goes from your server to the provider, not through us, unless you route Claude through Hep.gg's account pool (section 03).

Data leaves your machines through HydraCode only in the ways this policy describes: a headless server linked to your account copies its thread history to the account (section 08), the relay carries a phone's connection when it cannot reach a machine directly (section 07), and notifications carry short excerpts through Apple (section 06).

03

The desktop app and the server

Signed out, the desktop app and the server only talk to:

  • The desktop app's own built-in server, and the SSH machines you connect it to. Reaching any other machine needs an account. HydraCode offers only Tailscale and private network addresses for direct connections, never public IP addresses.
  • The services you set up yourself: Codex, Claude, your Git remotes and Tailscale.
  • Our release feed, to check for and download updates. Like any web request, this shows your IP address and the platform being updated to Hep.gg's file storage, which Team Hydra runs.
  • Public information your server keeps current, such as Anthropic's published list of Claude models.

Neither sends analytics or usage data to us. Tracing (OpenTelemetry) is off unless you turn it on, and then it goes only to the endpoint you choose.

Separately from the HydraCode account, you can link a machine to CCAS, Hep.gg's pool of Claude accounts. A linked machine sends its Claude requests through Hep.gg's proxy, and reports usage and activity (such as the project, branch and model of a running thread) to Hep.gg for its usage meters and time tracking. It can also sync your Claude Code settings files and, if you turn it on, show your project as a Discord presence. Hep.gg is also run by Team Hydra, and CCAS is covered by Hep.gg's privacy policy. Without a link, none of this happens.

04

Your account

An account is optional for the desktop app and the server, and it is how the iPhone and iPad app finds your machines. You sign in with a link we email you, or with your Hep.gg account. Your first sign-in creates the account. The account service keeps:

  • Your account. A random account id and your email address. If you sign in with Hep.gg, also the identifier Hep.gg uses for your Hep.gg account. We never receive your Hep.gg password, and we do not keep the tokens Hep.gg issues during sign-in.
  • Sign-in requests. The email address a sign-in link was sent to, the name of the device that asked (for example "HydraCode server wagyu"), and when the request expires. Links expire after 15 minutes and work once.
  • Sessions. Each signed-in desktop, server, phone and browser has a session: its name, when it was created and when it was last used. We keep only a hash of the session token. A session ends when you sign it out or revoke it, or after 365 days without use; each use moves that date forward.
  • Your machines. For each server and desktop linked to the account: its name, kind, HydraCode version, operating system and processor type, the Tailscale and private network addresses it offers for direct connections, whether it lets devices on your account connect, and when it was first and last seen.
  • API keys. The name you gave a key, its first few characters so you can tell keys apart, a hash of the key, and when it was created, last used and revoked. A key can reach every headless server on your account: its requests and your servers' answers pass through code.hep.gg on the way and are not stored.
  • A custom sound. If you upload your own finished-turn sound, the audio clip (at most ten seconds) and its name, so your other devices can play it.

We use your email address to send you sign-in links. We do not send marketing email.

Like any website, code.hep.gg sees the IP address of every request. Apart from access records (section 07) and logs (section 11), the account service does not store it. It uses addresses in memory to slow down repeated sign-in attempts.

05

The iPhone and iPad app

The app is a remote control for your own machines. Your messages, attached photos, transcripts, diffs, files and terminals travel between the app and your servers, directly over Tailscale or your local network whenever it can reach them, and through the relay otherwise. The app reaches only the machines on the account you sign in to.

When you sign in to your account, the app sends code.hep.gg:

  • A device id. 32 random characters made when the app is installed and kept in the Keychain. It is not the advertising identifier or any Apple identifier, and it identifies this install of the app to your account, your servers, notifications and the relay.
  • A device name and system. A name such as "HydraCode on iPhone", the kind of device (phone or tablet) and the iOS or iPadOS version. They name the phone's session and show in your servers' list of authorized clients.
  • A public key. To connect directly, the app asks the account for an access grant to one of your machines. The machine seals a single-use access code, valid for five minutes, to a key that never leaves the phone. code.hep.gg passes on only the sealed grant, which it cannot open, and keeps a hash of the public key in the access record (section 07).
  • Sign-in codes. To sign in without typing a password, you show a code on a signed-in desktop (Settings, Sync, Sign in a phone) or on code.hep.gg/account, then scan or type it in the app. A code lasts five minutes and works once. We keep only a hash of it, with the name, system and device id of the phone that used it.
  • Synced settings. Preferences such as your favourite models, shared with your desktops (section 09).

The camera is used only to scan sign-in and server approval codes and, when you choose, to take a photo to attach to a message. Photos go to your own server. The app contains no analytics, advertising or third-party tracking code.

06

Notifications and Live Activities

If you allow notifications and are signed in, the app registers with the account so it can alert you while it is closed: when a turn finishes or fails, when an agent needs your approval, and when it has a question. Only headless servers send these alerts.

For this the account keeps the phone's Apple push token, its device id, which alerts you want, your preview setting, and the names of the sounds to play. While the app is open it tells the account so every 30 seconds, along with the thread on screen, so you are not alerted twice. That report lasts 60 seconds, is held only in memory, and is never stored.

code.hep.gg writes each alert from your server's activity at the moment it is sent, and Apple Push Notification service delivers it. What the alert says depends on the Push previews setting in the app (Settings, Notifications):

  • Full message shows the thread title, the project and server names, and a short excerpt: the command waiting for approval (for example "Bash: npm test"), the agent's question, the last words of its reply (up to 180 characters) or the error.
  • Minimal shows only the server name and the thread title, with "finished", "failed", "needs your approval" or "has a question".

A Live Activity shows a running turn on the Lock Screen and in the Dynamic Island. The app hands the account the activity's update token, the server and thread it follows, and when the turn started, and the account sends the updates through Apple: the thread title, what the agent is doing, how many tools it has used and, while it waits, what it is asking to run. The Minimal setting shortens the alerts a Live Activity raises, but not what the activity itself shows. The app also hands over the token iOS uses to start a Live Activity for an approval or a question.

The content of notifications and Live Activity updates is never written to our database or logs; it is held in memory only as long as it takes to deliver it. Turn alerts off, or choose which ones you get, in the app under Settings, Notifications, or in the iOS Settings app.

07

The relay

The app connects to your machines directly over Tailscale or your local network when it can. When it cannot, it connects through the relay at code.hep.gg: the relay asks your machine to open a connection back to code.hep.gg, then passes the traffic between the two. This works only for machines linked to your own account, and only while the machine allows devices on your account to connect.

Everything you would send or see over a direct connection, including messages, photos, code, diffs and terminal output, then passes through code.hep.gg. Each leg is encrypted with TLS: one between your phone and code.hep.gg, and one between code.hep.gg and your machine. The relay is not end-to-end encrypted, because code.hep.gg decrypts each leg to pass the traffic to the other. It does this in memory, and it does not read, log or store what passes through.

When a signed-in device asks for a relayed connection or a direct access grant, we keep an access record: the account, the machine, the session, the device's id and name, the outcome (opened, issued, or why it was refused), the IP address the request came from, a hash of the phone's public key for a grant, and for a relayed connection how much data went each way, how it closed and when it started and ended. Access records are deleted after 90 days.

To keep a machine off the relay, turn off "Let devices on my account connect to this computer" in the desktop app (Settings, Connections), or set accountAccess.enabled to false in a headless server's settings.json. No device on your account can reach that machine then, directly or through the relay.

08

Server history sync

A headless server linked to your account (with hydra account link, which the installer runs, or by a signed-in desktop that already had a connection to it) copies its event log to the account. That log is the full history of its projects and threads: your messages, the agents' replies and their tool activity. It is how hydra restore brings a server's history back after a reinstall. The copy is stored on our database server and is not encrypted end to end.

Desktops linked to the account do not upload their history. Removing a server from the account (on code.hep.gg/account or in the desktop app) deletes its copy. hydra account unlink stops a server syncing but leaves its copy on the account.

09

Synced settings and the vault

Signed in, your desktops and phones share preferences through the account: theme, fonts, sidebar layout, favourite and visible models, the finished-turn sound, and the portable part of your servers' settings, such as which models to use and which providers are on. The account also keeps the list of machines your devices know, with their names, ids and private addresses. Every change is kept as a history entry with the id of the device that made it, so that devices that were offline can catch up without losing or reviving settings, and each syncing device's name, platform, app version and last sync time are kept with it. The latest change to each setting is kept; a change that a later one replaced is deleted once it is more than seven days old. Tokens, provider credentials, SSH secrets and private keys are never part of it.

The encrypted vault is a backup of your desktop's saved connections and their credentials, made only when you choose to. Your device encrypts it with a recovery passphrase before uploading (AES-256-GCM, with a key derived from the passphrase), and we store only the encrypted result. We never see the passphrase and cannot decrypt the vault or recover it if you forget the passphrase.

10

Other parties

We do not sell or rent personal information, and we do not share it except with the services below, as far as each needs, or when the law requires it.

  • Apple. Apple Push Notification service receives the push and Live Activity tokens and the content of each alert and update it delivers. Apple also distributes the app through the App Store and may share aggregate app statistics with us if you choose to share them with app developers. See Apple's privacy policy.
  • Hep.gg. If you sign in with your Hep.gg account, Hep.gg confirms your email address and account identifier to us. If you link a machine to CCAS, Hep.gg handles that traffic under its own privacy policy. Hep.gg is also run by Team Hydra.
  • Email delivery. Sign-in links travel through our outgoing mail service and your own email provider.
  • Hosting. The account service, the relay, the database and its backups run on servers Team Hydra operates in Canada.
  • This website. code.hep.gg loads its fonts from Google Fonts, so your browser contacts Google when you open a page. See Google's privacy policy.
  • Services you choose. Codex (OpenAI), Claude (Anthropic), Tailscale and your Git hosts work with your machines under your own accounts and their own terms. We are not part of that exchange.

Apple and Google may process data outside Canada.

11

How long we keep it

WhatHow long
Your account, email address and sign-in identityUntil you delete the account.
Sign-in links and requestsThey expire after 15 minutes and are deleted a day later.
Phone sign-in codesThey expire after five minutes and are deleted a day later.
Server approval requestsThe server's name, id, platform and version and the address it asked from. They expire after ten minutes and are deleted a day later.
SessionsActive until signed out, revoked, or unused for 365 days. The record of an ended session (its name and dates) stays with the account until you delete it.
Machines on the accountUntil you remove the machine or delete the account. A removed machine leaves a note of its id and removal date, so your other desktops do not link it back, until you add it again or delete the account.
Headless server historyUntil you remove the server or delete the account.
Synced settings and their historyThe latest change to each setting until you delete the account. A change that a later one replaced is deleted once it is more than seven days old.
Encrypted vaultReplaced by each new backup; deleted with the account.
Custom soundUntil you replace or remove it, or delete the account.
API keysA revoked key stops working at once. Its record stays until you delete the account.
Push registrationsUntil you sign out in the app, Apple reports the token is no longer valid, or you delete the account. Nothing is sent once the session that registered it has ended.
Live Activity tokensUntil the activity ends. A token is never used after eight hours and is cleared within a day of that. All of a phone's Live Activity tokens go as soon as its session signs out.
Foreground reports60 seconds, in memory only.
Notification and relay contentNot stored.
Access records (relay and direct access)90 days.
Service logsThe account service's log has a fixed size (about 50 MB) and older entries are overwritten as new ones arrive. It records events and errors with account, device and machine ids and machine names, not your messages or code. Our web server also keeps standard access logs, including IP addresses, for security and troubleshooting.
Database backupsTaken every six hours and kept for about 30 days.

12

Deleting your account

Delete your account in the iPhone and iPad app under Settings, Account, Delete Account, or on code.hep.gg/account under "Delete your account". You type "delete my account" to confirm. It cannot be undone.

Deleting the account removes, at once:

  • Your account, its email address and how you signed in, including unused sign-in links.
  • Every session, so every desktop, server, phone and browser is signed out.
  • Every machine on the account and the history headless servers synced to it. Linked machines are asked to revoke the access they gave your devices, then signed out of the account, and they stop linking.
  • Synced settings and their history, the encrypted vault and your custom sound.
  • API keys, phone sign-in codes, server approval requests, push and Live Activity registrations, and access records.

Nothing on your own machines is deleted: their projects and threads stay where they are, and the desktop app keeps working with its own built-in server without an account. Your other machines can be added to a new account.

What lingers: the account service logs one line saying that the account's random id was deleted and how many records went, without your email address. Older log entries can still mention the account's id or your machines' names until they are overwritten. Database backups taken before the deletion still contain your data until they expire, within about 30 days.

13

Your choices and rights

  • Use the desktop app with its built-in server signed out.
  • Choose which alerts you get and how much they show, or turn them off.
  • Keep a machine off the account and the relay with its account access switch.
  • Sign out devices, remove machines and revoke API keys on code.hep.gg/account.
  • Delete your account at any time.

You can also ask us for a copy of the personal information the account service holds about you, ask us to correct it, or ask us to delete it, by emailing support@teamhydra.dev from the address on your account. We answer within 30 days. If you are not satisfied with our answer, you can contact the Office of the Privacy Commissioner of Canada or the data protection authority where you live.

14

Children

HydraCode is a tool for software developers and is not directed at children. We do not knowingly collect personal information from children under 13. If you believe a child has created an account, email support@teamhydra.dev and we will delete it.

15

Changes to this policy

We update this page, and its "Last updated" date, whenever HydraCode changes what it collects, why, or how long it keeps it. The version on this page is the one that applies.

16

Contact

Questions and requests about privacy:

support@teamhydra.dev

For help with HydraCode, see Support. To report a security issue, see the security policy.

HydraCode

Codex and Claude, on your machines.

AccountSupportPrivacySecurityTerms