LEGAL REFERENCE

How We Handle Your Account Data

This is the wings138 slot privacy policy — the page that explains what we collect when you open an account, what we keep on file while you move...

Privacy PolicyIndonesiaAccount DataCookiesLast Updated
wings138 slot How We Handle Your Account Data

Our Privacy Posture for Indonesia

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

HELP CHANNELS

Privacy Contact Paths

Team online

Privacy Inbox

Email our privacy desk for any request tied to your account record — access, correction, export or deletion. We respond within working hours and confirm the action against your registered contact before changes go through.

Live Chat

Open the chat bubble in the lobby and ask for the privacy team. The agent escalates data questions off the general queue so your request lands with someone who handles policy matters directly.

Account Settings

Inside your account you can review the contact details we hold, update marketing preferences, and pull the cookie panel back up. Most privacy tweaks don't need a ticket — they're already in your dashboard.

WHY THIS PLATFORM

Editorial Trust Signals for This Policy

Reviewed Quarterly

Our policy desk re-reads this page every quarter and after any change to how the lobby, sportsbook or wallet integrations handle your data, so the wording you see matches what actually runs in production.

Plain-Language Drafting

We write the policy in the same voice you hear across the brand. If a clause needs legal phrasing, we add a short explainer next to it so you don't need a lawyer to follow what we mean.

Versioned Changes

Every revision carries a date and a short note on what shifted. Older versions stay on file, so if you signed up under earlier wording you can compare it against the current page.

Named Owner

A single privacy lead signs off this document. Requests routed through support reach that desk directly rather than bouncing between unrelated teams inside the brand.

Indonesia-Aware

Wording reflects how DANA, OVO, GoPay and QRIS settle in Indonesia and what record-keeping that creates. We don't copy a generic template that ignores the wallets you actually use.

No Hidden Sharing

If we add a new processor — analytics, KYC, payment — it appears in this policy before it goes live. You won't find a partner here that wasn't disclosed on the page first.

Consistency Across Our Policy Pages

Privacy Policy
This page. Covers what we collect, why we hold it, how long it stays, and the controls you have over your record while your account is open with us.
Cookie Notice
A sister page that drills into the specific cookies and local-storage keys our lobby sets, with the same retention logic and the same opt-out routes you see referenced here.
Terms of Service
Defines the agreement around using the lobby. Privacy sits alongside it — terms tell you the rules, this policy tells you the data side of those rules.
KYC Notice
Explains the verification step for wallet-linked withdrawals. The data points listed there match what this policy lists under identity, with no extra fields hiding in the KYC flow.
Payments Disclosure
Describes how DANA, OVO, GoPay and QRIS references attach to your account. The retention windows quoted there mirror the financial record-keeping window stated on this page.
Marketing Preferences
Documents the channels we may contact you on. Whatever you toggle there is honoured by the systems referenced in this privacy policy without a separate request.
Security Statement
Outlines the controls behind the storage we describe here. Same encryption posture, same access limits, written for a technical reader rather than a policy one.
SERVICE CONTEXT

What Shapes This Policy Page

Clear Section Headings Each block on this page answers one question — what...
Dated Revisions A revision date sits at the top of the policy...
Inline Definitions Terms like processor, retention and lawful basis are defined where...
Your Controls Surfaced Access, correction, export and deletion routes are pulled out of...
Scope Markers Each clause notes whether it applies to lobby browsing, account...
Linked Sister Pages Where a topic lives in more depth on the cookie...

Privacy Policy Questions

At sign-up we take the contact details you enter, a username and password hash, and the device signals your browser sends. Nothing else is requested until you choose to verify a wallet for withdrawals through DANA, OVO, GoPay or QRIS.

Active account records stay on file while the account is open. After closure, we hold financial and identity data for the retention window local law sets for gaming and payment records, then the record is removed from live systems.

Only with processors who help us run the service — payment partners for DANA, OVO, GoPay and QRIS, identity checks, infrastructure hosts. Each one sees the minimum needed for its task. We don't sell your data to advertisers or list brokers.

Yes. Email the privacy inbox from your registered address and we'll prepare an export of your account record. We confirm identity before sending it so the file only ever reaches the account holder it belongs to.

Account data sits on access-controlled infrastructure with encryption applied to credentials and wallet references. Internal access is scoped by role, and our security statement page describes the technical controls in more depth than this policy needs to.

We update the dated header and flag material changes on your next sign-in. Older versions stay archived so you can compare wording. Continued use of the lobby after a change indicates acceptance, where local law permits that approach.

Request deletion from account settings or through the privacy inbox. We close the account, remove marketing data immediately, and retain only the financial and identity records the retention window requires before those are removed too.