Reference

Privacy Policy For Your Account

ube gaming slot Privacy Policy explains what we collect when you open an account, sign in, browse Lightning Roulette Room or use DANA and QRIS.

Account dataWallet recordsCookie choicesAccess controls
ube gaming slot Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Help Near Your Account

A privacy question should not leave you guessing which route to use. We keep account help close to the login and cashier path so you can ask about a record, a wallet…

Account access If your phone verification or sign-in does not match, contact support from the account help path. We use the details you provide to check ownership, explain the next privacy step and avoid exposing account data to an unverified requester.
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, include the transaction reference and approximate time rather than your wallet password. We can connect the request with the correct account record and explain which details we retain for payment checking.
Privacy requests Ask us to access, correct or remove eligible personal details through the same support route. We may request an account step or phone verification before responding, because a privacy reply must reach the person connected to the record.
DATA CONTROLS

What We Do With Your Personal Data

We handle privacy as part of the account path, not as a separate page you have to decode.

Account security

Before we discuss account data, we may compare your sign-in details with the phone verification step used at account access. Never send a password or one-time code to support. This check helps us keep a privacy request tied to the correct account.

Cookies

Cookies can retain selected settings and help us understand which Privacy Policy pages are opened. Your browser controls whether optional cookies remain. Blocking them may change how preferences are remembered, but it does not erase records already required for account or security work.

Payment records

A wallet or bank record may include a reference, amount, channel and status so we can reconcile a request. We do not need your wallet password for that check. DANA, OVO, GoPay, QRIS and virtual account questions follow the same account-linked process.

Device signals

When you sign in on a new phone or browser, technical signals such as device type and session details may be recorded for access protection. These signals help us investigate an unexpected login without turning them into a public account profile.

Retention

We keep personal data while it serves account operation, security, payment reconciliation or a legal requirement. When a record no longer has one of those purposes, we remove it or make it no longer linked to you, subject to applicable retention duties.

Change requests

To request a correction or eligible deletion, tell us which account detail is affected and use the support contact connected to your account. We may ask for phone verification, explain any retention reason and confirm the outcome through the same private route.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions you may ask before opening an account or returning to the lobby. We explain the practical points: what data enters the account path, why wallet records appear, how cookies work, how to request a change and what happens when access depends on local law. If your situation is not covered, use the support path above and describe the specific record or device step involved.

It covers account details, phone verification, sign-in activity, device signals, cookies, support conversations and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps. It also explains retention, security access and how you can request an eligible change.

A wallet reference and payment status help us match a receipt with the correct account when you use DANA, OVO, GoPay or QRIS. We use that information for reconciliation and support checks. We do not need your wallet password to investigate an unclear transaction.

Contact us through the account support route and state that you are making a Privacy Policy data request. Identify the account detail or record you want to access. We may use phone verification or another account step before sending a response to the verified contact.

Yes, send a correction request through support with the affected account field and the accurate replacement detail. We may confirm ownership before changing it. If the detail also appears in a payment record, we will explain which parts can be updated and which must remain for reconciliation.

Cookies may remember settings and show us which policy pages are used, while required technical data supports sign-in and security. You can manage optional cookies in your browser. Removing them may reset preferences, but it does not remove records needed for account protection.

We keep a record while it is needed for account access, phone verification, security checks, payment reconciliation, support or a legal duty. After that purpose ends, we remove or unlink it where permitted. A support reply can explain the reason for a particular retention period.

The policy describes our handling of personal data for accounts using the site where local law permits. Access and eligibility depend on local law, so the applicable position can vary by location. If you are unsure, contact support before sharing additional account or wallet details.