Reference

go138 Privacy Policy for Your Account

Our go138 Privacy Policy explains what we collect when you open an account, sign in, browse Speed Blackjack or check a football market, and how we use those…

Account recordsWallet detailsCookie choicesAccess requests
go138 go138 Privacy Policy for Your Account
REQUEST HELP DIRECTLY

Account Help for Privacy Requests

A clear support path matters when you want to ask what data we hold or correct an account detail.

Data access request Ask us to identify the account records connected with your sign-in, device activity or…
Correction request If your contact detail or account record is inaccurate, send the requested correction through…
Wallet record check For a DANA, OVO, GoPay or QRIS receipt question, include the reference shown in…
CONTROL YOUR RECORDS

Cookies, Devices and Account Records

Your Privacy Policy choices work alongside practical account controls. We use cookies and similar device signals to keep a sign-in session working, remember selected settings and detect unusual access; you can manage…

Cookie controls

Browser cookies can keep your account session and selected privacy settings available between pages. You can change cookie permissions in your browser; refusing some cookies may require repeated sign-ins or limit account preference storage.

Device signals

We may record device type, browser details, approximate access signals and session events to protect account entry. These signals help us compare a new mobile sign-in with the account path you normally use.

Account security

Clear phone verification comes before account access, and sign-in events can be checked when activity looks unusual. Never place a password, verification code or wallet PIN inside a support request.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect a receipt to the correct account record. We use that match for status checks and do not need your wallet password.

Retention timing

We keep account, security and transaction records for the period needed for the stated service, protection or legal purpose. A support request can ask which category applies to a particular record held about you.

Policy changes

When this Privacy Policy changes, we place the updated wording on this page and may show an account notice where appropriate. Check the page before entering new details so you can understand the current handling terms.

Privacy Policy Answers for go138

These Privacy Policy answers cover the questions we hear before an account is opened or a wallet is connected. They explain the practical route for access, correction, cookies, retention and contact. If your situation involves a specific DANA, OVO, GoPay or QRIS reference, use the support path inside your account and include only the details needed to locate that record.

It covers account details, phone verification, sign-in and device records, cookies, support messages, game or market activity signals, and payment references. It also explains why we use each category, when a provider may process it, and how you can ask about access or correction.

We collect the details you submit for account creation, the phone verification result needed before access, sign-in events, device signals and records from your support requests. If you connect DANA, OVO, GoPay or QRIS, payment status and reference details may also be recorded.

We use DANA and QRIS references to match a payment receipt with your account, check a pending status and investigate a mismatch. The same approach can apply to OVO, GoPay, bank transfer or virtual account records. We do not ask for your wallet PIN.

Yes. Use the support route shown inside your account and request access to the records connected with your sign-in. We may verify the account detail or phone verification first, then explain the available record set and any limits that depend on local law.

Send a correction request through account support and identify the field that needs changing, such as a contact detail. We compare the request with your account verification record, update the relevant field when confirmed and tell you if another step is needed.

Yes, cookies and similar device signals can support your sign-in session, remember selected settings and help identify unusual access on a mobile browser. You can change browser permissions, but refusing some cookies may mean signing in again or losing saved preferences.

Retention depends on the record type and the operational, security or legal purpose described in our Privacy Policy. Account, wallet and support records may therefore have different periods. Ask through account support about a specific record, and we will explain the applicable basis where local law permits.