Reference

Privacy Policy For Your Account

The mahjong505 Privacy Policy shows what account data we collect, why we use it and how you can request a correction before opening access.

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

Privacy Help Through Your Account

A clear contact path helps when you want to ask about a Privacy Policy request, a wallet reference or a login record. Start from the support link in your account area and include the email or phone detail connected to your account, without sending a password or one-time code. If your question follows a DANA or QRIS receipt, keep that reference ready so we can locate the relevant record without asking for unrelated data.

Team online

Account support

Use the support link inside your account to ask about collected data, a correction request or the Privacy Policy. We may ask you to confirm the account detail already on file before discussing private records.

Wallet status

For DANA, OVO, GoPay or QRIS records, send the payment reference shown in your account rather than a wallet password. This lets our support route check the relevant status while limiting the data shared.

Data request

Ask us to access, correct or delete eligible account data through the site contact route. Include the request type and your account identifier; we will use an account check before making a change.

DATA PRACTICES

Six Ways We Handle Your Data

We keep the Privacy Policy practical by connecting each data practice to an account action you can recognise.

Collection

We collect account details you submit, verification events, device signals and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match requested account activity.

Purpose

We use data to provide account access, check a login, connect a receipt to your account, answer a support request and meet applicable legal duties. We do not need every device detail for every request.

Cookies

Cookies can keep a session open, remember a selected setting and help us understand which page caused a support issue. You can manage browser cookie controls, although some account steps may then need to be repeated.

Account security

Phone verification may be required before account access or a data change. We do not ask you to disclose a password or one-time code in support messages, and a new-device signal can prompt an account check.

Retention

We retain account, support and payment-reference records only for the time needed for the stated purpose, account protection or applicable legal duties. When a record is no longer needed, our handling follows the policy process.

Your request

To request access, correction or removal of eligible data, use the contact path in your account area. Tell us which record you mean, such as a phone detail or QRIS receipt, so we can check it accurately.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to ask about before using mahjong505. We explain wallet references, cookies, device checks and data requests in plain language, while eligibility remains where local law permits. If your case is not covered, use the support route linked from your account area and include only the details needed to identify the request.

The mahjong505 Privacy Policy covers account details, login and verification events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access and how you can request access, correction or removal of eligible data.

Yes. The Privacy Policy includes references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match a requested account action or answer a receipt question; we do not need your wallet password or one-time code.

A phone or device check helps us confirm that the person requesting account access or a data change is connected with the account. We may use device and connection signals to identify unusual login behaviour, then ask for phone verification before continuing.

Cookies can support a login session, remember a setting and help us trace a page issue. Your browser controls let you manage cookies. If you block some of them, the account path may not remember your choice and you may need to repeat a step.

You can request access to eligible account data or ask us to correct a phone detail, contact record or other account field. Use the account support route, name the record you mean and complete the account check before we discuss private data.

We keep payment references for as long as they are needed to match the requested account activity, protect the account, resolve a support question or meet applicable legal duties. The Privacy Policy process applies when a record is no longer needed.

Open the support link from your account area and select a data or Privacy Policy request. For a DANA or QRIS query, include the reference shown in your account. Do not send passwords or one-time codes; access and eligibility depends on local law.