Reference

Open mapan777 Privacy Policy Clearly

mapan777 explains how we collect, use and protect the details connected with your account, including login records and wallet activity.

Account dataCookie choicesWallet recordsContact path
mapan777 Open mapan777 Privacy Policy Clearly
CONTACT OPTIONS

Ask Support About Your Privacy Policy

A clear contact path helps when you want to understand a record, change an account detail, or ask why a privacy request needs verification. We keep privacy questions close to the account and cashier paths, so you can include the relevant login or receipt reference without sending sensitive details through an unrelated channel.

Team online

Account contact form

Open the contact route inside your signed-in account and choose the privacy subject. Include your account identifier, but never send a password, wallet PIN, or full payment credential.

Wallet status query

For a DANA, OVO, GoPay or QRIS record, attach the receipt reference and date. We use those details to locate the event while limiting exposure of unnecessary wallet data.

Access assistance

If phone verification blocks your request, tell support which step stopped you and the device path used. We may ask for identity checks before discussing account-linked data.

DATA PRACTICES

Browse How We Handle Your Data

The practical details below explain how we approach privacy during ordinary account activity. We separate account access, payment references, device signals and contact requests so each request can be handled with the…

Account details

We use your registration details and verified phone number to create, maintain and protect your account. If a detail changes, contact us from the account path so we can confirm the request safely.

Cookies and browser signals

Cookies and similar browser signals can keep sessions working, remember selected settings and help detect unusual sign-in activity. You can manage browser permissions, though some account functions may then require another login.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep references needed to match status and receipts. We do not need your wallet PIN or full password for that matching step.

Account security

Phone verification, sign-in records and device signals help us identify unusual access. When a request concerns private account data, we may ask you to complete the same verification path before sharing details.

Retention periods

We retain records only for as long as needed for account operation, security checks, dispute handling and applicable legal duties. When a record is no longer needed, our processes are designed for deletion or secure restriction.

Changes and requests

You can ask for access, correction, clarification or deletion where applicable by contacting us through the account contact route. We assess each request against identity checks, technical needs and local legal requirements.

Find Privacy Policy Answers Before Opening

These common questions focus on the records and choices that matter when you use an account from Indonesia. If your situation is not listed, contact us from the signed-in account area and describe the specific Privacy Policy request without sharing secret credentials.

It covers account details, phone verification, sign-in events, cookies, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Use the privacy contact route inside your signed-in account, state that you want an access request, and provide the account identifier or receipt reference needed to locate the correct records.

Yes, you can ask us to correct inaccurate account details through the account contact path. We may confirm your phone verification or another account step before applying a change.

Yes. It explains that cookies and browser signals can support sessions, settings and unusual-access checks. On a mobile browser, restricting cookies may require more frequent sign-ins to your account.

We use limited references to match a wallet or bank event with your account, confirm status and handle receipt questions. We do not need your wallet PIN or full sign-in password.

Retention depends on the record and why it is needed, such as account operation, security, disputes or legal duties. When the purpose ends, data is deleted or securely restricted where applicable.

Yes. Start from the signed-in account contact route and select the privacy subject. If phone verification stops access, describe that step and the device path so support can direct your request.