Trust

SteamHelper safety: permissions, trades and user control

SteamHelper is built for players who want more context on Steam without handing over control. The extension keeps sensitive decisions visible and keeps its permission scope focused.

Password and account boundaries

SteamHelper does not ask for a Steam password. Steam sign-in uses Steam OpenID through the SteamHelper backend, and Steam credentials remain with Steam.

  • No Steam password form inside SteamHelper
  • Steam OpenID handles sign-in
  • Session-bound features stay tied to user-triggered workflows

Permission scope is explainable

SteamHelper is scoped to supported Steam and SteamHelper surfaces. It does not need permission to read every website a user visits.

  • Steam Community and Steam Market helpers
  • SteamHelper API access for account-bound features
  • Settings and cached context stored for visible product features

Actions stay visible

Important actions such as selling, trade review and settings changes remain review-first. SteamHelper provides context and shortcuts, but the user reviews the result.

  • Trade values are shown before acceptance
  • Selling queues can be inspected before posting
  • Users can disable helpers they do not need

Questions users ask before installing

Is SteamHelper affiliated with Valve?

No. SteamHelper is independent and is not affiliated with Valve Corporation or Steam.

Does SteamHelper use remote code?

No. Executable extension code is packaged in the uploaded extension. API responses are treated as data for user-facing features.