Reference

dian4d Privacy Policy For Your Account

Our Privacy Policy shows how dian4d handles the details linked to your account, mobile browser, wallet activity and support requests.

Clear data purposesWallet activity contextCookie choicesAccount request path

Browse Our Lobby Read FAQ

DANA And QRIS Data In Scope

dian4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details you enter during account opening, including your phone number, verification details and security records. It also covers device information from the browser you use, account sign-in events, support messages and transaction references connected with DANA, OVO, GoPay or QRIS. When you

1
use bank transfer or a virtual account through BCA, BRI, Mandiri or BNI, we may receive the reference needed to match your account activity. We use these records to provide account access, check wallet status, protect against unauthorised use and respond to your requests. We do
2
not ask for unrelated device content such as contacts or personal photos. Our handling and any access to the service depends on local law. Where local law permits, you may request details about stored data, ask us to correct an error or raise a concern through
3
the support path shown in your account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where To Ask About Privacy

You can raise a Privacy Policy question without searching through unrelated account pages. We route privacy requests through the account support path, where you can identify your account, describe the request and…

Account support route Open support from your signed-in account and select the privacy subject. Include your registered phone number so we can locate the correct account record before responding.

Wallet record check For DANA, OVO, GoPay or QRIS questions, provide the transaction reference shown beside the cashier record. We use that reference to investigate without requesting your wallet password.

Device access request If the mobile browser path keeps an old session, tell support the device and browser involved. We can separate a cookie issue from an account-security concern before changing records.

DATA PRACTICES

How dian4d Handles Account Data

Our privacy process follows the account steps you actually take, from phone verification to a wallet status check and a request sent to support.

Collection in context

We collect details when you open an account, complete phone verification, sign in, contact support or select a title such as Fishing God. We use each record for the action it supports.

Cookies and browsers

Cookies can keep your signed-in session and remember required settings on a mobile browser. You can clear them through browser controls, although doing so may require another account sign-in.

Account security checks

We review sign-in patterns, device details and verification status when protecting account access. Never send a wallet password in a support message, receipt attachment or Privacy Policy request.

Retention decisions

We retain account, support and transaction references only for the period needed for stated service, security, dispute or legal purposes. When a record is no longer needed, our process addresses its removal.

Who receives requests

Our account support team receives questions about stored data, cookies, correction or deletion. Payment references may be checked with the relevant processing path, while unrelated account details stay outside that request.

Changing your details

Ask us to correct a phone number, verification detail or other account record through support. We may ask you to confirm ownership before making a change, so another person cannot alter your account.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the searches we hear most often about dian4d accounts in Indonesia. They explain what happens after phone verification, how wallet references are treated, what you can request and which account path to use when a privacy concern needs attention.

It covers account details, phone verification, browser and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer activity.

We use your phone number to create and protect your account, complete the required verification step and help support locate the correct record when you ask about Privacy Policy rights.

Yes. The policy covers session cookies, browser settings, device signals and sign-in events used to keep account access working and identify unusual activity. You can clear cookies in your browser.

We use wallet and transaction references to match account activity, check a status question and investigate a receipt concern. We do not need your wallet password to handle a Privacy Policy request.

You can request details about stored account, device or support records through the signed-in support path. We may confirm account ownership first, and the request depends on local law.

Send a correction or removal request through account support with the affected detail identified. We review the request, confirm ownership where needed and respond according to applicable retention duties.

Use the support route inside your account and choose the privacy subject. Add a transaction reference only when relevant, such as a QRIS or bank transfer question, and avoid sharing passwords.

dian4d Privacy Policy For Your Account

Where To Ask About Privacy

How dian4d Handles Account Data

Collection in context

Cookies and browsers

Account security checks

Retention decisions

Who receives requests

Changing your details

Privacy Policy Questions For Indonesia

01 What does the dian4d Privacy Policy cover?

02 Why does dian4d need my phone number?

03 Does the Privacy Policy cover mobile browser data?

04 How are DANA and QRIS records used?

05 Can I ask dian4d for my stored account data?

06 How do I correct or remove my account details?

07 Who should I contact about a Privacy Policy concern?

Related Pages