Privacy

What RepoLens reads

Only public GitHub data, through GitHub's official API, and only when someone asks for an analysis. RepoLens never requests access to private repositories. Requests are made one at a time, capped per visitor and per hour, and paused automatically whenever GitHub signals a rate limit.

What RepoLens stores

For each analyzed GitHub username: the score, the primary language and the date — these power the leaderboard, percentiles and score history. It also keeps a cached copy of the latest analysis so repeat views don't query GitHub again; that copy is replaced whenever the profile is re-analyzed and kept until then, or until removal is requested.

To enforce per-visitor limits, RepoLens stores a salted hash of the visitor's network address that changes every day. Raw IP addresses are never stored, and the hashes are deleted after 24 hours. An email address is stored only if someone subscribes to score alerts — a feature that is currently switched off.

AI features and Google Gemini

The written review, README drafts and job matching may be generated with Google's Gemini API free tier. Google may use content sent to its free tier to improve its products, including human review. RepoLens therefore sends only project data — repository names, descriptions, languages, topics and scores — plus any job description you paste. It never sends names, bios or usernames. Visitors in the European Economic Area, the United Kingdom and Switzerland are always served by the built-in rules engine instead, and nothing they do is sent to Gemini.

Tokens and sign-in

A GitHub token pasted into the form is used for that one analysis and never stored. Optional GitHub sign-in, used only to open pull requests on your own repositories, keeps its token in an httpOnly cookie in your browser for eight hours; RepoLens does not store it on its servers.

Other services

RepoLens is hosted on Vercel and uses Vercel Web Analytics and Speed Insights for aggregate, cookieless traffic and performance numbers. Scores are stored in a Neon Postgres database. The Feedback button is powered by Feedex, which receives what you type into it together with your browser, viewport and the page you were on.

Search engines

Individual report pages (/u/username) are marked “noindex”, so a person's score can be shared by link but isn't published into search results.

Removing a profile

If your GitHub profile appears on RepoLens and you'd like it removed — from the leaderboard, percentiles, score history and the cache — ask through the Feedback button on any page, or open an issue on the RepoLens repository. Include your GitHub username. Everything RepoLens holds about that username is then deleted.

Last updated 2026-09-25 · how scoring works