Reference

Privacy Policy for Indonesian Accounts

Our Privacy Policy explains what we collect, why we keep it, and how you can ask us to change it.

Account dataCookie settingsVerified contact pathDANA, OVO, GoPay, QRIS

Browse Lobby Read FAQ

How We Handle Data in Indonesia

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

We handle privacy data in a practical way: the name on your profile, contact details, login history, device identifiers, and the payment trail tied to DANA, OVO, GoPay, and QRIS are used to run the account, confirm requests, and detect unusual access. When you reach us

1
about a correction, a payout check, or a closed-session dispute, we match the request against the verified email or chat thread before we change anything. Cookie data helps us remember your language, session state, and banner choices on mobile and desktop. We keep records only as
2
long as needed for security, accounting, dispute handling, and legal duties under Indonesian rules or the rules that apply where local law permits.

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

REQUEST CHANNELS

Where to Send Privacy Requests

The fastest privacy request is the one that reaches the right inbox. You can contact us by live chat, email, or WhatsApp, and we ask you to use the email already linked to the account so we can verify ownership before changing records. Live chat is staffed daily from 09:00 to 23:00 WIB, while email stays open around the clock for corrections, access requests, and deletion requests where local law allows.

Team online

Live chat

Use live chat for a quick privacy question, a cookie choice update, or a request to see what we store. We verify the account first, then route the case during 09:00-23:00 WIB.

Email

Send email from the address on file if you want a copy of your data, a correction, or a clarification on payment records linked to DANA, OVO, GoPay, or QRIS. We log every request and reply in order.

WhatsApp works well when you need to attach a screenshot from Android, iPhone, or desktop browser. We use it to confirm the request, point you to the account step, and move the case into our support queue.

KEEPING RECORDS TIGHT

How We Keep Your Data Clear

This policy sits next to the way we run the account: login checks, cookie choice, payment records, and support logs all stay linked to the same verified profile.

Data handling

We store only what we need for login, support, and payment reconciliation, including the session logs from live tables, slots, and crash games you opened. The file stays tied to your verified account, not to any broader profile.

Cookie control

Your browser controls cookies on mobile and desktop. If you clear them in Chrome, Safari, or Firefox, the saved session ends and we ask you to sign in again on the next visit.

Account security

We pair password checks with email verification before we process sensitive requests. If the message comes from a new device, we may ask for extra proof through the verified chat thread.

Retention

Records stay only for the period needed to handle disputes, audit access, and meet legal duties. After that, we remove or anonymise what we no longer need for the account.

Change requests

To update your details, send the exact field that changed and the new value from your verified address. We then confirm the edit and note the change in the account history.

Access and correction

If you want to know what we hold, ask for a data copy from the email on file. We will return what can be shared and explain any item we must keep.

Privacy Questions We Hear Most

These questions cover what most people ask before they open an account or send a privacy request. We keep the answers tied to the account, the device you used, and any payment record connected to DANA, OVO, GoPay, or QRIS. If something needs a correction, use the verified contact path first so we can match the request quickly and keep the record accurate.

We collect profile details, login history, device data, support messages, and the payment references needed to verify account activity. We do not need more than that to run the account, and access questions follow local law.

Yes, but only the transaction references needed for reconciliation, fraud checks, and request verification. We keep those records attached to your verified account path, not as a public payment feed.

Yes. Send the request from the email on file or through live chat after verification, and we will share the data we can lawfully provide in a readable form.

Use the verified contact channel, tell us the exact field that changed, and attach supporting detail if asked. We update the record only after the change is matched to your account.

We keep records for the time needed to support login security, payment checks, disputes, and legal duties. After that period, we delete or anonymise items we no longer need.

Yes. Cookies work differently on each browser, so Chrome on Android, Safari on iPhone, and desktop browsers each store their own session state. Clearing them ends the remembered session.

Access or eligibility depends on local law and is available only where local law permits. For an account tied to Indonesia, we still follow the same request flow and verify the contact path first.

Privacy Policy for Indonesian Accounts

Where to Send Privacy Requests

Live chat

Email

WhatsApp

How We Keep Your Data Clear

Data handling

Cookie control

Account security

Retention

Change requests

Access and correction

Privacy Questions We Hear Most

01 What information do you collect from my account?

02 Do you keep payment records from DANA, OVO, GoPay, and QRIS?

03 Can I ask for a copy of my data?

04 How do I correct my profile details?

05 How long do you keep my data?

06 How do cookies work on mobile and desktop?

07 Does this policy apply in Indonesia only?

Related Pages