Privacy Policy

The short version

RepoKit has no backend server. There is nothing for your data to be sent to except GitHub's own API, which your browser talks to directly. RepoKit doesn't collect analytics, doesn't track your browsing, and doesn't sell or share data — because there's no infrastructure on RepoKit's side capable of doing any of that in the first place.

What RepoKit accesses

Public GitHub repository data — file trees, sizes, and contents, fetched from GitHub's public API for any public repository you visit. This requires no authentication and is the same data anyone can already access.
Private GitHub repository data — only if you explicitly connect a personal access token, and only for repositories that token has read access to. RepoKit never attempts to access private data without an explicitly connected token.

Where your GitHub token is stored

If you connect a personal access token, it is stored using Chrome's local extension storage (chrome.storage.local) on your own device. It is used solely to attach an authorization header to requests your browser sends directly to api.github.com. It is never transmitted to any server operated by RepoKit, because no such server exists in this extension's architecture. You can revoke the token at any time from your GitHub account's developer settings, independent of RepoKit.

What RepoKit does not do

It does not operate a backend server of any kind.
It does not collect analytics, telemetry, or usage tracking.
It does not sell, share, or transmit your data to any third party.
It does not read or access browsing activity outside of github.com pages.
It does not modify, commit, or write anything to your repositories — all functionality is read-only.

Permissions requested, and why

Host access to github.com, api.github.com, and raw.githubusercontent.com — required to read repository data and display it inline on the pages you're already viewing.
Storage — required to save your connected token (if any) and light local preferences, locally on your device.

Changes to this policy

If this policy changes, the update will be reflected on this page with a revised "last updated" date. Material changes affecting how data is handled will also be reflected in the extension's Chrome Web Store listing.

Contact