Reference

jarumslot Privacy Policy For Your Account

Our Privacy Policy explains what jarumslot collects when you open an account, enter the casino lobby, or check DANA and QRIS payment status.

Account dataWallet recordsCookie choicesAccess requests
jarumslot jarumslot Privacy Policy For Your Account
HELP WITH DATA

Get Policy Support Through Your Account

A clear support route helps when you want to ask about a stored detail, a wallet reference or a device session. Start from the support path connected to your account and include the phone number or email linked to your profile, without sending a password. If your request concerns a payment receipt, use the cashier-linked support path so we can match the record without asking you to repeat unrelated personal details.

Team online

Account request

Use the account support path to ask what personal data is linked to your profile, including phone verification records and login activity. We may request account details to confirm your identity before responding.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, attach the payment reference rather than a wallet password. This lets us trace the relevant entry while limiting unnecessary disclosure.

Access correction

If a name, phone number or email is incorrect, tell us through the support route shown after login. We assess the request against account security checks before changing stored details.

HANDLING YOUR DATA

What We Do With Account Data

Our handling process follows the account actions you take: opening access, verifying a phone number, entering the lobby, checking wallet status or contacting support.

Data collected

We may receive your account name, contact details, phone verification result, login timestamps, device type, browser signals and payment references. Game selections such as Rocket Crash or Mega Fishing can also appear as service activity.

Cookie controls

Cookies and similar device storage can keep your session connected between login and the lobby. You can adjust browser controls, although blocking required cookies may interrupt account access or remove saved preferences.

Account security

We use phone verification, session signals and payment matching to help identify unusual access. Never share your password or one-time code through support, and sign out when using a shared device.

Retention periods

We keep account, security and payment records only as long as needed for the stated service purpose, dispute handling or a legal requirement. When a record is no longer needed, our process removes or de-identifies it.

Policy changes

If this Privacy Policy changes in a material way, we will place the revised date and updated wording on this page. Check the page before opening an account or continuing after a major change.

Request a change

You can ask for access, correction or deletion through the account support route. We may need identity checks, and some records may remain where retention is required by local law.

Privacy Policy Answers For jarumslot

These Privacy Policy answers address the searches we hear most often before account access. They explain wallet records, device behaviour, account requests and the support path in direct terms, so you can decide what details to share and how to ask for control over them.

It covers account details, phone verification, device and browser signals, cookies, lobby activity, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Payment references help us match an account action with a wallet or bank transaction, investigate an incorrect status and respond to a receipt request. We do not need your wallet password for that check.

Yes. Send an access request through the support route connected to your account, describe the records you need and complete the identity check. We assess the request under applicable local law.

Use the account support path to request a correction to your name, phone number or email. We verify that you control the account before changing profile data or phone verification details.

Cookies or similar storage may preserve your login session and lobby preferences on a phone or tablet. Browser controls can remove them, but required session storage may be needed to access your account.

Retention depends on the type of record and its purpose. Account, security and payment entries may remain for dispute handling or legal duties, then they are removed or de-identified when no longer needed.

Start with the support route shown inside your account. Include the relevant payment reference or profile detail, but never send a password or one-time code. We will use the submitted contact path to respond.