Skip to content
Agent Friendly Code

Privacy policy

What Agent Friendly Code collects when you visit, what it deliberately doesn't, and how to reach us about your data.

Last updated: October 28, 2026.

Changed on October 28, 2026: Microsoft Clarity heatmaps and session recordings, and leaderboard search terms in analytics.

Overview

Agent Friendly Code (the “Service”) is operated by Himanshu Singh as an independent, MIT-licensed project. There are no user accounts. The Service scores publicly accessible source repositories and ranks the ones it tracks. This policy explains the limited information collected when you visit and how it is used.

What we collect

  • Analytics. We use Google Analytics 4, which does not log or store IP addresses, to measure aggregate traffic patterns — page views, leaderboard searches (the words searched and how many repos matched), filter and sort changes, Live Score results, package lookups, clicks on the share, badge, copy, agent and “Score your repo” buttons, referrers, approximate location, device and browser type, and time on page. This data is not used to identify individual visitors.
  • Heatmaps and session recordings. We use Microsoft Clarity to see where visitors click and how far they scroll, and to replay visits as recordings of mouse movement, clicks and scrolling. Text typed into fields is masked before it leaves your browser, though a leaderboard search also appears in the page address.
  • Server logs. Our hosting provider (Vercel) may record standard request metadata — IP address, user-agent, timestamps — and keep it briefly, for operational and security purposes.
  • Public repository data. Scores and signals shown on the Service are derived from public source repositories on GitHub, GitLab, and Bitbucket. No private code or non-public information is read or stored.
  • Live Score. A repository URL you submit is sent from our server to GitHub to read that repository's public file list, its basic details, and the few files the checks read. The result is cached on our servers for up to one hour and is not added to our database. The page address, which includes the repository name, is recorded as a page view in analytics.
  • Browser storage. The repositories you scored, with their scores, the last release notice you were shown, and your analytics choice are kept in your browser's localStorage. They are never sent to us, and clearing site data for this site removes them.

We do not ask for, or store, your name, email address, payment details, account credentials, or any content you submit — beyond a repository URL sent to Live Score and leaderboard search terms, as described above, and information you optionally include in GitHub issues filed via links from this Service (which are governed by GitHub's own privacy policy).

Cookies

The Service's own code sets no cookies. Cookies may be set by Google Analytics and Microsoft Clarity, which we embed for usage measurement. The Service shows no advertising. You can disable or delete cookies in your browser at any time; only analytics is affected, not the Service.

For visitors from the European Economic Area, the United Kingdom, and Switzerland, Google Analytics sets no cookies until they accept, and sends only cookieless pings that carry no identifier. Microsoft Clarity sets no cookies for them until they accept. They can change their answer below; declining removes Clarity's cookies at once and stops it from loading on later pages.

Third-party services

Your rights (GDPR / UK GDPR / CCPA)

Because the Service does not associate visit data with you as an individual, in most cases there is no per-person data for us to access, correct, or delete. If you reside in the European Economic Area, the United Kingdom, or California, you nonetheless have the right to request information about, correct, delete, export, or object to the processing of any personal data we may hold about you. To exercise these rights, email hsnice16@gmail.com.

Data retention

Google Analytics keeps event data for 14 months. Microsoft Clarity keeps session recordings for 30 days, and heatmaps and a sample of recordings for up to 9 months. We do not maintain a separate database of visitor information.

Children's privacy

The Service is not directed to children under 13, and we do not knowingly collect personal information from children.

Changes to this policy

We may update this Privacy Policy from time to time. The “Last updated” date at the top reflects the most recent revision. Material changes will be summarised at the top of this page.

Contact

Questions, requests, or concerns about this policy: hsnice16@gmail.com. See also our Terms of Use.