Reference

thor138 Privacy Policy for Your Account

Your account details, device activity and wallet references are handled under the thor138 Privacy Policy, so you can understand what we collect before opening access to Andar Bahar…

Clear data purposesWallet reference controlsAccount access choices
thor138 thor138 Privacy Policy for Your Account
HELP PATHS

Where to Ask About Privacy Policy

A direct support route helps you ask what data is linked to your account without sending wallet credentials in a message. From the account or cashier path, describe the privacy request and include the phone number connected to your profile. We use those details to locate the right record, while questions about DANA, OVO, GoPay or QRIS can be matched to the relevant payment reference.

Team online

Account request

Use the account help path for a copy, correction or explanation of personal details connected with your thor138 profile and phone verification record.

Cashier query

For wallet data, mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account and provide the transaction reference rather than your wallet password.

Access concern

If a login or device check appears unfamiliar, contact us through account help and tell us which phone or browser showed the activity so we can investigate.

DATA PRACTICES

Account Security Across Your Devices

Privacy is easier to manage when the account trail is clear. We separate profile details, payment references and device signals so a support request can be checked without asking you to disclose…

Collected details

We may handle your name, phone number, verification result, login records and payment references supplied during account access or a request involving DANA, OVO, GoPay or QRIS.

Cookie choices

Cookies and similar browser storage can remember session settings and help us understand account access. You can clear them through your browser, though sign-in may need to be repeated.

Device signals

Phone, tablet and desktop details, browser type and approximate access events help us identify unusual sign-ins without reading private content stored in your device.

Account protection

Phone verification is used before account access, while login records and status checks help us investigate activity that does not match your usual account path.

Record retention

We keep account, support and payment-reference records only for the period needed for security, service requests or legal duties, then delete or anonymise them when appropriate.

Change requests

Ask us to correct, provide or delete eligible personal details through account help. Include your connected phone number and the specific record so we can verify the request.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers address the account and payment questions you may have before opening access. We keep the wording practical: what we collect, why a device check appears, how to request a change and which local-law condition applies to your account.

It covers account details, phone verification, login and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

No. We use payment references, status and account identifiers to match a request. Do not send your DANA, OVO, GoPay or QRIS password to support.

Device type, browser details and login events help us recognise unusual account access. These records support security checks on your phone, tablet or desktop without reading private device content.

Use the account help path and state whether you want a copy, correction or deletion of eligible data. Include your connected phone number and enough detail to locate the record.

We retain account, support and payment-reference records for the period needed for security, service requests or legal duties. When no longer needed, records are deleted or anonymised.

Yes. Clear site data through your mobile browser settings. This may end your session and require phone verification again, while essential account records remain governed by the Privacy Policy.

Yes. Account access and eligibility depends on local law. Our Privacy Policy applies to activity where local law permits, and support can explain which request path fits your account.