Reference

jellyslot Privacy Policy For Your Account

jellyslot Privacy Policy explains how we collect, use and protect details connected with your account, phone verification and wallet activity.

Account dataWallet recordsCookie choicesPhone verification
jellyslot jellyslot Privacy Policy For Your Account
HELP ROUTES

Support Beside Your Wallet Status

A clear support route matters when a Privacy Policy question follows a phone check or wallet event.

Account questions Ask us which account details we hold and why they are needed.
Wallet records If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the visible transaction…
Privacy requests Request access, correction or deletion through support.
DATA PRACTICE

Cookies, Devices And Auto Roulette Data

We apply this Privacy Policy to the practical data trail created when you sign in, browse the lobby or contact support.

Account details

We use your registration details and phone verification result to connect sign-in activity with the right account. This helps us answer a Privacy Policy request without exposing another person’s records.

Cookie controls

Cookies can remember session preferences and help us detect an unusual sign-in. You can adjust browser cookie settings, though removing required cookies may interrupt the account path.

Device signals

Your browser, device type, connection data and security events may be recorded when you open the lobby on mobile or desktop. We use these signals to protect account access.

Lobby activity

We may record the title or section you open, such as Auto Roulette, Monopoly Live or Fish Hunter, to maintain sessions, resolve support questions and check technical errors.

Retention choices

Records remain available while needed for account operation, payment reconciliation, disputes or legal duties. After that period, we delete, anonymise or restrict them where applicable.

Change requests

Contact support to request a copy, correction, restriction or deletion of your personal details. We may ask for phone verification before completing a request involving account security.

Privacy Policy Answers For DANA And Access

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover wallet references, cookies, device records, phone verification, retention and requests for changes. If your situation is not listed, contact support with the account reference you can see, and we will check the relevant record under the applicable local requirements.

It covers account details, phone verification, device signals, cookies, support messages and wallet references connected with DANA, OVO, GoPay or QRIS. It also explains retention and requests for changes.

We use phone verification to confirm account ownership before access and before discussing sensitive records. It helps us send a Privacy Policy response to the correct person without revealing account details.

Yes. We may store the reference, status and time linked to a DANA or QRIS instruction so we can match the account event. The provider keeps separate records under its own terms.

We may receive browser type, device category, connection details, approximate location and security events when you sign in or open the lobby. These signals help protect sessions and investigate technical requests.

Use the support route and state that you want an access request under the Privacy Policy. Include your account reference, then complete phone verification if we need to confirm ownership.

You can request correction, restriction or deletion through support. We assess the request against account operation, wallet reconciliation, dispute records and legal duties before confirming what can change.

We retain records while they are needed for account security, support, wallet reconciliation, disputes or legal duties. When the applicable need ends, we delete, anonymise or restrict the data.