Reference

Privacy Policy For Your max889 Account

max889 Privacy Policy explains how we collect, use and protect details connected with your account, including phone verification, device access and wallet status for DANA, OVO, GoPay and…

Account dataWallet checksCookie choicesDevice security
max889 Privacy Policy For Your max889 Account
CONTACT PATHS

Privacy Policy Help From Your Account

A clear contact path matters when a Privacy Policy question involves your identity, wallet record or device. We ask you to use the support route inside your max889 account so we can connect the request with the correct phone verification record. If you are in Makassar or elsewhere in Indonesia, include the relevant transaction reference and the email or phone detail linked to your account. We use the submitted details only to investigate the policy request and return an answer through the same account path.

Team online

Account support

Open the support path after login and select the Privacy Policy topic. Include your verified phone number and the exact question, so we can locate the right account record without asking for a wallet PIN.

Wallet record check

For a DANA, OVO, GoPay or QRIS concern, send the transaction reference and status shown in your account. We use those details to trace a record, not to request your private wallet password.

Correction request

If your account detail is wrong, describe the correction through support and identify the affected field. We may ask for a phone verification step before changing information that controls access to your account.

DATA CONTROL

How max889 Applies Privacy Policy

We apply the Privacy Policy at the points where your data enters the account flow: phone verification, login, wallet selection and support contact.

Data purpose

We use phone and account details to create access, maintain your session and answer Privacy Policy requests. Wallet references support status matching for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Cookie settings

Cookies can remember a session and help us identify device behaviour connected with login. You can manage browser cookie controls, but switching them off may require another phone verification step when you return.

Account security

We treat your phone verification and login events as security signals. Never send a password or wallet PIN through support. If a session looks unfamiliar, contact us from the account route and describe the device or access time.

Device access

The mobile path records technical session details needed to keep your account open as you move from login to the lobby. Desktop and mobile checks can differ, so mention the device type when reporting a privacy concern.

Retention timing

We retain account, support and payment-status records only as long as needed for the stated service, security checks or legal duties. A removal request may not erase records that must remain for a permitted legal purpose.

Policy changes

If we change how personal data is used, we update this Privacy Policy and show the revised wording on the policy page. Check the page before opening an account or continuing access where local law permits.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the searches we hear most often from Indonesian account holders. They explain what we collect during phone verification, what appears in a wallet record, how cookies affect a mobile session and how to ask for access or correction. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, include that reference when you contact us through your account.

The max889 Privacy Policy covers account details, phone verification, login events, cookies, device session data, support messages and payment-status references. It explains why we use each category, how retention works and how you can request access or a correction where local law permits.

When you open an account, we collect the details needed to create access and complete phone verification. We can also record login and device session details for security. We do not need your DANA, OVO, GoPay or QRIS wallet PIN for this account step.

Yes. The Privacy Policy covers transaction references and status information linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These records help us match a payment event and investigate a status question without receiving your wallet password.

You can request a correction through the support route inside your account. Tell us which field is inaccurate and include the phone detail linked to access. We may ask for another verification step before changing data that protects your account.

Cookies can keep your session active and help us recognise technical device behaviour during login. Your browser controls can limit them, but the mobile path may then ask for another verification step. The Privacy Policy explains the purpose of these cookies and related session records.

We keep personal data only for the period needed to provide account access, protect the service, answer support requests or meet a permitted legal duty. A request to remove data can have exceptions when a record must remain for security or legal reasons.

Log in and use the account support path, choosing the Privacy Policy topic. Include your question, verified phone detail and any relevant wallet or transaction reference. Access and eligibility depend on local law, and we handle requests through the account route where local law permits.