Your repositories never leave your machine.

Your code. Your commit messages. The names and paths of your repositories. Your branches, remotes, history and diffs. Your Git name and email. None of it is transmitted, uploaded, logged or inspected, and none of it is stored anywhere except on your own disk where Git already keeps it.

There is no telemetry, no analytics inside the app, no crash reporting service and no usage tracking. The list of repositories you have added is stored locally so the app can show it again next time, and it goes no further.

A licence check. When you activate Riggit, and once at each launch afterwards, it sends your licence key and an identifier for the device to our licensing provider so they can confirm the subscription is active and that the seat is not in use elsewhere.

The device identifier is derived from your machine and exists only to count devices against a seat. It is not a name, an address or an account, and it cannot be used to identify you personally.

If that check cannot be reached, Riggit continues working for seven days on the last successful result before asking again. It does not queue anything to send later.

A version check. Once when the app starts, Riggit asks GitHub which version it has published most recently, so it can tell you when a newer one exists. It is an ordinary public request that anyone could make, it carries nothing about you, your machine or your repositories, and the answer is a version number. If it fails, the app says nothing and carries on.

Optional, and off until you ask for it. Riggit can read your name and the email addresses on your GitHub account, so that your commits carry an address GitHub recognises. Commits carrying an address it does not recognise land in your history and never appear on your graph, which is the problem this solves.

It uses GitHub's device flow, which means you authorise it in your own browser and Riggit never sees your password. The permission it asks for is read-only: your profile and your email addresses. That exchange is between you, your browser and GitHub. It does not pass through us, and we are not told it happened.

The token from that sign-in is used once, to read those values, and then discarded. Nothing is stored and there is nothing to revoke.

Publishing is the one case that asks for more. If your saved Git credentials are refused, Riggit can ask for permission to push on your behalf, and that permission does cover your repositories. It is only ever offered after a push has already failed, you can decline it, and if you accept it the token is kept in your operating system's keychain until you remove it from settings.

When you turn on push, Riggit runs Git's own push against the remote your repository already has, using the credentials Git already uses. That traffic goes to your Git host, not to us, and it is the same traffic that pushing from your terminal produces. We never see it, and we are never told that it happened.

Payments are handled by Polar as merchant of record. They collect what they need to take the payment and issue an invoice, which typically means your email address, your billing country and your card details. Those card details go to their payment processor and are never seen by us.

We receive from them only what is needed to support a subscription: that a licence exists, whether it is active, and the email address it belongs to.

These pages are static files served by GitHub Pages. There are no cookies, no tracking pixels, and no fonts fetched from anyone else's server.

There is one third party script: Cloudflare Web Analytics, which counts page views. It sets no cookies, stores nothing on your device, and builds no profile of you, so there is no identifier following you between visits or between sites. We see how many people opened a page and roughly where in the world they were, and nothing that points at a person.

That is also why there is no consent banner. One is required for tracking that identifies you, and this does not do that. If we ever add something that does, the banner arrives with it.

GitHub serves the files and, like any web host, records the requests it receives. That is their logging, under their terms, and it happens for every site hosted there.

The only personal data connected to Riggit is what your payment carries: an email address and a billing record. You can ask for a copy of it, ask for it to be corrected, or ask for it to be deleted. Deleting it ends the subscription, since a licence with no owner cannot be supported.

Nothing on your machine needs our involvement to remove. Uninstalling the app removes it, and every commit it made is an ordinary Git commit that belongs to your repository.

The one thing worth doing by hand: if you granted permission to push, remove it from settings before uninstalling, since a key kept in your operating system's keychain is not ours to delete. You can also revoke it from GitHub at any time, which works whether or not Riggit is still installed.

Write to our privacy address for any of the above.

If this policy changes in a way that affects what is collected, the date at the top changes with it. The commitment that your repositories stay on your machine is architectural rather than a policy choice, and it is not something a future version of this page will quietly reverse.