Reference

tor138 Privacy Policy For Your Account

The tor138 Privacy Policy explains what we collect when you open an account, sign in, use VIP Baccarat or browse the lobby, and how we protect those records.

Clear data purposesCookie choicesAccount access rights
Explore Our Lobby Read FAQ
tor138 tor138 Privacy Policy For Your Account
HELP WITH DATA

Get Privacy Answers Near Your Account

Privacy questions should be easy to raise, especially when a wallet status or login check leaves you unsure about a record.

Account support path Open the support option from your signed-in account and choose a privacy request. Include your registered phone number only through that secure route, never in a public message. We use the account step to match your request with the correct tor138 record.
Wallet record check For DANA, OVO, GoPay or QRIS questions, send the payment reference, date and status shown in your account. Do not send a wallet PIN or password. We can investigate a duplicate, failed or pending record without asking for your private wallet credentials.
Privacy change request Ask us to correct an inaccurate name, phone detail or account preference through the same support path. We may confirm ownership before making a change, then explain whether a legal, security or transaction record must remain stored.
DATA CONTROL

What We Do With Your Personal Data

Our privacy process follows the data journey you can see: account creation, phone verification, wallet activity, lobby access and support contact.

Account details

We may hold your phone number, login identifiers and account settings so we can create access, verify ownership and answer requests. We do not need your wallet PIN for a DANA or QRIS status check. Keep your password private and contact us if the account details no longer match you.

Payment references

A wallet or bank record can include a reference, amount, method and processing status. These details help us reconcile a GoPay, OVO, bank transfer or virtual account event with your account. We use the payment record for service, security and required retention rather than for unrelated profiling.

Cookies and devices

Cookies and device signals can support sign-in continuity, fraud checks and basic page measurement. Your mobile browser may clear them, which can require another login or preference choice. Clearing cookies does not automatically erase account records; request that separately through support.

Security checks

Phone verification before account access helps us distinguish an authorised sign-in from an unfamiliar attempt. We may compare session, device and account signals when access looks unusual. Never share a one-time code, password or wallet PIN with anyone claiming to speak for us.

Retention approach

We keep personal data only for the period needed for account operation, security investigation, payment reconciliation or a legal duty. When a record no longer has a valid purpose, our processes can remove, anonymise or restrict it, subject to records that must remain available.

Your requests

You can ask for a copy, correction, restriction or deletion of eligible personal data. Send the request through the signed-in account support route and describe the record, such as a phone detail or QRIS reference. We may verify your identity before responding to protect your account.

Privacy Policy Answers For tor138

These Privacy Policy answers cover the searches we hear most often from Indonesian account holders. They explain why we request particular details, what happens when you use a mobile device, and how to contact us about a record. If your question concerns eligibility or access, remember that availability depends on local law and may differ by location.

It covers personal data connected with your account, phone verification, device session, cookies, wallet references, support requests and lobby activity. The Privacy Policy also explains security use, retention, your request options and the circumstances in which access depends on local law.

We use your phone number to create an account identifier, confirm ownership before account access and help locate a support request. It can also help us detect an unfamiliar sign-in. We will not ask you to disclose a one-time code or wallet PIN in support messages.

Yes. A DANA or QRIS action may leave a reference, amount, status and time record linked to your account. We use that data to reconcile the transaction, investigate a stalled status and meet applicable record duties. Wallet credentials are not needed for this check.

You can request a correction for eligible details such as a phone number, name or account preference. Use the signed-in support route, describe what is wrong and provide the relevant account record. We may confirm ownership before changing data that affects account access.

Cookies can remember a session or selected preference and may support basic page measurement. If your mobile browser clears them, you may need to sign in again. Browser controls can limit cookies, but that action does not erase stored account or payment records.

Retention varies by the record's purpose. Account, security, payment and support records remain while needed for service, investigation, reconciliation or a legal duty. When no valid purpose remains, we can remove, anonymise or restrict the data, subject to required records.

Sign in and open the account support option, then select the privacy request route. State whether you want access, correction, restriction or deletion and identify the relevant record. We may request ownership checks, and access is handled where local law permits.

Related Pages

tor138 Indonesia Account information agenbola108 VIP Baccarat studiobet88