Reference

Open kudaliarslot Privacy Policy for Indonesia

We keep the Privacy Policy close to the account flow so you can see what we collect before you open an account or use DANA, OVO, GoPay, or…

Account dataCookie useRetentionDANAQRIS
kudaliarslot Open kudaliarslot Privacy Policy for Indonesia
CONTACT PATHS

Browse the ways to reach us

If you want to read, correct, or remove details, we keep three direct paths open: live chat, email, and an in-account ticket.

Live chat Use live chat for a fast privacy request when you need a copy of your data, a correction, or a question about cookies. We confirm your account before we share anything, so the request stays tied to you.
Email Send an email if you want a written trail for a change request. Include your username, the phone or email on file, and the exact detail you want adjusted so we can verify it without delay.
In-account ticket Open an in-account ticket from the same device you use to log in. That path is useful for removal, retention, or access questions, and it helps us match the request to your account record quickly.
SAFE HANDLING

Switch between data, cookies, and access

Our privacy handling is built around four things: the data you submit, the cookies that keep the session working, the account checks that protect changes, and the retention rules that stop records…

What we collect

We collect the details you enter at sign-up, login signals, and payment references from DANA, OVO, GoPay, or QRIS. We do not need extra fields that are not tied to account use or legal duties.

Cookies and devices

Cookies keep your session active, remember language choice, and help us spot unusual logins. When you switch from slots to live tables on Android Chrome or iPhone Safari, the same session rules apply until you log out.

Account security

When you change your password, phone number, or email, we ask for a verification code sent to the registered channel. That step protects your account from changes made by someone who does not own the login.

Payment records

Payment traces from DANA, OVO, GoPay, and QRIS are kept with the account record for reconciliation and dispute handling. We use those references only for the transaction path, not for unrelated messaging or extra profiling.

Retention window

We keep records only as long as needed for support, security, and legal duties. After that, we remove or anonymise them where the law allows, so old access logs do not stay forever in active storage.

Your requests

You can ask to read, correct, or delete certain records, and we will process the request when local law permits it. Use live chat, email, or an account ticket so we can verify you first.

Open common Privacy Policy questions

These answers cover the parts we hear about most: what data we collect, how cookies work, how long we keep records, and how you can ask for a correction or deletion. If local law limits a request, we follow that law and only process it where local law permits. For faster verification, use the same email, phone, or browser session tied to your account.

We collect the details you submit for the account, the device and browser signals that protect sign-in, and payment references from DANA, OVO, GoPay, or QRIS. If local law limits a request, we handle it only where local law permits.

Cookies keep you signed in, remember your language choice, and reduce repeated checks when you move between phone and desktop. You can clear them in your browser, but some privacy settings may change how the page remembers you.

Yes. Send the correction request through live chat, email, or an in-account ticket, and include the exact field you want updated. We verify your account first so the change reaches the right record.

We keep privacy records only as long as needed for account security, dispute handling, and legal duties. After that, we remove or anonymise them where the law allows, so old logs do not stay active without a reason.

Only staff who need the data to run the account, handle a request, or meet legal duties can see those records. Payment references stay limited to transaction checks and are not used to build unrelated contact lists.

Yes. The same privacy terms apply when you use Android Chrome, iPhone Safari, or desktop browsers. The device may change the session length or cookie behaviour, but the data rules stay the same across screens.

Use live chat, email, or the in-account ticket. If you send from the same browser or phone tied to your account, we can verify the request faster and start the process without unnecessary back-and-forth.