LEGAL REFERENCE

Our Privacy Policy, Plain and Direct

This page is where we explain how wayang slot88 handles the personal data tied to your account. We've kept the language readable so you can scan the parts...

Account dataCookie notesRetention windowsYour controlsIndonesia scope
wayang slot88 Our Privacy Policy, Plain and Direct

How We Handle Your Account Data

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

HELP CHANNELS

Privacy Contact Paths

If you have a question about your data — what we hold, how to change it, or how to remove it — these are the channels we monitor. Each one routes to the privacy desk rather than general lobby support, so your request lands with someone who can action it directly.

Team online

Privacy Inbox

Email our privacy desk directly with data access, correction or deletion requests. We confirm receipt the same day and aim to close the ticket within the window your region expects of us.

In-Account Form

Once you're signed in, the privacy form sits inside your account settings. Submitting from there auto-attaches your account reference, which speeds up identity checks and shortens the back-and-forth on sensitive requests.

Live Chat Escalation

Start with live chat in the lobby and ask to be routed to privacy. The agent will hand you off to the data team rather than trying to handle the request inside the general support queue.

PLATFORM TRUST SIGNALS

How This Policy Is Maintained

We don't treat the privacy policy as a one-time document. It's reviewed on a schedule, edited when our processing changes, and dated so you can see the last touch.

Reviewed Quarterly

Our privacy text is read against current processing every three months. If a step has changed — a new wallet partner, a new retention window — the wording is updated before the change goes live in the lobby.

Versioned Changes

Each edit is logged with a date stamp at the foot of this page. You can see when a clause was last touched, which matters if you're checking whether a recent update affects your account.

Legal Sign-Off

Material changes pass through legal counsel familiar with Indonesia data rules before publication. We don't push wording live just because product wants to ship — the policy desk has the final read.

Plain-Language Pass

After legal, an editor rewrites dense clauses into readable English. If you can't understand what we're doing with your data, the policy isn't doing its job, regardless of how watertight the legal text is.

Internal Access Logs

Staff access to account data is logged and reviewed. Only roles that need a record to do their job can open it, and the audit trail is kept separately from the lobby's operational systems.

Reader Feedback

If a clause reads ambiguously to you, send the line back to us. We've reworded sections more than once based on direct reader pushback, and we credit that feedback in the change log.

Consistency Across Our Policy Pages

Our privacy policy sits alongside the terms, cookie notice and account rules. We keep the wording aligned across all of them so you don't read one thing here...

Privacy vs Terms
The terms cover what you agree to when using the lobby; this page covers data only. Where they overlap — account closure, for example — both pages reference each other rather than restating clauses.
Privacy vs Cookies
Cookies have their own notice because the consent flow is separate. This policy summarises what's collected; the cookie notice lists each tag, its purpose and its lifespan in detail.
Privacy vs Account Rules
Account rules govern lobby behaviour. Privacy governs the data that behaviour generates. We cross-link both so a question about a flagged session points you to the right page first time.
Privacy vs KYC
KYC documents are processed under this policy but kept on a tighter retention clock. The KYC page details which documents are required; this page covers how long they're held.
Privacy vs Marketing
Marketing consent is opt-in and recorded separately from account data. Withdrawing consent on marketing does not affect the account data we must keep for transactional reasons.
Privacy vs Payments
Wallet references for DANA, OVO, GoPay and QRIS are processed under this policy. The payments page explains the flow; we explain what's stored from it and for how long.
Privacy vs Support
Support transcripts are retained on a shorter window than account records. If you've shared sensitive details in chat, you can request that specific transcript be purged independently.
AT A GLANCE

What You'll Find On This Page

To make the policy easier to scan, we've laid it out in fixed sections. Here's what each block on this page covers, so you can jump straight to the part relevant to your question.

01
Data Collected A clear list of the fields we capture when you open an account, plus the optional ones tied to verification. If a field isn't listed here, we aren't collecting it through the standard sign-up flow.
02
Purpose Of Use Each data category is paired with the reason we hold it — account security, transaction confirmation, regulatory record-keeping. You'll see the purpose alongside the field rather than buried in a separate clause.
03
Retention Periods Concrete time windows rather than vague phrasing. Where a record must be kept under Indonesia rules, the period is stated; where it's our own choice, we explain why we picked that window.
04
Your Rights Access, correction, export and deletion rights are spelled out with the exact channels to exercise each one. We've put the request links inline so you don't hunt for them at the end of the page.
05
Third Parties Where data is shared with processors — payment partners, identity checkers, hosting providers — we name the category and the reason. Sharing is limited to what's needed to run your account.
06
Change Log The footer carries the last-updated date and a short note describing what changed. If you've read the policy before, the change log lets you skim only the lines that have moved since.

Privacy Policy — Common Questions

At sign-up we hold your name, contact details, login credentials and the wallet reference you use for funding. Verification adds an ID document where local law requires it. Nothing beyond that runs through the standard flow.

Transactional records are held for the period our supported regions require, typically several years for tax and audit reasons. Marketing data is purged on closure, and support transcripts run on a shorter window than account data.

Yes. Submit a deletion request through the in-account privacy form or the privacy inbox. We'll remove what we're not legally required to retain and confirm in writing which categories had to stay on file.

Only the references needed to process your DANA, OVO, GoPay or QRIS transaction. Payment partners receive the transaction detail, not your full account record. We don't pass marketing data to them under any circumstance.

Open account settings and edit the field directly, or send the correction through the privacy form if the field is locked for verification reasons. Identity-linked changes may need a supporting document before they're applied.

Hosting locations are listed in the change log section. Where data leaves Indonesia, we use processors that meet the standards our supported regions expect, and the transfer basis is recorded against each processor.

Material changes are emailed to the address on your account and flagged in the lobby on your next sign-in. Minor edits appear in the change log at the foot of this page with the date and a short note.