Privacy and storage information

Verified operator identity, registered address, registration details and support/privacy contacts have not yet been published. This information is incomplete. No licensed gambling service or prize promotion is offered in this demo.

Depending on your sign-in method, the service stores account identifiers, display name, avatar, email, password hash or linked Steam/Google identifier, self-declared country/region and adult status. It records terms acceptance, sessions, security events, two-factor settings, game actions, virtual balance ledgers, play restrictions, and staff actions. Display names, avatars and public game results may be visible to other players. Never put sensitive information in your public name.

These records support sign-in, account security, shared games, balance reconciliation, fraud prevention, account restrictions and dispute investigation. A future real-value product would need a separate assessment of legal bases, identity checks and disclosures before collecting verification documents. The demo does not ask you to submit identity documents or a postal-entry address.

The essential skinstake_session cookie identifies a server session and expires after up to 30 days. Sign-in and security flows may use temporary cookies. Local storage remembers currency, sound and game preferences, panel placement, and pending game commands so a retry does not duplicate an action. Clearing browser storage does not erase your server records or lift account restrictions.

Selected sign-in services receive information when you use them. Transactional email, hosting and infrastructure providers process data needed for their services. Loading remotely hosted avatars or game images can disclose your IP address to that host. The operator must publish the actual processor list, hosting/transfer locations, applicable safeguards and legal bases before treating this notice as complete.

Account, game, ledger and security records are stored on the server. A complete retention/deletion schedule and operational access, correction, export, objection and deletion process have not yet been published. Removing local storage or signing out does not delete them. Play-restriction records need protection against circumvention; retention must still be reviewed against applicable privacy law. Use the verified privacy contact above once published; do not send identity documents through public chat.

Payment and identity integrations are disabled by default. Authorized developers may deliberately open a provider sandbox. These requests share an internal reference with Breeze or payabl., or an account reference with Sumsub; the provider also receives connection information when its page or verification frame loads. Sandbox tests must use test identities and test payment details. Skinstake stores minimal order, applicant-status and callback receipts, not card numbers, document images or biometric records. Simulated identity results expire after two hours and never count as genuine verification. No provider frame loads simply by browsing games or the wallet.