Public data. Clear boundaries.

Profile information we use

The backend retrieves and stores public Steam IDs, profile names, avatars, library ownership, playtime and available game catalog details. Stored profile projections let the site serve statistics without contacting Steam for every visit.

Public profiles with games may appear in the sitemap. Comparison result pages and fictional examples are marked nonindexable. Search engine indexing and removal happen on the search engine’s schedule.

Private libraries and cached data

When the backend reports a library as private, the frontend omits its game rows and statistics, including interactive component data. If either player is private, comparison rows and overlap counts are omitted too. Public identity information can remain visible.

Changing privacy settings on Steam is not an immediate deletion request here. Cached visibility changes after a successful profile refresh. Crawlers read cached data and cannot refresh profiles themselves. See the playtime and privacy guide for the settings Steam provides.

Requests and external content

The frontend passes the request’s user agent and a request ID to the backend for crawler handling and request correlation. As with other web services, the hosting servers receive network connection information.

Avatars and game artwork load from Steam image services, so your browser contacts those services. Fonts are served from this site. Links to Steam Community and the Steam Store take you to external websites.

Project and questions

This is an independent project, not a Valve or Steam service. Thefrontend repositoryincludes project details and a way to raise questions. Avoid including sensitive personal information in a public issue.