Reference

Privacy Policy for Your Account Data

We keep this policy tied to the data we actually use: account details, device signals, cookie records, and support history.

Account dataCookie recordsDANA, OVO, GoPay, QRISLocal law

Browse the lobby Read FAQ

How This Policy Applies Locally

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

This policy explains how we collect, use, store, and share personal data when you open and manage an account with us. The exact rights and duties can change by jurisdiction, so if a local rule gives you more protection, we follow that rule in the Indonesia

1
area where local law permits access. We use your registration details, device data, and support history to run login, security checks, and account recovery. When you use DANA, OVO, GoPay, or QRIS, we may store the transaction reference and status needed to match the payment with
2
your account. We do not keep extra data for the sake of it; we keep what is required for the request, the record, or the legal duty that applies. If you want a copy, correction, or deletion check, send the request through your account panel or
3
live chat and we will verify it before acting.

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

CONTACT ROUTES READY

Contact Paths For Privacy Requests

If you want to ask about your data, send the request through chat, email, or the in-account form.

Live chat Use live chat from 09:00-23:00 WIB for corrections, access checks, or questions about stored data. We verify the account first, then answer inside the same thread so your request does not drift across channels.

Email Send a message with your registered contact detail and the request type. We keep the exchange attached to your privacy record and reply in the order it arrives, which helps us trace changes clearly.

In-account form The form inside your account is the cleanest path for a copy, correction, or removal check. It ties the request to your profile and gives us the context we need before we touch stored data.

PRIVACY CONTROL LAYER

How We Handle Your Data

We built this policy around the data flow we actually run: registration fields, device signals, cookie data, and support records.

Account data

We keep the name, contact detail, and account status you provide so we can confirm ownership before any change. That record stays attached to the account and is not used for unrelated profiling.

Cookies

Cookies help us remember a signed-in session, language choice, and device state. They do not replace your password, and you can clear them in your browser if you want a fresh session.

Device checks

We log browser type, device type, and IP signals to spot repeated logins, unusual access, or a failed reset. Those checks help us protect the account without asking you to repeat the same verification.

Payment records

DANA, OVO, GoPay, and QRIS references stay in the wallet record only when they are needed to match a payment to your account or settle a support case. We do not keep more than the task requires.

Retention

We keep records for the period needed to run the account, answer a dispute, or meet a legal duty. When that period ends, we remove, mask, or archive the data according to the rule that applies.

Change requests

If you want access, correction, or deletion where allowed, send the request through support and include the account detail we can verify. We will check the request against the law and your record before we act.

Privacy Questions We Hear Most

These are the questions we hear when someone checks what we collect, how long we keep it, and how to ask for changes. The answers stay focused on the account record, cookie use, and support checks, not on broad platform topics. If a local rule gives you a different right, we follow it in the Indonesia area where local law permits.

We collect the registration details you enter, the device signals needed for security, and any support note linked to your account. If you use DANA, OVO, GoPay, or QRIS, we may also keep the payment reference that matches the record.

Cookies help us keep you signed in, remember language and device state, and spot a session that does not match the account. You can clear them in your browser, but some settings may need to be set again.

We keep the record only for the time needed to run the account, resolve a dispute, or meet a legal duty. After that, we remove, mask, or archive it using the rule that applies to the record.

Yes. Send the request through chat, email, or the in-account form, and we will verify that the request comes from the account holder before any update. If the law limits a change, we will explain why.

Only staff or service partners who need the data to run login, support, security checks, or payment matching can see it. We limit access by role and keep the record tied to the request that created it.

Yes. Your rights can vary by jurisdiction, and where local law gives you stronger protection, we follow that rule. Access is available only where local law permits, and we adjust our handling to that requirement.

Use live chat from 09:00-23:00 WIB, email support, or the in-account form. Tell us what you want checked, and we will verify the account before we discuss or change anything.

Privacy Policy for Your Account Data

Contact Paths For Privacy Requests

How We Handle Your Data

Account data

Cookies

Device checks

Payment records

Retention

Change requests

Privacy Questions We Hear Most

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

02 Why do you use cookies on this page?

03 How long do you keep my privacy records?

04 Can I ask you to change my details?

05 Who can access my account data?

06 Does local law affect my privacy rights?

07 How do I contact you about this policy?

Related Pages