Reference

Privacy Policy for DANA and QRIS Accounts

Our syair sdy oovin Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Blackjack Table or use DANA and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
Browse Our Lobby Read FAQ
syair sdy oovin Privacy Policy for DANA and QRIS Accounts
REQUEST A HAND

Policy Help When Wallet Status Stalls

A clear contact route matters when a privacy question arrives beside an account or wallet issue.

Account privacy request Use our website support path to ask what account details we hold, why a phone verification step appears, or how to correct an inaccurate name or contact record. Include the phone number linked to your account so we can match the request without asking for your password.
Wallet record question If a DANA, OVO, GoPay or QRIS receipt does not match the account page, send the transaction reference, date and amount through support. We use those fields to locate the relevant status record; never send a wallet PIN, card secret or one-time code.
Cookie and device help For questions about cookies, saved login choices or a mobile browser session, tell us the device type and browser path you used. We can explain the setting to change, while your browser remains the place where you clear stored site data.
SIX DATA CONTROLS

Six Controls Around Your Account Data

Privacy protection is handled through account steps rather than broad promises. Phone verification helps us connect a request to the correct account, while session checks help us spot unusual access.

Phone verification

Before account access is completed, we use the phone verification step to link the account to the contact detail you supplied. This reduces confusion between two records and gives us a practical reference when you ask for a copy, correction or access change.

Payment matching

A DANA, OVO, GoPay or QRIS event is handled as a transaction record with status fields, not as permission to view your wallet PIN. Bank transfer and virtual account references are used to match the account event and investigate an incomplete receipt.

Cookie choices

Cookies can remember a session, support account navigation and help us understand which page path was requested. Your browser settings let you remove or block them. If a blocked cookie affects access, support can explain the related sign-in step without requesting secret credentials.

Mobile sessions

On a mobile browser, we may record device type, browser version and session time so an account request can be checked against its access path. We do not treat the device alone as proof of identity; phone verification and account details remain separate checks.

Retention checks

We keep account, support and transaction records only for as long as needed for the stated service purpose, dispute handling, security checks or applicable legal duties. When a record is no longer needed, our process is to remove it or separate it from direct account identification.

Request handling

A privacy request should include your linked phone number, the action you seek and enough detail to locate the record. We may ask for an account check before changing data, and we will explain any restriction when local law does not allow the requested action.

Privacy Policy Questions Indonesian Accounts Ask

These answers address the privacy searches we hear most often before an account is opened or a wallet receipt is checked. They explain the account path, device records, payment references and ways to contact us without turning a policy question into a general product discussion.

It covers account details, phone verification, device and session records, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account use. It also explains retention, security checks and how to request access or correction where local law permits.

We may collect the contact details needed for account creation, the phone verification result, account activity timestamps and device or browser details connected with a session. If you use a wallet or bank rail, we also receive the transaction reference and status needed to match that event.

Yes. We handle the receipt reference, amount, time and status needed to identify a DANA or QRIS event linked to your account. We do not need your wallet PIN or one-time code. OVO, GoPay, bank transfer and virtual account records follow the same matching principle.

Send a request through the support contact path on our website and include the phone number linked to your account, the record you want checked and the action you seek. We may perform an account check before responding, so another person cannot change your details.

You can ask us to remove eligible account data through support. We first check whether a record is still needed for security, a payment dispute, account protection or a legal duty. Where local law permits removal, we will process it and explain any records that must remain.

Cookies can keep a session active, remember navigation choices and connect a mobile browser request to the correct account page. You can clear or block them in your browser settings. Removing them may require another phone verification or login step when you return.

The policy applies to the data handling described on our website, but account access depends on local law. We may restrict or decline an account request where required. If that affects a privacy request, support can explain the applicable step without asking for secret wallet credentials.

Related Pages

syair sdy oovin Indonesia Live Blackjack Table Access guide Piala Presiden Over Under FAQ