Trust

SteamHelper permissions explained

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.

Host access is scoped

SteamHelper needs access to supported Steam pages and SteamHelper services so it can render overlays, fetch product data and support account-bound features.

  • Steam Community and Steam Market pages
  • SteamHelper API
  • Steam Web API and selected supporting endpoints where needed

Storage supports settings and sessions

Extension storage is used for settings, authentication state, cached profile data and optional feature data. This helps the extension remember user choices.

  • Feature toggles
  • Cached public profile context
  • Optional user-bound feature data

Notifications and alarms are feature-specific

Notifications and alarms support price alerts and optional gift checks. They do not mean SteamHelper monitors unrelated browsing.

  • Price alert notifications
  • Manifest V3 service worker wakeups
  • Optional gift-only checks

Questions users ask before installing

Does SteamHelper request access to every website?

No. SteamHelper is scoped to supported Steam and SteamHelper surfaces rather than every website the user visits.

Why does storage matter?

Storage lets SteamHelper remember settings, session state and optional feature data inside the browser extension.