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.
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.
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.
When you analyze a repository, OctoCounts sends the repository URL to the public GitHub API to resolve the branch, tag, or commit SHA. OctoCounts does not store GitHub credentials and only accesses public repository metadata.
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.
OctoCounts is open source. You can inspect the full codebase at github.com/huanglizhuo/OctoCounts.
Questions about this policy? Open an issue on GitHub.
Last updated: July 2026