Reference

Privacy Policy for mahjong118 Accounts

The mahjong118 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use local wallet options in Indonesia.

Account clarityWallet contextCookie choicesLocal access
mahjong118 Privacy Policy for mahjong118 Accounts
HELP WITH PRIVACY

Get Help With Your Privacy Request

A privacy question should not interrupt your account path, so we keep requests tied to the same support route used for login and wallet status matters. Contact our support channel from the account area and state the email or phone detail connected with your profile, along with the request you want us to handle. We may ask for a verification step before discussing personal data. This protects your account when a DANA receipt, QRIS reference or device session needs checking.

Team online

Account request

Use the support path beside your account area to ask for a copy, correction or removal of personal details. Include the phone number or email connected to mahjong118 so we can locate the correct profile before responding.

Wallet reference

If your request concerns DANA, OVO, GoPay or QRIS records, share the relevant receipt reference without sending a password or one-time code. We use the reference to separate a payment question from unrelated account data.

Session concern

Tell us when an unfamiliar phone or desktop session appears in your account. We can check the sign-in record, guide the account-security step and explain which data the Privacy Policy covers for that event.

DATA HANDLING

What Your Privacy Controls Cover

We handle privacy requests through identifiable account details rather than vague platform-wide requests.

Collected details

We may receive your phone or email, verification result, sign-in timestamps, device and browser signals, support messages and transaction references. We collect these details to connect your account, investigate faults and keep wallet status attached to the right session.

Cookie settings

Cookies can keep your selected settings and help us understand whether account pages load after sign-in. You can manage available browser controls, although switching off certain cookies may require you to repeat an account step.

Account security

Phone verification and session checks help us identify unusual access before account details are discussed. Never send your password or one-time code through support. We use a verification step when a request could expose your profile.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may appear in service records. We use that reference to check status and receipts, while the Privacy Policy does not replace the terms of your payment provider.

Retention period

We keep personal data while it serves account access, security, support, dispute handling or a legal requirement. When the relevant purpose ends, we remove or de-identify the record according to our operational process.

Change request

You can ask us to correct inaccurate profile details or explain how a record is used. Send the request through support from the account path, identify the affected detail and complete any check needed to protect your profile.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we expect before an Indonesian customer opens an account or connects a wallet. We keep the wording practical: what we collect, why a device record appears, how to request a change and what happens when access depends on local law. If your situation is not covered, use the support path with the account detail you want us to check.

It covers personal data connected with your account, including phone or email details, verification results, sign-in records, device signals, cookies, support messages and payment references. It explains why we use each category for account access, security, support, service operation and required record keeping.

Phone verification helps us connect account access to the correct profile and reduce the chance of discussing personal data with the wrong person. We may use the result when you sign in, request a data change or ask support to inspect a wallet status.

Yes. The Privacy Policy covers DANA, QRIS, OVO, GoPay, bank transfer and virtual account references that appear in our service records. We use them to check transaction status or a receipt question, while your payment provider keeps its own separate data practices.

You can contact support from your account path and request a copy, correction or explanation for personal data linked to your profile. State the affected phone or email detail and complete verification when requested. We assess the request under this Privacy Policy and local requirements.

We may record browser, device and session signals to identify sign-in activity, diagnose loading faults and protect account access. Cookies can remember settings and measure page function. Browser controls may limit some cookies, but you might need to repeat an account step.

We retain a record while it supports account operation, security checks, support, disputes or a legal requirement. After the relevant purpose ends, we remove or de-identify it through our operational process. A payment or support record may therefore remain longer than a temporary session signal.

Access or eligibility depends on local law. Where local law permits, you can use the account path from a supported phone or desktop browser. If you are unsure about your position, check the rules that apply to you before opening an account or sending a request.