Privacy Policy
Last updated: 6 October 2026
GitFit ("GitFit", "we", "us") is an open-source tool for managing your GitHub repositories, stars, issues and pull requests. This policy explains what data GitFit handles when you use it and what we do with it. The short version: GitFit has no database, does not store your GitHub data, and does not track you.
1. What we receive when you sign in
You sign in with your GitHub account. GitHub then shares with GitFit:
- your name, email address and profile picture (avatar);
- an access token that lets GitFit act on your behalf on GitHub, limited to the permissions you approve (see section 3).
These are kept in an encrypted session cookie in your own browser. They are not saved in any database. The access token is never sent to your browser in readable form and is only decrypted on our server for the moment needed to call GitHub. The session lasts up to 30 days, or until you sign out.
2. What happens when you use GitFit
When you open a page or run an action (for example, archiving repositories), our server uses your access token to call GitHub's official API and passes the result straight back to your browser. Your repository, star, issue and pull-request data is not stored, cached, sold or shared by GitFit.
Some preferences stay only in your browser's local storage: your settings (default sort and stale-issue threshold), your GitFit pin board, and whether the sidebar is collapsed. They never leave your device, and you can delete them by clearing your browser's site data.
3. GitHub permissions we ask for
repo: list and change your repositories, issues and stars (archive, change visibility, rename, add topics, close issues, unstar).delete_repo: only used when you explicitly delete repositories and confirm it.read:org: show issues and repositories from organizations you belong to.read:useranduser:email: your name, avatar and email for sign-in.
GitFit only performs actions you start yourself. You can revoke GitFit's access at any time in GitHub → Settings → Applications.
4. Cookies
GitFit only uses cookies that are strictly necessary for signing in: the encrypted session cookie, plus short-lived security cookies used during sign-in (CSRF protection and the return address after GitHub sign-in). We use no advertising, analytics or tracking cookies, so there is no cookie banner.
5. Service providers
- GitHub provides sign-in and all repository data. Your use of GitHub is covered by GitHub's privacy statement.
- Vercel hosts GitFit. Like any web host, it processes technical request data (such as IP address, browser type and the pages requested) to deliver the site and keep it secure, and keeps short-lived server logs. See Vercel's privacy policy.
We do not sell or rent personal data to anyone.
6. Your rights
Because GitFit keeps no account database, there is nothing stored about you on our side to access, correct or delete beyond the session cookie in your browser. To remove everything: sign out (which deletes the session cookie), clear GitFit's site data in your browser, and revoke GitFit in your GitHub settings. Depending on where you live, laws such as the EU and UK GDPR or India's Digital Personal Data Protection Act, 2023 give you rights over your personal data. To exercise them or ask a question, email us at the address below.
7. Children
GitFit is not directed at children. You must meet GitHub's minimum age requirement (13, or older where local law requires) to use it.
8. Changes to this policy
If we change how GitFit handles data, we will update this page and the date above. Material changes will also be noted in the project's public repository.
9. Contact
Privacy questions or requests: harshalpatel6828@gmail.com.
Questions? Email harshalpatel6828@gmail.com. See also our Privacy Policy and Terms of Service.