LEGAL REFERENCE

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...

Account DataCookiesE-Wallet HandlesSession LogsYour Rights
desa88 How desa88 Handles Your Account Data

Our Privacy Posture and Scope

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP CHANNELS

Privacy Contact Paths

Reach our privacy desk through any of these channels and we'll route your request to the right team.

Privacy Inbox Email our privacy desk directly with your account handle and a short note about what you'd like — a data copy, a correction, or full deletion. We reply within five working days.
Live Chat Open the chat bubble inside the lobby and ask for the privacy team. The agent will confirm your identity, log the ticket and pass it to the data officer who handles Indonesia account requests.
Account Settings Some changes — marketing preferences, saved e-wallet nicknames, session reminders — you can flip yourself from the profile panel without writing in. Look under the Privacy tab once you're signed in.
PLATFORM TRUST SIGNALS

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.

Consistency Across Our Policy Pages

Same Definitions
Terms like account data, session log and e-wallet reference mean the same thing on this page as they do on our terms and cookie pages — no drift between documents.
Aligned Retention
How long we hold a record is stated once here and mirrored in our terms. If one updates, both update together so you never see conflicting timelines.
Shared Contact Desk
The privacy inbox listed here is the same address used on our cookie notice and account-closure page. One route, one ticket queue, one response time.
Matched Jurisdiction
Every policy page uses the phrase where local law permits in the same way, so the access rules don't read differently depending on which document you open.
Unified Revision Dates
When we revise privacy wording, the cookie and terms pages get a refresh stamp too if the change touches them, keeping the footer dates honest.
Single Data Map
The list of fields we collect appears here and is referenced — not rewritten — on sibling pages, removing the chance of two pages naming different fields.
Consistent Tone
We write each policy page in the same plain second-person voice, so moving between privacy, cookies and terms feels like one document, not three styles.
AT A GLANCE

What This Policy Page Shows You

Plain Wording We skip the legalese where we can. If a clause...
Field-Level Detail Each data field we hold — phone, e-wallet handle, IP...
Retention Windows We tell you how long each category stays on our...
Your Rights Panel Access, correction, deletion and objection rights are spelled out with...
Sharing Map Who sees your data outside desa88 — payment partners, regulators...
Update Trail A revision date sits at the foot of the page...

Privacy Questions We Hear Most

We collect your name, date of birth, phone number, an e-wallet handle for DANA, OVO, GoPay or QRIS payouts, and the device signals needed to keep your session secure. Nothing beyond what the signup form shows.

Only with payment partners processing your top-up reference, and with regulators if a lawful request reaches us. We do not sell your data, and marketing partners never receive your phone number or e-wallet handle.

Email the privacy inbox from the address on your account, or open chat and ask for a data export. We'll verify it's you, then send the file within five working days where local law permits.

Yes. Close the account from your profile or message support. We purge personal fields once retention rules our licence sets have run out — typically transaction references stay longer for audit, while marketing data goes immediately.

A login token, a language preference and a small analytics cookie that helps us see which slot rooms get opened most. You can clear them anytime from your browser and they reset on your next visit.

Most fields — phone, e-wallet nickname, language — are editable from the account panel. For name or date of birth fixes, message the privacy desk with a document showing the correct detail and we'll update the record.

The revision date sits at the foot of this page and updates each time the wording changes. If you want a copy of the previous version for comparison, our privacy inbox will send the archived text on request.