Reference

Privacy Policy for Your thor 138 Account

Your phone verification, wallet status and device choices stay connected to a clear Privacy Policy at thor 138, so you can understand what happens before opening the lobby.

Account dataWallet referencesDevice choicesPolicy requests
thor 138 Privacy Policy for Your thor 138 Account
HELP WITH YOUR DATA

Get Policy Help Beside Your Account

A clear support route matters when a Privacy Policy question involves a login, wallet reference or device record.

Account access request Ask us to confirm which account details are connected with your phone verification step. Use the account help path beside the cashier and provide the contact detail already attached to your account, not a new document or unrelated personal message.
Wallet record question For DANA, OVO, GoPay, QRIS, virtual account or bank transfer references, send the transaction date and receipt code through account support. We use those details to locate a status record while keeping the request focused on payment data.
Correction or removal Tell us which field you want corrected or which eligible record you want removed. We may need to verify your account first, then explain whether retention still applies under local law before changing or deleting the requested data.
DATA CONTROL PATH

What We Do With Your Account Details

The Privacy Policy is supported by practical controls rather than a broad promise. We separate login checks from wallet references, describe why a browser may store a cookie, and give you a…

Account details

We use information such as your phone number, account identifier and verification state to help provide account access and respond to account requests. The same details can help us spot a mismatch before a wallet status or cashier record is discussed.

Cookies and browsers

A browser may keep a cookie or similar setting so the session can remember necessary access choices. You can clear stored browser data through your phone settings, although doing so may require another phone verification step when you return.

Account security

We treat phone verification as an account checkpoint, not as permission to disclose every record to anyone who knows your number. Keep your sign-in details private and contact account support if a device you used is no longer under your control.

Payment references

A DANA, OVO, GoPay or QRIS receipt reference can help us trace a cashier status, while a virtual account or bank transfer reference can identify the matching request. Send only the reference needed for the specific Privacy Policy question.

Retention periods

We keep account, support and transaction records only as long as they serve the stated access, security, dispute or legal purpose. When a retention period ends, we remove the record or separate it from direct account identifiers where the process allows.

Requesting changes

You can ask for access, correction or eligible removal through the account support path. Include your account contact, the requested action and any relevant receipt code; we may verify ownership before explaining the result where local law permits.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account steps you are most likely to ask about before using thor 138. We focus on phone verification, cookies, wallet references, support requests and access rights so you can decide what to share and how to contact us. If a request involves a legal restriction, our response will use the rule that applies where local law permits.

It covers account details, phone verification, browser cookies, device session data, support messages and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity. It also explains how to request access, correction or eligible removal where local law permits.

Phone verification helps connect an account request with the correct account holder and reduces the chance of disclosing account or wallet status to the wrong person. We may ask you to complete that checkpoint before discussing a record or changing account details.

Yes. The Privacy Policy covers payment references used to match a cashier request with DANA, QRIS, OVO, GoPay, virtual account or bank transfer activity. A receipt code and date are usually more useful than sending a full wallet statement or unrelated personal details.

Use the account support path beside the cashier and state that you want an access request under the Privacy Policy. Include your account contact and the record type you want checked. We may verify your account before responding, and the result depends on local law.

You can request a correction by naming the field that is inaccurate and supplying the updated detail through account support. We may first complete phone verification, then check the account record and explain any limitation that applies where local law permits.

The retention period depends on why the record exists. Account access, security checks, support requests and transaction references may need different periods for operational or legal reasons. When the relevant period ends, we remove or separate the data where the process allows.

Clear the stored browser cookie and session data through your phone settings, then return through the account access path. You may need phone verification again. If an old device remains connected or a record looks wrong, contact account support with the affected account detail.