Reference

Open 99jtu Privacy Policy Details

Live Blackjack Elite, Ceme Turbo Round and wallet records each need clear data handling, so our Privacy Policy explains what we collect, why we use it and how…

Account clarityWallet recordsCookie choices
99jtu Open 99jtu Privacy Policy Details
PRIVACY HELP

Use A Clear Account Contact Path

A direct privacy question should not get lost beside a wallet status issue. Our support path starts with the account details you can identify, then moves to the specific request: access, correction, deletion, cookie choice or an explanation of a transaction record. When your question concerns DANA, OVO, GoPay or QRIS, include the relevant receipt reference without sending a password. We use the same careful approach for mobile browser sessions and desktop access, and we ask for only the details needed to locate your request.

Team online

Account request

Tell us which account detail you want to access or correct, and include the contact detail attached to your account. We use that account step to reduce confusion between a privacy request and a normal login question.

Wallet record

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and approximate date rather than a wallet password or full security code. This helps us check the right record while limiting unnecessary exposure.

Policy question

Ask about cookies, retention, account security or a deletion request through the support route shown in your account area. State the outcome you want, and we can keep the response focused on this Privacy Policy.

DATA CARE STEPS

Explore How Privacy Controls Work

Privacy is handled through practical account steps rather than broad promises. We separate information used to identify your account from payment references used to check wallet or bank-transfer status, and we apply…

Data handling

We use account details to provide access, respond to support and protect the account. Transaction references from DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI can help us identify a payment record without treating the wallet itself as our account.

Cookies

Cookies and similar browser data can help keep a mobile session connected to the right account and remember necessary settings. You can ask what these technologies do and request guidance on available browser controls.

Account security

A clear phone verification step can be part of account access. We do not ask you to send a password in a privacy request, and we may verify your identity before sharing or changing account data.

Retention

We keep information only for the operational, security or legal purpose that calls for it, subject to applicable requirements. A request about retention can name the record type, such as a login event or wallet receipt.

Request changes

Where local law permits, you can ask us to correct inaccurate details, explain a processing purpose or remove information that no longer needs to be kept. We assess the request against account security and required records.

Contact route

Use the support contact available through your 99jtu account area and describe the privacy action you need. For a mobile request, keep the browser session open until you receive the request reference or next step.

Browse Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before account access. They explain the records connected with login, verification, cookies and local payment status without turning a privacy question into a general lobby description. If your situation is unusual, include the relevant account step, device path or receipt reference when contacting us. Access depends on local law, and where local law permits, we will explain how a request is handled and whether an exception affects the result.

The 99jtu Privacy Policy covers account details, phone verification, device and browser information, cookies, support messages and payment references. It explains why we use those records, how security controls apply and how you can ask for access, correction or another privacy action.

Where local law permits, you can request access to personal data connected with your account. Use the account support path, identify the contact detail on the account and complete any identity check needed to prevent another person receiving your information.

We may use a DANA, OVO, GoPay or QRIS reference to match a receipt with an account and check a pending status. Send the reference and date when asking for help, but do not include a password, PIN or full security code.

Yes. The Privacy Policy explains how cookies or similar browser data can support account continuity, security and necessary settings on a mobile browser. You can ask which cookie purpose applies and use your browser controls where available for optional storage.

Contact us through the account support route and name the detail that is wrong, such as a contact record. We may verify the account before making a change, then explain whether the correction is completed or whether a required record must remain.

Where local law permits, you can request deletion of personal data that no longer needs to be retained. We assess the request against security, account administration and required record duties, and we explain any information that must remain and why.

We limit the request to the information needed, verify account ownership before disclosing or changing data and avoid asking for passwords. For a wallet question, a transaction reference is more appropriate than a PIN, including when you contact us from a shared device.