Privacy Policy

Data Collection

OctoCounts does not require accounts and does not assign browser-extension users persistent identifiers. The extension does not collect browsing history. When you request a repository analysis, OctoCounts processes the repository provider, owner, repository name, ref or commit, and generated code statistics needed to provide the report.

Optional GitHub Login

Public repository analysis does not require GitHub login. The Chrome extension optionally offers GitHub OAuth login with the public_repo scope. If you choose it, the backend exchanges the authorization code with GitHub; the extension stores the returned GitHub login and access token in local extension storage. The token can be sent to the backend when you explicitly connect it to retrieve repository star history. The backend uses the token for that operation without persisting it. Logging out removes the local login and token; revoke the app in GitHub settings to revoke its GitHub authorization. Edge and Firefox builds do not offer this login flow.

Analytics

The website uses Umami for aggregate page and interaction analytics. We use this to understand whether the web app, report pages, and install links are working. We do not use this data for personalized advertising.

Aggregate Product Statistics

OctoCounts may publish aggregate operational statistics such as total reports generated, total public repositories analyzed, total lines counted, source breakdown by product surface (web, extension, CLI, GitHub Action, MCP, API, seed), cache hit rate, and error rate. These statistics are based on report activity and are not a user-level activity feed.

Repository Host APIs

When you analyze a repository, OctoCounts sends the repository URL to the public GitHub API to resolve the branch, tag, or commit SHA. Repository analysis only accesses public repository metadata and requires no user credentials. Optional extension sign-in uses the separate token flow described above; the extension stores its login token locally.

Data Storage

SLOC reports are cached by repository owner, name, commit SHA, tokei version, and analysis options. This cache contains public repository metadata and language statistics. Cached public reports can be accessed by anyone who knows the repository URL and commit.

Source Code

OctoCounts is open source. You can inspect the full codebase at github.com/huanglizhuo/OctoCounts.

Contact

Questions about this policy? Open an issue on GitHub.

Last updated: October 25, 2026