PRIVACY / WORKING POLICY

Privacy by architecture.

HydraCode is local-first. Coding content stays on computers and servers you control unless you deliberately send it to Codex, Claude, or another service you configure.

Optional accounts

If account sync is enabled, the service processes account identifiers, registered device and private environment metadata, settings mutations, recovery records, and operational security logs. Environment bearer and pairing secrets remain device-local unless an end-to-end encrypted credential vault is explicitly enabled. Signing in is not required for local use or direct pairing.

Settings history

The sync service retains mutation history and tombstones to prevent data loss and stale resurrection. Account deletion must remove active records and schedule retained backups for expiry under the production retention policy.

Providers and networks

Codex, Claude, Tailscale, Git hosts, and infrastructure vendors process data under their own terms. HydraCode does not intentionally publish server addresses and only advertises Tailscale or private LAN routes.

Contact

Privacy requests: privacy@hep.gg. The final production policy must be reviewed with the operating legal entity, vendors, jurisdictions, and retention schedule before launch.