Reference

How We Handle Your Data

From Jakarta to Yogyakarta, the same account rules apply: we keep login data, device stamps, and payment references from DANA, OVO, GoPay, and QRIS only as long as…

Browse Lobby Read FAQ

What This Policy Covers

ombak789 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This policy explains what we collect, why we collect it, how long we keep it, and when we share it for account checks or dispute handling. We use only the details needed to run sign-in, payment matching, fraud checks, and support replies. If you pay by

1
DANA, OVO, GoPay, or QRIS, we store the reference, amount, and result status so your account ledger stays matched. Cookies remember language, session state, and device settings. Session logs from live tables, slots, and sportsbook pages help us detect duplicate logins and protect disputes. For Indonesian
2
accounts, local law and the request path you choose can change what we can disclose or change. When you open a request from an account in Jakarta or elsewhere, we may ask for a fresh login or a one-time code before we change profile fields.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REACH US ANYTIME

How to Contact Our Team

If you want a copy of your data, a correction, or a check on a consent choice, you can reach us through in-account chat, email, or the privacy form after login. Chat stays open 24/7, while email requests are handled every day from 09:00-21:00 WIB. We keep one ticket thread so you do not repeat the same details when the request moves from intake to verification.

Team online

In-account chat

Open the help chat from your account dashboard any time. We use it for data access, correction, and deletion requests, and our team replies with a ticket number you can keep.

Email request

Send your privacy request from the registered email address so we can match it to the right account. We confirm receipt and return with the next step, usually the same day.

Privacy form

Use the privacy form after login when you need to update consent, cookie choices, or profile details. If extra verification is needed, we ask for the smallest proof set.

STORAGE AND ACCESS

How We Protect Records

We keep the privacy process narrow: only staff with a task can see your records, cookie choices stay tied to your browser, and account changes need a fresh login or code.

Data scope

We collect only account, device, and transaction details needed to verify logins, match deposits, and respond to privacy requests. We do not ask for extra fields when a simple account check is enough.

Cookies

Cookies keep your session alive, remember language choice, and save device settings between visits. You can clear them in your browser on Android, iPhone, or desktop, and we explain what may reset.

Account security

Password changes, one-time codes, and fresh login checks protect changes to phone number, email, or payout destination. If the request looks unusual, we pause it until you confirm control.

Retention

We hold logs and payment references only for the period needed for reconciliation, fraud checks, dispute handling, and legal duties. After that, we delete or anonymise records according to our internal schedule.

Access requests

You can ask for a copy of your stored data from the registered account. We answer through the same ticket thread and may ask for a recent login to confirm the request is yours.

Corrections

If your name, phone number, or email changes, send the request and we will update the record where local law permits. Any blocked change is explained with the reason and next action.

Common Privacy Questions You Ask

These are the questions we hear most when you want to check your data, change a detail, or close a request. We answer in the same thread so the record stays clear, and we may ask you to confirm control of the account before we change anything. If a request touches local legal duties, we explain what we can do and what we must keep.

We keep the details needed to create and secure your account: email or phone, login timestamps, device type, and the payment reference from DANA, OVO, GoPay, or QRIS. We avoid collecting extras that do not help with access or support.

Yes, but only the fields needed to reconcile deposits and withdrawals. That usually means the channel, reference number, status, and time stamp. We do not store wallet PINs or full token details, and we mask sensitive parts where our systems allow.

You can request updates to your phone number, email, and similar account details from the registered login. We may ask for a fresh code or recent session check before we edit anything that could affect access.

We keep records only as long as needed for security, payment matching, dispute handling, and legal duties. When the retention period ends, we remove or anonymise the data so it no longer identifies your account.

Cookies remember your session, language choice, and device settings so you do not have to reset them each time. You can clear them in your browser, though some pages may ask you to sign in again.

Only staff who need the record for support, verification, payments, or security checks can open it. Access is limited inside our team, logged, and checked when a request or incident needs a second look.

Send the request through chat, email, or the form inside your account, then confirm control of the registered contact. We will tell you what we can provide or change under local law.

How We Handle Your Data

How to Contact Our Team

In-account chat

Email request

Privacy form

How We Protect Records

Data scope

Cookies

Account security

Retention

Access requests

Corrections

Common Privacy Questions You Ask

01 What data do you collect when I open an account?

02 Do you keep my payment history?

03 Can I change my profile details?

04 How long do you keep my data?

05 Do cookies remember my device?

06 Who can see my account data?

07 How do I ask for a copy or deletion?

Related Pages