Reference

Open denver99 Privacy Policy Before Access

Our Privacy Policy explains how we handle the account data connected with Live Casino, Aviator and other lobby activity, including phone verification and wallet records.

Account dataWallet recordsCookie choicesMobile access
denver99 Open denver99 Privacy Policy Before Access
CONTACT ROUTES

Check Privacy Help From Your Account

A clear contact route matters when you want to ask about stored data or correct an account record. We keep privacy requests connected to the account area so we can match the request with the right phone verification and wallet reference. If a DANA receipt, QRIS reference or login record appears incorrect, open the support path beside your account and describe the issue without sending a full wallet password. Access remains dependent on local law.

Team online

Account support path

Open the support link beside your account to ask how we use your data, request a copy of account records, or ask why a particular data field is needed for access.

Wallet record request

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, include the date and reference shown in your receipt. We use those details to locate the correct transaction record.

Access correction route

If your phone number, device record or account detail needs correction, send the request through the same support route. We may ask for a verification step before changing protected data.

DATA PRACTICE

Browse denver99 Data Handling Details

We handle account data according to the purpose for which it was collected. Phone verification helps connect an account with the person requesting access, while device and session records help us investigate…

Account data use

We use your name, phone details and account activity to create access, maintain the correct profile and answer requests about Live Casino, Aviator or other activity linked to your account.

Payment references

DANA, OVO, GoPay and QRIS may return a reference, status or timestamp. Bank transfer and virtual account records can carry similar details, which help us match a receipt without storing your wallet password.

Cookie controls

Cookies can remember a session, support account navigation and show whether a privacy choice has been made. You can manage browser cookie settings, although some account functions may then require another sign-in.

Device security

When you sign in from a mobile browser or desktop, we may record device and session signals. These checks help us spot an unusual sign-in and protect changes to your phone or wallet details.

Retention approach

We keep account, support and transaction references for the period needed to provide the requested service, resolve disputes, protect access or meet a legal duty. When a record is no longer needed, our process addresses its removal.

Your request rights

You can ask what account data we hold, request a correction, ask about a processing purpose or raise a deletion request where local law permits. Use the support path and describe the specific record clearly.

Ask About Privacy Policy Access

These Privacy Policy answers address the questions we expect when you are deciding whether to open an account from Indonesia. We explain the records connected with phone verification, mobile browsing, local wallet references and support requests in plain terms. If your question concerns a particular account record, use the support path after signing in so we can check the correct details. Any access or eligibility decision depends on local law.

It covers account details, phone verification, sign-in and device records, cookie choices, support requests, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security steps and the requests you can make.

We use your phone number to create and verify the account, connect you with the correct sign-in record and protect requests to change sensitive details. If you ask about a record, the verification step helps us avoid disclosing account data to the wrong person.

Yes. The policy covers payment references, status details and timestamps connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These records help us match a receipt or investigate a wallet-status question without requesting your wallet password.

We may record browser type, operating system, session time and signals linked with a mobile browser or desktop sign-in. These details help us investigate access problems and protect account changes. The policy explains the purpose for each category and how long it may be retained.

Open the support path from your account and state whether you want access to a record, a correction or an explanation of its use. Include the relevant date or reference, but do not send a wallet password. We may complete phone verification before handling the request.

Retention depends on why the record exists. We keep account, support and transaction references while they are needed for access, payment matching, security, dispute handling or a legal duty. The Privacy Policy describes the relevant purpose, and you can ask support about a specific record.

You can submit a removal request through the account support route, and we will assess it against the applicable purpose and legal requirements. Some records may need to remain for security, payment matching or legal duties. Any request outcome depends on local law.