Reference

tgr99 Privacy Policy For Your Account

tgr99 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet activity and device access.

Clear data purposesWallet record controlsAccount contact pathMobile privacy steps
Explore Our Lobby Read FAQ
tgr99 tgr99 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path matters when a privacy question overlaps with login or wallet status. We ask you to use the support route shown inside your account so we can connect the request with the correct profile without exposing details in a public message. Include the account phone number, the issue category and any relevant payment reference, but never send a password or one-time code. We handle requests according to the Privacy Policy and where local law permits.

Team online

Account data request

Use the account support path when you want to ask what personal details we hold, why a field is needed or which account step produced a particular record. We may ask for account verification before discussing private information.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, provide the date, amount and visible transaction code through support. We use those details to locate the record while keeping your wallet password and one-time code out of the request.

Correction request

If your phone number or account detail is inaccurate, contact us through the signed-in support route and describe the correction. We compare the request with the account record before changing information that affects phone verification or wallet matching.

DATA PRACTICE

How We Handle Your Personal Data

We limit personal data use to account operation, safety checks, payment reconciliation, support and legal duties that apply to the service.

Account details

We use your submitted account details to create the profile, complete phone verification and keep the correct person connected with account actions. If a required field changes, send a correction request through support rather than opening a second profile.

Device signals

Browser type, device information, login times and security events help us identify unusual account access and keep sessions functioning. These signals are handled for protection and troubleshooting, not as a replacement for your account credentials.

Cookies

Cookies and similar storage can remember a session, preserve selected settings and help us understand whether a page is working. You can manage browser cookie controls, although changing them may interrupt login, phone verification or account navigation.

Wallet records

Payment references help us match account activity with DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps. We use the reference needed for reconciliation and do not ask you to send a wallet password or one-time code.

Security checks

Phone verification and account event checks help us confirm that a request comes from the account holder. Keep your phone and login details private, and tell support promptly if a login or payment reference does not belong to you.

Retention and changes

We retain personal records only as long as needed for the stated purpose, account safety, dispute handling or applicable legal duties. To request access, correction or deletion where available, contact us through the signed-in support path.

Privacy Policy Questions For tgr99

These Privacy Policy answers address the account questions you may have before opening an account or when checking an existing profile. We explain the data connected with phone verification, wallet references, cookies, device access and requests for changes. If your situation is not covered, use the support route inside your account and describe the specific record or action involved. Any access or eligibility decision depends on local law.

The tgr99 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, security events and payment references. It explains why we use each category, how we protect account access and how you can request access or correction where local law permits.

Phone verification helps connect account activity with the person opening or using the profile. We may use it during account access, a data request or a security check. Keep the verification code private, and contact support if a code arrives without an action from you.

No. The Privacy Policy covers payment references needed to match an account action, such as a DANA or QRIS transaction code, but we do not ask for your wallet password or one-time code. Share only the reference details requested through the signed-in support path.

Use the support route shown after signing in and ask for an account data request. Include the phone number linked to the profile and the categories you want checked. We may verify account ownership before responding, and the available scope depends on local law.

Yes. Send a correction request through the account support path and identify the inaccurate field, such as a phone number or profile detail. We compare the request with account records before making a change that could affect phone verification or wallet reconciliation.

On a mobile browser, cookies or similar storage can preserve your session and selected settings while you move from login to the lobby. Browser controls can remove or block them, but that may require another login or interrupt account verification.

We keep personal data for the period needed for the purpose described in the Privacy Policy, account protection, payment reconciliation, dispute handling or applicable legal duties. To ask about a particular record, contact support with the account phone number and relevant date.

Related Pages

tgr99 Indonesia FAQ Account information Access guide nagaabola