Reference

Privacy Policy For Your mos77 Account

The mos77 Privacy Policy explains what we collect when you open an account, sign in from your phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
mos77 Privacy Policy For Your mos77 Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact route helps you act on the Privacy Policy instead of searching through account screens.

Account desk Ask us to locate the account details connected with your registered phone or email.
Wallet records If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send its reference and…
Security contact Report suspected account access through the support channel shown in your account area.
DATA PRACTICES

Six Practical Privacy Commitments

We keep the Privacy Policy connected to real account work: sign-in checks, wallet reconciliation, device sessions and support handling.

Account creation

When you open an account, we collect the details needed to create your profile and confirm contact ownership.

Wallet matching

A DANA, OVO, GoPay or QRIS reference can be used to match a payment status with your account.

Device sessions

We may record device and browser signals when you sign in from a mobile phone or desktop.

Cookie controls

Cookies can keep a session working and help us understand basic page use.

Retention choices

We retain account and transaction records only while they support the stated service, security, dispute or legal purpose.

Change requests

To correct, access or question personal data, contact us with your registered account detail and the request you want handled.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account questions you are most likely to ask before using mos77 from Indonesia. They cover what we collect, how wallet records are used, how to request a change and what happens when you contact support. If your situation is not listed, send a specific request through the account support path so we can check the relevant record and respond with the next step.

It covers account details, contact verification, device and browser signals, cookie choices, support messages and payment status records. The policy explains why we use each category, how security checks work and how you can ask about access, correction or retention.

Yes. It includes operational records such as a DANA or QRIS reference, amount status and processing result when connected with your account. We use those details to reconcile a request, investigate a mismatch and answer a receipt question.

Contact our account support path and state that you want a Privacy Policy data-access request. Include your registered phone or email, but never include your password or one-time code. We verify ownership before explaining which records can be provided.

You can ask us to correct inaccurate account details through support. Tell us which field is wrong and provide the registered contact used for verification. We check ownership first, then confirm whether the change was made or needs additional evidence.

Device and browser signals help us identify unusual sign-in patterns and protect your account. They can also explain a security prompt when you move between a mobile phone and desktop. The Privacy Policy sets out how these signals are handled.

We use cookies for session continuity, account functions and limited page-use measurement. You can adjust cookie settings in your browser. Blocking some cookies may interrupt sign-in or prevent a preference from being retained during a later visit.

You may contact us to ask whether deletion applies to your records. We first verify the account and assess active service, security, dispute and legal retention needs. Where local law permits, we remove or de-identify data that no longer needs to remain.