How desa88 Handles Your Account Data
This is the desa88 privacy policy, written plainly so you know what we collect when you open an account, browse our slot rooms or place a sportsbook ticket...
Our Privacy Posture and Scope
This policy applies where local law permits and across supported regions for Indonesia. We collect identity details at signup, transaction references when you top up through DANA, OVO, GoPay or QRIS, and device signals that keep your session secure. We don't sell your data. We share it only with payment partners that need a reference to clear your deposit, and with regulators
if a lawful request reaches us. You can request a copy of your record, correct a typo in your profile, or close the account and ask us to purge personal fields, subject to retention rules our licence sets. Cookies on our lobby remember your language, last-played category and login token — nothing beyond what keeps the brand usable.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
Reach our privacy desk through any of these channels and we'll route your request to the right team.
How We Review This Policy
Internal Review
Our compliance team reads this page each quarter and after any change to how we process account data. If wording shifts, the revision date at the foot of the policy updates with it.
Legal Sign-Off
Counsel familiar with Indonesia consumer rules signs off the language before we publish. That keeps our wording aligned with what regulators expect a licensed brand to disclose.
Payment Partners
DANA, OVO, GoPay and QRIS partners each have their own privacy terms covering the transaction leg. We link to those so you can see where your reference travels once it leaves our servers.
Security Audit
Encryption, access controls and log retention are reviewed by an external security firm. Their findings shape how long we hold session data and who on staff can open an account record.
Staff Training
Anyone on our support floor who can see account fields completes a privacy module before going live. Refreshers run twice a year and any breach drill is logged internally.
Clear Versioning
Old versions of this policy stay archived. If you want to compare what changed between revisions, ask our privacy inbox and we'll send the prior text alongside the current one.