Reference

tt789 Privacy Policy For Your Account

Clear control over account, phone, wallet and device data starts with the tt789 Privacy Policy.

Account recordsWallet referencesMobile sessions
tt789 tt789 Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Questions Beside Account Support

A clear contact route helps when you want to ask about the Privacy Policy, correct an account detail or question a wallet record. Include the phone number tied to your account and the relevant receipt or session date, but never send a password or one-time code. We use those details to find the right record, check whether the request concerns DANA, GoPay, QRIS or another payment path, and reply through the support route shown in your account area.

Team online

Account data request

Ask us to explain the personal data connected with your account after phone verification. We may request the same account detail again so we do not disclose records to the wrong person.

Wallet record query

Send a DANA, OVO, GoPay or QRIS receipt reference when a payment record looks unfamiliar. We compare the reference with account activity and explain the status without asking for your wallet password.

Policy change request

Use our account support path to request a correction, restriction or deletion review. Tell us which field or record concerns you, and we will explain what can change under local law.

DATA HANDLING

What We Protect And Retain

We handle Privacy Policy requests through practical account controls rather than broad promises. Phone verification helps us link a request to the correct account, while session checks help us spot unusual sign-ins…

Collected account data

When you open an account, we may collect your name, phone number, verification result and account activity. These fields let us provide account access and respond to a Privacy Policy request about your own records.

Device and session data

The mobile browser path can create device, browser, IP and session records. We use them to keep sign-in checks consistent across the lobby, including when you move from Fishing War Mobile Play to account settings.

Cookie choices

Cookies and similar storage can remember sign-in state, language settings and security preferences. You can manage browser permissions, although removing necessary storage may require another phone verification before account access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave reference numbers and timestamps in our records. We use these for matching and status checks, not to collect your wallet password.

Retention review

We keep records while they support account administration, security, payment reconciliation or an unresolved request. After those needs end, we review whether a record should be deleted or kept for a stated legal purpose.

Security response

If you notice an unfamiliar sign-in or account detail, contact support through the account path and mention the date and device. Do not share a password or verification code; we use account checks to investigate safely.

Privacy Policy Answers For tt789 Accounts

These Privacy Policy answers cover the questions you are most likely to ask before opening or using an account. We keep the wording practical: what data we collect, why payment references appear, how device records work, and where to send a correction or deletion request. Access to the service depends on local law and applies where local law permits.

The tt789 Privacy Policy covers account details, phone verification, device and session records, cookies, payment references and support requests. It explains why we use each category, how we protect it, how long we assess keeping it and how you can contact us.

We use your phone number to create and identify your account, complete the clear phone verification step before account access and connect a policy request to the right record. We do not need your DANA, OVO or GoPay password for that process.

Yes. The Privacy Policy covers payment references, timestamps and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those records to match a transaction and answer a status question, not to access your wallet credentials.

When you sign in through a mobile browser or desktop browser, we may record device type, browser details, IP address and session events. These records help us check account security and understand an access issue without reading unrelated files on your device.

You can contact our account support path to ask what personal data is linked to your account or to request a correction. Include your verified phone number and the field in question. We may confirm ownership before responding, where local law permits.

Send a deletion request through the support route shown in your account area and identify the records you want reviewed. We assess the request against open payments, security checks, support matters and local legal requirements before explaining the result.

Tell us the approximate time, device and account detail that looks unfamiliar. We compare session records, may ask you to complete phone verification again and help secure the account. Never include a password or one-time code in your Privacy Policy request.