Privacy Built Around Your Account
396 slot keeps your account data, lobby activity and DANA, OVO, GoPay or QRIS references under a clear privacy policy for Indonesia. Open your account in seconds and...
How Our Privacy Policy Works
This Privacy Policy explains how we collect, use, store and protect the data connected to your 396 slot account, including sign-in details, device signals, lobby activity, support chats and transaction references where local law permits. We use this data to create your account, keep access stable, detect misuse, maintain records, answer your requests and show you the account areas you choose to
explore. We do not sell your personal data. We may share limited records with service partners that help us operate identity checks, security monitoring, support handling and payment reconciliation for supported regions. When you use DANA, OVO, GoPay or QRIS, we handle only the references needed to match your account action with the service involved.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths We Maintain
You can reach us about privacy requests through account support, live chat or email-style contact forms shown inside your account area. We keep these paths focused on privacy correction, access questions, deletion requests where available, and consent choices tied to your account. Our team may ask you to confirm account ownership before changing records.
Account help desk
Use the account help desk when you want us to check saved profile data, login records or device activity linked to your 396 slot account.
Live chat privacy route
Start live chat for faster privacy routing. We may move sensitive requests to a secure follow-up path before discussing account-specific data.
Request confirmation
For correction or deletion requests, we confirm control of the account first so private records are not changed by the wrong person.
Policy Review And Data Care
We write this Privacy Policy for you in plain English, with Indonesia access and supported regions in mind. Our internal review looks at how account data moves through sign-up, lobby access, security...
Plain language
We avoid legal fog where possible, so you can see what data we collect, why we use it and how it supports your account access.
Account-first scope
Our review starts with your account journey, from joining to lobby access, then checks which records are needed at each step.
Partner checks
Where partners help with security, hosting, support or reconciliation, we limit shared data to what the service needs to perform its role.
Security alignment
Privacy review is linked with security controls, so stored records, access logs and account actions are handled with role-based internal access.
Change tracking
When we update privacy wording, we check that it still matches current account flows, support routes and available consent choices.
Local context
We consider Indonesia access patterns, local wallet references and QRIS records when describing how account data is processed in supported regions.
Consistency Across Policy Pages
Our privacy wording is designed to sit consistently beside our terms, cookie wording and account rules. Each page has a different job, but the same brand voice: direct...
Visible Policy Layout Highlights
We built the policy-side layout so you can find privacy essentials without digging through unrelated platform copy. The page separates collection, use, sharing, storage, contact routes and account choices into clear blocks. Short labels...