Reference

xo368 Privacy Policy for Your Account

Lightning Roulette, Starburst, MotoGP Betting and Crash Games all run behind one account profile, and this Privacy Policy explains what data we collect when you browse, fund with…

Account data explainedDANA and QRIS contextCookie choicesDevice checks
xo368 xo368 Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Through Local Channels

Fast privacy help matters when a payment receipt, login alert or account name needs checking. We keep privacy requests inside account support so you do not have to repeat sensitive details across public channels. Start from Live Chat, WhatsApp support or the account inbox, then include the last four digits of the linked phone number, your payment rail, and the record you want us to inspect.

Team online

Live Chat

Use Live Chat from 09:00 to 02:00 WIB for cookie questions, login alerts and data correction requests. Our team will verify your account first, then move sensitive details into a private support thread.

WhatsApp Support

WhatsApp is useful when you need to share a DANA, OVO, GoPay or QRIS receipt screenshot for a privacy check. We ask for only the receipt area needed to match your wallet record.

Account Inbox

For copy, correction or deletion requests, use Account > Inbox after signing in. That path lets us link the request to your profile without asking you to send extra identity details in open chat.

DATA HANDLING

How We Handle Your Privacy Choices

Good privacy practice is operational, not decorative. We collect the smallest practical set of data for login, wallet use, support, security checks and account records.

Account setup data

When you create an account, we record your username, contact details, password status and region setting. These fields let us protect your login, send account messages and match wallet activity to the right profile.

Payment record care

DANA, OVO, GoPay and QRIS transactions create wallet references, timestamps and confirmation details. We use those records to reconcile deposits, check withdrawals and resolve payment disputes with less repeated questioning.

Cookie controls

Cookies keep your session active, remember language choices and help detect unusual sign-in patterns. You can clear them through Chrome Settings > Privacy and security, but doing so may require a fresh login.

Device session checks

From Profile > Security > Devices, you can see active sessions and remove a phone you no longer use. We log device type, rough location signal and sign-in time to spot account misuse.

Retention practice

We keep account and payment records only as long as needed for service, dispute handling, fraud checks and legal duties. Chat transcripts tied to privacy requests are restricted to support staff who handle account verification.

Correction requests

If your name, phone number or linked wallet changes, contact us before making another withdrawal request. We will ask for account verification, compare the current record and update only the fields we can confirm.

Privacy Questions Before You Open Account

Before you join, you should know how your data moves through the account flow. These answers focus on the Privacy Policy only: what we collect, how payment records are handled, how cookies affect your session, and how you can reach us when something needs correction or removal.

It covers account details, login activity, device signals, cookie records, support chats and payment references tied to DANA, OVO, GoPay or QRIS. It also explains why we keep certain records for security, disputes and account service.

No. We record payment references, timestamps, receipt details and wallet matching results, not your wallet password or full app access. If a receipt needs review, we ask for only the visible part needed to confirm the transaction.

Sign in, open Account > Inbox, and send a privacy request with the record type you want. We verify your account first, then prepare the available data linked to your profile and wallet activity.

Yes, if we can verify the change. Contact Live Chat or the account inbox, tell us which field is wrong, and provide the account checks we request before your next withdrawal or payment dispute.

We use device type, sign-in time and rough location signal to protect account access. For example, a new phone on mobile data may trigger a check before wallet changes, especially after repeated failed login attempts.

Cookies keep your session active, remember basic choices and help detect unusual access. You can clear them in your browser settings, but you may need to sign in again and repeat some security checks.

We keep privacy request records for as long as needed to answer you, document the action taken, manage disputes and meet legal duties. Records no longer needed for those purposes are removed or separated from active account use.