Reference

Privacy Policy for Your dian89 Account

Our Privacy Policy explains how dian89 handles the details connected to your account, wallet activity and device access.

Account dataWallet recordsDevice accessCookie choices

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

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

This Privacy Policy applies when you open, access or manage a dian89 account through a supported browser or mobile device. We may handle account identifiers, contact details, verification details, login events, device signals and records needed to match a payment status. For example, a DANA, OVO,

1
GoPay or QRIS reference can help us trace whether a cashier request reached the account ledger. We use these records to provide account access, investigate disputed status and protect the wallet path from misuse. Where local law permits, we may also process data needed for the
2
lobby and account services you request. The policy applies to access from Indonesia, including your connection from Medan, subject to local rules.

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

PRIVACY CONTACT

Get Help With a Privacy Request

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

DATA PRACTICE

How We Handle Account Data

We handle privacy as an operating task attached to each account step, from phone verification through wallet status checks.

Collection

We collect details you provide during account opening, such as a contact route and verification response, plus technical events created when you log in. We use those details to connect your request with the correct account rather than building an unrelated profile.

Cookies

Cookies may keep a browser session available, remember a selected setting or help us understand a failed account step. Your browser controls cookie storage, while our support path can explain which cookie-related issue is affecting access to the policy or cashier page.

Account security

Phone verification takes place before account access where that step is required. We review login and device signals when activity looks unusual, and we avoid asking for wallet passwords or complete payment credentials during a support conversation.

Payment matching

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference can be matched with the account ledger. This helps us investigate a missing status while limiting the payment detail shown to the people handling your request.

Retention

We keep account, support and payment records for the period needed to operate the requested service, resolve a dispute or meet an applicable legal duty. When a record is no longer needed for those purposes, our retention process addresses its removal or restriction.

Your request

You can contact us to ask what personal details are linked to your account, request a correction or ask about deletion. We may verify account ownership first, then explain any limits that depend on local law before taking the requested action.

Privacy Policy Answers for dian89

These Privacy Policy answers address the searches we hear most often from people deciding whether to open an account. Each answer stays focused on the account, device and payment records connected with dian89. Where a request depends on identity checks or local rules, we explain that step directly so you know what to prepare before contacting support.

The Privacy Policy covers details you submit during account opening, phone verification and support contact, along with login, device and payment status events. We use those records for account access, security, cashier reconciliation and policy requests, subject to purposes and limits that depend on local law.

We may retain a payment reference, status and related account record needed to match a DANA, OVO, GoPay or QRIS request. We do not need your wallet password for that check. The exact record handled depends on the payment path and the request you make.

When you log in from a phone or browser, we may record device and session signals such as access time and unusual activity indicators. These signals help protect account access and investigate failed steps. They are handled under the Privacy Policy, not used as a reason to request your private wallet code.

Yes. Contact the policy support path with the email or phone route linked to your account and state whether you want access to a record or a correction. We may verify ownership before responding, then explain any restriction that depends on local law.

We keep records for the time needed to provide the requested account service, check a DANA, QRIS or bank transfer status, resolve a dispute or meet an applicable legal duty. Retention can differ by record type, and we address removal when that purpose ends.

Yes. Ask through the privacy contact path and identify the browser or account step where the cookie question appears. Cookies may support login sessions or stored preferences. Your browser also provides controls for storage, while our response explains the relevant policy purpose.

The page is available for you to read before opening an account, but account eligibility and some data requests depend on local law. Where local law permits, we handle the request described in the Privacy Policy after confirming the account details needed for a secure response.

Privacy Policy for Your dian89 Account

Get Help With a Privacy Request

How We Handle Account Data

Collection

Cookies

Account security

Payment matching

Retention

Your request

Privacy Policy Answers for dian89

01 What does the dian89 Privacy Policy say about account data?

02 Does dian89 store DANA, OVO, GoPay or QRIS details?

03 How does the Privacy Policy treat device information?

04 Can I request a copy or correction of my dian89 data?

05 How long does dian89 keep payment and support records?

06 Can I ask dian89 about cookies used on my device?

07 Does access to this Privacy Policy depend on local law?

Related Pages