Reference

pt 89 Privacy Policy For Your Account

Our Privacy Policy shows how we handle the details connected with your pt 89 account, from phone verification to wallet activity linked with DANA, OVO, GoPay or QRIS.

Account recordsWallet activityPolicy requests

Explore Our Lobby Read FAQ

How DANA And QRIS Fit This Policy

pt 89 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers data created when you make an account, complete phone verification, sign in, or select a payment route. A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and time record so we can match the wallet event to your

1
account. Bank transfer and virtual account steps may also produce bank or reference details needed for reconciliation. We do not describe these rails as permission to access every service; access depends on local law. The policy also applies when you use a mobile browser, move between
2
casino and sports pages, or open titles such as Zeus vs Hades. We keep this payment context separate from your policy requests, so a question about a QRIS record can be handled without asking for unrelated account details.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

POLICY CONTACT

Where To Ask About Policy Access

A clear contact path helps when you need to understand a record, request a correction or ask why a policy request needs account verification.

Account data request Ask for a copy or explanation of account records through the policy contact route. We may confirm your phone verification before discussing details connected with your pt 89 account.

Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, share the reference shown in your cashier history, not your wallet password or one-time code.

Access concern If a policy page or account request does not open on your phone, tell us your browser and device path. We use that detail to trace access without asking for unnecessary content.

SECURITY PRACTICE

How pt 89 Protects Account Records

We handle this policy area through practical account controls rather than broad promises. Phone verification helps us connect a request to the right account, while device and browser signals help us investigate…

Data handling

We use account details for sign-in, phone verification, payment matching and policy support. Records connected with Live Football Odds, Bingo or Fishing God are handled as account activity, not as a separate identity profile.

Cookie choices

Cookies can keep your session and selected page settings available while you move through the mobile lobby. Your browser controls whether cookies are stored, and changing them may affect policy-page access.

Account security

We may use phone confirmation, sign-in details and device signals to reduce account mix-ups. Never place a password, wallet PIN or one-time code inside a policy contact message.

Payment records

DANA, OVO, GoPay and QRIS references help us match a payment status to your account. Bank transfer and virtual account records may be retained for reconciliation and policy-related questions.

Retention period

We retain records only for the period needed for account operation, payment matching, security checks or a legal request. Ask support which record category your retention question concerns.

Changes and requests

You can request access, correction or removal by using the policy contact route. We may ask for phone verification before changing records, and eligibility for a request depends on local law.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the account, wallet and device questions you may search before opening pt 89. We keep each response tied to a practical request, including data access, cookie settings, payment records and account contact steps.

It covers account creation, phone verification, sign-in activity, cookies, device signals, payment references and support requests connected with your account. It also explains retention and how to ask for changes.

Our policy concerns payment references and status details needed for matching. Do not send a DANA, OVO, GoPay or QRIS password, PIN or one-time code to support.

Yes, you can use the policy contact route to ask for account records or an explanation. We may confirm your phone verification first, and the request depends on local law.

Cookies can keep your session and selected settings available when you open the lobby in a mobile browser. Your browser can block or remove them, though some account paths may change.

Send a correction request through the policy contact path with the affected account detail. We check the request against your verified phone record before changing information connected with your account.

Retention depends on the record type and whether it is needed for payment matching, account security or a legal request. Ask support about the specific DANA, bank transfer or virtual account reference.

You can open the policy page from a supported Indonesian device path, including a mobile browser. Account access and eligibility remain available where local law permits, with requests handled through support.

pt 89 Privacy Policy For Your Account

Where To Ask About Policy Access

How pt 89 Protects Account Records

Data handling

Cookie choices

Account security

Payment records

Retention period

Changes and requests

Privacy Policy Questions About Your Account

01 What does the pt 89 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS password?

03 Can I request my personal data from pt 89?

04 How does the Privacy Policy use cookies on mobile?

05 How do I correct an account detail under this policy?

06 How long does pt 89 keep payment records?

07 Can I access the Privacy Policy from Indonesia?

Related Pages