Reference

Privacy Policy for Your mahong777 Account

Our Privacy Policy explains how we handle the details connected with your mahong777 account, including phone verification, DANA or QRIS records, cookie settings and access from your device.

Account detailsWallet recordsCookie choicesPhone checks
mahong777 Privacy Policy for Your mahong777 Account
CONTACT ROUTES

Where To Ask About Privacy

A direct support route helps you resolve a privacy question without repeating your account story across several channels. Use the support chat linked from your signed-in account and include the email or phone detail attached to your profile, not a password or one-time code. We can then locate a DANA receipt, device sign-in or cookie request more safely. If you are in Medan, the same digital route applies while access depends on local law.

Team online

Account privacy chat

Ask about the Privacy Policy through the signed-in support chat. We use your account identifier to check the request, while you should keep passwords, verification codes and wallet PINs out of the message.

Wallet record request

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the receipt reference and approximate time through support. We can compare the payment status with your account record without asking you to disclose a wallet PIN.

Access correction path

For a wrong phone number, email detail or device sign-in record, request a correction from support after signing in. We may ask for an account step to confirm that the request comes from you.

HANDLING PRACTICES

How We Handle Your Account Data

Privacy becomes clearer when each handling step has a defined purpose. We use account and device records to maintain sign-in security, connect payment status with the correct profile and respond to requests…

Data collected

We may collect your account name, phone or email detail, verification result, sign-in time, device signals and payment references. For DANA, OVO, GoPay and QRIS, we use status or receipt details needed to match an account step.

Cookie controls

Cookies can keep a session active, remember selected settings or help us detect unusual sign-ins. You can manage browser cookie settings, although removing required cookies may interrupt account access or require another phone check.

Account security

We check sign-in patterns, device changes and phone verification events to reduce mistaken access. Never share your password or one-time code with support; our team can handle a request using account details without those secrets.

Retention approach

We retain records for as long as needed for the stated account, security, payment reconciliation or support purpose, then remove or separate them when no longer needed, subject to local requirements and an unresolved request.

Correction requests

You can ask us to correct inaccurate profile details or explain a device or wallet record. Include the affected field, the reason for the request and your account contact so we can verify ownership before making a change.

Policy contact

Privacy questions belong in the account support chat linked to your signed-in area. Tell us whether your request concerns cookies, retention, access, phone verification or a QRIS receipt so the right record can be checked.

Privacy Policy Questions Answered

These Privacy Policy answers focus on the account situations you are most likely to face before opening access or while checking a wallet record. We describe the practical request path, the data involved and the security step used to protect your profile. Where eligibility or access is relevant, it depends on local law.

The mahong777 Privacy Policy covers account details, phone verification, device and sign-in events, cookies, support messages and payment references. It explains why we handle those records, how retention works and how you can ask for correction or clarification through signed-in support chat.

Phone verification helps us confirm that an account request comes from you and helps protect access after a device change. We record the verification result and related event, not your private code for support use. Keep the code private, even when asking about the Privacy Policy.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS when they are used in an account step. We use those records to match a receipt or status with the correct profile, not to publish wallet details.

Sign in and open the support chat, then state the field that is wrong, such as a phone or email detail, and explain the requested change. We may ask an account verification question before updating the record so another person cannot alter your profile.

We keep account, security, support and payment reconciliation records for the period needed for their stated purpose and applicable local requirements. When a record is no longer needed, we remove or separate it where appropriate. Support can explain the category connected with your request.

You can change cookie controls in your browser or device settings. Some cookies support sessions or security checks, so removing them may sign you out or require another phone verification step. The Privacy Policy explains the effect of these controls on account access.

Use the support chat inside your signed-in account and identify the request as a Privacy Policy matter. You can ask about access, correction, cookies, retention or a payment reference. Do not send passwords, one-time codes or wallet PINs; access depends on local law.