Skip to content

Legal

Privacy

A zero-knowledge product has an unusually short privacy page: most of what a service like this would store is either encrypted or never collected.

What we store

  • Ciphertext versions: the encrypted bytes, their size, version number and timestamp.
  • Metadata: project and environment names, and audit rows, who pushed, pulled, rolled back, invited or revoked, and when.
  • GitHub profile basics from sign-in: account id, handle, display name, avatar URL and, when GitHub returns it, an email address.
  • Device records: a device name, the IP address that asked, a status and a last-seen timestamp, the same details the approval page shows you.
  • The SHA-256 hash of each CLI token. The token itself lives only on your machine.

What we never store

Variable names, variable values, your project key, your private key, your passphrase, the recovery key. No plaintext .env file reaches the server, and no request carries a key. We could not read your file if we wanted to, there is no key material in the database, the logs or the request path.

No tracking

No analytics, no advertising pixels, no third-party scripts, no cross-site identifiers, no profiling. After you sign in there is one httpOnly session cookie; nothing on this site sets a marketing cookie. The pages you are reading are static and fetch nothing about you.

Logs

Our host keeps short-lived function logs, request path, status, latency, errors, for debugging and abuse control. We don't build profiles from them, and we don't sell or share data with anyone.

Retention and deletion

Deleting a version or a project removes its rows; deleting your account removes the rest. Backups roll off on a short window, so a deleted row can survive briefly in an archive we do not query. Device approval codes expire after 10 minutes whether or not you act on them.

Third parties

GitHub for sign-in, Vercel for hosting. That is the entire list, and neither gets more than the request requires. No data brokers, no advertisers, no sales of any kind.

No support inbox yet. Reach out via the repository , issues and discussions are the honest channel.