Reference

Open rubikslot Privacy Policy for Your Data

rubikslot Privacy Policy shows how we handle account details, device signals and wallet records while you use our Indonesia-facing service.

Account dataWallet recordsCookie choicesAccess requests
rubikslot Open rubikslot Privacy Policy for Your Data
REQUEST HELP DIRECTLY

Contact us about your privacy requests

A clear contact path helps when you want to ask about account data, a cookie choice or a wallet record.

Account data request Ask us to locate the data connected with your account, including phone verification details…
Wallet record question If a DANA, OVO, GoPay or QRIS receipt appears unclear, contact support with the…
Cookie choice support Tell us if you want help changing cookie settings on your phone or desktop…
HOW DATA IS HANDLED

Check how rubikslot handles account data

We keep this Privacy Policy practical: each data use connects to an account action, security need, support request or legal duty.

Account details

We use the account details you provide to create your sign-in record, complete phone verification and respond to account requests.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account step can create a payment reference and status record.

Device signals

Your browser, device type, session time and security events may be recorded to protect account access.

Cookies and choices

Cookies can keep a selected setting in place and show us whether a policy page is being opened correctly.

Retention periods

We keep account, payment and security records only for the period needed for support, disputes, fraud checks and applicable legal…

Changes and contact

If your details change or you want to question our data use, contact us through account help.

Browse Privacy Policy questions before opening

These Privacy Policy answers cover the points you are most likely to check before creating an account from Indonesia. We explain what we collect, why wallet records appear, how cookies work and how to reach us when you want a data change.

It covers account details, phone verification, device and session signals, cookies, payment references, support requests, retention and your available data requests when you use rubikslot where local law permits.

We use phone verification to connect an account access request with the correct account and reduce mistaken or suspicious sign-ins. We may use the verified detail when confirming a privacy request.

Yes. The Privacy Policy covers payment references and status records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps, so we can match receipts and resolve account questions.

We may record device type, browser settings, session time, approximate connection data and security events. These details help us investigate unusual access and keep account sessions safer without reading personal messages.

Use the support contact route inside your account help area and state whether you want access, correction or deletion. Include your account email or verified phone detail so we can confirm the request.

Yes. Use your mobile browser settings to limit or remove cookies, or contact support for help understanding the available choices. Some sign-in or preference steps may behave differently afterward.

We retain records for the time needed for account support, payment disputes, security checks and applicable legal duties. Where local law permits, you can ask us about a particular record or retention reason.