GitHub Hacker · Privacy

GitHub Hacker Privacy Policy

How GitHub Hacker stores account information and communicates with GitHub.

Effective date July 22, 2026 · Updated July 22, 2026

Local account storage

GitHub Hacker stores account aliases, usernames, and access tokens in ~/.githubhacker/accounts.json. The current format is plain JSON, not an encrypted credential store. Protect the file with appropriate local permissions and never commit, publish, or send it to an untrusted location.

GitHub communication

The CLI sends the access token required for the selected operation to GitHub through the GitHub API. Star, watch, fork, status, identity, and repository information commands are subject to GitHub’s own service and privacy terms.

Website

This website does not receive GitHub Hacker tokens or account configuration. It uses no account, cookies, advertising, analytics script, or contact form.

Removing local data

Use the logout command to remove individual aliases. To stop using the tool completely, remove the local account configuration after confirming you no longer need it.