Reference

kopi77 Privacy Policy For Your Account

Our Privacy Policy explains how kopi77 handles the account, device and wallet data used when you move from login to the lobby.

Account dataWallet referencesDevice controlsAccess depends on local law
kopi77 kopi77 Privacy Policy For Your Account
CONTACT PATHS

Where To Ask About Account Data

A clear contact path helps you resolve a data question without sending sensitive details through the wrong route. Start from the support link inside your account and include the phone number or account identifier requested there. For wallet issues, keep the DANA, OVO, GoPay, QRIS or bank reference visible, but never send a password or full security code.

Team online

Account access

Use the support path shown after login when your phone verification, account details or device approval needs checking. We use the account record to route the request and may ask for a matching identifier.

Wallet status

For a DANA, OVO, GoPay, QRIS, virtual account or bank transfer query, share the reference and status shown in your cashier record. We use that detail to locate the related event.

Privacy request

Ask through the account support route when you want to access, correct or remove eligible data. We may confirm account ownership before making a change, so another person cannot alter your record.

HANDLING DETAILS

Device Security For Mobile Wallet Access

The policy works alongside practical account controls, so your data is considered at each step rather than only at account creation.

Data we handle

We may handle your phone or account identifier, verification state, device details, sign-in events and payment references. These records help connect activity to your account and investigate access or wallet status questions.

Cookies and storage

Cookies and similar storage can remember session settings, support sign-in continuity and help us detect unusual browser activity. You can manage browser storage through your device settings, though some account steps may then need repeating.

Account security

Phone verification and device checks help protect the account before access is completed. Never place a password or one-time security code in a support message, even when discussing a DANA or QRIS record.

Retention approach

We keep account, security and transaction records only as long as needed for the stated service purpose, dispute handling, account protection or a legal requirement. When a record is no longer needed, our process removes it or separates it from direct account use.

Who can access

Access is limited to people or service partners who need a record for account support, security checks, payment matching or a valid legal request. We do not treat your wallet password as a support detail.

Requesting changes

You can ask us to access or correct eligible account data through the support route inside your account. We may verify your phone or account identifier first, then explain the result and any required next step.

Privacy Policy Questions For DANA Accounts

These Privacy Policy answers focus on the account steps Indonesian customers ask about most often. They cover wallet references, device access, correction requests and the limits that apply when local rules affect account handling.

It covers account identifiers, phone verification, device signals, sign-in events, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

No. We use payment references and status details to match an account event, but you should never send a DANA password, wallet password or one-time security code through support.

Phone verification helps confirm that the person requesting account access or a data change controls the matching account. We may use that check before discussing records or updating account details.

Yes. Use the support route inside your account and state which detail needs correction. We may confirm your account identifier or phone before reviewing the request and applying an eligible change.

We may record device type, browser signals and security events connected with login. This helps identify unusual access when you move from a mobile login to the lobby or payment status page.

We retain payment references for the period needed for account support, status matching, disputes, security work or a legal requirement. After that purpose ends, the record is removed or separated from direct use.

Yes. Contact us through the support path inside your account and describe the access, correction or removal request. Any account eligibility or handling requirement depends on local law and may require ownership checks.