Privacy

Your account: a login name, an email address, a display name, and an Argon2id hash of your password.

Your repositories, as ordinary bare git repositories on disk, plus the metadata around them — issues, pull requests, comments, releases, stars, teams and permissions.

Your SSH public keys, and the names and SHA-256 hashes of your access tokens.

An audit log of security-relevant actions, which records the client IP address. You can read your own.

We do not sell your data. We do not train software on your private code. We do not read private repositories, except where you ask us to investigate something and say so.

There is no advertising on this site, and no third-party analytics or tracking script on any page. The Content-Security-Policy this site sends would block one. The one third-party script is Cloudflare Turnstile, on the registration page only, which checks that a person and not a bot is creating the account.

Three companies, for three specific jobs.

• Sentry receives a crash report when a page or an API request fails. A report contains the error, a stack trace, the browser version, and the URL of the page — which includes the owner and repository name in the path. It does not contain your session cookie, your access token, your password, or the contents of any file: those are removed before the report is sent. We do not record browsing sessions.
• Resend receives your email address, so that we can send you the messages you asked for: verification, password reset, and notifications.
• Vercel and Cloudflare carry the traffic for this website, so they see the request metadata any host and any DNS provider sees. On the registration page, Cloudflare Turnstile also receives signals from your browser to tell a person from a bot.

Git traffic does not pass through Cloudflare’s proxy. The git. and ssh. hostnames resolve straight to our server.

• Your password. Only an Argon2id hash exists.
• Your access tokens. Only a SHA-256 hash is stored. That is why a token is shown exactly once.
• Your SSH private keys. We never had them.

These are cases where not holding your data is the point, rather than an oversight.

Every repository is a normal git repository, and every piece of metadata is readable through the public REST API. Deleting a repository removes it and its history from our servers, and we cannot undo that for you.

The roadmap states these as rules rather than as intentions, and changing one is a public commit.

This page describes the instance you are reading it on. If you run GitCamp yourself, none of it applies to you: error reporting and email are off unless you configure them, and no data reaches us at all.