LEGAL REFERENCE

Your Privacy at tigerjp88 apk

tigerjp88 apk keeps your casino, slots and sportsbook account flow clear by showing what data we collect, why we use it, and how you can contact us. Open...

Account dataDevice signalsSupport accessIndonesia focus
View Game Library Read FAQ
tigerjp88 apk Your Privacy at tigerjp88 apk

How This Privacy Policy Applies

This Privacy Policy explains how we handle personal details connected with your tigerjp88 apk account, identity checks, security logs, support chats, promotion preferences and payment references where local law permits. We collect only what we need to run your account, protect the lobby, process account actions, answer your requests and meet legal duties in supported regions. When DANA, OVO, GoPay or QRIS

appears in your account flow, we may store transaction references, timing, status and support context, not your full wallet credentials. We may share limited records with service partners who help us host, verify, secure or support the platform, under controls that restrict unrelated use. You can ask us to access, correct or remove eligible records, subject to security, fraud prevention and legal

retention needs.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PLAYER SUPPORT

Privacy Contact Paths

Use these contact routes when your question is about privacy, account records or consent choices. We keep the request focused, ask for enough detail to confirm your account, and avoid collecting extra...

Account privacy desk Send your account privacy request through the logged-in support area. We can match your message to your profile faster and respond about access, correction or deletion choices.
Payment reference help If a DANA, OVO, GoPay or QRIS reference needs checking, share the time and amount only. We will never ask for wallet passwords or private PINs.
Consent preferences Use support to update marketing consent, message frequency or promotional contact choices. We record the change so your account preferences stay aligned across active channels.
REVIEW SIGNALS

Policy Checks We Keep Visible

We write this policy as the brand that operates the account flow, not as a third party. Each privacy statement is checked against how our forms, wallet references, security logs and support...

Plain wording

We avoid legal fog where simple wording works. You should understand what we collect, why we need it, and which choices remain available inside your account.

Operational matching

Policy claims are compared with account screens, support scripts and transaction reference fields. If the product flow changes, the privacy wording must follow that change.

Limited sharing

Partner access is kept to the task being performed, such as hosting, security, verification or support. We do not describe broad sharing as if it were unlimited.

Local context

Indonesia wallet names and QRIS references are described in the privacy context you actually see. We separate payment status records from private wallet credentials.

Retention checks

We keep account records only for practical, security and legal reasons. When a record no longer has a valid purpose, we remove or reduce it where possible.

Request handling

Privacy requests are handled through controlled support paths. We may verify your account first so personal records are not released to the wrong person.

Consistency Across Our Policy Pages

Our legal pages are designed to work together, so privacy wording does not conflict with account terms, cookie controls or promotion rules. This page stays focused on personal...

Account terms alignment
The Terms page explains account duties, while this page explains personal data handling. We keep both pages aligned so privacy promises do not clash with account controls.
Cookie page alignment
Cookie controls cover browser storage and tracking tools. This Privacy Policy connects those signals to broader account records, security checks and preference handling.
Promotion terms alignment
Promotional rules may use eligibility records, opt-in status or account history. This page explains how those records are handled, stored and updated when you change preferences.
Support policy alignment
Support conversations can include account details, device clues and transaction references. Our privacy wording explains why those records are kept and how access is controlled.
Payment reference alignment
Wallet and QRIS pages may show transaction status. This page clarifies that we use payment references for account support, reconciliation, security and legal record keeping.
Security wording alignment
Security language covers login protection, fraud checks and abuse prevention. Privacy wording explains the data behind those checks without turning it into unrelated profiling.
Regional access alignment
Where access is discussed, we use supported regions and where local law permits. Privacy records are handled with that same regional framing across our legal pages.
PLATFORM SNAPSHOT

Policy Layout You Can Read

This page is built to help you act, not search through long blocks of legal copy. The layout separates account data, local wallet references, support contact routes and...

Clear opening summary The first screen states the privacy purpose before anything else...
Short context chips DANA, OVO, GoPay and QRIS appear as context chips because...
Action-focused contacts Support cards explain which path to use for privacy requests...
Readable trust signals The policy check section shows how we keep wording tied...
Linked legal logic Comparison cards explain how this policy connects with terms, cookies...
Practical FAQ The FAQ answers common privacy questions in direct language. It...

Privacy Questions Before You Join

We collect account details, login records, device signals, support messages, preference choices and transaction references. The exact record depends on which account actions you take and which features you choose.

We use your data to create and manage your account, protect the lobby, answer support requests, record consent choices, process references and meet duties that apply in supported regions.

No. We may store reference numbers, status, timing and support context for DANA, OVO, GoPay or QRIS activity, but not your private wallet password, PIN or full credential set.

Yes. Contact support from your account and tell us what needs access, correction or deletion. We may verify you first and may keep records required for security or legal reasons.

We keep records while they are needed for account service, security checks, dispute handling, fraud prevention and legal duties. When the purpose ends, we remove or reduce eligible records.

We share limited records with service partners that help with hosting, verification, security, analytics or support. Their access is tied to that task and not for unrelated independent use.

You can update promotional contact choices through support or available account settings. We record your preference so marketing messages match your consent status across active tigerjp88 apk channels.