Reference

thr89 Privacy Policy, Clearly Explained

Our thr89 Privacy Policy shows what account, wallet, device and cookie data we collect, why we use it, and how you can ask us to correct or remove…

Account dataWallet recordsDevice choicesCookie controls
thr89 thr89 Privacy Policy, Clearly Explained
CONTACT ROUTES

Ask About Your Privacy Policy Rights

You do not need to guess where a privacy question belongs. Start from the support route linked to your account and tell us whether your request concerns access, correction, deletion, cookie choices or a payment record. We may ask for account details so we can locate the right record without exposing it to the wrong person. Our policy contact path also covers sign-in concerns and wallet status questions.

Team online

Account request

Use the support path connected to your thr89 account when you want a copy of account data, a correction to your phone details, or clarification about a verification record. We may confirm your identity before discussing information tied to the account.

Wallet question

For a DANA, OVO, GoPay or QRIS receipt, include the relevant account reference and payment date in your privacy request. We use those details to find the transaction record while keeping wallet information limited to the people who need it.

Access concern

If a sign-in alert, phone verification step or device record looks unfamiliar, contact us through the account support route. We can check the event, explain what record we hold and point you to the next privacy step where local law permits.

SIX DATA PROMISES

How We Handle Your Account Details

Privacy work is part of the account flow rather than a separate screen you never see. We record the minimum operational detail needed to connect your sign-in, phone verification, wallet status and…

Collected at key steps

We collect details when you create an account, verify your phone, sign in, contact support or use a payment route. A QRIS receipt and a virtual account reference may be stored as transaction evidence, while optional profile details are handled for the purpose you provide.

Cookies have a role

Cookies and similar device signals can help keep your session connected, remember a selected setting and identify repeated sign-in attempts. You can manage browser cookie controls, although turning them off may affect account access or require you to repeat a verification step.

Security follows access

Phone verification before account access helps us connect a sign-in to the right account. We also examine login events and device signals for unusual activity, then may ask for another account check before discussing private details or changing an account record.

Retention follows purpose

We keep account, support and payment records only for as long as they serve the stated account, security or record-keeping purpose, subject to applicable duties. A DANA status check and a bank transfer reference may therefore follow different retention needs.

Requests need matching

To request access, correction or removal, send the account identifier and explain the record involved. We may need to confirm that you control the account before responding. Some records can remain where local law requires retention or where they are needed to resolve a dispute.

We explain a decision

If we cannot complete a privacy request, we will explain the reason in the response available through our support route. You can ask about a phone record, device event, cookie choice, payment reference or account message without needing to describe unrelated activity.

Privacy Policy Answers for Indonesia

These questions cover the privacy searches we hear most often before an account is opened. Each answer points to a practical account or payment detail, including phone verification, device access, local wallet records and the support route. If your situation is not listed, contact us through the account path and mention the specific record you want us to locate.

The thr89 Privacy Policy covers account details, phone verification, login and device events, cookie signals, support messages and payment records. That includes references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity where those records are used for your account.

Use the support route linked to your account and ask for a copy of the data connected with your account identifier. Tell us whether you need account, phone verification, device, cookie, support or payment records. We may confirm account control before sending a response.

Yes, you can ask us to correct inaccurate account information through the same support path. Include the detail that needs changing and the replacement value, such as a phone record or account contact detail. We may verify the request before editing information tied to your account.

Yes. Our Privacy Policy covers transaction references and status details created when you use DANA or QRIS, along with OVO, GoPay, bank transfer and virtual account records. We use these details to match a payment status, answer a receipt question and maintain required records.

We use device signals and cookies to keep a sign-in session working, remember selected settings and identify unusual access patterns. Browser controls can limit cookies, but you may need to repeat a login or phone verification step. The policy explains these uses without changing your account choices.

You can request removal through account support, and we assess the request against the purpose for holding the record. We may retain certain account, security, support or payment details when local law requires it, or when the record is needed to settle an unresolved account matter.

Access and eligibility depends on local law. We assess your request and location before applying the relevant process, including requests about account copies, corrections, cookie choices or payment references. Where local law permits, we will explain the available action through the support route.