Reference

rajamahjong Privacy Policy for Your Account

Your account path, phone verification and wallet records are explained in one clear Privacy Policy, so you know what we collect before opening access.

Account dataWallet recordsCookie choicesPrivacy requests
rajamahjong rajamahjong Privacy Policy for Your Account
REQUEST SUPPORT

Where to Ask About Personal Data

A privacy question should have a clear route, especially when a login or wallet status stalls. Use the support channel shown in your account area and include the email or phone detail tied to your account, plus a payment receipt reference when your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a password.

Team online

Account access

Ask us to check a phone-verification record or account-data correction through the support route displayed after sign-in. Please do not send your password, one-time code or full wallet credentials.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the receipt reference and approximate date. We can then match the request to the relevant payment record.

Privacy request

Request access, correction or deletion through the same support channel, stating which account detail is concerned. We may ask for account verification before changing or releasing personal data.

DATA PRACTICE

Six Ways We Handle Your Account Data

We keep this policy practical by connecting each data use to an account step you recognise. Phone verification helps us distinguish your account from another sign-in, while device and browser records help…

Data we collect

We may receive your account details, phone-verification result, sign-in activity, device or browser signals and payment references. We collect these details when you submit them or when the site records an account event.

Why we use it

We use account and payment data to provide access, check a wallet status, connect a receipt with the right account and answer support requests. We do not need your password for ordinary privacy enquiries.

Cookie choices

Cookies can remember sign-in preferences and basic site settings across a mobile browser or desktop session. Your browser controls can limit cookies, although some account steps may then need to be repeated.

Account security

Phone verification and sign-in checks help protect the account path. Keep your password and one-time codes private; our support route will not require you to disclose either when checking a data request.

Retention period

We retain records only for the period needed for the purpose described in this policy, account security, payment matching or a legal requirement. When that need ends, records are removed or handled in a restricted form.

Changes and contact

You can ask for a copy, correction or eligible deletion of your personal data through the support channel in your account area. We may verify account ownership before completing the requested change.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the account steps Indonesian customers usually ask about before continuing. They cover payment records, cookies, mobile access, correction requests and the checks we may use to protect your account. If your question is not listed, use the privacy request route in the support area; access depends on local law.

It covers account details, phone verification, sign-in activity, device and browser signals, cookies, payment references and support requests. It also explains retention, security, correction and eligible deletion requests.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records used to match a receipt to your account.

Phone verification helps us connect an account request with the correct account and detect unusual sign-in activity. We record the verification result, not your private one-time code.

Use the privacy request path in your account support area and name the data you want copied or corrected. We may ask you to verify account ownership before releasing or changing records.

Yes. Your mobile browser settings can limit or remove cookies. Some preferences may not remain saved, so you might repeat a sign-in or account setting step during your next visit.

We keep payment references only as long as needed for account security, receipt matching, support handling or a legal requirement. The applicable purpose determines when the record is removed or restricted.

You can submit an eligible deletion request through the support channel in your account area. We first verify the request and may retain specific records where account security or local law requires it.