Reference

Privacy Policy for Your dadar88 Account

Our Privacy Policy explains how dadar88 handles the details you provide when you open an account, verify your phone and access the lobby from a mobile or desktop…

Account detailsPhone verificationWallet choicesDevice access
dadar88 Privacy Policy for Your dadar88 Account
CONTACT YOUR WAY

Privacy Help Beside Account Support

A clear contact path helps you ask about the Privacy Policy without explaining your whole account history. Start with the account help route when you need to ask about stored details, phone verification or a sign-in record. Use the cashier or payment-status route for a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record. Include the email or phone linked to your account and the date of the relevant event, while leaving out passwords and access codes.

Team online

Account data request

Ask us to identify the account details connected with your sign-in, phone verification or profile record. We may check account ownership before discussing personal data, so your request reaches the correct account holder.

Wallet record question

For a payment record, name the wallet or rail involved, such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We can then direct the question to the matching account and status path.

Policy change request

If a detail is wrong, outdated or no longer needed for the stated purpose, tell us what should change and why. We will assess the request under the Privacy Policy and where local law permits.

DATA HANDLING

What We Do With Account Data

The Privacy Policy is built around practical account handling rather than broad promises. We separate sign-in, payment-status and device signals so each detail serves a defined operational purpose.

Account records

We may hold your name or contact detail, phone verification result, account identifier and access history so we can open…

Payment records

A DANA, OVO, GoPay or QRIS action may create a transaction reference, status and time record.

Device signals

Browser type, device markers, session time and basic access signals can help us identify unusual sign-in activity.

Cookies

Cookies or similar storage can retain session preferences and help the account area function after sign-in.

Security checks

Phone verification and sign-in checks help keep account details apart from another person’s session.

Retention requests

We keep records only while needed for account operation, security, payment matching or legal duties.

Privacy Policy Answers for dadar88

These Privacy Policy answers address the account and access questions that commonly arise before you open an account or connect an Indonesian wallet. They explain the data path in plain language, including what to send when you need help. Access or eligibility depends on local law, and a request may require an account ownership check.

The Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, payment-status records and contact requests. It explains why we use each category, how we protect access to it and how you can ask about correction, access or retention.

We may collect the contact details you submit, your phone verification result, account identifiers and records of sign-in or account actions. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, related status and reference data may also be recorded.

Yes. Send an account data request through the account help path, using the contact detail linked to your account and a clear description of the records requested. We may verify ownership first, then explain what can be provided under the Privacy Policy and local requirements.

Cookies or similar browser storage can keep a session active and retain selected access settings. Mobile and desktop sessions may create separate device signals for security. You can clear or restrict storage in your browser, but doing so may require another sign-in or affect session functions.

We use payment references and status details to connect an account action with the correct wallet or QRIS event and to answer a receipt question. The Privacy Policy does not ask you to send a wallet PIN or password when requesting help.

Retention depends on the purpose of the record, such as account operation, security, payment matching or a legal duty. When a record is no longer needed for those purposes, we assess deletion or anonymisation. You can ask about a specific category through the policy contact path.

You can ask us to correct inaccurate details or assess deletion of a record by describing the account and data involved. We will check ownership and consider operational and legal duties. Where local law permits, we will explain the available action and any reason a record must remain.