Privacy Policy
HLTB for Steam — Unofficial has no accounts, analytics, advertising, telemetry, or developer-operated server. The developer does not receive, collect, sell, or analyze user data.
Data processed
When a supported Steam game page is opened, the extension processes public website content: the Steam App ID, game title, and artwork URL. In Chrome and Firefox, the game title is sent over HTTPS directly to HowLongToBeat to request current completion-time information. This tells HowLongToBeat which title is being looked up, and HowLongToBeat processes that request under its own privacy practices. Inside Steam's embedded browser, lookup uses the packaged snapshot and the title is not sent to HowLongToBeat.
Successful network responses, the requested title, Steam App ID, and extension preferences are stored locally in browser extension storage. Cache retention is configurable to 1, 7, or 30 days. An expired entry may remain locally as a stale fallback until it is replaced or the user clears the cache. Steam artwork is displayed from its existing HTTPS URL and is not stored by the extension. Users can clear cached game data from the extension popup.
The data is used only to display completion times and operate settings and cache. It is not used or transferred for advertising, profiling, credit decisions, or sale. Use of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Permissions
- Storage: stores preferences and cached completion times locally.
- Steam game-page content scripts: read the public game identifier, title, and existing artwork and display the card only on declared Steam
/app/*pages. - Access to howlongtobeat.com: requests current completion-time data.
- Declarative network request with host access: applies required request headers only to the HTTPS HLTB search endpoints.
Contact
For privacy questions, use the project's support page. Security reports should follow the private process in the Security Policy.