Reference

Privacy Policy For Your tor666 Account

Our tor666 Privacy Policy explains what we collect when you open an account, verify your phone and use the mobile browser from Medan or elsewhere in Indonesia.

Account dataWallet checksCookie choicesContact requests
tor666 Privacy Policy For Your tor666 Account
CONTACT ROUTES

Contact Paths For Policy Questions

A clear contact path helps you ask about the Privacy Policy without sending account details through random channels. Use the support chat linked beside your account and cashier area, and include the phone number on the account plus the subject of your request. We use that first account step to locate the right record, while you should not send a password, one-time code or full wallet credentials.

Team online

Policy questions

Send a message through the account support chat when you need to know what data the Privacy Policy covers. Add your registered phone number and request type, but keep passwords, one-time codes and complete DANA, OVO or GoPay credentials out of the message.

Wallet records

For a QRIS, bank transfer or virtual account receipt, share the transaction reference rather than a complete wallet login. We use that reference to locate the account event, explain the stored field and separate a payment-status question from a Privacy Policy request.

Account changes

If your phone number or account details need correction, contact support from the signed-in account where possible. We may ask for phone verification before changing access details, so the request is connected to the correct person and does not expose another account.

DATA PRACTICES

How We Handle Account Data

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Collected details

We collect details you enter for an account, such as a phone number, together with login time, verification state and…

Cookie controls

Cookies can keep a mobile-browser session active, remember a selected setting or help us detect repeated sign-in attempts.

Account security

We use phone verification before account access changes and may compare device or login signals when activity looks unusual.

Wallet references

DANA, OVO, GoPay and QRIS references help connect a payment event with your account.

Retention period

We keep account, support, security and payment-reconciliation records only while they serve those purposes or while a legal requirement calls…

Change requests

Ask us to access, correct or remove eligible personal data through the signed-in support route.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and device questions you are most likely to have before opening an account. They also explain how wallet references, cookies, phone verification and local access fit together, so you know which details to provide when contacting tor666 support from Indonesia.

The tor666 Privacy Policy covers account details you submit, phone verification status, login and support records, plus relevant device and browser signals. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account may also be stored to match a transaction event.

Phone verification connects an account request to the correct phone number before access or account-detail changes are completed. It also helps us investigate unusual sign-in activity. We will not ask you to place a password or one-time code in support chat.

We use DANA and QRIS references, status details and related timestamps to match a payment event with your account. The Privacy Policy does not require your wallet password for that check. For a question, send the transaction reference through the signed-in support route.

Yes. Contact support from the signed-in account and state whether you want access to eligible records or a correction. Include your registered phone number and the specific field. We may confirm account control first, then explain the next Privacy Policy step.

We retain account, security, support and payment-reconciliation records only while they support those purposes or a legal requirement calls for storage. After that need ends, the handling process moves the record toward deletion or anonymisation, subject to any required exception.

You can clear or restrict cookies through your mobile-browser settings. The Privacy Policy explains that this may end your session, remove selected settings and require phone verification again. Cookie changes do not erase every account or payment record automatically.

Yes. Account access and related processing depend on local law and are available where local law permits. If you need clarification about your location, account record or a Privacy Policy request, contact support through the signed-in account path.