Reference

tupaiwin Privacy Policy for Your Account

Our Privacy Policy explains how tupaiwin handles the account, wallet and device data connected with your access to Speed Baccarat, Phoenix Rises and other lobby areas.

Account dataWallet recordsCookie choicesAccess requests
tupaiwin tupaiwin Privacy Policy for Your Account
PRIVACY HELP DESK

Get Help With Your Data Request

A privacy question should not require you to search through payment screens. Use the support link inside your account and include the email or phone number attached to your profile, plus the subject of your request. We can help trace a QRIS receipt, explain a device record or route a correction request without asking you to send wallet passwords or full bank credentials.

Team online

Account support path

Open the support link after login and state whether your request concerns account data, phone verification, a DANA receipt or another wallet record. We use the attached account details to locate the correct case.

Payment data check

For OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference and date only. We can check status and receipt matching without requesting your wallet PIN or banking password.

Access correction request

Tell us which profile detail or device record needs attention. We may ask for phone verification before changing account data, helping us protect your profile from an unauthorised request.

SIX DATA CHECKS

Six Privacy Checks Behind Your Account

Privacy work follows the same account path you use to reach the lobby: we identify the account, check the request, protect the record and keep only what has a clear operational or…

Account data

We use your contact details and phone verification result to create, sign in and protect your account. We also connect relevant account activity with requests made through the support path.

Wallet records

DANA, OVO, GoPay and QRIS references help us identify a payment attempt, match its status and address a receipt question. We do not need your wallet PIN or bank password.

Cookie controls

Cookies and similar device storage can remember session choices and help us understand sign-in errors. You can manage browser permissions, although some account functions may then need another sign-in.

Device security

We may record browser, device and sign-in signals to spot unusual access. If a login looks different, we can ask for phone verification before account details or wallet status are changed.

Data retention

We keep account and payment records for as long as needed for account support, transaction matching, security checks or applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

Changes and contact

To request access, correction or deletion of eligible data, use the account support link and describe the record involved. We may verify ownership before making a change and explain any legal reason for keeping it.

Privacy Policy Answers for Indonesia

These answers focus on the questions we expect you to ask before opening an account or linking a local wallet. They explain the data connected with tupaiwin access, how to request changes and what happens when you use the service from a mobile browser in Indonesia.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references and support requests connected with your tupaiwin account. It also explains your choices and how to contact us.

Phone verification helps us confirm account ownership before access or profile changes. It can also support security checks when a sign-in or wallet request comes from an unfamiliar device.

Yes. The Privacy Policy covers references, timestamps, status and receipt details linked to DANA or QRIS activity. We use those records to match payment steps and handle support questions, not to collect wallet passwords.

Sign in, open the support link in your account and ask for an access copy of the data connected with your profile. Include your account contact detail; we may verify ownership before responding.

Yes. Send a correction request through the account support path and identify the field that is wrong. We may require phone verification, then update eligible details or explain why a record must remain.

Cookies can preserve a session and help us diagnose sign-in or device errors. Your browser settings control them, but disabling certain cookies may require repeated login or affect account access.

Access, eligibility and some data choices depend on local law. If a rule applies to your location, we will follow that requirement and explain the available process when you contact support.