Reference

Read the jos129 Privacy Policy

Our jos129 Privacy Policy shows what we collect when you open an account, sign in on mobile, browse Mahjong Ways 2 or use DANA and QRIS.

Clear data choicesWallet contextAccount access
jos129 Read the jos129 Privacy Policy
CONTACT ROUTES

Use Our Privacy Contact Path

A clear contact route helps when your Privacy Policy question involves a sign-in record, wallet reference or device entry.

Account request Ask about stored account details through our support path after sign-in. Include your verified phone contact and the specific Privacy Policy request, such as access, correction or deletion.
Wallet trace For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference only. We use it to check status without requesting your wallet password or personal PIN.
Policy question If you cannot sign in, use the contact route shown on the site and identify your account carefully. We may ask for verification before discussing private records or changing account data.
ACCOUNT SAFETY

Check How Account Data Is Handled

We keep this Privacy Policy practical by linking each data choice to an account action you recognise.

Data we collect

We may receive your phone or contact details during account creation, plus sign-in, device and transaction records. Browsing activity around Aviator, Bingo or Fish Hunter may also be linked to your account session.

Cookies and devices

Cookies and device signals help keep a signed-in session working and identify unusual access. On mobile, they can connect the login path with the lobby without exposing wallet credentials in the page.

Account security

Phone verification comes before account access, and we may check sign-in details when a request concerns private data. Never send us your password, wallet PIN or one-time security code.

Record retention

We retain account, payment-reference and support records for the period needed for service operation, security checks and legal duties. The Privacy Policy explains how those periods apply to each record type.

Changing your details

You can ask us to correct inaccurate account information through the support path linked to your verified contact. We may confirm ownership before changing a phone number or other sensitive field.

Requesting access

You can ask which personal data we hold and request a copy where local law permits. Tell us the account contact, request type and relevant date so we can narrow the search.

Find Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before account access. They explain the connection between your verified contact, device behaviour, wallet references and requests sent to jos129. If your situation is not listed, use the account support path and describe the record you want us to check.

The jos129 Privacy Policy covers account creation, phone verification, sign-in activity, device signals, cookies, wallet references, support messages, retention and requests about your personal data.

We use the phone contact supplied during account creation to support verification, account access and ownership checks. It also helps us identify the correct record when you request a data change.

Yes. The Privacy Policy explains how DANA, QRIS, OVO, GoPay, bank transfer and virtual account references may be used to match a transaction status with your account.

Send an access request through the account support path, using the verified phone or contact detail on your account. We may confirm ownership before sharing private records where local law permits.

You can ask us to correct inaccurate account information through support. Include the field that needs changing and your verified contact; sensitive changes may require an additional ownership check.

The Privacy Policy explains that device signals and cookies can maintain a sign-in session, detect unusual access and connect your mobile route to the lobby without displaying your wallet PIN.

Use the support route connected to your account and state that your request concerns retained data. Include a date range or transaction reference, but never send a password, PIN or security code.