Effective August 10, 2026
When you're on a GitHub profile page, the extension reads information already present on that page to check for common gaps:
All of this is read directly from the page's content in your browser — the same information anyone visiting that public profile could already see.
If you use the optional Compare feature and type in a second GitHub username, the extension fetches that public profile's page directly from github.com (the same as if you'd visited it yourself) to run the same checks against it. This only happens when you explicitly type a username and submit it — it's not automatic, and it only ever touches public GitHub pages, never a private or authenticated endpoint.
github.com itself, made by your own browser, the same way any webpage you visit would loadWe have no way to see which profiles you view, which usernames you compare, or anything else about your usage — there's simply nothing that reports back to us.
Profile Fix uses your browser's local extension storage (chrome.storage.local) for exactly one thing: remembering which checklist items you've manually marked "done" for a given GitHub username, so that choice is still there the next time you visit that profile.
This data stays on your device. It is never transmitted anywhere, and we have no access to it. Uninstalling the extension removes it.
Nothing else is stored persistently — for example, a username you type into the Compare box exists only in memory while the panel is open and is cleared as soon as you navigate away or close the tab.
If what the extension does changes in a way that affects this policy, we'll update this page and the effective date above.
Questions about this policy or the extension: hello.veerweb@gmail.com