Reference

Privacy Policy For Your Account Journey

mahjong2000 Privacy Policy explains what we collect when you open an account, use the mobile lobby, contact support or select DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesIndonesia access
mahjong2000 Privacy Policy For Your Account Journey
HELP WHEN NEEDED

Get Policy Help Beside Account Support

Questions about our Privacy Policy should have a clear route, especially when a phone verification step or wallet status needs checking.

Policy questions Use the account support route to ask how we collect, use or retain your…
Access requests If you want a copy, correction or removal request, identify the account step involved…
Wallet records A receipt or status question may involve OVO, GoPay, QRIS, bank transfer or virtual…
CONTROL YOUR DETAILS

How We Apply Privacy Policy

We apply this Privacy Policy to the account journey rather than treating every visit alike.

Account data

When you open an account, we may collect your contact details, phone verification result and sign-in events.

Device signals

Your mobile browser or desktop session can provide device, browser and security signals around sign-in.

Cookies

Cookies can keep a session active, remember a language or preserve a page choice.

Payment references

DANA, OVO, GoPay and QRIS activity can produce a reference, status and time connected with your account.

Retention

We keep account, support and payment records for as long as they serve the stated operation, dispute handling or a…

Change requests

Send a correction, access or deletion request through account support and tell us which record needs attention.

Privacy Policy Answers For mahjong2000

The questions below focus on the parts of our Privacy Policy that matter before account access: the details we collect, the role of cookies, wallet references, device checks and your request options. We keep the answers tied to the mahjong2000 account journey, so you can decide what to provide and where to ask for help.

It covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, access requests, corrections and deletion requests where local law permits.

We use the phone verification result to connect an account to the person completing the access step and to reduce mistaken or suspicious sign-ins. The result can also help support locate the correct account when you ask about a wallet status or Privacy Policy request.

Yes. Our Privacy Policy covers the payment reference, selected rail, status and time that may be linked to an account request through DANA or QRIS. It does not require you to send wallet passwords or one-time codes to support, and those credentials stay with the payment provider.

Contact us through the account support route and identify the email or phone detail attached to your account. State that you want an access copy under the Privacy Policy. We first check the requester's identity, then explain the records available and any lawful reason a part cannot be released.

You can send a correction or deletion request through account support and name the record, such as a contact detail, device entry or wallet reference. We verify the request, assess any operational or legal retention need, and tell you what action is possible where local law permits.

Cookies may keep your session, language choice or page setting available between visits. You can block or remove them in your browser, but the account path may then ask you to sign in again. Our Privacy Policy describes cookies as part of this browser-based access process.

Yes. Account access and eligibility depend on local law. The Privacy Policy explains how we handle related account and security records, but it does not override local requirements. If your location or account status creates a restriction, contact support through the signed-in account path for clarification.