Reference

jon4d Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open a jon4d account, sign in on mobile, use DANA or QRIS, and contact support.

Clear data purposesWallet details explainedAccount access controlsCookie choicesContact route

Explore Our Lobby Read FAQ

How DANA And QRIS Data Is Used

jon4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details you provide during account creation, including your contact details and the phone verification step required before account access. We also receive technical data from the device and browser you use to sign in, such as session markers, language settings and security

1
events. When you choose DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, payment partners may send us a reference, amount, status and time so we can match the transaction to your account. We do not need the wallet password itself. Game activity connected with
2
Speed Baccarat, Fortune Rabbit, Bingo or Fishing God may be recorded for account history and security checks. Where local law permits, we use these records for service operation, fraud prevention and lawful requests. If you stop using the account, retention follows the purpose, unresolved account matters
3
and applicable legal duties.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY CONTACT

Where To Ask About Privacy Policy

A clear contact path matters when a name, phone number, wallet reference or device record looks incorrect.

Account request Ask us to correct account details through the support area after sign-in. We use your registered phone or email to locate the right record before discussing a request.

Wallet query For DANA, OVO, GoPay or QRIS records, include the payment reference and date. Never send a wallet PIN or password; our team needs the reference to trace status.

Access concern If a new phone, browser session or verification step blocks access, describe the device path and account email. We use those details to separate access help from privacy requests.

DATA CONTROL

Inside Our Data Handling Practices

We keep this policy practical: you can see why account, device, cookie and wallet records are connected to your use of the service.

Account records

We use your contact details and phone verification result to create, protect and maintain account access. If a detail changes, ask us to update the record through the support route.

Device signals

Browser type, device markers and sign-in time help us identify unusual access. They are used as security signals, not as a request for your device password or private files.

Cookie choices

Cookies can keep a session active and remember selected settings. Your browser can restrict or delete them, although doing so may require another login before account access.

Payment matching

A DANA, QRIS, OVO or GoPay reference lets us match a wallet event to the correct account. We receive status details needed for reconciliation, not your wallet PIN.

Retention approach

We retain records for the purpose described, unresolved support matters and applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

Change requests

You can ask about access, correction or deletion of personal details through the account support route. We may verify ownership before making a change or sharing account data.

Privacy Policy Answers For jon4d Accounts

These Privacy Policy answers address the account, wallet, device and contact questions you may have before opening an account. Each answer stays focused on how we handle your personal details and what you can ask us to change.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support requests, game activity records and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

Phone verification helps connect the correct person to an account before access is provided. It also gives us an account reference when you request a correction, access check or privacy change.

No. The Privacy Policy describes receiving payment references, status, time and amount for transaction matching. We do not need your DANA, OVO, GoPay or QRIS wallet PIN or password.

We may record browser type, device markers, language settings, session details and sign-in events. These signals help protect account access when you move from a mobile phone to a desktop browser.

Sign in, open the account support area and send a request naming the detail you want corrected or removed. We may verify your registered phone or email before changing the record.

We retain records for the stated purpose, unresolved account support and duties that apply where local law permits. When those reasons end, records are removed or de-identified through our process.

Use the privacy contact route shown in the account support area. Include your registered contact and a short description, such as an incorrect QRIS reference or an unfamiliar sign-in event.

jon4d Privacy Policy for Your Account Data

Where To Ask About Privacy Policy

Inside Our Data Handling Practices

Account records

Device signals

Cookie choices

Payment matching

Retention approach

Change requests

Privacy Policy Answers For jon4d Accounts

01 What does the jon4d Privacy Policy cover?

02 Why does jon4d request phone verification?

03 Does the Privacy Policy store my wallet PIN?

04 What device data does jon4d collect?

05 How can I request a change to my personal data?

06 How long does the Privacy Policy keep my records?

07 Who should I contact about a jon4d privacy concern?

Related Pages