Reference

Privacy Policy for Your dki4d Account

dki4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPolicy requests
dki4d Privacy Policy for Your dki4d Account
REQUEST PATHS

Support Routes for Privacy Requests

A clear contact route matters when your account data or wallet record needs attention. We ask you to send a privacy request from the account contact route connected to your dki4d profile so we can check ownership before discussing details. If login access stalls, use the support entry beside the login flow and state whether your request concerns account data, device access or a DANA, OVO, GoPay or QRIS reference.

Team online

Account contact

Use the contact route attached to your account when asking for a copy of personal data. We may request the phone verification detail already associated with your profile before releasing account-specific records.

Wallet record

For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate date rather than a wallet password. This helps us locate the correct cashier event while limiting the details shared in support.

Login support

If you cannot reach the privacy page after signing in, open the support entry beside the login path and identify your device type. We can then separate an access issue from a request to change stored data.

DATA CONTROLS

Six Controls Behind Our Privacy Practice

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We collect the details needed to create and maintain your account, then use them to support sign-in and phone verification. We do not need your DANA, OVO or GoPay wallet password to match a payment record.

Device signals

A mobile or desktop sign-in can create technical security records such as device type, browser and time. These signals help us spot unusual access and protect your account without treating them as a substitute for your account credentials.

Cookies

Cookies can keep a session active, remember selected settings and help the privacy page load correctly. You can manage browser cookie controls, although changing them may require another sign-in before account or wallet pages open.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to connect a cashier event with your account. We use the reference and status needed for reconciliation, rather than collecting a wallet password.

Retention

We retain account, security and payment records for the period needed for account protection, dispute handling and legal duties. When that period ends, records are removed or separated from direct account identification where practical.

Your request

You may ask what personal data we hold, request a correction or ask about deletion through the account contact path. We check the requester's identity first and explain any limit that depends on local law.

Privacy Policy Questions for dki4d

These Privacy Policy answers focus on the account actions you are most likely to check before opening access from Indonesia. We explain why phone verification, device records and wallet references appear in our systems, how to reach us from mobile or desktop, and what happens when you ask for a copy, correction or deletion. Where local law permits, we handle each request through the account contact path.

The dki4d Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It applies when you open the account, use the mobile lobby, check Blackjack or Fish Hunter, or connect activity with DANA, OVO, GoPay or QRIS.

We use phone verification to confirm that an account access request belongs to the person who controls the registered contact. It can also help us respond to a Privacy Policy request safely. We do not ask you to send a wallet password through support.

No. The Privacy Policy describes payment references and status records for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. Those references help match a cashier event to your account; your wallet password should remain with the relevant payment service.

Use the contact route connected to your account and ask for a personal data access request. Include the registered contact and the record type you want checked. We verify account ownership before sharing details, and the response path depends on local law.

Yes, you can ask us to correct inaccurate account or contact details through the account support path. State which field is wrong and provide the current value. We may request phone verification before changing the record so another person cannot alter your account.

We keep account, device security and payment-reference records only while they support account protection, dispute handling or legal duties. Retention can differ by record type. When the applicable period ends, we remove the record or reduce its direct link to your account.

You can contact us to ask about deleting personal data linked to your account. We first check ownership and then assess the request against security, dispute and legal needs. Where local law permits, we remove eligible records and explain any data we must retain.