Reference

Privacy Policy for Your t6com Account

Our Privacy Policy explains how t6com handles the account, device and payment details you provide when you open an account or access titles such as Live Roulette Prestige…

Clear data purposesWallet activity explainedAccount access controlsContact route included
t6com Privacy Policy for Your t6com Account
HELP WITH ACCESS

Get Privacy Policy Help From Your Account

A clear support path helps when you want to ask about a record, change a detail or understand a wallet reference. Start from the account support route and include the phone number or transaction reference connected with your request, without sending a wallet password. We use the case details to locate the right record and keep the response focused on this Privacy Policy.

Team online

Account support route

Open support from your signed-in account when you need to ask how a phone verification record, sign-in event or device entry is used. We can connect the request to your account without asking you to post private details in a public message.

Wallet status question

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time shown in your account. We use those details to trace the relevant wallet event, while you should keep your wallet PIN and password private.

Correction request

If your phone number, contact detail or account record needs correction, tell us which field is inaccurate through the account support path. We may ask for an account step to confirm that the request comes from you before changing the record.

DATA PRACTICE

What Our Privacy Policy Does For You

We keep the Privacy Policy practical by linking each data use to an account action you can recognise, such as signing in, selecting QRIS or returning to the lobby on a mobile…

Account data

We use the phone number and verification result you submit to create and protect account access. Sign-in history and related device signals can help us identify an unusual attempt before account details or wallet references are displayed.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action may create a reference, amount status and time record. We use those fields to match the account event, answer a query and identify a duplicated or incomplete request.

Cookies and devices

Cookies and similar device signals help keep a signed-in session working and remember practical choices such as a mobile layout. When you move from login to a slot room, these signals can support session continuity without revealing your wallet password.

Account security

We limit account access through phone verification and session controls. Do not share a one-time code, PIN or password with anyone contacting you. If a sign-in does not look familiar, use the account support route and mention the device or time shown.

Retention choices

We keep records only for the period needed for account operation, payment matching, security checks and applicable legal duties. When a record is no longer needed for those purposes, our handling follows the retention process that applies to that data type.

Changes and contact

You can ask about a data use, request a correction or ask whether a record can be removed through support after signing in. Include the relevant account step, such as QRIS selection or a device entry, so we can assess the request accurately.

Privacy Policy Answers For t6com Accounts

These Privacy Policy answers address the account and wallet questions you may have before opening an account or returning to t6com from a mobile device. Each answer points you toward a practical next step, and access depends on local law.

The t6com Privacy Policy covers account details, phone verification, sign-in and device records, cookies, wallet references and support requests. It explains why we use each category, how security controls apply and how you can ask about or correct data connected with your account.

Yes. Privacy Policy treatment includes the reference, status and timing linked with a DANA, OVO, GoPay or QRIS action. We use those fields to match the wallet event with your account. Keep your PIN and wallet password private; we do not need them for support.

We use your phone number to create and verify account access, help identify the correct account during support and reduce mistaken sign-ins. The verification step happens before account access. If the number is wrong, use the correction request route after signing in where local law permits.

The Privacy Policy allows us to use session and device signals to keep login working, remember practical browser choices and identify unusual access. These records may appear when you move from a mobile login to Fishing War Mobile Play. They are not your wallet password.

You can ask us to correct an inaccurate phone number, contact detail or account record through the signed-in support route. Include the field and account step involved. We may verify your identity before making a change, and the outcome depends on local law and retention duties.

We retain account, payment-reference, security and support records only while they are needed for account operation, reconciliation, protection against unusual access or applicable legal duties. The period can differ by record type. You can ask support whether a particular record remains within its retention period.

Sign in, open the account support route and describe the Privacy Policy question using a relevant reference, such as a QRIS transaction code or device entry time. Do not include a wallet PIN or password. We use the submitted details to locate and assess your request.