Reference

Legal access for Indonesia accounts

We keep legal access tied to your location, so you only move forward where local law permits.

Local law firstAccount-linked recordsDANA, OVO, GoPay, QRISChrome and Safari

Browse lobby Read FAQ

What local law changes here

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

Our legal position is simple: access depends on local law, and we only process an account where the rules in your location allow it. When we need to confirm ownership or answer a records request, we ask for the smallest set of details needed and keep

1
the case linked to your account ID, so the trail stays clear from first message to final reply. That rule stays the same across live casino tables and slot rooms, because the access check sits on the account, not on the game page. We also keep
2
payment logs for DANA, OVO, GoPay, and QRIS tied to the same record set, because deposits, withdrawal checks, and dispute handling often need a matching time stamp. If your region changes, or the law changes around you, access can pause or adjust without guesswork. If you
3
send a correction request, we confirm the current details first, then update only what the law and the account record allow.

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

REQUEST CHANNELS

Where your legal request goes

If you need a correction, a copy of your account record, or a question about access in Indonesia, start from the chat icon or the contact form inside your account. We keep one thread per case, ask for your account ID only when needed, and answer during 09:00-23:00 WIB. On mobile, the same request path sits in Chrome or Safari, so you can check status without losing the conversation.

Team online

Live Chat

Use the chat icon from desktop or mobile, share your account ID, and tell us whether the issue is access, data, or a correction request. We answer 09:00-23:00 WIB and keep the case in one thread.

Contact Form

Send a written request from the form in your account area if you want a copy of stored data or a change to your record. We confirm the message against your account before we act.

Security Page

Open Account > Security on Chrome or Safari to see recent logins, device type, and session history. If something looks unfamiliar, reply in the same thread so we can lock the case to your record.

DATA CARE PRACTICES

How we handle your records

Our handling is narrow and account-based. We keep only the details needed to verify access, process lawful requests, match wallet records, and maintain a clear support trail.

Data Minimisation

We ask for only the fields needed for an access check or correction request: account ID, contact route, and the specific issue. We do not collect extra details just to fill a form.

Cookie State

Cookies keep the session active, remember your language, and reduce repeated checks while you move between pages. They do not replace your account record, and you can clear them from your browser if needed.

Account Security

Change your password from Account > Security, then confirm the new login on your device. We use that same path to flag unusual sign-ins and to keep case handling tied to your own session.

Record Retention

We keep support threads, access logs, and payment traces only as long as needed for verification, dispute handling, and lawful record keeping. After that period, we reduce or remove what is no longer required.

Request Changes

If you need a correction, send the exact field that should change, the current value, and the new value. We verify the request against your account before any update goes live.

Contact Routing

Use live chat for urgent access questions, the contact form for written requests, and your account page for status checks. That routing keeps each request easy to trace and easy to answer.

Questions about access and records

When you check the legal side of your account, we keep the answers tied to real actions: access by location, record requests, corrections, cookies, and contact routes. If you switch between desktop and mobile, the same account path stays available in Chrome or Safari, so your question reaches us with the same case ID and no extra back-and-forth.

Yes, where local law permits. Eligibility depends on your location, so we only move an account forward after the local rule check is clear. If access is not permitted in your area, we keep the request closed.

We keep the minimum set tied to your account: login history, device type, contact route, support messages, and any payment time stamp that matters to the case. We do not add extra fields without a reason.

Send the field name, the current value, and the value you want changed through live chat or the contact form. We confirm the request against your account first, then update only what the record allows.

We keep support threads and access logs only as long as needed for verification, dispute handling, and lawful record keeping. After that, we shorten or remove what no longer needs to stay in the file.

Cookies remember session state and language, but they do not replace your account record or change a legal decision on their own. You can clear them in your browser if you want a fresh session.

Only staff handling your request and the systems that route it can see the thread. It stays linked to your account ID, and we do not share it outside the case process unless required by law.

Legal access for Indonesia accounts

Where your legal request goes

Live Chat

Contact Form

Security Page

How we handle your records

Data Minimisation

Cookie State

Account Security

Record Retention

Request Changes

Contact Routing

Questions about access and records

01 Can I access duit808 from Indonesia?

02 What data do you keep on my account?

03 How do I request a correction?

04 How long do you keep records?

05 Do cookies change my legal settings?

06 Who sees my case thread?

Related Pages