Browser extension permissions can look intimidating. SteamHelper's permission model should be explainable: every permission exists to support visible Steam inventory, market, alert or account workflows.
SteamHelper needs access to supported Steam pages and SteamHelper services so it can render overlays, fetch product data and support account-bound features.
Extension storage is used for settings, authentication state, cached profile data and optional feature data. This helps the extension remember user choices.
Notifications and alarms support price alerts and optional gift checks. They do not mean SteamHelper monitors unrelated browsing.
No. SteamHelper's host access is limited to Steam Community, the Steam Web API, SteamHelper's own API and a few declared service hosts. It cannot read other websites you visit.
SteamHelper uses your existing Steam session so features like the in-app trade offer list can talk to Steam on your behalf. Cookie access is limited to the hosts SteamHelper declares, not other websites.
Storage keeps your settings and sign-in state. Alarms let the background worker run scheduled checks for price alerts and the optional Gift Auto Accept, and notifications tell you when an alert fires.
It opens Steam's official sign-in page in a secure browser window for the optional Steam login. SteamHelper never sees your password; it only receives a session token after Steam confirms who you are.
