Device binding
Understand mandatory device verification and its practical security limits.
Each public ScriptBunker key is linked to one device when it is issued. The same key cannot normally be used from a different device, which helps prevent casual key sharing.
ScriptBunker does not show raw device identifiers to creators and does not permanently IP-lock a key. Device verification depends on what the executor can reliably provide, so it should not be described as unbreakable or guaranteed hardware identity.
A device mismatch means the key is already bound to a different device signal. The user should return through the loader's Get key flow. Creators can reset a bound active key from the current Keys UI; this keeps its expiration and lets the next compatible device bind it.