Reference

OVO Casino Hub Privacy Policy for Your Account

OVO Casino Hub Privacy Policy explains how we handle your account details, phone verification, wallet references and device signals when you use the service in Indonesia.

Account dataWallet referencesCookie choicesAccess requests

Explore Our Lobby Read FAQ

How DANA and QRIS Data Is Used

OVO Casino Hub Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy explains which details we may receive when you open an account, complete phone verification or ask us to check a wallet status. Payment references can include the selected rail, transaction identifier, amount status and receipt details for DANA, OVO, GoPay, QRIS, bank transfer

1
or a virtual account; we do not need your wallet password to match a payment record. We use these records to identify the account request, investigate a stalled status and meet applicable legal duties. Device type, browser signals and login time can help us protect access
2
and connect a support request to the right account. Retention depends on the purpose and applicable rules. Where local law permits, you may ask how your data is used, request a correction or contact us about deletion.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATH

Privacy Help for Wallet Status

A clear contact route helps when a Privacy Policy question sits beside an account or payment record.

Account access If phone verification blocks account access, use the account support route and describe the device, browser and time of the attempt so we can match the request safely.

Wallet status For DANA, OVO, GoPay or QRIS questions, attach the payment receipt reference rather than private wallet credentials. We use the reference to check status and limit unnecessary data sharing.

Policy request Ask for a copy, correction or removal of personal data through the privacy contact path displayed in your account. We may verify account ownership before changing or releasing records.

DATA PRACTICE

Mobile Cookies and Account Security

Privacy work is part of each account step, from the first phone check to a mobile return to the lobby.

Data we receive

We may handle your account name, phone verification result, login records, device details and payment references. These fields help us connect an account request with a receipt without collecting a wallet password.

Cookies on mobile

Cookies and similar browser storage can remember access settings and help us understand whether a session belongs to the same device. You can manage browser permissions, though some account steps may need them.

Account protection

Phone verification, login timing and device signals help us check that an account request is genuine. When you return from a mobile browser to Auto Roulette or another lobby room, these checks may apply again.

Record retention

We keep records only for the purpose and period needed for account support, payment matching, security or legal duties. The applicable period can vary, so ask us for the reason behind a retained record.

Who to contact

Use the privacy contact route shown in your account for questions about collection, cookies, wallet references or access. Include enough account detail for verification, but never send a wallet password.

Requesting changes

You can ask us to correct inaccurate account details, explain a data use or consider deletion where local law permits. We may first confirm your phone verification and account ownership.

Privacy Policy Questions About Your Account

These Privacy Policy answers cover the searches we hear most often before account access. They explain what we connect to your account, how Indonesian wallet references are handled and how you can contact us when a record needs attention. If your question is not listed, use the privacy contact route shown after account access.

It covers account details, phone verification, device and browser signals, cookies, payment references, retention and requests to access or change personal data. It applies when you use the service where local law permits.

Our policy does not require your DANA or OVO wallet password for payment matching. We may use a receipt reference, selected rail and status details to connect a transaction with your account.

Phone verification helps connect an account request to the person seeking access and supports security checks when login activity changes. We may ask for confirmation before handling a private data request.

Use the privacy contact path displayed in your account and state that you want a copy of your personal data. Include your linked phone number or receipt reference so we can verify ownership.

Yes. Send a correction request through the account privacy contact route and identify the field that is wrong. We may confirm your phone verification before changing the account record.

Cookies or similar storage may keep access settings and help connect a session to your device. Your browser controls these choices, but disabling them can affect phone verification or account access.

Yes. You may ask us to consider deletion or restriction where local law permits. We first assess account support, payment matching, security and legal duties before confirming which records can be removed.

OVO Casino Hub Privacy Policy for Your Account

Privacy Help for Wallet Status

Mobile Cookies and Account Security

Data we receive

Cookies on mobile

Account protection

Record retention

Who to contact

Requesting changes

Privacy Policy Questions About Your Account

01 What does the OVO Casino Hub Privacy Policy cover?

02 Does the Privacy Policy store my DANA or OVO password?

03 Why does OVO Casino Hub collect phone verification data?

04 How can I request a copy of my personal data?

05 Can I ask for incorrect account data to be changed?

06 How are cookies handled on my mobile browser?

07 Does the Privacy Policy explain data deletion?

Related Pages