StakeClaimer

Is StakeClaimer Safe? Script Permissions, Data Flow and Password Access

StakeClaimer does not ask for your Stake password, card details, wallet keys, or raw cookie values. It uses your existing logged-in Stake tab; review the exact permissions and data flow before installing.

Review exact permissions Install StakeClaimer

What the script can do

  • Read the Stake page you are logged into so it can confirm your username.
  • Connect to the StakeClaimer relay to receive Telegram code drops.
  • Submit bonus codes and auto reload claims from your open Stake tab.
  • Open StakeClaimer pages for trial, subscription, support, and updates.

Data used for the service

  • A random first-run install id.
  • Periodic presence data that may include Stake username, script version, region, subscription tier, and readiness metrics.
  • General reliability timing and error categories.
  • Subscription and payment metadata described on the privacy page.

Data not requested in the script

  • Stake password or two-factor authentication code.
  • Raw browser cookies or session-token values.
  • Wallet keys or seed phrases.
  • Payment card details.
  • Bonus codes or raw Telegram messages in diagnostic beacons.
Version-bound reviewReviewed against StakeClaimer v1.9.24
View changelog

Exact userscript permissions

The values below are read from the userscript metadata used by this website build instead of being maintained as a separate manual list.

Declared @grantWhy StakeClaimer uses it
unsafeWindowUse the Stake page's own application context for account and claim integration.
GM_infoRead the installed userscript name and version for update and diagnostic display.
GM_setValueStore local StakeClaimer settings and installation state.
GM_getValueRead those locally stored StakeClaimer settings.
GM_xmlhttpRequestConnect to the StakeClaimer relay and approved service endpoints.
GM_openInTabOpen official trial, pricing, support, and update pages when requested.

@run-at document-idle ยท @noframes

View exact @match rules (66)
  • https://stake.com/settings/offers*
  • https://stake.com/*/settings/offers*
  • https://stake.ac/settings/offers*
  • https://stake.ac/*/settings/offers*
  • https://stake.games/settings/offers*
  • https://stake.games/*/settings/offers*
  • https://stake.bet/settings/offers*
  • https://stake.bet/*/settings/offers*
  • https://stake.pet/settings/offers*
  • https://stake.pet/*/settings/offers*
  • https://stake.mba/settings/offers*
  • https://stake.mba/*/settings/offers*
  • https://stake.jp/settings/offers*
  • https://stake.jp/*/settings/offers*
  • https://stake.bz/settings/offers*
  • https://stake.bz/*/settings/offers*
  • https://stake.ceo/settings/offers*
  • https://stake.ceo/*/settings/offers*
  • https://stake.krd/settings/offers*
  • https://stake.krd/*/settings/offers*
  • https://staketr.com/settings/offers*
  • https://staketr.com/*/settings/offers*
  • https://stake1001.com/settings/offers*
  • https://stake1001.com/*/settings/offers*
  • https://stake1002.com/settings/offers*
  • https://stake1002.com/*/settings/offers*
  • https://stake1003.com/settings/offers*
  • https://stake1003.com/*/settings/offers*
  • https://stake1004.com/settings/offers*
  • https://stake1004.com/*/settings/offers*
  • https://stake1005.com/settings/offers*
  • https://stake1005.com/*/settings/offers*
  • https://stake1021.com/settings/offers*
  • https://stake1021.com/*/settings/offers*
  • https://stake1022.com/settings/offers*
  • https://stake1022.com/*/settings/offers*
  • https://stake1067.com/settings/offers*
  • https://stake1067.com/*/settings/offers*
  • https://stake1069.com/settings/offers*
  • https://stake1069.com/*/settings/offers*
  • https://stake.us/settings/offers*
  • https://stake.us/*/settings/offers*
  • https://stake.br/settings/offers*
  • https://stake.br/*/settings/offers*
  • https://stake.com/*
  • https://stake.ac/*
  • https://stake.games/*
  • https://stake.bet/*
  • https://stake.pet/*
  • https://stake.mba/*
  • https://stake.jp/*
  • https://stake.bz/*
  • https://stake.ceo/*
  • https://stake.krd/*
  • https://staketr.com/*
  • https://stake1001.com/*
  • https://stake1002.com/*
  • https://stake1003.com/*
  • https://stake1004.com/*
  • https://stake1005.com/*
  • https://stake1021.com/*
  • https://stake1022.com/*
  • https://stake1067.com/*
  • https://stake1069.com/*
  • https://stake.us/*
  • https://stake.br/*
View exact @connect domains (25)
  • relay.stakeclaimer.net
  • stakeclaimer.net
  • stake.com
  • stake.us
  • stake.ac
  • stake.games
  • stake.bet
  • stake.pet
  • stake.mba
  • stake.jp
  • stake.bz
  • stake.ceo
  • stake.krd
  • stake1001.com
  • stake1002.com
  • stake1003.com
  • stake1004.com
  • stake1005.com
  • stake1021.com
  • stake1022.com
  • stake1067.com
  • stake1069.com
  • stake.br
  • staketr.com
  • challenges.cloudflare.com

Broad https://domain/* match rules allow StakeClaimer to run on any supported page. Settings > Offers is optional.

Data flow: Telegram relay to your Stake tab

  1. Monitored Telegram channelAn eligible Stake-related message reaches the StakeClaimer relay.
  2. StakeClaimer relayThe relay publishes the eligible event and subscription authorization to connected browsers.
  3. Your browser scriptThe userscript receives the event and checks the matching region, login state, and access level.
  4. Your open Stake tabThe browser submits through the existing logged-in Stake session.
  5. Result and diagnosticsThe panel shows the result; disclosed aggregate reliability categories may be reported without bonus codes or raw Telegram messages.

Related StakeClaimer guides