Reference

988bet Privacy Policy For Your Account

Our Privacy Policy shows how 988bet handles the details you provide for account access, wallet checks and support, including DANA, OVO, GoPay and QRIS references.

Account dataWallet referencesCookie choicesAccess requests
988bet 988bet Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A direct support request is the practical route when you want to understand a record connected with your account. Tell us which Privacy Policy question you have, identify the relevant account step, and include only the minimum detail needed for us to locate the matter. We can then explain the request path without asking you to post private wallet data publicly.

Team online

Account access request

Ask us to confirm which account details are linked to your login or phone verification step. We may need account checks before discussing records, so keep DANA or QRIS references out of public messages.

Wallet data question

If a DANA, OVO, GoPay or QRIS reference appears in a cashier record, tell us the transaction context rather than sharing a full wallet credential. We use the request to trace policy handling.

Correction request

Send the specific detail you believe is inaccurate and explain the requested change. We review the account context, apply identity checks where needed, and reply according to local access rules.

CONTROL YOUR RECORD

What We Do With Cookies And Records

Privacy choices work best when you know what each record does. We separate account, device and payment-reference handling so a question about a Rocket Crash page is not treated as a wallet…

Account details

We use information supplied during account creation and phone verification to maintain access, answer account questions and connect a support case with the correct record. We do not need public posts containing your private credentials.

Device signals

When you move from a mobile login to the lobby, we may receive device, browser and session signals. These details help identify unusual access around pages such as Super Bingo without replacing your account checks.

Cookies

Cookies and similar session tools can remember sign-in state, language preferences and the page path you opened. You can adjust browser controls, although some account access steps may then need to be repeated.

Payment references

A transaction record can contain a payment method label, amount context and status reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use it to reconcile the related account request.

Security checks

We may compare login, phone verification and cashier details when a request concerns account access. These checks help us avoid disclosing records to the wrong person, including when the request mentions Royal Fishing.

Retention and changes

We retain records for the period needed for account, security and support purposes, subject to local rules. You can request a correction or ask how a record is handled through our account support path.

Privacy Policy Answers Before Account Access

These answers address the searches we hear before someone opens an account or asks about a wallet record. We keep the wording practical: what we collect, why a device may appear in a record, how to request a change, and when local rules affect the reply. If your case is specific, use the account support path rather than sharing private details in an open channel.

It covers account details, phone verification, device and session data, cookies, support records, and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect account access with the correct person, protect support replies and investigate login issues. Any request about those details may require an account check before we respond.

Yes. When you use a mobile browser to move from login toward a lobby page such as Live Roulette, we may process browser, device and session signals for access security and troubleshooting.

We handle DANA and QRIS references as transaction context, not as a request for your wallet credential. We use method labels and status details to connect a cashier question with the relevant account record.

Use the account support path, state which detail is inaccurate and describe the correction you seek. We may ask for verification before changing a record, and the result depends on local law.

You can ask us to explain the account, device, cookie or payment-reference records connected with your request. We confirm identity first and provide the response where local law permits.

Records remain available for the period needed for account access, security and support handling, subject to applicable local rules. Ask through support for the retention context of a particular record or request.