Reference

apk hijau slot Privacy Policy for Your Account

Our Privacy Policy explains how apk hijau slot handles the account, device and payment details you provide when you open an account or enter the lobby.

Account dataDevice signalsWallet recordsPolicy requests
apk hijau slot apk hijau slot Privacy Policy for Your Account
CONTACT ROUTE

Need Help With a Privacy Request

A clear contact route matters when your account record or wallet reference needs attention.

Privacy request desk Use the in-site support desk when you want a copy of your account data, an explanation of a device record or help sending a correction request. Include your account identifier so we can match the request safely.
Account contact path If phone verification blocks your privacy request, contact support from the same signed-in account where possible. We use the account step and device session to reduce the chance that a third party receives your details.
Wallet record check For DANA, OVO, GoPay or QRIS references, share the receipt code rather than a wallet password or full secret. We check the payment record against your account and explain what can be corrected or retained.
ACCOUNT SAFEGUARDS

What We Do With Account Data

We keep this policy practical by linking each data use to an account action. A login from the mobile browser, a phone verification step and a wallet status check can create different…

Collection scope

We collect details you submit for account creation and phone verification, plus technical records needed to keep a login session working. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match account activity.

Cookie choices

Cookies and similar browser storage can keep your session connected to the correct account and remember security settings. You can manage browser permissions on your device, although changing them may require another login or repeat phone verification.

Device signals

Our mobile browser path may record device type, browser version, network details and session time. These signals help us spot an unusual sign-in and are not a substitute for the account details you provide during verification.

Security step

Phone verification helps connect account access to the person completing the account step. Never send a password, wallet PIN or one-time code through support; we use account checks and limited record matching instead.

Retention period

We retain account, security and payment references only as long as needed for the stated service, dispute handling, security checks or legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Change request

You can ask us to correct inaccurate account details or explain a record through the support desk. We may verify your identity first, then confirm whether the requested change is possible under local law and our record duties.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or send a support request. They explain account data, wallet references, browser records, correction requests and access wording in plain terms. If your question concerns a specific DANA, OVO, GoPay or QRIS entry, keep the receipt reference ready and contact us through the in-site support desk.

It covers account creation, phone verification, sign-in records, device signals, cookies, payment references and support requests. It also explains why we use those records, how long they may be retained and how you can request access or correction.

We may handle the details you submit for an account, verification records, login history and technical device signals. We use them to connect you with the correct account, protect sign-in activity and respond to a request about your records.

We may retain transaction references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account so an account action can be matched to a payment record. Do not send wallet PINs or passwords; support needs only the relevant receipt reference.

Contact our in-site support desk from your signed-in account where possible and state whether you want access, correction or clarification. We may ask for phone verification or another account check before releasing details or changing a record.

Yes. Cookies and browser storage may keep your session connected and preserve security settings. You can adjust permissions in your mobile browser, but clearing storage can sign you out and may require phone verification when you return.

Access and eligibility depends on local law. We apply the Privacy Policy to supported Indonesia requests, but a request or account action may have limits where legal duties require us to retain records or verify identity first.

Use the in-site support desk and include your account identifier plus a short description of the concern. For a wallet matter, add the DANA, OVO, GoPay or QRIS receipt code, never a password or private wallet code.