Reference

Privacy Policy for talas 789 Accounts

talas 789 Privacy Policy shows what we collect, why we use it and how you can ask for a correction before opening an account.

Account clarityWallet recordsDevice controlsContact route
talas 789 Privacy Policy for talas 789 Accounts
CONTACT YOUR WAY

Contact Us About Privacy Requests

A clear contact path helps when you want to ask what data we hold or why an account check was needed. Use the support route inside your account and include the phone number linked to your profile, without sending a password or wallet PIN. We can then match your request to the correct record and explain the next step. This route also works when a DANA or QRIS reference appears in a support conversation.

Team online

Account support

Open the support route after login and identify your account with its linked phone number. We use that detail to locate a Privacy Policy request without asking you to send a password or wallet PIN.

Cashier questions

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and date through account support. We use those details to check the correct wallet event while keeping unrelated account data out of the request.

Access problems

If login stalls on your phone, start with the account support path rather than creating another profile. We can check the linked device and phone verification status before discussing any personal data request.

DATA CONTROL POINTS

Check How We Handle Your Data

Privacy choices are easier to use when each data category has a practical purpose. We separate account access details from payment references, use cookies for essential session behaviour, and apply checks before…

Account details

We use your name, phone number and login details to create and maintain one account. Phone verification helps us confirm that a request to change access comes from the person linked to the profile.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in our records. We use them to match payment status, investigate a question and separate one account's transaction from another.

Cookies

Essential cookies keep your session connected while you move from login to the lobby. They can also remember a basic device setting; clearing them may require you to complete account access steps again.

Device security

We may record device and browser signals linked to an account login. This helps us notice an unusual access pattern, while a new phone may prompt another phone verification step before account details are shown.

Data retention

We keep account, support and transaction records for the period needed to operate services, resolve disputes and meet applicable legal duties. When a record is no longer needed, we remove it or make it non-identifying.

Changes and questions

Ask us to correct inaccurate personal data, explain a collection purpose or clarify a retention period through account support. Include the linked phone number and the specific record so we can respond to the right request.

Find Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before account creation and during wallet support. We keep the route practical: use your linked phone number, name the relevant payment reference and avoid sending passwords or wallet PINs. If a question concerns access or eligibility, remember that it depends on local law and where local law permits.

It covers data connected with your account, phone verification, login, device signals, support messages and payment references. It also explains cookies, retention, correction requests and the way we handle questions about DANA, OVO, GoPay, QRIS or bank transfer records.

Phone verification helps connect account access and privacy requests to the correct person. We may use the result when you open an account, change access details or ask us to disclose or correct personal data. Never send us your password or wallet PIN.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to check status or resolve a question, rather than requesting your wallet password or private wallet credentials.

Use the support route inside your account and provide the phone number linked to your profile, plus the specific detail that needs correction. We may ask for an additional account check before changing a phone number, login detail or other sensitive record.

We keep personal data for as long as it supports account operation, payment questions, dispute handling or applicable legal duties. After that need ends, we remove the record or make it non-identifying, subject to any period required by local law.

You can submit an access request through account support using your linked phone number and a clear description of the data you want clarified. We verify the request before responding, helping prevent account details from being sent to the wrong person.

Yes, the policy applies when you access the account from a phone, tablet or desktop browser. Device and browser signals may help recognise a login, and switching devices can trigger phone verification before account data or support history is displayed.