Reference

Privacy Policy for Your tuan900 Account

Our Privacy Policy explains how we collect, use, protect and remove data connected with your tuan900 account, including details used for phone verification and wallet status checks.

Clear data purposesWallet privacyDevice accessRequest support
tuan900 Privacy Policy for Your tuan900 Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A direct request is the quickest way to clarify how our Privacy Policy applies to your account. We ask you to use the same account details connected with the request so we can avoid disclosing records to the wrong person. Include the subject of your request, the relevant account step and any receipt or status reference you already have. Our support path is designed for privacy questions as well as login and wallet-status issues, while access remains dependent on local law.

Team online

Account request

Send a request through the account support path when you want to ask what personal data we hold, correct a phone detail or understand why a verification record is linked to your account. We may ask for account details before discussing private records.

Wallet receipt

For a privacy question linked to DANA, OVO, GoPay or QRIS, include the payment reference and the date shown on your receipt. This lets us separate your account record from a bank transfer or virtual account status check.

Access concern

If your account opens on one device but not another, tell us the device path, browser state and approximate time. We use those details to investigate access security without asking you to send a password or private wallet PIN.

DATA PRACTICES

What We Do With Account Records

Privacy at tuan900 is handled through practical account controls rather than broad promises. We separate information needed for phone verification from payment references used to check DANA, OVO, GoPay, QRIS, bank transfer…

Data collection

We may collect account identifiers, phone verification details, payment references, device signals and support messages when you use the service. We collect these details for a stated account, security, payment-status or support purpose rather than treating every page visit as the same record.

Cookie choices

Cookies and similar session tools can keep an account page connected while you move from login toward the lobby. If you clear them or block them, the device path may ask you to authenticate again. This can change access behaviour without changing your underlying account record.

Account security

Phone verification helps us connect account access to the correct account holder, while device and session details help us investigate unusual sign-ins. Never send us your password, wallet PIN or one-time code in a privacy request. We only need enough detail to locate the issue.

Payment records

A DANA, OVO, GoPay or QRIS reference can be used to match a cashier event with your account. Bank transfer and virtual account records may require a separate reference check. We use payment data for status handling, account support, security and required record keeping.

Retention requests

You can ask how long a particular account, support or payment record is kept and request removal where applicable. We may retain limited records when needed for security, unresolved payment questions, disputes or legal duties. We explain the reason if a request cannot be completed fully.

Correction route

If your phone detail, account name or contact record is inaccurate, contact support with the correction you want made. We verify the request before changing private data, then use the updated record for future account access and support conversations where the change is allowed.

Privacy Policy Answers for Indonesia

These Privacy Policy questions cover the account and payment situations you are most likely to encounter. We keep the answers tied to actual tuan900 steps, including phone verification, mobile access, wallet references and requests to see or change your data. If your situation is not listed, contact us through the support path with the smallest useful set of account details. Access and eligibility depends on local law.

The tuan900 Privacy Policy covers data connected with account creation, phone verification, login sessions, device access, cookies, payment references and support requests. It applies when you use account pages or cashier steps involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

We use phone verification to connect account access with the correct account record and to investigate login concerns. If you ask about a private record, we may request matching account details before responding. Do not include your password, wallet PIN or one-time code.

Yes. Our Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account checks. We use those references to match a cashier event, answer a status question, investigate an account issue or meet required retention duties.

Use the account support path and state that you want a copy of your tuan900 data. Tell us which area matters, such as phone verification, device access, cookies, wallet status or support messages. We verify your identity before sharing records connected with your account.

You can ask us to correct inaccurate account or contact details and request removal where applicable. We first confirm the request belongs to you. Some records may remain when needed for security, payment disputes, account administration or legal duties, and we explain that reason.

Mobile access can create device and session details used to protect account access and investigate unusual sign-ins. Cookies may keep your login path connected; clearing them can require authentication again. We do not need your password or wallet PIN to investigate a device question.

Send the question through our account support path and include the relevant account step, such as phone verification, a QRIS receipt or a device access concern. Use only details needed to locate the record. We handle the request subject to security checks and local law.