Reference

Privacy Policy For Your tiger189 Account

Privacy Policy is where we explain how tiger189 handles your account details, phone verification, device signals, and payment references.

Clear data choicesWallet-aware controlsIndonesia access
tiger189 Privacy Policy For Your tiger189 Account
CONTACT ROUTE

Get Privacy Help Through Support

Privacy questions should have a clear route, especially when a wallet receipt or login check contains personal details. From your account support area, tell us whether your request concerns phone verification, a DANA or QRIS reference, cookie choices, or a data correction. From Medan, the same support path helps us locate the right record through the details you provide and respond through our support channel. It can also clarify how privacy applies when you reach the lobby from an Android or computer browser.

Team online

Account privacy request

Tell us the account identifier and the change you need, such as correcting a phone detail or asking how a verification record is used. We check the request against your account before discussing personal data, so the reply reaches the right account.

Wallet record question

Include the payment rail, reference and approximate time when asking about DANA, OVO, GoPay, QRIS, bank transfer or virtual account data. We can then explain which record the Privacy Policy covers and what account check may be needed.

Cookie or access query

Ask how cookies and device signals work in your mobile browser, what setting you can change, and how that choice affects a later login. We answer using the Privacy Policy wording and point you to the relevant request path.

ACCOUNT SAFETY

Protect Wallet Records Across Devices

Your privacy choices sit beside the account controls used for the lobby, so the policy connects everyday access with data handling.

Data we collect

We collect account details, phone verification results, device or browser signals, payment references, and support messages for the purposes stated in our Privacy Policy. Your account step tells you what is requested before access, so you can decide what to submit where local law permits.

Wallet records

Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests let us match status questions to an account. We use the reference to investigate the payment record, not to treat a wallet choice as permission to collect unrelated account details.

Cookies and browsers

Cookies help remember a session choice in your mobile browser and let us understand whether a sign-in step was completed. Our Privacy Policy describes the cookie purpose and your available settings, including what happens when you clear cookies before returning to the lobby.

Phone verification

Phone verification before account access helps us distinguish an account request from an unknown sign-in. We also review unusual access signals when a privacy or wallet request arrives. Never place a full password in a support message; identify the account through the requested verification step instead.

Retention periods

We keep account, support and payment records for the period needed for the stated purpose, account administration, and applicable legal duties. The Privacy Policy explains retention factors rather than promising one fixed period for every record, because a QRIS reference and a support request can follow different rules.

Request a change

You can ask us to correct account data, ask what we hold, or request removal where local law permits. Use the support path, identify your account, name the specific record, and explain the change. We may ask for account verification before releasing or changing personal details.

Privacy Answers For Your tiger189 Account

These answers focus on the questions you may ask before opening a tiger189 account or sending a wallet request. They cover what the Privacy Policy says about collected data, device access, cookies, payment references, retention, and corrections. We keep the wording tied to DANA, QRIS, phone verification, and browser access so you can understand the practical step behind each policy point before you submit personal details or use the support path.

Our Privacy Policy covers account details, phone verification, browser and device signals, cookies, payment references, support messages, retention, and requests to change or remove data. It also explains why we handle those records and which access conditions apply where local law permits.

We use DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account references, to match a payment status request to your account. Our Privacy Policy describes that handling and the account check needed before we discuss a personal transaction record.

Yes. Send a request through our support path with your account identifier and the specific record or field you want checked. We may confirm your account first, then explain whether correction, access, or removal is available where local law permits.

Phone verification helps us protect account access and connect a legitimate sign-in with the right record. We explain the verification result, its purpose, and related retention in the Privacy Policy. Do not send your password in a support message.

Yes. The Privacy Policy covers cookies and device signals used around a mobile browser session. We explain the purpose, the setting you can change, and what may happen to login continuity after cookies are cleared before you return to the lobby.

Retention depends on the type of record and the purpose stated in our Privacy Policy. A QRIS payment reference, phone verification record, and support message may follow different periods. Ask through support for the rule relevant to your account request.

Use the support path shown in your account area and describe the Privacy Policy question, account step, or payment reference involved. Include only the details needed to locate the record. We verify account ownership before discussing or changing personal data.