Reference

rubik slot Privacy Policy for Your Account

DANA, OVO, GoPay and QRIS records are handled alongside your account details under the rubik slot Privacy Policy.

Account dataWallet recordsCookie choicesAccess depends on local law
rubik slot rubik slot Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account Route

A clear contact route matters when a data request meets a login or wallet-status issue.

Account access If you cannot sign in to ask about your Privacy Policy rights, contact support…
Wallet record For a DANA, OVO, GoPay or QRIS data question, send the payment reference and…
Change request To request a correction, deletion or copy of personal data, state the exact account…
DATA PRACTICE

What Our Privacy Process Covers

We keep the Privacy Policy practical by linking each data use to an account action you recognise.

Collection

We collect account details during the clear account path, including your phone number and verification status. We also receive payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity so the account record can show the correct status.

Cookies

Cookies and similar device storage can remember sign-in preferences, session choices and security signals. You can manage cookie settings in your browser, although switching them off may require another account step before the mobile lobby opens.

Account security

We use phone verification before account access and examine sign-in signals such as device type, browser details and unusual location changes. Never send a password or wallet PIN through support; our Privacy Policy does not require those secrets for a data request.

Retention

We retain account, payment and security records for the period needed to provide account servicing, resolve a receipt question, meet legal duties or investigate misuse. When a purpose ends, our process removes or anonymises the record where applicable.

Your request

You can ask what personal data we hold, request a correction, seek a copy or ask whether deletion is available. Include your account identifier and the specific request; we may verify your identity before releasing or changing any record.

Regional access

Eligibility and access handling depends on local law. If you connect from Denpasar, Yogyakarta or another Indonesian location, regional checks may affect which account actions are available, and support can explain the data step involved.

Privacy Policy Answers For rubik slot

These Privacy Policy answers cover the searches we hear most often before an account is opened or a data request is sent. We focus on account access, wallet references, cookies, device records and the contact steps used by Indonesian customers. If your question is not listed, use the support route and identify the record or account action involved.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, security events, game activity and payment references. It explains why we use each category, how retention works, and how you can request access, correction or deletion where applicable.

We use your phone number to create and locate your account, complete the phone verification step and help prevent unauthorised access. It can also help support identify the correct account when you ask about a DANA, OVO, GoPay or QRIS record.

Yes. The Privacy Policy includes payment references and status details linked to DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account references. We use these details to match an account transaction and handle receipt or status questions without requesting your wallet PIN.

Use the support contact path in your account area and state that you want a copy of your personal data. Add your registered phone number or account identifier and describe the records requested. We may complete an identity check before sending data.

You can request a correction or ask whether deletion is available for a specific record. We first confirm the account and explain any retention duty, security need or legal exception that prevents immediate removal. Access and eligibility depends on local law.

We may store device type, browser details, session signals, approximate region and security events connected with account access. These records help us recognise unusual sign-ins and keep the mobile path safe. They are handled for the purposes described in the Privacy Policy.

We keep data for as long as it is needed for account servicing, payment matching, security checks, dispute handling or legal duties. After the relevant purpose ends, records are removed or anonymised under our retention process where applicable.