Reference

idn789 apk Privacy Policy Explained

Our idn789 apk Privacy Policy shows how we handle the account details behind Live Roulette Diamond, Padang Mega Prize and the mobile lobby, including data linked to DANA…

Account dataWallet recordsDevice controlsCookie choices
idn789 apk idn789 apk Privacy Policy Explained
CONTACT ROUTES

Where Privacy Questions Reach Our Team

A clear contact path helps when you want to ask about the Privacy Policy, correct account data or understand a wallet record. Start from the support contact route shown after login, and include the phone number attached to your account without sending a password or one-time code. If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include the payment reference and status shown in the cashier path. We use those details to locate the right record while keeping the request tied to your verified account.

Team online

Policy requests

Use the support contact route inside your account to ask what personal data we hold, why it is used or how long a record remains. We may ask you to complete phone verification before discussing account-specific details, so a private request does not expose your data.

Wallet records

For a DANA, OVO, GoPay or QRIS question, attach the cashier reference and status rather than a full wallet password. Bank transfer and virtual account queries follow the same path, letting us match the transaction record without requesting unnecessary credentials.

Access help

If the mobile login path stalls, tell us your device type, browser version and the time of the attempt. We can separate a device cookie issue from an account verification issue, then explain the next privacy-safe step without asking you to share a secret code.

HANDLING DETAILS

How We Protect Account Data

Privacy protection is part of the account path, from phone verification through a return to the lobby.

Account data

We use your registration details and phone verification result to create and protect your account.

Payment separation

A DANA, OVO, GoPay or QRIS reference records the payment event, not your wallet password.

Cookies

Cookies help keep your session active, remember selected settings and connect a device to the correct login step.

Device signals

Your phone or desktop browser may provide language, browser, operating system and connection signals.

Retention choices

We retain account, security and payment records for as long as needed for the stated purpose, account support and applicable…

Change requests

You can ask us to correct an inaccurate phone, contact or profile detail through the account support route.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, device and wallet questions you may have before using idn789 apk. We explain the practical steps for access, data requests and payment references without asking you to publish private credentials. Eligibility depends on local law, and our support route remains available for account-specific clarification.

The idn789 apk Privacy Policy covers account registration, phone verification, login events, device signals, cookies and payment references. It explains why we use each category, how we protect account access and how you can ask for correction, access or clarification through the support route.

We may collect the contact and phone details needed to create your account, plus verification results and login activity. Your browser or device can provide security signals such as operating system and language. We use these details for access and protection, not for unnecessary profile building.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay or QRIS, including status, time and matching details. Bank transfer and virtual account actions can create similar records. These references help us investigate a cashier question without requesting your wallet password.

Use the support contact route shown after login and ask for an account data request. Include the phone number attached to your profile, but never send a password or one-time code. We may require phone verification before releasing account-specific details, where local law permits.

You can request a correction for an inaccurate contact, phone or profile detail through account support. State what appears wrong and what should replace it. We may check your account ownership first, then explain whether the change is applied or limited by a legal retention duty.

A new device, changed browser setting or unusual login pattern can trigger an extra check. Device signals and cookies help us distinguish a normal return from an unfamiliar access attempt. Keep your phone verification step private, and contact support if the check repeats.

Retention depends on the purpose of the record, account support needs and applicable legal duties. Payment references may remain while a transaction requires matching or explanation. The Privacy Policy describes deletion or de-identification handling when identifiable retention is no longer needed.