Privacy Policy for Indonesia Accounts
Sweet Bonanza, Live Baccarat, Aviator and our sportsbook sit behind one account flow, and this Privacy Policy explains how we handle the account data, lobby logs and QRIS...
How Our Privacy Policy Works
This Privacy Policy applies when you create an api naga account, browse our lobby, contact us, or use account features where local law permits. We collect data needed to run your account, keep access secure, manage service messages, handle checks, and maintain records tied to DANA, OVO, GoPay, QRIS, bank references, device activity, and session history. We use that data only for
account operation, compliance checks, support handling, security monitoring, service improvement, and communication that relates to your account. We may share limited data with service providers, verification partners, hosting teams, and legal or regulatory channels when required for supported regions. We keep records only as long as needed for these purposes, then delete, anonymise, or restrict them according to our retention process.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Clear
We write this Privacy Policy for your account journey, not as a generic legal wall. Each check looks at the same practical points: what we collect, why we...
Plain wording checks
We keep privacy wording direct so you can understand how your account data, session records, and support messages are used...
Purpose mapping
Every data category in this Privacy Policy is tied to a purpose, such as account access, security checks, support handling...
Access control checks
We limit internal access to account data based on work needs. Support, security, and operations teams receive only the data...
Partner handling checks
When we use vendors for hosting, verification, analytics, or service delivery, we assess how they handle data and restrict use...
Retention discipline
We keep records for practical account, security, and legal needs, then remove, anonymise, or restrict them when they no longer...
Request handling logs
Privacy requests are tracked so we can confirm what was asked, who handled it, and how we replied. That helps...
Consistent Privacy Across Our Pages
This Privacy Policy sits beside our other legal pages, but it has one job: explaining how data moves through your api naga account. We keep related pages aligned...
Visible Privacy Layout Highlights
We designed the policy layout to be easy to scan while still covering the details that matter to your account. The visible elements below help you...
Clear account scope
The page starts by showing that the Privacy Policy covers account creation, lobby browsing, support contact, device activity, security checks, and transaction references tied to your profile.
Short data categories
Data categories are grouped into readable blocks, so you can separate contact details, session records, device signals, communication choices, and account activity without losing the thread.
Purpose-first structure
We place the reason for each data use close to the data category itself. That makes it easier to see why we collect something before you keep reading.
Request routes shown
Contact options appear on the page so you can ask about access, correction, deletion, restriction, or other privacy concerns without leaving the policy flow.
Regional wording included
Where access depends on supported regions or local law, the policy says so plainly. We avoid making privacy promises that do not match real operating conditions.
Update signals visible
When policy wording changes, the page can show clear update signals so you know the privacy terms you are reading are the current account-facing version.