Reference

Privacy Policy for Your mono77 Account

Our Privacy Policy explains what we collect when you open a mono77 account, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record detailsPhone verification contextIndonesia access wording
mono77 Privacy Policy for Your mono77 Account
CONTACT ROUTES

Three Ways to Ask About Your Data

A clear contact path helps when you need a copy, correction or explanation under our Privacy Policy. Start from your signed-in account so we can match the request to the correct phone-verified profile. If wallet activity is involved, include the relevant DANA, OVO, GoPay or QRIS receipt reference without sending a password or one-time code.

Team online

Account privacy route

Open your signed-in account area and use the privacy contact route for a data question. We match the request with your phone-verified account before discussing profile details, which helps prevent another person from receiving account records.

Wallet record check

For a payment-data question, provide the date, rail and receipt reference for DANA, OVO, GoPay or QRIS. We can use those details to locate the relevant status record while keeping your password, PIN and one-time code private.

Correction request

Tell us which account detail appears incorrect and what should change. We may ask for an account step or phone verification before making an amendment, especially where the request affects login access or a wallet status record.

DATA PRACTICES

Six Privacy Controls We Explain Clearly

Our Privacy Policy is written around the actions you take inside the account, not vague promises.

Account details

We collect details you provide when opening or maintaining an account, such as contact data needed for access. The Privacy Policy explains why each category is used and how you can ask us to correct an entry that no longer matches your account.

Phone verification

A clear phone verification step helps us connect a privacy request to the right account. We do not ask you to place a password or one-time code in a support message, and we use verification details for access and security purposes described in the policy.

Device signals

Login time, browser and device signals can help us identify unusual account activity. These signals support security checks when you move from a mobile browser to desktop, while the policy sets out their purpose and the period they may be kept.

Cookies

Cookies help keep an account session working and remember practical choices during a visit. Our Privacy Policy explains the cookie categories, what they do for account access and how browser settings can affect the way a signed-in session operates.

Wallet references

A DANA, OVO, GoPay or QRIS receipt may appear as a payment-status reference rather than as your wallet password or PIN. We use that reference to check a transaction question and explain the related handling in the Privacy Policy.

Retention and changes

Some records remain available for account security, accounting or dispute handling, even after a session ends. You can ask what we hold, request a correction or ask about deletion through the account privacy route, subject to local law and required records.

Privacy Policy Answers for mono77

These questions address the parts of our Privacy Policy you are most likely to check before opening an account or linking a local wallet. Each answer points back to an account action, a data category or a contact step, so you know what to prepare before asking us to check your records.

It covers account details, phone verification, login and device signals, cookies, wallet references, contact messages and retention. It also explains why we use each category, how we protect account access and how you can request a copy, correction or clarification where local law permits.

Yes. The policy explains how DANA, OVO, GoPay and QRIS references may be used to check payment status or answer a receipt question. We do not need your wallet PIN or password for that route. Keep the receipt reference available when contacting us.

Open your signed-in account area and use the privacy contact route. State whether you want a copy, a correction or an explanation, then identify the relevant account detail. We may use phone verification to confirm that the request belongs to you before sharing account records.

You can ask us to correct an account detail that is inaccurate or outdated. Send the requested change through the account privacy route and explain which field is affected. We may check your phone-verified account first, especially when the change could affect login access.

Retention depends on the record and its purpose. Account security, accounting and dispute handling can require certain records to remain available after a session ends. The Privacy Policy explains these categories, and you can ask us which retention rule applies to a specific record.

Yes. Cookies used for session continuity and practical account settings are described by category and purpose. You can adjust cookie controls in your browser, although limiting them may affect a signed-in session or require you to verify access again when returning.

The policy is available from the account area, while service access and certain data requests depend on local law. We apply the stated handling where local law permits and will explain when a legal, security or record-keeping reason affects a request.