Reference

Privacy Policy for Your thor89 Account

Our Privacy Policy explains what we collect when you open a thor89 account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess controls
thor89 Privacy Policy for Your thor89 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should not leave you guessing which account step caused it.

Privacy request Use our account support path to ask what personal details are linked to your…
Payment reference If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction date…
Access concern When a phone or desktop session looks unfamiliar, tell us through the account help…
DATA CONTROL

What We Do With Account Details

We keep this Privacy Policy practical by connecting each data category to an account task. Phone details support verification, device signals help us identify unusual access, cookies remember selected settings, and payment…

Phone verification

Your phone number is used to complete the account access step and help distinguish your profile from another account. If you ask to change it, we may request a verification check before updating the record attached to your login.

Device signals

A mobile browser or desktop session can create technical signals such as browser type, operating system and login time. We use these signals to investigate access concerns and protect the account; they are not a substitute for your phone verification.

Cookies

Cookies can remember session settings and help the privacy controls work as you move between account pages. You can adjust browser cookie settings, though limiting them may require you to repeat sign-in or preference steps on a later visit.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account help us identify which account action a receipt belongs to. We use the reference for reconciliation and status checks rather than requesting your wallet PIN.

Retention period

We retain records only for the account, security, transaction or legal reason that requires them, subject to applicable local requirements. When a record is no longer needed for that reason, our process is to remove it or separate it from direct account identifiers.

Change request

To request access, correction or deletion of eligible personal details, contact support with your account identifier and the precise change you want. We verify ownership first, explain any limit under local law, and confirm the action or reason it cannot be completed.

Answers Before You Open Your Account

These Privacy Policy answers cover the account and wallet questions we expect you to ask before using thor89 from Indonesia. They explain the practical path for access requests, corrections, cookies, device records and payment references. If your situation is not covered, contact us through the account support route with only the details needed to identify your request. Account eligibility depends on local law.

It covers information connected with your account, phone verification, sign-in sessions, device signals, cookies, support messages and payment references. It also explains why we use those details, how retention works and how you can request access or a correction where local law permits.

We use your phone number for the account verification step and to help protect access when a login or account detail changes. If you request a phone update, we may verify account ownership before making the change, so another person cannot redirect your account.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account references. We use those records to match a receipt, check status and resolve account questions without asking for your wallet PIN.

You can contact us through the account support path and state whether you want access to, or correction of, a particular record. Include your account identifier and the reason for the request. We verify ownership and explain any restriction that depends on local law.

Cookies may keep your session and selected privacy settings available as you move between account pages on a mobile browser. Your browser controls can limit or remove them. After that change, you may need to sign in again or repeat preference choices.

Retention depends on why the record exists, such as account security, a payment status check or a legal requirement. We aim to remove or separate information when that reason ends, subject to applicable local requirements and any unresolved account or transaction request.

Use the account support route promptly and describe the device, approximate login time and account identifier, without sending your password or wallet PIN. Sign out of other sessions if that control is available, then complete any phone verification requested before access details are changed.