Reference

Read the jaguar33 Privacy Policy

Our Privacy Policy explains what we collect when you open a jaguar33 account, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet recordsCookie choicesAccess requests
jaguar33 Read the jaguar33 Privacy Policy
PRIVACY HELP ROUTE

Contact us about your data

A direct support route helps you resolve privacy questions without searching through the lobby. Open the account help area and include the email or phone detail linked to your account, plus the request you want us to handle. We use those details to locate the right record, check account ownership and reply with the next step where local law permits.

Team online

Account support path

Use the support link beside your account and describe whether you need access, correction or deletion. We may ask for a phone verification step before discussing private account records.

Wallet record query

For a DANA, OVO, GoPay or QRIS question, share the transaction reference rather than extra wallet credentials. This lets us check the payment record while keeping unrelated account details out of the request.

Cookie assistance

If browser storage affects your policy choices, tell us which device and browser you use. We can explain the available cookie controls and what changes after you clear stored data.

DATA HANDLING DETAILS

Check how account data stays protected

We keep this policy practical by linking each data use to an account action you recognise.

Account details

We may hold your name, contact detail, phone verification result and account activity needed to operate access. Keeping these fields together helps us distinguish your account from a similar wallet record.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account events can create reference, amount and status records. We use those details to match a transaction and investigate a stalled cashier status.

Device signals

When you use a mobile browser or desktop browser, we may record device and connection signals linked to login protection. These checks help identify unusual access without requiring your wallet password.

Cookies

Cookies and similar browser storage can remember a session, protect account access and retain selected settings. You can manage or clear them in your browser, although some account steps may then need repeating.

Retention period

We retain account, payment and support records only for the period needed for the stated purpose, account safety and applicable legal duties. When a record is no longer needed, our handling process addresses removal or restriction.

Changes and contact

Ask us to correct an inaccurate field, explain a data use or handle another permitted request through account support. Include enough detail to locate the record, and we may verify ownership first.

Find Privacy Policy answers before joining

These answers focus on the questions you may search before opening a jaguar33 account. They explain the practical path for account data, local wallet records, browser behaviour and requests. For a situation that depends on your location or circumstances, use the policy contact route so we can assess the request under local law.

The jaguar33 Privacy Policy covers account details, phone verification, payment references, device signals, cookies, support records, retention and requests to access or correct your data.

We use DANA and QRIS reference details to match a wallet event to your account, show the correct payment status and investigate a receipt question without requesting unrelated wallet credentials.

Yes. Contact us through the account support path, identify the field that needs correction and provide enough account detail for ownership checks. The available action depends on local law.

Yes. It explains how cookies and browser storage can support sessions, account protection and saved settings. You can clear or manage them in your mobile or desktop browser, though some steps may repeat.

We use phone verification and device or connection signals as part of account protection. If access looks unusual, we may request an additional ownership check before discussing private records.

Retention depends on the purpose of the record, account safety and applicable legal duties. The Privacy Policy explains this approach, and support can address a specific record request where local law permits.

Open account support and state whether you want access, correction, deletion, an explanation or a cookie question. Include your linked contact detail, then complete any ownership check we request.