Reference

tr288 Privacy Policy for Your Account

The tr288 Privacy Policy explains what we collect when you create an account, sign in, use DANA or QRIS, and move between Auto Roulette Live and other lobby…

Clear collection rulesWallet record clarityAccount access controlsCookie choices
tr288 tr288 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path matters when you want to ask about the tr288 Privacy Policy, correct a phone detail or understand a wallet record.

Account data request Ask us to confirm which account details we hold, such as your phone verification status or sign-in record. We will use the account path to match your request and may ask for an account step before discussing private details.
Wallet record question For DANA, OVO, GoPay, QRIS or bank transfer records, share the reference shown in your account rather than your wallet password. We can explain the stored payment status and identify whether the entry is pending, completed or under review.
Policy change request If a detail is inaccurate or you want to ask about its use, send the request through account support beside the cashier path. Tell us what should change, why it is incorrect and how we can reach you through the verified account route.
DATA HANDLING

How tr288 Applies This Policy

We apply the Privacy Policy through practical account controls rather than broad promises. A mobile sign-in creates device and session records, while a wallet action creates a payment reference that helps us…

Account details

We collect the details needed to create and maintain your account, including contact data, verification results and selected account settings. We do not ask you to place a password or wallet PIN in a support message, and we use the account path to match a request.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, amount, status and time record linked to your account. Bank transfer and virtual account entries may carry their own reference details so we can reconcile the action without storing your wallet PIN.

Cookies and devices

Cookies and device signals help keep a mobile browser session connected to the correct account and detect unusual sign-in patterns. If you clear cookies or change devices, we may ask you to repeat phone verification before account access continues.

Security checks

We use phone verification, sign-in records and session checks to reduce the chance of another person entering your account. When an account action looks unusual, we may pause discussion of private records until you complete the requested account verification step.

Retention periods

We retain account, payment and security records only for the period needed for account service, dispute handling, security checks and legal duties. When a record is no longer needed for those purposes, we remove it, anonymise it or restrict its use.

Your requests

You can ask for access, correction, deletion or a reason for processing through the account support route. We assess each request under applicable rules, confirm your identity where needed and explain any part we must retain because of a legal or security requirement.

Privacy Policy Questions for tr288

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account or using the lobby. We keep the wording practical: what is collected, why a record exists, how a mobile device affects sign-in and where to send a request. If your question concerns eligibility or access, the answer depends on local law and the details shown for your location.

It covers account details, phone verification, device and session records, cookies, payment references and requests about those records. It applies when you open an account, sign in, use DANA, OVO, GoPay or QRIS, and move through account areas such as Fishing War Quick Arena.

We use phone verification to connect account access to the contact detail you provided and to reduce unauthorised entry. A verification result can also help us confirm a privacy request. Access or eligibility depends on local law, and we apply the required local conditions.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account actions. We may retain the reference, status and time needed to reconcile an account event, answer a dispute and meet applicable legal duties.

A new device or cleared browser cookies can create a fresh session record. We may ask you to repeat phone verification before showing private account details. This check helps us distinguish your new mobile sign-in from an unfamiliar attempt and protects the account record.

Use the account support route beside the cashier path and identify the record you want corrected. Include your account identifier, the incorrect detail and a safe contact route. We may verify ownership first, then confirm the change or explain why a record must remain.

You can send a deletion request through account support, and we will assess it under applicable rules. Some records may need to remain for payment reconciliation, security checks, disputes or legal duties. We will explain the result and restrict further use where deletion is not available.

Where local law permits, we show the account and lobby access available for your location after the relevant checks. The Privacy Policy still governs the data created by that process, including sign-in, wallet and device records, even when a location-based restriction applies.