Reference

Privacy Policy for Your mma128 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your mma128 account, including phone verification and wallet status.

Clear data purposesCookie choicesAccount access stepsContact for changes
mma128 Privacy Policy for Your mma128 Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact route matters when you want to ask about stored data, correct an account detail or understand a security check. Start from the support path connected to your mma128 account and include the phone number or account identifier used during sign-in. We can then match your request to the right record without asking you to send wallet passwords or full payment credentials. If you are checking a DANA, OVO, GoPay or QRIS reference, share only the transaction detail needed for us to locate it.

Team online

Account request

Use the account support route to ask what personal details are connected with your login. We may request a phone verification step before discussing private account records, helping us avoid sending account data to the wrong person.

Payment privacy

For a wallet or bank transfer question, provide the reference shown in your payment history rather than a password, PIN or complete card detail. We use the reference to check status while limiting the payment data included in the request.

Security concern

If a login event or device record looks unfamiliar, contact us through the account support path and change your password from your account settings. We can review the related access record and explain which security step may be required.

DATA PRACTICES

What We Do With Account Details

Your account details are handled for a defined operational reason, not collected as a general profile.

Account records

When you open an account, we may use your phone number, verification result and sign-in history to connect you with the correct profile. This supports account recovery and helps us identify whether a request comes from the account holder.

Device signals

A mobile browser or desktop session can create device, browser and connection records linked to access activity. These signals help us spot unusual sign-ins without requiring an installed app, and they can be reviewed when your access behaves differently.

Cookie choices

Cookies can keep a session active, remember selected settings or help us understand basic page use. Your browser controls can remove or block them, although changing those settings may require you to sign in again when opening the lobby.

Wallet references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, amount and status record for account reconciliation. We use that operational detail to match a payment event, while we do not ask for your wallet PIN or login password.

Retention requests

You can ask us whether a particular account record is still retained and why it remains stored. We assess deletion or correction requests against open account needs, security checks and any recordkeeping duty that applies where local law permits.

Policy changes

If this Privacy Policy changes, we place the revised wording on this page and update the effective wording shown with it. Checking this page before using your account helps you see how collection, cookies, contact steps or retention handling may have changed.

Privacy Policy Questions From Indonesia

The answers below address the account and data questions we expect you to ask before opening or continuing an mma128 account. They cover what we collect, why wallet references appear, how cookies work, how to request access or correction, and what happens when local rules affect account eligibility. If your situation is specific, use the account support path with the smallest amount of detail needed to locate your record.

The mma128 Privacy Policy covers information linked to your account, including phone verification, sign-in events, device signals, support messages, cookie use and payment references. It also explains how we use, retain and protect those records when you access the service where local law permits.

Phone verification helps us connect account access with the correct person and supports recovery when a login issue occurs. We may use the verification result as an account-security record, but you should never send us your phone password, wallet PIN or login password.

Yes. The Privacy Policy covers operational records created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These can include a payment reference, status and account link used for reconciliation, rather than your private wallet credentials.

Contact us through the support path connected with your mma128 account and ask for an account-data access request. Include the phone number or account identifier used at sign-in. We may complete a verification step before confirming which records can be provided.

You can request a correction when an account detail is inaccurate or no longer current. Send the request through account support and identify the field that needs attention. We may verify ownership first, then assess the change against security and recordkeeping needs.

Cookies can remember a browser session, save selected settings or provide basic usage signals. You can manage them through your browser controls, but blocking certain cookies may sign you out or affect account access. The Privacy Policy explains their purpose before you make that choice.

Yes. Account access and eligibility depends on local law, and some requests or features may be handled differently by jurisdiction. We assess privacy requests against the rules that apply to your access location, then explain any limit through the account support path.