A userscript running in your browser is not automatically safe. Its permissions, code, update source and network access matter. This article provides checks to make before enabling a claimer; it is not an independent security audit or a guarantee about any release.
Review access, not just where the script runs
Browser-side code can interact with the page and account session according to its permissions. It may also communicate with external services. “Runs locally” does not prove that credentials cannot be read or transmitted. Review the installation source, the sites on which it runs and the requested permissions before enabling it.
Use the download links on the installation page. Treat an unexpected update source or an unexplained request for broader access as a reason to pause and ask for clarification. Check the changelog when reviewing an update.
Desktop and app setup are different
The desktop userscript uses a signed-in browser session. The app's session-import flow involves copying a session key, as described on the session-key page. That key is a login credential, not a read-only identifier. Import it only into the intended app on your own device; do not send it through chat, email or shared notes.
When reporting a problem, redact session keys, passwords and other credentials from screenshots and logs. Share the visible error and device details through the support options.
Security and platform permission are separate questions
Stake.com's terms, section 5.1(y), restrict software-assisted methods for participation in its games or services. Using the platform's API does not establish that third-party automation is permitted. Check the terms applicable to your platform and obtain clarification from Stake about your intended use; StakeClaimer cannot grant that permission.
Keep control of the installation
Know how to disable the script or app before using it. If you suspect credential exposure, stop using the tool and use the platform's account-security controls or support to secure the account. The product safety page provides additional implementation information, but product documentation does not replace verification of the version you install.