Reference

Open dinas123 Privacy Policy Clearly

dinas123 Privacy Policy explains what we collect when you open an account, use the mobile lobby and check DANA or QRIS payment status.

Account dataCookie choicesWallet recordsSecurity steps
Explore Our Lobby Read FAQ
dinas123 Open dinas123 Privacy Policy Clearly
CONTACT ROUTES

Use Account Support for Privacy Requests

A clear contact route helps you ask about a Privacy Policy request without mixing it with a game question.

Account request Use the account support path for a Privacy Policy question about your contact details…
Wallet record If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the receipt reference…
Access concern When a phone, browser or login change raises a privacy concern, tell us which…
DATA PRACTICES

Protect Your Account Data at Each Step

Our Privacy Policy follows the account journey rather than treating every visit alike. We separate contact details, device events, cookie choices and payment references so a support request can be checked without…

Collected details

When you open an account, we collect the details needed to create access and complete phone verification. A visit to the mobile lobby can also create device, browser and session records. We use those records to connect a request to your account and to investigate an access concern.

Cookie controls

Cookies help us remember account flow choices and understand whether a page request came from the same browser session. You can review available cookie choices in the page controls. Changing a cookie choice may affect convenience, but it does not erase account records or payment references by itself.

Account security

Phone verification is part of the access step before account use, and sign-in events may be checked against the device path you used. If you switch from mobile browser to desktop, that change can appear in security records. Keep passwords and verification codes private when contacting us.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a receipt to the correct account without storing a guess about your wallet balance. Bank transfer and virtual account checks may include the named rail, such as Mandiri or BNI, and the reference needed to resolve a status question.

Retention period

We keep account, security and payment records for as long as they are needed for the stated account purpose, dispute handling or a legal requirement that applies to us. When a record is no longer needed, our process is to remove it or keep it in a restricted form.

Changes and contact

You can ask us to access, correct or delete eligible personal details through the account support path. Describe the requested change and provide the account identifier connected to it. We may ask for a verification step before making a change, so another person cannot alter your records.

Find Privacy Policy Answers Before Access

These Privacy Policy answers cover the account questions that usually matter before you open the lobby. We address phone verification, cookies, device records, payment references and requests for access or correction in plain language. If your situation is not covered, use the account support path with the relevant receipt or sign-in date, and we will connect the request to the correct record.

The dinas123 Privacy Policy covers account details, phone verification, device and sign-in records, cookies, payment references and support requests. It explains why we use each category, how retention works and how you can ask for access, correction or removal of eligible details.

Phone verification helps us confirm that the person opening or accessing an account is connected to the supplied contact detail. It also gives support a way to check an account request. Never place a verification code in a support message or share it with another person.

We may retain references needed to match DANA, OVO, GoPay or QRIS activity to your account and resolve a receipt or status question. Bank transfer and virtual account records can include the relevant rail and reference. The policy does not treat these references as a wallet balance.

On a mobile browser, cookies can remember account-flow choices and connect a browser session to a page request. You can use the available cookie controls to change your preference. A cookie change does not automatically remove account, security or payment records already retained for a valid purpose.

Yes. Send the request through the account support path with the contact detail linked to your account and a clear description of the copy or correction needed. We may ask for an account verification step before responding or changing records, which helps prevent access by another person.

Retention depends on why a record exists. Account, security and payment references may remain while needed for account operation, dispute handling or a legal requirement that applies. When the purpose ends, our process is to remove the record or restrict it rather than keep it without a reason.

Use account support and include the payment rail, receipt reference and approximate date. For DANA, OVO, GoPay or QRIS, include the wallet name; for BCA, BRI, Mandiri, BNI or a virtual account, name the bank rail. Do not send passwords, full credentials or verification codes.

Related Pages

dinas123 Indonesia Europa League Over Under Account information Badminton All England Bet FAQ