Reference

jaguar33 Privacy Policy For Your Account

Our Privacy Policy explains how jaguar33 handles the details you provide during phone verification, account access and wallet activity.

Clear data purposesWallet record contextCookie choicesAccount access requests
jaguar33 jaguar33 Privacy Policy For Your Account
CONTACT ROUTES

Wallet Receipt Questions Reach Our Support Route

A clear contact path matters when a Privacy Policy question concerns a real account event.

Account access If phone verification blocks access, contact the account-support route shown after sign-in or on the access screen. Tell us which step stopped, and we can direct a Privacy Policy request without asking you to publish your password or wallet PIN.
Payment records For a DANA, OVO, GoPay or QRIS record, include the payment reference, date and account phone number through our support path. We use those details to locate the status while keeping the request focused on the relevant transaction record.
Privacy requests To ask about access, correction or deletion, state the request clearly in your account-support message. We may ask for an account check before changing data, because a policy request must not expose another person’s account or payment details.
HANDLING DETAILS

How jaguar33 Handles Dragon Tiger Data

We apply the Privacy Policy to the account activity around every area you open, including Dragon Tiger Live and the mobile lobby.

Data we receive

We may receive your phone number, verification result, sign-in time, device or browser signals, support messages and payment references. If you open Dragon Tiger Live, the policy concerns the account and session records connected with that activity, not a request for unrelated personal details.

Cookie controls

Cookies can keep a session active, remember a selected setting or help us identify repeated access attempts. Your browser controls whether some cookies are stored. Blocking them may affect sign-in or policy-request forms, so check the browser settings used on your mobile device.

Account security

Phone verification is part of the account-access check, and we may compare device or session signals when a request looks unusual. Never send your password, wallet PIN or one-time code in a support message. These steps help us protect your data before responding.

Retention periods

We keep account, support and payment references only for the period needed for the stated service purpose, account protection or a legal obligation that applies to us. When a record is no longer needed, our handling process considers removal or separation from active account use.

Requesting changes

You can request access to, correction of or deletion of personal details through the account-support route. Explain which field or record is concerned, such as a phone detail or QRIS reference. We may verify account ownership before making a change.

Policy contact

Questions about this Privacy Policy should include the account phone number and a short description of the issue, but not your password or wallet PIN. Our support path can route a request about cookies, retention, account data or payment-status records.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain what to prepare before contacting support, how wallet references fit into the policy and what access wording applies when you use jaguar33 from a phone or desktop browser. If your situation is unusual, send the specific request through the account-support route.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, account-security checks and ways to request access, correction or deletion.

Your phone number supports account identification and the verification step required before account access or a sensitive data request. We may use the verification result to protect your records, but you should never send a password, wallet PIN or one-time code through support messages.

Yes. When you use DANA or QRIS, we may retain a reference, amount status and related account detail so a payment question can be checked. The same policy treatment applies to OVO, GoPay, bank transfer and virtual account records connected with your account.

Use the account-support route and state whether you want access to a record or correction of a specific detail. Include your account phone number and the affected item, such as a verification detail or payment reference. We may verify ownership before responding.

You may send a deletion request through the support route, and we will assess it under the Privacy Policy and any applicable retention duty. Some account, security or payment records may need to remain for a required period before removal or separation.

Cookies can support a sign-in session, remember a setting and help identify unusual access. Your mobile browser lets you manage cookie storage, although blocking required cookies may interrupt account access or a policy-request form. The same choices can be checked on desktop.

Yes, access and eligibility depend on local law. Our Privacy Policy describes data handling for permitted use, but it does not change local requirements. If you are unsure whether access is available in your location, check the applicable rule before opening or using an account.