Player pairing and consent for developers
The player holds the switch.
- 1
Your game
Shows a pairing QR code on its webpage.
- 2
Player
Scans it in the Staminabar app.
- 3
Staminabar app
Displays your verified game and publisher.
- 4
Player
Taps Allow or Deny. Nothing flows before Allow.
- 5
Your game
Reads the nine attributes while the pairing is active.
- 6
Player
Can revoke anytime. Reads stop within 60 seconds.
60s
Revoke cutoff
Design for attributes disappearing. When a player revokes, your game stops receiving values within 60 seconds and should fall back to its default balance.
Pairing security
- / Pairing codes work once, expire after 5 minutes, and die after five wrong tries.
- / Your game server makes its own key pair. We only ever hold the public half.
- / Score requests are signed, with a 5-minute clock window and a replay check.
- / When a player removes access, reads stop within about a minute.
- Full security practices
Scores are game attributes, not health advice.
Developer access