Our Privacy Policy, Written Plainly
This is the dewacasino privacy policy — the page that tells you what we collect when you open an account, why we hold it, and how long it...
Policy Posture and Jurisdiction Notes
We process your personal data under the framework that applies to your account region, and for Indonesia that means handling identifiers, device data and transaction logs only where local law permits. We collect what we need to verify you, fund your wallet and keep the lobby secure — nothing decorative. Marketing data sits in a separate bucket you can switch off in
your account settings. Where supported regions require disclosure to a regulator or payment partner, we share the minimum field set and log every request. Anything outside that scope stays with us.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
Privacy Inbox
Email our privacy desk for any data request — access, correction, deletion or export. We reply inside the window your jurisdiction sets and confirm the action against your verified account.
Live Chat Escalation
Open chat from the lobby footer and ask for the privacy queue. The agent routes you to a reviewer who handles consent changes and cookie preferences without touching wallet flows.
Account Settings
Most privacy controls sit inside your account panel — marketing toggles, session history, device list and a download button for the data we hold against your profile.
How We Review This Policy
Editorial Owner
A named privacy lead owns this page. Every clause change goes through them before it reaches you, so the wording you read matches what our backend actually does with your account fields.
Quarterly Review
We re-read the full policy each quarter against Indonesia data rules and our payment partners' terms. Updates ship with a visible date stamp at the top of the page.
Plain Language
We strip legal filler where we can. If a clause needs a defined term, we define it in line rather than burying it in a glossary you have to hunt for.
Change Log
Material edits are summarised in a short change log so returning account holders can see what shifted since their last visit without re-reading the whole document.
Third-Party Audit
Our data flows are reviewed by an external assessor against the standards our license requires. The findings shape the retention windows and access rules quoted here.
Reader Feedback
If a clause reads ambiguously, tell us through the privacy inbox. We log the comment, route it to the editorial owner and rewrite the section if the point lands.
Consistency Across Our Policy Pages
| Privacy vs Terms | This page covers data handling only. Wagering rules, bonus mechanics and account closure sit in our Terms — we link across so the boundary is clear. |
|---|---|
| Privacy vs Cookies | Cookie specifics live on the cookie page; this policy summarises the categories and points you to the toggle panel for granular consent. |
| Privacy vs KYC | Identity checks are described here at a category level. The KYC page lists exact document types we accept for Indonesia accounts. |
| Privacy vs Payments | DANA, OVO, GoPay and QRIS data flows are summarised here; the payments page carries the operational detail like cut-off times. |
| Privacy vs Security | Encryption and session controls are mentioned here in scope; the security page describes the technical posture in more depth. |
| Privacy vs Marketing | Marketing consent is covered here as a right; promotional terms and opt-out paths are mirrored on the promotions page. |
| Privacy vs Support | Contact routes are listed here for data requests only. General help, wallet questions and lobby issues route through the support page. |