LEGAL REFERENCE

Privacy Policy for Your Account

37 2d protects your account flow from log-in to DANA, OVO, GoPay and QRIS record handling, so you know what data we collect before you join. Open your...

Account data clarityIndonesia policy focusWallet record careSupport-ready requests
Account access Read FAQ
37 2d Privacy Policy for Your Account

How We Handle Your Data

Our Privacy Policy explains how we handle the data you share when you open an account, verify your profile, contact support, or make wallet records visible to our team. We write for Indonesia and apply this policy only where local law permits access to our casino and sportsbook services. We collect only what we need to run your account flow, protect your

session, check transactions, and answer your requests. When DANA, OVO, GoPay, or QRIS appears in your account history, we treat those references as sensitive account records, not promo material. You can ask us to explain, correct, or limit stored details through the support paths below. We keep retention periods tied to account, security, legal, and service needs, then remove or anonymise data

when those needs end.

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

24/7 SUPPORT

Privacy Contact Paths

You should not have to search across the site to ask about privacy. Use these contact paths when you want to check stored data, update account details, question a record, or ask...

Privacy Chat Open live support and ask for privacy help when you need a quick read on account records, wallet references, or policy wording. We route the chat to the team that can handle data questions.
Email Request Send an email when your privacy request needs attachments, dates, or a longer explanation. Include your account email only, then we’ll confirm what else is needed before we access any record.
Account Centre Use your account centre to correct basic profile details before raising a privacy ticket. Keeping your visible details current helps us match your request without asking for extra proof too early.
REVIEW SIGNALS

How We Keep Policy Clear

A privacy page should feel practical, not hidden behind legal fog. We check this page against account flows, wallet references, support handling, and Indonesia-facing wording so you can understand what happens before...

Plain Language

We write privacy wording in direct English for Indonesia, avoiding legal clutter where a clear sentence works better. You should be able to see what we collect, why we collect it, and who handles it.

Country Fit

We align policy wording with supported regions and include where local law permits whenever access is discussed. That keeps privacy promises tied to the markets where we can actually provide service.

Data Mapping

We connect policy statements to real account events such as log-in, verification, wallet references, support chats, and security checks. This helps prevent vague claims that do not match your actual account flow.

Security Input

Our security checks shape the policy sections on session data, device signals, and suspicious activity handling. Privacy and account protection sit together, so we explain both without turning the page into a tech manual.

Change Control

When we adjust privacy wording, we check whether the change affects collection, retention, sharing, or your choices. Bigger changes are kept visible so you can revisit the policy before continuing.

Support Feedback

Questions sent to support help us spot confusing privacy wording. If you keep asking about the same data point, we use that signal to make the next version clearer and easier to act on.

Consistency Across Policy Pages

Our privacy wording connects with related policy pages without repeating the whole site. Each page has a job: this one explains personal data handling, while linked pages cover...

Cookie PolicyThe cookie page explains browser storage and device signals, while this Privacy Policy explains how those signals may connect to your account. Together, they show why session protection and preference handling matter.
Terms PageThe terms page sets account rules, but this page explains the data used to support those rules. If an account check happens, this policy covers the records we may need to read.
Security PageSecurity wording focuses on protection steps, while this page explains the personal data behind those steps. Device signals, log-in history, and suspicious activity checks are treated as privacy-relevant account records.
Promotions PagePromo pages may show account-facing offers, but this policy explains how related account eligibility data is handled. We do not treat wallet references or identity details as marketing copy.
Wallet RecordsWallet references involving DANA, OVO, GoPay, or QRIS may appear in account history. This page explains how we handle those references when support, security, or reconciliation checks are needed.
Support TermsSupport pages tell you how to reach us, while this policy explains what support may access during a privacy request. We limit handling to what is needed for the question raised.
Access LimitsAccess wording on other pages may mention supported regions. This Privacy Policy adds the data side, explaining how we handle requests and account records only where local law permits.
QUICK SIGNAL

Privacy Policy Page Highlights

This page is built so the privacy points are easy to scan before you open an account. The layout keeps account data, support routes, retention, and wallet-reference handling visible without pushing you through dense...

01
Short Hero Badges The badges near the hero show the privacy themes at a glance: account clarity, Indonesia focus, wallet record care, and support routes. They help you decide where to read next.
02
Readable Legal Block The main legal block explains data handling in one connected paragraph, not scattered fragments. You get collection, purpose, wallet references, correction requests, and retention in a single privacy-first section.
03
Visible Contact Cards Support cards sit close to the legal wording so you can act after reading. If you need access, correction, or clarification, the next step is visible without leaving the policy page.
04
Editorial Checks The trust section shows how we keep privacy wording aligned with real account flows. It makes the policy feel current, practical, and connected to how your account is actually handled.
05
Cross-Policy Links The comparison section separates privacy from cookies, terms, support, and security language. That makes each page easier to read while still showing how your account data connects across them.
06
FAQ Closure The FAQ closes the page with direct answers to the privacy questions you are most likely to ask before joining. It keeps the final step focused on your data choices.

Your Privacy Policy Questions

We collect the details needed to create, verify, protect, and service your account. That can include profile data, log-in records, device signals, support messages, and transaction references tied to your account history.

When those names appear in your account history, we treat them as sensitive account references. We use them for support, reconciliation, security checks, and legal needs, not as casual marketing material.

Yes. Contact us through chat, email, or your account centre and explain what needs correction. We may ask for matching account details before updating records, so the request stays secure.

This policy applies to our Indonesia-facing service only where local law permits access. If a feature, contact path, or account flow is unavailable in your region, related data handling may also differ.

We keep account data only for account operation, security, support, legal, and record needs. When those reasons end, we remove, anonymise, or reduce stored data according to our retention process.

Only team members who need to answer, verify, or process the request should access it. We keep privacy tickets limited to the purpose you raised, with extra care for wallet references.