Reference

diva4d Privacy Policy For Your Account

Our Privacy Policy explains how diva4d handles the details connected with your account, from phone verification before access to wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessYour choices
diva4d diva4d Privacy Policy For Your Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact path helps you act on this Privacy Policy without guessing which team to reach. Start from the support link beside the account or cashier path and include the phone number attached to your account, the relevant date, and a short description of your request. We use those details to locate the correct record without asking you to disclose a password or full wallet credential. If you are in Semarang, the same account support route applies where local law permits.

Team online

Account data request

Use the support route beside your account area when you want to ask what personal details we hold. Include your verified phone number and the requested record type, such as sign-in history or profile details, so we can check the correct account.

Wallet record query

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference shown in your cashier history. We can compare that reference with the stored payment status while keeping your wallet PIN, one-time code and full banking credentials out of the message.

Access concern

If a phone verification step or device sign-in looks unfamiliar, contact us through the account support link and pause further attempts. Tell us the device type and approximate sign-in time; these details help us check access events without requesting your password.

DATA PRACTICES

Six Privacy Controls Behind Your Login

Our handling of this policy area follows the practical steps you see around your account rather than a vague promise.

Account creation

When you open a diva4d account, we collect the details needed to create your profile and connect your verified phone number. We use that account record to distinguish your sign-in from another device and to direct privacy requests to the correct account.

Phone verification

Phone verification takes place before account access, so the number attached to your profile is part of our access record. If that number changes, ask through support rather than creating duplicate details; this helps us check ownership before changing the account record.

Device signals

A mobile visit to Fishing War Mobile Play or Aviator Fast Round may create device, browser, session and security-event records. These signals help us maintain a session and investigate unusual access; they are not a request for the contents of your personal device.

Cookies

Cookies can remember necessary sign-in and privacy choices on the browser you use. You can clear or restrict them through your browser controls, although some account steps may then need to be repeated. We use cookie data for site operation and access checks described in this policy.

Retention

We keep account, support, security and payment-reference records only for as long as needed for the purpose described here, account administration, dispute checking or applicable legal duties. When a record is no longer needed, our handling follows deletion or anonymisation processes appropriate to that record.

Change requests

To request correction, deletion, access or clarification, contact us from the account support path with your verified phone number and a precise request. We may ask for an account check before making a change, so another person cannot alter your profile or obtain its records.

Privacy Policy Answers For diva4d Accounts

These Privacy Policy answers address the searches we expect before you open an account or connect an Indonesian wallet. They explain the records linked to your login, the role of payment references, browser behaviour, and the route for exercising your choices. If your situation is not covered, use the support path beside the account area and refer to the specific part of this policy you want clarified.

It covers data connected with your account, phone verification, sign-in activity, device and browser signals, cookies, support messages and payment references. It also explains retention, security handling and requests for access or correction when you use account services where local law permits.

We may collect your account identifiers, contact details, verified phone number, sign-in events, device details, browser data and messages sent through support. We also retain transaction references and wallet status details needed to match DANA, OVO, GoPay or QRIS activity.

Yes. The Privacy Policy covers the payment reference, status and receipt details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use these records to reconcile an account action, not to request your wallet PIN.

Use the support link beside your account path and state that you want an account data request. Include your verified phone number, the record category and a useful date range. We may complete an ownership check before sending or displaying records linked to your account.

You can contact us through the account support route to request a correction, deletion or clarification. Tell us exactly which detail is involved and why it is incorrect. We assess the request against account administration, dispute records and applicable legal duties before changing it.

Cookies can remember necessary sign-in and privacy selections on your current browser. You can clear or restrict them through browser settings, but doing so may sign you out or require phone verification again. Our Privacy Policy explains the cookie purposes connected with account access.

Yes. Access, eligibility and certain privacy requests depend on local law and apply where local law permits. If a request needs a legal or ownership check, we will use the account support path to explain the next step without asking for your password or wallet PIN.