Reference

Privacy Policy For Your mp008 Account

Our Privacy Policy explains what account, device and wallet details we use when you open mp008 in Indonesia.

Clear data purposesWallet detail contextAccount access stepsMobile browser choices
mp008 Privacy Policy For Your mp008 Account
CONTACT PATHS

Get Privacy Policy Help Before Access

A direct support path helps you resolve a privacy question without guessing which account step matters.

Account privacy request Use our account support path to ask what personal details are linked to your mp008 account, why a field is needed, or how to request a correction. We may ask you to confirm account ownership before discussing private records.
Wallet reference question If DANA, OVO, GoPay, QRIS, bank transfer or virtual account details appear in your account history, tell us the date and reference shown. We can explain the stored payment reference without asking you to reveal a wallet PIN.
Device access concern If a mobile browser or desktop session looks unfamiliar, contact the support desk with the affected account detail. We can help identify the access record and explain the account step needed to secure future sign-ins.
DATA PRACTICE

What We Keep And Why It Matters

We keep this policy practical: each data group should have a clear account, payment, security or support reason.

Account details

We use the details attached to your account to identify your access request, respond to account questions and complete the clear phone verification step before account access. Keep your contact detail current so privacy requests reach the right record.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us match a wallet status, while bank transfer and virtual account references can support transaction questions. We focus on the reference needed for the account record, not your private wallet PIN.

Browser storage

Cookies or related browser storage may preserve a session choice or help the account path work on mobile and desktop. You can manage browser storage through your device settings, though clearing it may require you to sign in again.

Account security

We use account and device signals to help identify unusual access. You should keep your password private, complete phone verification when requested and contact support if a sign-in record does not match your own mobile browser or desktop session.

Retention approach

We retain personal details only for the account, payment, security or support purpose that requires them, subject to applicable obligations. A retention question should include your linked contact detail so we can explain which record and purpose are involved.

Change request

You can ask us to correct account details, clarify a data purpose or explain access to a record through the support path. We may verify ownership first, then confirm what can be changed and what must remain for an active account.

Privacy Policy Answers For mp008

These Privacy Policy answers address the account and access questions we expect from Indonesian customers. They cover the data used around phone verification, mobile browsing, local wallet references, cookies, corrections and contact requests. If your situation is not listed, use the support path with your linked account detail and we will explain the relevant policy step. Access depends on local law and remains available where local law permits.

The mp008 Privacy Policy covers account details, phone verification, device signals, browser storage, payment references and support requests. It explains why we use each category, how it supports account access and how you can ask about a record connected with your account.

Phone verification helps us confirm that an account access request belongs to the person who controls the linked contact detail. It also gives our support desk an account step to use when handling a privacy, sign-in or wallet-status request.

Yes. The Privacy Policy explains how payment references from DANA, OVO, GoPay and QRIS may be used to match account activity or answer a status question. We do not need your wallet PIN for that support context.

You can contact our support desk to request a correction to account details. Include the linked email or phone detail and describe the field that needs attention. We may confirm account ownership before changing or discussing private information.

When you use the mobile browser path, we may handle device signals and browser storage that support session operation and account security. You can manage cookies through device settings, but clearing them may sign you out or remove saved session choices.

Retention depends on the account, payment, security or support purpose involved and any applicable local requirement. Ask our support desk about a specific record using your linked account detail, and we will explain the relevant handling and retention context.

Use the mp008 account support path and include your linked contact detail, the subject of your request and any relevant payment reference. Do not send a password or wallet PIN. We will use the account context to route your Privacy Policy question.