Reference

Open Our Privacy Policy

This privacy policy tells you what we collect, why we keep it, and how you can ask for a correction or removal where local law permits.

Account dataDevice logsCookiesLocal law

Browse Lobby Read FAQ

Browse What We Keep And Why

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

We keep this policy narrow: we collect only the details needed to open and secure your account, check local payment requests, answer support messages, and meet legal duties where local law permits. That can include your name, contact number, device type, browser session, and a record

1
of DANA, OVO, GoPay, or QRIS activity tied to your account. Cookies help us keep you signed in, remember language choice, and stop repeated verification steps. When you ask for a correction, we compare the request with the last verified account record before we change it.
2
We keep logs only as long as needed for support, dispute handling, and security checks, then remove or anonymise them when the hold period ends. If local law says a record must stay longer, we follow that rule and limit access to approved staff only.

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

ASK US DIRECT

Switch To Privacy Support

Fast contact matters when a privacy request is time-sensitive. You can reach us through live chat, WhatsApp, or email, and we ask for your account email plus one recent device detail so…

Live chat Use live chat when you need a quick privacy request logged against your account. We ask for your email and one recent device detail, then confirm the change path before we edit any record.

WhatsApp Send WhatsApp if you prefer a written thread on your phone. We use it to check identity, note the request type, and keep you updated when a correction or access request moves forward.

Email Email works well when you want a full record of the request. Include DANA, OVO, GoPay, or QRIS if the issue touches a payment record, plus the date and the field you want changed.

KEEPING DATA SAFE

Explore How We Protect Data

We design our handling around the least data needed for the job. Device sessions, cookie settings, payment matching notes, and support history sit in separate records so access is limited to staff…

Data Scope

We collect the name, contact detail, device type, session logs, and payment-matching records needed to open and secure your account. For DANA, OVO, GoPay, and QRIS, we keep only the reference needed to confirm the request.

Cookie Control

Cookies remember your language, signed-in status, and page path so you do not repeat the same steps. You can clear them in your browser at any time, though some saved settings will reset after that.

Account Safety

If a password reset, new device, or contact change looks unusual, we may ask for a quick verification step. This protects your record from edits that do not come from you.

Retention Window

We keep support logs and payment references only for the period needed to handle access, correction, and security checks. After that, we delete or anonymise them unless local law requires a longer hold.

Change Requests

Send the exact field you want changed and the replacement value. We compare it with the last verified record, then update the account once we confirm the request belongs to you.

Legal Access

When local law permits and a valid request arrives, we may share limited records with the right authority. You can ask what was shared, and we will explain the scope we are allowed to disclose.

Open Common Privacy Questions

These are the questions we hear most when you want to know what we store, why we ask for it, and how to request a change. The short version is simple: we keep account data only for the job it serves, we check requests before edits, and we rely on support channels that leave a clear record. If local law restricts a request, we tell you what we can still do.

We keep the details needed to open, secure, and service your account: name, contact number, device logs, and payment references tied to DANA, OVO, GoPay, or QRIS. We do not keep more than the request needs.

Cookies help us keep you signed in, remember language settings, and save the path you used. That cuts repeat steps on mobile and desktop browser, and you can clear them whenever you want.

We keep records only as long as needed for support, verification, security checks, or legal hold periods. After that, we delete or anonymise them, unless local law says a longer hold is required.

Yes. Send the exact field, the correct value, and one account check we can match, such as a recent device or payment reference. We update it after verification and keep a log of the change.

Use live chat any time, WhatsApp for a phone thread, or email for a written record. If your request touches DANA, OVO, GoPay, or QRIS, add the rail name and date so we find it faster.

Yes. Access is available only where local law permits, and some actions can change by region. If a request is limited, we explain the part we can handle and the part we must decline.

Yes, you can ask. We review the request, confirm the account, and remove or anonymise records that are no longer needed, unless a legal hold applies. If anything must stay, we tell you why.

Open Our Privacy Policy

Switch To Privacy Support

Explore How We Protect Data

Data Scope

Cookie Control

Account Safety

Retention Window

Change Requests

Legal Access

Open Common Privacy Questions

01 What data do you keep from my account?

02 Why do you use cookies on my device?

03 How long do you keep my records?

04 Can I ask you to change my details?

05 How do I contact you about privacy?

06 Does access depend on local law?

07 Can I ask you to delete my data?

Related Pages