Reference

game slot Privacy Policy: Your Data Path

Our Privacy Policy shows what we collect when you open a game slot account, use the mobile lobby from Denpasar, or check wallet status through DANA, OVO, GoPay…

Clear data purposesWallet record detailsRequest steps
game slot game slot Privacy Policy: Your Data Path
CONTACT ROUTES

Three Ways To Raise A Privacy Question

A clear request helps us find the right account record without asking you to send unnecessary details.

Account data request Ask us to locate the personal data linked to your account. Include your registered contact detail and the specific record you want us to check, such as sign-in activity or a verification entry. We will use an account step to confirm that the request concerns you.
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, tell us the date, amount and wallet name without sending a full credential. We can compare the reference with the account ledger and explain what was recorded for that transaction.
Correction or deletion Use the privacy contact route when your name, contact detail or other eligible record needs correction or removal. We will explain any identity check and tell you if a transaction or security record must remain under local legal requirements.
HANDLING DETAILS

How game slot Handles Personal Data

We keep the privacy process practical: collect the details needed for an account action, limit access to people handling that action, and retain records only for a stated operational, security or legal…

Account details

We use your submitted contact and verification details to create the account, confirm an account action and respond to a privacy request. Before we disclose account-specific data, we may compare the request with the account step used at sign-in.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are handled as transaction references rather than as a reason to request your full wallet credential. We use matching details to trace payment status and answer a cashier-related question.

Cookies and sessions

Our browser storage can keep a session active, remember a language or display choice and help detect repeated sign-in failures. You can manage cookie settings in your browser, though limiting essential storage may interrupt login or return you to the account step.

Security signals

Device type, browser details, approximate connection data and sign-in events can help us identify unusual access. We use these signals to protect your account and may ask you to verify ownership before changing contact details or discussing records.

Retention choices

We separate records that support an active account from records kept for transaction tracing, fraud prevention or legal duties. When you request deletion, we check whether a record can be removed or must stay for one of those reasons.

Request changes

You can ask us to access, correct or delete eligible personal data through the privacy contact route. State the account detail concerned and the change you want; we will confirm the identity step, scope and any limit that depends on local law.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. If your situation is not covered, use the privacy contact route and describe the account step, device path or payment reference involved. We will keep the response focused on your data and the request you made.

We may collect account details you submit, verification records, device and browser signals, cookie settings, support messages and transaction references. This can include activity connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use, without requiring your full wallet credential.

Payment references let us match a deposit or account transaction to the correct account and investigate a status question. The Privacy Policy covers these records because they can relate to you, even when the underlying wallet or bank service handles the payment itself.

Yes, you can ask for a copy of eligible personal data through the privacy contact route. Include your registered contact detail and describe the records requested, such as sign-in events, cookie choices or a QRIS reference. We may verify account ownership first.

Send a correction request through the account help route and identify the field that is wrong. We may ask you to complete an account verification step before changing contact or verification data. Requests and available remedies depend on local law and the record involved.

Retention depends on the type of record and its purpose. Active account details support account access, while transaction, security and legal records may remain when needed for tracing or compliance duties. If you request deletion, we explain which records can be removed.

Essential session storage can keep you signed in while moving from a mobile login to the lobby, and other cookies can remember selected settings. You can limit optional cookies in your browser, but blocking essential storage may require another account step.

Yes. Requests to access, correct or delete personal data depend on local law, and some transaction or security records may need to remain. We will explain the identity check, available scope and reason for any restriction when we respond to your request.