Reference

Open with supraslot Privacy Policy

supraslot Privacy Policy gives you a clear view of how we handle account details, wallet records and device signals when you access Live Roulette Diamond, Live Dragon Tiger…

Account dataWallet recordsDevice accessYour requests
supraslot Open with supraslot Privacy Policy
CONTACT PATHS

Browse your Privacy Policy contact routes

A clear contact route matters when a wallet reference, phone check or device record looks unfamiliar. We ask you to start from the account support path and include the email or phone detail connected to your account, plus the relevant DANA, QRIS, OVO or GoPay reference where one exists. That lets us locate the right record without asking you to send a password or full wallet credentials.

Team online

Account access

Use the account support path when you need to ask what personal data is linked to your supraslot account or why phone verification is required before access. We may request account identifiers to confirm that the request comes from you.

Wallet records

For a DANA, OVO, GoPay or QRIS data question, provide the transaction reference and date rather than your wallet password. We use those precise markers to check the record and explain what we retain for payment matching.

Privacy requests

Ask us to access, correct or remove eligible account data through the same support route. We may first confirm your identity, then reply with the action taken, any reason a record must remain and the next available step.

DATA PRACTICE

Switch through our privacy handling steps

We keep this policy practical by connecting each data use to an account action you recognise.

Data collected

We may receive your account name, contact detail, phone verification result, sign-in history, device signals and payment reference. We collect these items when they are needed for account access, wallet matching, support handling or security checks.

Cookie choices

Cookies can remember a session setting and help us see whether a page works as intended. You can adjust cookie controls in your browser, although restricting them may affect sign-in continuity or the way the Privacy Policy page loads.

Account security

We do not ask you to share a password in a support message. Phone verification and sign-in checks help us distinguish your account request from an unfamiliar device, while payment references remain separate from secret wallet credentials.

Retention timing

We keep account and payment references while they support access, dispute handling, fraud checks or legal duties. When a record no longer serves one of those purposes, we delete it or reduce its link to your account.

Your corrections

If your contact detail or account record is inaccurate, tell us which field needs attention and why. After confirming your identity, we can correct eligible data and explain any connected record that cannot be changed immediately.

Request handling

Send privacy questions through account support with enough context for us to find the record. We may ask for a verification step, then explain whether we accessed, corrected, removed or retained the requested data.

Open answers about Privacy Policy

These Privacy Policy answers address the questions we expect you to have before creating an account or checking wallet activity. We keep the wording tied to real account steps: phone verification, mobile sign-in, payment references and the support route. If a question depends on eligibility or location, access depends on local law.

It covers data connected with your account, phone verification, sign-in device, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains our purposes, retention approach and the way you can request access or correction.

Phone verification helps us confirm that an account access request belongs to you and helps identify unusual sign-ins. We record the verification result for that security purpose, not your wallet password. We may ask you to repeat the check when a device or account detail changes.

Yes. The Privacy Policy covers references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity when those references help match an account event. We use the reference and related status for checking, support or dispute handling rather than storing secret wallet credentials.

Use the account support path and state that you are making a Privacy Policy data request. Include the account contact detail and the record you want us to locate. We may confirm your identity before sharing eligible data, so your account details are not disclosed to another person.

Yes. Tell us which account field is incorrect and provide the corrected value through support. We may verify your identity before making the change. If a payment or security record must remain for dispute or legal reasons, we will explain why that connected record cannot be removed.

We retain data while it is needed for account access, phone verification, payment matching, security checks, support history, disputes or legal duties. When those purposes end, we remove the record or reduce its connection to you according to our operational retention process.

Access and eligibility depend on local law. If you are checking the Privacy Policy from Indonesia, contact support through your account path with your location and request. We will explain the available handling for your account and will not ask you to bypass a local restriction.