Chrome Extension Disclosure and Limited Use Policy

SteamHelper's single purpose is to help Steam users understand and manage Steam inventory, market, favorites, alerts and trade-related information directly on Steam pages. The extension adds visible, user-facing functionality such as price badges, inventory value, item comparison, favorite buttons, alert controls, trade-offer context and optional Steam account utilities.

The extension does not exist to collect unrelated browsing history, run background advertising profiles, sell data or monitor websites unrelated to the declared SteamHelper functionality.

SteamHelper requests storage so settings, account state and feature choices can persist locally in the browser. It requests identity so the extension can use the browser's extension redirect URL during Steam OpenID sign-in. It requests cookies so the background service can read selected Steam session cookies for user-facing Steam features that cannot work from an isolated content script.

SteamHelper requests alarms and notifications so price alerts and optional gift checks can wake the Manifest V3 service worker and notify the user. It requests declarativeNetRequest because specific Steam trade-offer actions require first-party Origin and Referer headers that a service-worker fetch cannot set directly. Host permissions are limited to the SteamHelper API, the extension redirect origin, Steam Community, the Steam Web API and a currency-rate endpoint used for price context.

The extension may process the Steam page content needed for its visible features, including item names, market hash names, app ids, context ids, asset ids, class ids, instance ids, listing context, selected inventory entries, trade-offer identifiers, profile identifiers and price lookup requests. If you sign in, it processes your SteamID64, public Steam persona data and SteamHelper session state.

Data is transmitted to the SteamHelper backend only where needed for a feature such as authentication, favorites, alerts, notification settings, item pricing, inventory value or account-bound state. Data may also be sent to Steam or Steam Web API endpoints when the extension performs a user-facing Steam-related request through your browser session.

For Chrome Web Store disclosure purposes, SteamHelper may handle personally identifiable information, authentication information, location, web browsing activity, user activity and website content. Location refers to technical metadata such as IP addresses in website, API, hosting, CDN, security and abuse-prevention logs; SteamHelper does not collect GPS coordinates or precise device location.

SteamHelper does not intentionally collect health information, payment card details, bank account details, creditworthiness data, private messages, emails, SMS, chat contents or unrelated personal communications.

SteamHelper uses extension user data only to provide or improve its single purpose. We do not sell extension user data, do not transfer it to advertising platforms or data brokers, do not use it for personalized advertisements and do not use unrelated web browsing activity for monetization.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Humans do not read individual user data unless the user asks for support and access is necessary, access is necessary for security or abuse prevention, the data is aggregated and anonymized for internal operations, or access is required by law.

SteamHelper does not use remote code. Executable extension code is packaged in the uploaded extension file. API responses from SteamHelper, Steam, Steam Web API and other declared hosts are treated as data for user-facing features, not as code to execute in the extension.

SteamHelper does not ask for your Steam password and does not provide a fake Steam login form. Steam sign-in is handled through Steam OpenID and Steam's own website. If you choose to connect a Steam Web API key, the extension stores it in browser.storage.local and uses it in the background context for Steam API calls. Content scripts do not receive the key.

Users can disable optional features in the extension settings, sign out of SteamHelper, disconnect an optional Steam Web API key, clear extension data or uninstall the extension. Removing the extension stops its content scripts from running and removes the extension's ongoing access to browser extension APIs.

Questions about this extension disclosure can be sent to [email protected] or [email protected].