Reference

tirai46 Privacy Policy for Your Account

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

Account dataWallet recordsDevice choicesPolicy requests
tirai46 tirai46 Privacy Policy for Your Account
REQUEST HELP SAFELY

Where To Ask About Privacy Policy

A clear contact path matters when you want to ask about stored data, correct an account detail or check a wallet record. Start from the support route inside your signed-in account, so we can connect the request with the right account without exposing details in a public message. If you are in Yogyakarta, the same account path applies whenever access is available where local law permits.

Team online

Account privacy request

Use the support path shown after login and state whether you want access, correction or removal of a personal detail. We may ask for account checks before responding.

Wallet record question

For DANA, QRIS, OVO, GoPay or bank transfer references, include the transaction date and receipt code through the cashier support path, not your wallet password.

Access concern

If a login or device change looks unfamiliar, contact support from the account route and secure your sign-in first. We use the account step to reduce mistaken disclosures.

DATA HANDLING LENS

What We Keep And How You Control It

Privacy choices should fit the way you actually reach the lobby. Our policy separates account records, payment references, device signals and cookie preferences so each request can be handled against the correct…

Account details

We use your submitted account details to create access, confirm ownership and respond to requests. Check your phone entry before continuing, because it helps link support messages to the correct account.

Cookie choices

Cookies and similar device signals can help remember a session and detect unusual login behaviour. Your browser controls can remove stored cookies, although a fresh login may then be required.

Sign-in security

We look at login time, browser and device signals when protecting account access. If your phone or device changes, complete the requested account check before wallet details are shown.

Retention practice

Account, support and payment records are kept for the period needed for service operation, security checks, dispute handling or legal duties. We do not promise a single period for every record type.

Correction requests

You can ask us to correct an inaccurate account detail through signed-in support. Describe the field that needs changing, and we may request a matching account check before editing it.

Who to contact

Privacy questions belong in the support route connected to your account. Include the subject of your request, such as data access, cookie use or a DANA receipt reference.

Privacy Policy Questions About tirai46

These answers address the questions we expect you to ask before opening an account or checking a wallet record. They explain what the Privacy Policy covers, which account steps may request extra detail and how to send a change request. If your situation is specific, use the support path connected with your signed-in account.

It covers account details, login and device signals, cookies, support messages, game activity records and payment references connected with DANA, OVO, GoPay, QRIS or bank transfers.

We use your phone details to create an account, confirm account ownership and connect a privacy request with the correct record. Account access is available where local law permits.

Yes. The Privacy Policy includes QRIS receipt references and related cashier records. Send the receipt code through signed-in support when you need a payment record checked.

We may use browser, device and login signals to keep sessions secure, detect unusual access and restore the correct account path. These signals are not a reason to collect unrelated details.

Yes. Use the account support route, name the detail that needs correction and provide the requested account check. We assess the request under the Privacy Policy and local requirements.

Send an access request through signed-in support and describe the records you want reviewed, such as account details, cookie use or wallet references. We may verify ownership first.

Retention depends on the record and why we hold it, including account operation, security, disputes and legal duties. The Privacy Policy does not assign one period to every data type.