Reference

join888 Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use, store and protect the details connected with your join888 account.

Clear data purposesWallet record controlsPhone verification contextIndonesia access wording
join888 join888 Privacy Policy For Your Account
REQUEST A RESPONSE

Privacy Policy Help Through Account Support

A clear support path helps you ask about the Privacy Policy without searching through unrelated account pages. Send a request through our account support route and include the phone number or account reference connected with your enquiry. We use those details to locate the correct record, while payment questions can be matched with a DANA, OVO, GoPay or QRIS receipt. If access is unavailable, state the device and sign-in step you reached so we can direct the request to the right team.

Team online

Policy questions

Ask how we collect, use or retain a particular account detail through the support path attached to your account. Include the Privacy Policy topic and the email or phone detail you used during account access, so we can check the relevant record before replying.

Wallet records

For a question about a DANA, OVO, GoPay or QRIS reference, send the receipt code, date and wallet name with your request. We use the payment reference to separate transaction data from general account activity and to explain what record we hold.

Access concerns

If phone verification or sign-in stops you from reaching your privacy request, tell us whether you are using a mobile browser or desktop browser. We can then check the account step involved without asking you to send a password or private security code.

HOW DATA IS HANDLED

Privacy Controls Across Your join888 Account

We keep the Privacy Policy practical by connecting each data use to an account task you can recognise.

Account data

We may hold your account name, contact detail, phone verification result and sign-in history to provide account access and answer a Privacy Policy request. We do not need your wallet password to match a DANA, OVO, GoPay or QRIS payment reference.

Cookies and sessions

Browser cookies can keep a session active, remember a setting or help us understand which account page produced an access error. You can manage cookies through your browser controls, although changing them may require another sign-in or affect a requested account function.

Security checks

A new device, repeated sign-in attempt or unusual account change may trigger an additional check. We use the device path and verification status to protect the account, and our support team will not ask you to reveal a password or one-time security code.

Payment references

A payment record can include the rail selected, such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account, together with a reference and status. This lets us trace a receipt or pending record while keeping the request tied to your account.

Retention choices

We retain account and transaction records for the period needed to provide the requested service, resolve disputes, investigate security events or meet applicable legal duties. When a record no longer serves one of those purposes, we assess it for deletion or further restriction.

Change requests

You can ask us to correct an inaccurate contact detail, explain a data use, provide a copy where applicable or restrict a particular handling request. Send the request through account support, identify the record concerned and complete reasonable account checks before changes are made.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account questions you are most likely to ask before opening or using join888 in Indonesia. They explain the data connected with phone verification, browser access, wallet receipts, security checks and requests for correction or deletion. If your case involves a specific account record, use the support path and include enough context for us to locate it without sending your password.

The join888 Privacy Policy covers account details, phone verification, browser and device activity, support messages, cookies and payment references. It explains why we use each category, how we protect account access, how long records may be retained and how you can ask about a particular record.

Phone verification helps us connect an account request to the correct contact detail and identify unusual sign-in activity. We record the verification result and related account event rather than asking for your private security code. Access or eligibility depends on local law.

Yes. The Privacy Policy covers transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may use the rail name, receipt reference, date and status to match a payment question to your account without needing your wallet password.

You can request a correction when a contact detail or other account record is inaccurate. Use account support, state which field needs attention and provide the account reference needed for a reasonable identity check. We will assess the request against security, operational and legal requirements.

Cookies can support your browser session, remember a setting and help us identify an access error. They may connect a browser event with your account session, but they do not replace your phone verification. You can manage cookies in browser settings, with some account functions possibly requiring another sign-in.

Send a Privacy Policy request through the account support route and describe whether you want access, correction, restriction or deletion. Include your account contact detail, but never send a password or one-time code. We may retain records needed for security, disputes or applicable legal duties.

Name the Privacy Policy issue, the account contact detail involved and the date or page connected with your request. For a wallet matter, add the DANA, OVO, GoPay or QRIS receipt reference. This helps us find the right record while limiting unnecessary data in your message.