Reference

Open tes188 Privacy Policy Before Account Access

tes188 Privacy Policy shows what we collect when you open an account, use the lobby from Jakarta, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet detailsDevice signalsPrivacy requests
tes188 Open tes188 Privacy Policy Before Account Access
ASK ABOUT PRIVACY

Contact Us When Data Questions Stall

A direct support path matters when a privacy request concerns login or wallet status. Send us the account detail you can safely share, describe the requested change, and include the relevant date or payment reference rather than sending a password or full wallet credentials. Our support team can route the matter to the people handling account records, verification checks and retention questions. If you are in Surabaya or elsewhere in Indonesia, the same privacy request path applies, subject to local law.

Team online

Account access

If phone verification or a sign-in record looks unfamiliar, tell us through the account help path beside the cashier area. We use the account identifier and your description to locate the record, then may ask for a further check before discussing private details.

Wallet records

For a DANA, OVO, GoPay or QRIS reference, include the date, amount reference shown in your account and the requested privacy action. Do not send a wallet PIN. We use the reference to separate a payment query from a request to change personal data.

Policy requests

Ask us to access, correct or remove eligible information by clearly naming the request in your message. We may confirm account ownership before responding, so one person cannot obtain another person’s account data through a simple support message.

DATA HANDLING

Browse tes188 Privacy Controls Clearly

Privacy depends on practical controls, not broad promises. We separate account details from payment references where our records allow, restrict internal access to people who need it for a defined task, and…

Collected details

When you open an account, we may receive your phone number, account credentials, verification result, device details and sign-in activity. When you use QRIS or a bank rail, we may record a reference and status needed to match the requested account transaction.

Cookie choices

Browser cookies can keep a session active, remember a selected language or help us understand whether a login page loaded correctly. Your browser can block or clear them. If you do, some account steps may ask you to authenticate again.

Account protection

We may compare a new device, login time and account activity with earlier signals when access appears unusual. This can lead to an ownership check before private records are discussed, including records connected with Live Blackjack Diamond or wallet activity.

Retention periods

We retain account, payment-reference and support records only while they support account administration, dispute handling, security checks or a legal duty. When a record no longer serves one of those purposes, our process can remove, aggregate or restrict it.

Change requests

You can ask us to correct an inaccurate phone number, contact detail or account record. Explain what is wrong and what should replace it. We check the request against the account before making a change, especially where wallet activity is attached.

Who receives requests

Privacy messages are routed to the support path that handles account and cashier questions, then reviewed by the relevant record owner. We do not ask you to disclose a password, wallet PIN or full payment secret to make a request.

Check tes188 Privacy Policy Answers

These Privacy Policy answers cover the searches most often made before account access. They explain phone verification, browser behaviour, wallet references, deletion requests and local access wording without turning the policy into a general lobby description. If your situation is not listed, use the support path above and describe the specific record or request you want us to examine.

The tes188 Privacy Policy covers details connected with account opening, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use those details, how we restrict access, how long records may remain and how you can request a correction or deletion.

Yes. Privacy Policy applies to references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account requests. We use those records to match an account action, not to request your wallet PIN or full private payment credentials.

Phone verification helps connect an account request with the person controlling the stated contact number. It also supports an ownership check when a new device, unusual login or privacy request appears. We may limit disclosure until that check is complete, where local law permits.

You can ask us to correct an inaccurate eligible record, such as a contact detail or account name. State the existing entry, the correct entry and the account identifier. We verify ownership before changing it, and a payment reference may remain where retention is required.

Send a clear deletion request through the account help path and identify the records involved. We assess whether they can be removed or must remain for account administration, dispute handling, security checks or legal duties. Access to this process depends on local law.

Cookies can retain a mobile session, language choice or sign-in state, while device signals can help detect unusual access. You can clear or block cookies in your browser settings. That may sign you out or require another verification step when you return.

Use our support path for account and cashier questions and label the message as a privacy request. Include the relevant account detail, date or payment reference, but never a password or wallet PIN. We will route the request for an ownership and policy check.