Cookie page
Where our cookie page mentions device identifiers, this Privacy Policy explains how those identifiers can connect to login safety, preference storage and account support without repeating the same wording.
LEGAL REFERENCE
Privacy Policy for Your api 888 Account
api 888 puts privacy controls beside your account flow, so your live casino, slots and sportsbook profile, plus DANA, OVO, GoPay and QRIS context, are explained before you...
Account privacyIndonesia scopeWallet contextSupport routes
How This Privacy Policy Applies
This Privacy Policy explains how we collect, use, keep and share account data when you open, verify or manage an api 888 account in supported regions of Indonesia. It covers identity checks, login records, device signals, contact choices, wallet references and support messages connected to your account flow. We process data to run your account, help prevent misuse, answer privacy requests and
meet duties that apply where local law permits. DANA, OVO, GoPay and QRIS appear here as context for transaction records, not as a separate promise about wallet operators. We keep access limited to teams and service partners that need the data for the stated purpose. If we change the policy, we refresh this page so you can read the current privacy terms
before you continue.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
EDITORIAL CLARITY
How We Keep Policy Careful
We treat this Privacy Policy as a live brand promise. Each privacy change is checked against our account flow, Indonesian access context and support language before the updated...
Policy owner
A named internal policy owner keeps this page aligned with account flows, support scripts and partner tasks. That gives you...
Scheduled checks
We check privacy wording on a planned cycle and after material account-flow changes. The aim is simple: your policy page...
Plain wording
We avoid dense legal phrasing where a direct sentence works better. If a data purpose is needed, we state the...
Data minimisation
We ask for account data only when it supports identity checks, security, support handling or legal duties. Extra collection is...
Wallet context
DANA, OVO, GoPay and QRIS records are treated as account-related context. We explain why those references may appear without turning...
Access wording
Where access depends on supported regions or local law, we say so directly. That helps you understand when a privacy...
WHY THIS PLATFORM
Consistent Privacy Across Related Pages
Privacy wording should not change tone from page to page. We keep related policy pages connected, so account terms, cookie details and support contact routes all point back to the same privacy...
Account terms
Our account terms describe account duties, while this policy explains the data side of those duties. The two pages should feel connected when you open them together.
Promo board terms
If a promo board needs account checks, this page explains the privacy reason behind those checks. The related terms should not add a new data purpose by surprise.
Wallet help
Wallet help may mention DANA, OVO, GoPay or QRIS labels, but this policy sets the privacy frame for keeping those references tied to your account record.
Support page
The support page tells you where to contact us. This Privacy Policy explains how support messages, attachments and identity checks may be handled after you reach out.
Security page
Security wording focuses on account protection. This page adds the privacy layer, including device signals, access control and why some records must be kept for safety.
Contact page
Our contact page should never make privacy feel hidden. It points you back here for data access, correction, deletion and questions about how your request is handled.
PLATFORM SNAPSHOT
Visible Privacy Layout Cues
This page is built to make privacy easy to scan before you join. We surface the policy scope, wallet context, contact routes and update cues in visible blocks instead of hiding them deep in...
01
Header privacy promise
The opening block states the privacy purpose before anything else. You can see that account data, lobby profile data and wallet context are handled under one policy frame.
02
Context chip row
Short chips show the account areas this policy touches, including Indonesia scope and wallet references. They help you scan relevance without reading every section first.
03
Support route cards
Privacy contact cards separate access, correction, deletion and follow-up paths. That layout helps you choose the right route before you send sensitive account details.
04
Policy date cue
A visible update cue helps you know when the privacy wording changed. We use that space to show that policy upkeep is part of the account experience.
05
Mobile reading flow
The policy is arranged for phone-first reading, with compact sections and direct labels. You can check privacy terms while opening an account without losing your place.
06
Cross-page links
Related policy links keep privacy connected to cookies, terms and support. The goal is a consistent account data story across every legal page you may open.
Your Privacy Policy Questions
We collect account data you provide, login records, device signals, support messages and wallet-reference context tied to DANA, OVO, GoPay or QRIS activity. The exact data depends on how you use your account.
Wallet references help us connect account activity with support, reconciliation and security checks. We treat DANA, OVO, GoPay and QRIS labels as account context, not as a separate profile about your wallet provider.
Yes. You can request access through our privacy contact route. We may need to confirm your identity first, and some access steps depend on supported regions and where local law permits.
If account details are wrong, contact us with the correction you need and any proof that helps us verify it. We update records when the request is valid and permitted by local law.
We keep account data only as long as needed for account operation, support, security, legal duties and dispute handling. Retention periods can differ by data type, request status and local requirements.
Access is limited to our teams and service partners who need the data for account support, security, technical operation or legal duties. We do not open account records to wider teams without purpose.