Reference

slot demo Privacy Policy for Your Account

Our Privacy Policy explains how slot demo handles the account, device and wallet details connected with Lightning Roulette, Gates of Olympus 1000 and the wider lobby.

Clear data choicesWallet detail checksMobile access clarityPolicy contact route
slot demo slot demo Privacy Policy for Your Account
CONTACT DATA CARE

Ask Support About Your Privacy Policy

Our support route is available for questions about the Privacy Policy, account records and wallet references. Include the email or phone number linked to your account, but never send a password, one-time code or full wallet credentials. We can use your account details to locate a request, check its status and explain the next step.

Team online

Policy questions

Use the support contact shown in your account when you need clarification about collection, storage or sharing. We will ask for an account detail so we can connect the reply to the right record.

Wallet record checks

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction date and masked reference through support. We use those details to check status without asking for your wallet password.

Account access help

For a privacy request after a login problem, tell us the phone verification stage and device type, such as Android browser or desktop browser. This helps us confirm ownership before discussing account data.

DATA HANDLING

Explore How We Handle Your Details

We keep the Privacy Policy connected to practical account steps rather than hiding it behind general wording.

Account details

We may collect your registration details, phone verification result and sign-in history to create and protect your account. We use only the account fields needed for access, support and transaction records.

Device signals

Your mobile browser or desktop browser can provide technical signals such as device type, session time and browser settings. These help us recognise unusual sign-ins and troubleshoot a blocked account path.

Cookie choices

Cookies and similar storage can keep a session active and remember selected settings. You can manage browser permissions, although changing them may require another login before reaching the lobby.

Wallet references

For QRIS, DANA, OVO, GoPay, bank transfer or virtual account activity, we retain matching references and status details. We do not need your wallet password to check whether a record belongs to your account.

Retention steps

We keep personal details only as long as needed for the stated account, security, dispute or legal purpose. When a retention period ends, deletion or restricted storage follows the applicable process.

Change requests

You can ask us to correct eligible details, explain a data use or request removal where local law permits. Send the request through support from your linked account so we can confirm ownership.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before account access. They explain what happens around phone verification, mobile browsing, local wallet references and requests for account changes, while the full policy remains the controlling text. If your situation is unusual, contact support with the smallest useful set of account details.

It covers account registration, phone verification, browser and device signals, support messages, wallet references, cookies, retention and requests to access, correct or remove eligible personal details.

Phone verification helps connect an account request to the person who controls the linked number. It also gives support a safer ownership check before discussing account data or changing access details.

Yes. The Privacy Policy covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, without requiring your wallet password.

You can contact support from the linked account and ask what eligible personal details we hold. We may verify ownership first, then respond according to the policy and applicable local requirements.

Send a correction request through the account support route, naming the affected field and the accurate replacement. For safety, do not include a password or one-time code in your message.

The policy may cover device type, browser settings, session timing and technical signals from your mobile path. These details help investigate sign-in issues and unusual access, not replace your account credentials.

You may request removal where local law permits. Some account, security or transaction records can remain when a legal duty, dispute or fraud-prevention need requires continued retention.