Reference

Terms for Indonesia Accounts

We set out the rules that govern your account, your payment rails, and how access works on phone or desktop.

Indonesia accountsDANA, OVO, GoPay, QRISPhone and desktopLocal law applies

Browse Lobby Read FAQ

Local Law, Access, and Wallet Rules

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

We write these terms for Indonesia accounts, and local law controls where it differs from our wording. If your region does not permit access, you should not continue, and we may restrict the account when our checks show a mismatch in identity, payment source, or device

1
use. DANA, OVO, GoPay, and QRIS transactions are accepted only when the account name, phone number, and wallet details match the record on file. We can ask for extra documents before we release funds, pause a session, or correct an error. The chips below show the
2
rails we reference most often in this section.

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

ASK OUR TEAM

Contact Paths for Terms Questions

If a clause feels unclear, the fastest path is live chat or WhatsApp, and we keep email open for written requests that need a trace. We answer terms questions daily from 09:00-23:00 WIB, which helps when you are checking the page on mobile or desktop. For anything that affects your account record, send the same email address you used at sign-up so we can match it quickly.

Team online

Live chat

Use live chat when you want a clause checked before you accept it. We answer in English and can point you to the exact section that covers account access, payment checks, or session logs.

Send a screenshot of the page, your account email, and the clause you want explained. Our WhatsApp desk works daily from 09:00-23:00 WIB, which helps when you are checking the terms on a phone.

Email

Use email for correction requests, dispute records, or a written copy of your acceptance history. We keep the thread with your account details so we can trace the exact version you saw.

HOW WE HANDLE

Data, Cookies, and Account Security

We handle this policy area by keeping the account trail tied to one login, one device history, and one payment record where possible.

Data use

We store the account details you submit, device logs, and payment references only to run the terms that apply to your account, confirm identity, and answer disputes. We do not ask for extra fields unless a clause requires them.

Cookies

Our cookie banner explains what session cookies do on desktop and mobile browser, including login persistence and language saving. You can clear them in Chrome, Safari, or your Android browser, and the next visit will ask again.

Security

We use password hashing, session timeouts, and step-up verification when a change request touches your email, phone, or withdrawal destination. If you log in on a shared phone, sign out before you hand it over.

Retention

We keep core contract records, support tickets, and payment references for the period needed to resolve account questions and audit requests. When that period ends, we delete or anonymise what no longer has a legal purpose.

Changes

If you want a correction to your name, email, or phone, send the request from the account email or through live chat. We compare it with your saved details before we amend the record.

Contact path

If you disagree with how a clause was applied, ask for a second check and attach the date, device, and screen you saw. That gives our support team the trail needed to reopen the case.

Questions About Our Terms

These are the questions we hear before a person accepts the terms. We answer them here so you can check access rules, contact paths, record handling, and what happens if your details change after sign-up. If you still need a specific clause checked, send us the date, the device you used, and the email on the account, and we will trace the exact version you saw.

You accept the account-use rules, the payment checks tied to your wallet or card, and the access limits that apply where you live. If local law changes, we apply the rule that fits the current location first.

Only where local law permits. If your region blocks access or your details do not match the permitted area, we may pause the account and ask you to confirm the information before you continue.

We use the details you give us to verify the account, process support requests, record payment checks, and resolve disputes. We do not collect extra fields unless a term or a verification step requires them.

Send the request from your registered email or through live chat, then wait for the verification step. We compare the new request with the record on file before we update name, phone, or email.

Cookies keep the login state, language, and page flow on your browser, including Chrome, Safari, or Android browser. If you clear them, you may need to sign in again and accept the banner once more.

Use live chat, WhatsApp, or email and send the date, device, and the text you saw. That gives our team enough detail to reopen the case and explain how the clause was applied.

We keep contract records, support threads, and payment references for as long as needed to settle questions or meet a legal request. After that, we remove or anonymise what no longer has a purpose.

Terms for Indonesia Accounts

Contact Paths for Terms Questions

Live chat

WhatsApp

Email

Data, Cookies, and Account Security

Data use

Cookies

Security

Retention

Changes

Contact path

Questions About Our Terms

01 What do I accept when I open an account?

02 Can I use to388 from any region?

03 How do you use my personal data?

04 How do I request a change to my details?

05 What happens to cookies during my session?

06 Who can I contact if I disagree with a clause?

07 How long do you keep contract records?

Related Pages