Reference

How Privacy Works Here

We keep privacy details tied to the account you open, so you can see what we collect before you add DANA, OVO, GoPay, or QRIS records.

Account dataCookie useSession logsLocal law
bukit777 How Privacy Works Here
CONTACT PATHS

Where You Can Reach Us

The fastest privacy request is the one sent through the account path already linked to your profile, because we can verify it without asking for extra…

Live chat Open live chat from your account area when you want a copy of stored…
Email request Send the request from the email linked to your account if you want a…
Privacy form Use the form in our help area when you want one ticket for the…
RECORD HANDLING

How We Handle Records

We treat privacy as record handling, not decoration. Collection stays limited to login, payment, device, and support data; cookies keep your session and language choice stable; and logs help us see whether…

What we collect

We keep the data that helps identify your account and handle requests: name, contact details, login time, device type, browser, language setting, and payment references tied to DANA, OVO, GoPay, or QRIS.

Cookies and session

Cookies remember your session and reduce repeated checks when you return on Android Chrome, iPhone Safari, or desktop. They also help the page keep your chosen language and the route back to your last screen.

Account security

We use login logs, device fingerprints, and time stamps to spot access from a new phone or browser. If something looks unusual, we may ask for a fresh account check before we change records.

Retention periods

We keep active account records while your account is open, then hold only what local law, payment disputes, or fraud checks require. After that, the extra copy is removed or archived under our retention rules.

Access and correction

If you spot a wrong name, number, or payment reference, send the correction from the account channel on file. We verify ownership first, then update the record where the law allows it.

Who to contact

For privacy requests, use live chat, the email path on file, or the form in the help area. That keeps the request tied to one ticket until we finish the check and reply.

Questions About Your Data

Before you send a name, number, or wallet trace, these are the questions we expect to hear. We answer in plain language so you can see what stays on file, what gets corrected, and when a record must remain for legal or dispute reasons. If your case includes DANA, OVO, GoPay, or QRIS activity, we keep the related trace with the same ticket.

We keep the details needed for login, verification, and request handling: name, contact fields, device type, browser, language choice, and payment references from DANA, OVO, GoPay, or QRIS when they appear in your case.

Cookies let us remember your session, keep the page state steady when you move between Live Casino, Slots, or Aviator, and reduce repeated checks after you return from another device.

Yes. Send a request from the email or account channel on file, and we will match it to your record before we send a copy or explain the legal reason if any part must stay.

Tell us what changed, attach the corrected field, and we will update the account where allowed. If a payment or security record must stay unchanged, we mark the request and keep the original for audit.

We keep active account data while your account is open, then retain only what local law, dispute handling, or fraud checks require. After that period, we remove or archive the rest.

Only staff who need it for account support, payment checks, safety checks, or legal requests can access it. We do not hand it out for marketing lists, and every access is logged.

If a request conflicts with local law, we cannot complete that part, but we will explain what we can share and what record must stay. The policy still applies only where local law permits.