Reference

Privacy Policy for Your tor4d Account

Your tor4d Privacy Policy gives you a clear view of the account, wallet and device data we use when you access our service in Indonesia.

Account clarityWallet contextCookie choicesAccess depends on local law
tor4d Privacy Policy for Your tor4d Account
CONTACT PATHS

Privacy Questions Reach Our Support Desk

A direct support route helps you resolve a privacy question without repeating your account story across several places. We ask you to use the contact path shown in your account area and include the email or phone detail connected with your access, plus the subject of your request. We can then check whether the matter concerns login, a wallet reference or a data request. For account questions from Jakarta or elsewhere in Indonesia, access remains dependent on local law.

Team online

Data request

Use the account contact path to ask what personal data we hold, why we use it or which records relate to your account. Include your registered phone detail so we can check identity before discussing private account information.

Wallet record

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment reference through our support route. We use that detail to compare the wallet status with the account record without asking you to share a password.

Access concern

When login or phone verification affects a privacy request, tell us the device path you used, such as mobile browser or desktop browser. We use those details to investigate access while keeping your account credentials private.

SIX DATA CHECKS

Six Checks Behind Your Data Handling

We handle this policy area through practical checks rather than vague promises. Account details support sign-in and phone verification; payment references help us match wallet or bank activity; and device records help…

Account data

We use your registered contact details to support login, phone verification and account messages. Before we disclose account-specific data, we may ask you to complete a verification step so another person cannot obtain your records.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to reconcile payment status. We focus on the reference and status needed for the account record rather than asking for your wallet password.

Device signals

Browser type, device details and access events can help us identify unusual sign-in activity. These signals support account security and troubleshooting; they do not replace the phone verification step required before account access.

Cookie choices

Cookies can remember selected settings and help us understand basic page movement, such as the path from login to the lobby. You can manage available cookie choices through your browser, although some account functions may then behave differently.

Record retention

We retain personal data only while it serves account administration, security checks, payment reconciliation, dispute handling or a legal duty. When a record is no longer needed, we remove it or separate it from direct account identifiers where suitable.

Changes and contact

You can ask us to access, correct or clarify personal data through the account contact path. Tell us which record needs attention, and we may request phone verification before making a change that affects your account.

Privacy Policy Questions About tor4d

These answers address the privacy searches we hear most often before account access. They explain what data is connected with login, wallets, cookies and support requests, while keeping the focus on your choices. If your question concerns eligibility, remember that access depends on local law and the account route available in your region.

The tor4d Privacy Policy covers account details, phone verification, payment references, device signals, cookies, retention and privacy requests. It applies to the website and account area you use, including access connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account records.

We use phone verification to confirm that the person requesting account access or private account data is connected with the account. It also helps us investigate login concerns without exposing your records to someone who only knows your payment reference.

Yes. The Privacy Policy covers the payment reference and status needed to reconcile a DANA or QRIS request, as well as comparable OVO, GoPay, bank transfer and virtual account records. We do not ask you to provide a wallet password for this check.

Cookies can remember selected settings and help us understand basic movement between login and account pages. Your browser provides controls for cookie choices. If you block some cookies, parts of the account path may not remember settings or may require another step.

Use the contact path shown inside your account area and state whether you want access, correction or clarification. Include the relevant registered contact detail and the record involved. We may complete an identity check before releasing or changing private account data.

We keep account information for as long as it supports account administration, security, payment reconciliation, dispute handling or a legal duty. When those purposes end, we remove the record or separate it from direct identifiers where that approach is suitable.

Yes, you can send a privacy question through the account contact path and describe the issue clearly. We will review the request using the available account details. Access and eligibility remain subject to local law, including for requests made from Indonesia.