Reference

tap99 Privacy Policy, Made Clear

Your tap99 Privacy Policy explains how we handle account details, wallet records and device data while you browse Live Dealer Lobby or Fishing God.

Account dataWallet recordsDevice choicesCookie controls
tap99 tap99 Privacy Policy, Made Clear
CONTACT OUR TEAM

Reach Support About Your Privacy Policy

A direct support route helps you resolve a privacy question without repeating your account story across different channels.

Account message Use the signed-in account message path for a Privacy Policy request about profile details…
Payment query For a Privacy Policy question linked to DANA, OVO, GoPay, QRIS, bank transfer or…
Access request If you cannot reach the account support area, use the contact route displayed on…
HOW WE HANDLE DATA

Browse tap99 Privacy Controls

Privacy choices are connected to ordinary account actions, so we explain what happens when you sign in, switch devices or move from the lobby to a wallet screen.

Account details

We use the contact details you provide to create the account, send account messages and complete phone verification before access. Check your profile when a number or email changes, and ask support to correct a record that no longer matches your current details.

Cookie choices

Cookies and device storage can keep your signed-in session active, remember a selected page and help us detect repeated login errors. You can adjust browser controls, although blocking necessary storage may sign you out or prevent the lobby and Privacy Policy page from loading correctly.

Payment records

A DANA, OVO, GoPay or QRIS reference lets us connect a payment status to your account without receiving your wallet PIN. Bank transfer and virtual account records may include a reference, amount and time needed to reconcile the cashier entry.

Device security

We record practical security signals such as login time, browser type and device changes to identify unusual account access. These signals can trigger an extra verification step, but they do not give us permission to read private files, photos or messages on your phone.

Record retention

We keep account, payment and support records only while they serve security, reconciliation, dispute handling or legal duties. When a record is no longer needed, we delete it or separate it from direct account identifiers, subject to required retention under local law.

Your requests

Ask for access, correction, deletion where allowed, or an explanation of a particular data use through the signed-in support path. Include the account email or phone and the affected record, then complete our identity check before we make a change.

Find Privacy Policy Answers

These Privacy Policy questions cover the account steps we hear about most often, including wallet records, cookies, device changes and requests for access. We keep the answers tied to tap99 rather than describing unrelated platform functions. If your situation is different, send the exact question through account support and include the page or transaction reference involved.

It covers how we collect, use, store and protect account details, verification records, device signals, cookies, support messages and payment references. It also explains your choices when you ask to access, correct, delete or limit a data use, where local law permits.

Phone verification helps us connect the account to the person opening it and reduces mistaken or unauthorised access. We use the verification status for account protection and support checks; we do not ask you to place a wallet PIN or authentication code in a support message.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These records help us match a cashier event to your account, while your wallet password remains outside our support request process.

Send an access request through the signed-in account support area and identify the email or phone on the account. Tell us which records you need, such as profile, device or payment history. We may complete an identity check before preparing the response.

You can request a correction whenever an account detail is wrong. You may also ask about deletion or restricted use, where local law permits. We first check whether a record must remain for account security, payment reconciliation, dispute handling or a legal duty.

On a phone, cookies and device storage can preserve your session, remember the page you opened and help identify repeated sign-in problems. Browser settings let you remove or block them, but necessary storage controls may sign you out or affect page access.

We retain some account, payment or support records after closure when they remain necessary for security, reconciliation, disputes or legal duties. Once that purpose ends, we delete the record or remove direct identifiers. Access and eligibility depends on local law and applicable retention rules.