Reference

Privacy Policy for Your olo4d Account

We built this Privacy Policy so you can see exactly what we collect, why we need it, and how it supports account access, payment checks, and help requests.

DANAOVOGoPayQRIS

Browse Lobby Read FAQ

What This Policy Covers in Indonesia

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

We collect the minimum data needed to run your account, match deposits, and handle identity checks when the request needs it. If you use DANA, OVO, GoPay, or QRIS, we may keep the reference code, time stamp, and amount so a payment can be matched to

1
the right account; we do not need more than that to complete the record. Device data, browser type, and login logs help us spot unusual access and keep your session stable on Android Chrome, iPhone Safari, and desktop browsers. When you move between slots and live
2
tables, the same cookie rules apply. We keep records only for as long as needed for support, fraud checks, and legal retention duties, then we remove or de-identify them. If you want to ask about your data, send the request through the contact paths below and
3
we will work from the details you provide, subject to local law and available only where local law permits.

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

CONTACT PATHS

How to Contact Us About Data

When you need a change to your data record, we keep the contact path simple and traceable. Send the request from the address or phone tied to your account, and include the exact field you want corrected or removed. We handle messages in English, and our team works from 09:00-21:00 WIB, with faster replies during local business hours. If you are in Surabaya or Jakarta, the same channels apply.

Team online

Email

Send the request from your registered email with your username, phone number, and the exact change you want. We use that match to protect the account before any data update is made.

Use WhatsApp for a quick privacy check when you need to confirm what we store or how to correct it. Replies run 09:00-21:00 WIB, and we may ask for a recent login time.

In-Site Form

The in-site form works well when you want a written trace. Add a clear subject, a screenshot if needed, and the account detail involved so we can process it without back-and-forth.

DATA SAFETY

How We Handle Data and Access

We treat privacy as an account-control job, not a slogan. Cookies keep your session signed in while you move between pages, and device signals help us spot risky logins without asking you…

Data Use

We use account, contact, and payment reference data to verify you, match records, and answer a request. We do not ask for more than the task needs, and we keep the purpose tied to the account action you requested.

Cookies

Cookies remember your login state, language choice, and the page you last used. On Android Chrome, iPhone Safari, and desktop browsers, that helps the session stay stable without exposing more personal data than needed.

Security

We protect access with password checks and session controls, and we may ask you to confirm a phone number or a recent activity detail before any sensitive change goes through.

Retention

We keep logs, payment references, and support messages only as long as they are needed for service, dispute handling, or legal duties, then we remove or de-identify them.

Requests

If you want a copy, correction, or removal request, tell us the exact account field involved and send it from a verified contact path so we can identify the right record quickly.

Contact

Questions about this policy go to our email, WhatsApp, or in-site form. We read those channels during 09:00-21:00 WIB and use the same process for Indonesia wherever local law permits.

Questions About Your Data and Access

These are the questions we hear most when you want to know what we store, how long we keep it, and how to ask for a change. Each answer below points you to the exact step we use: verified contact, account match, and a clear description of the field involved. If local law affects a request, we will say so before we proceed. That keeps the process clear when you are using mobile or desktop.

We keep the details needed to create and verify the account, such as your contact channel, login history, and payment references when you use DANA, OVO, GoPay, or QRIS. We do not collect extra data just because it is available.

Send the request from your registered email or WhatsApp number, name the exact field you want changed, and include any proof that helps us match the record. We check the account before making the update.

We store device and browser signals to keep sessions stable and to spot unusual access. On Android Chrome, iPhone Safari, and desktop browsers, that data helps us protect the account without changing how you use it.

We keep data only for the period needed for support, verification, payment matching, dispute handling, and legal duties. After that, we remove it or reduce it to a form that no longer identifies you.

Yes. Ask through email, WhatsApp, or the in-site form, and we will tell you what we can share from the verified account record. Some parts may stay restricted if local law requires it.

Yes. Any access or eligibility step depends on local law and is available only where local law permits. If a request touches a restricted area, we will explain the limit before we move forward.

Privacy Policy for Your olo4d Account

How to Contact Us About Data

Email

WhatsApp

In-Site Form

How We Handle Data and Access

Data Use

Cookies

Security

Retention

Requests

Contact

Questions About Your Data and Access

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

02 How do I ask for a data change?

03 Do you keep my device data?

04 How long do you keep my data?

05 Can I ask what you store about me?

06 Does access to the service depend on local law?

Related Pages