Reference

Open the montigo 88 Privacy Policy

The montigo 88 Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesContact route
montigo 88 Open the montigo 88 Privacy Policy
CONTACT YOUR WAY

Switch to help when privacy questions stall

A direct support route helps you ask about the Privacy Policy without explaining your concern to several teams.

Account help Use the account help path when you want a copy of your stored profile data, need a correction, or cannot identify a phone verification record. We will ask for the linked contact detail and avoid sending private account content to an unverified address.
Cashier path Choose the cashier support path for a DANA, OVO, GoPay, QRIS, bank transfer or virtual account receipt question. Share the reference shown on your account, not your wallet password or one-time code, so we can trace the payment record safely.
Access request When you ask about access, deletion or eligibility, we check the request against the account record and local requirements. Access depends on local law, and we will explain the available route rather than changing data without confirming that the request belongs to you.
HOW WE HANDLE RECORDS

Browse the safeguards behind this policy

Privacy choices work best when the handling steps are visible. Our Privacy Policy separates account security, payment tracing, cookie behaviour and retention instead of treating every record alike.

Account security

Phone verification helps connect sign-in activity to the account holder before account access. Keep your password and one-time codes private; our support path will not need those secrets to check a login event or explain a security flag.

Device signals

When you use the mobile lobby or return on desktop, we may record browser type, device signals, session time and approximate network details. These records help identify unusual sign-ins and are not treated as a complete profile of your interests.

Payment references

For DANA, OVO, GoPay and QRIS activity, we use the transaction reference, amount status and related account details to match a receipt. Bank transfer and virtual account checks follow the same purpose, without asking for your wallet password.

Cookie controls

Cookies can keep a session open, remember a language or help us detect repeated sign-in attempts. You can adjust cookie permissions in your browser settings, although removing essential cookies may require another login before you reach your account.

Retention choices

We retain records while they support account security, payment disputes, support requests or legal duties. Once a record no longer serves one of those purposes, we remove it or separate it from direct account identifiers where practical.

Change requests

You can ask us to correct an account detail, explain a stored record, or discuss deletion through support. Include the contact detail linked to your profile; we verify ownership first and tell you if a legal or payment record must remain.

Check answers before opening your account

These Privacy Policy answers cover the questions we expect you to ask before creating a profile or connecting a local wallet. If your situation involves a disputed receipt, a changed phone number or access from a new device, use the matching support path and provide only the account details needed for us to locate the record.

It covers account creation, phone verification, sign-in records, device signals, cookies, payment references, support messages and retention. It also explains how to request a copy or correction and how local requirements affect an access or eligibility request.

We may collect the contact details you submit, phone verification status, sign-in events, device and browser signals, support messages, and payment references. We use these records for account security, payment matching, support handling and legal needs described in the Privacy Policy.

Yes. We may use DANA, OVO, GoPay and QRIS references to match a receipt with your account and confirm its status. For bank transfer or virtual account activity, we apply the same limited payment-tracing purpose and do not need your wallet password.

Open the account help route and send the email or phone number linked to your profile with a request for your stored records. We verify ownership before sharing personal data, then explain the scope, format and any records that must remain.

You can ask us to correct a profile detail through support. Include the current account contact and describe the change without sending a password or one-time code. We confirm ownership first, then update the record where the request is valid.

Essential cookies can maintain your session and help identify unusual sign-in activity, while other cookies may remember settings. Browser controls let you adjust optional cookies. If essential cookies are removed, you may need to sign in again on your phone.

We keep records for as long as they support account security, payment disputes, support handling or legal duties. After that purpose ends, we remove the record or separate it from direct identifiers where practical, subject to local requirements.