Reference

ziatogelslot Privacy Policy For Your Account

ziatogelslot Privacy Policy explains what we collect when you create an account, verify your phone, enter the lobby from a mobile device in Jakarta, or use DANA and…

Account dataWallet recordsCookie choicesSecurity controls
ziatogelslot ziatogelslot Privacy Policy For Your Account
REQUEST HELP

Privacy Contact Routes Beside Your Account

A clear contact path matters when a Privacy Policy question affects your account or wallet record. We ask you to send the account identifier connected to the request, describe the change you need and avoid sharing a password or one-time verification code. From Jakarta or elsewhere in Indonesia, use the support route shown beside the cashier area so we can connect the request with the right account record.

Team online

Account privacy request

Use the account support route to ask what personal data is linked to your profile, explain the request clearly and provide the contact detail used during phone verification.

Wallet record question

For DANA, OVO, GoPay or QRIS records, include the payment reference and approximate date. We use those details to locate the relevant status without asking for your wallet password.

Security concern

If a login or device event looks unfamiliar, report it through the account help path beside the cashier. Do not send passwords, PINs or one-time codes in your message.

DATA CONTROL ROOM

Privacy Safeguards From Login To Wallet

We handle Privacy Policy requests as account operations, not as a general lobby question.

Collected account details

We may receive your name or contact detail, phone verification result, login history, device information and messages you send to…

Cookie operation

Cookies can keep your session active, preserve a selected setting and help us locate technical errors.

Wallet matching

DANA, OVO, GoPay, QRIS and bank transfer references are used to match a payment status with the correct account request.

Login protection

Phone verification and device signals help us identify unusual account access.

Retention approach

We retain account, payment and support records for the period needed for service operation, security checks, dispute handling or a…

Change or deletion request

Ask us to correct, access or remove eligible personal data through the support route.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the practical searches we receive before an account is opened or a wallet is connected. We keep the route specific: identify your account, name the data involved and use the support path shown in your account area. Access remains where local law permits.

It covers account and contact details, phone verification, login and device events, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the verification result to support account access and help identify unusual login activity. It also gives us a way to check that a request to change account data comes from the account holder.

Yes. The policy explains that QRIS, DANA, OVO and GoPay references can be retained to match payment status with the right account, investigate a missing receipt and respond to a specific support request.

Send the request through the account support route, identify the contact detail used for verification and name the record you want reviewed or corrected. We may verify account control before responding.

Your browser may let you remove or restrict cookies. Some session or preference functions may then require another login, while technical records needed to protect account access can still be processed.

We keep account, payment and support records only for the period needed for service operation, security, dispute handling or a legal request, then remove or restrict them under our retention process.

Use the support route displayed beside your account and cashier area. Include your account contact, the data category involved and any relevant DANA, OVO, GoPay or QRIS reference, without sending passwords or codes.