LEGAL REFERENCE

Privacy Built Around Your Account

99 2d keeps your privacy flow clear before you open an account: what we collect, why we need it, and how your choices stay visible while you explore...

Indonesia privacyAccount dataQRIS contextClear choices

See the Lobby Read FAQ

How This Privacy Policy Applies

This Privacy Policy explains how 99 2d handles personal data connected with your account, identity checks, login activity, lobby preferences, device signals, service messages and transaction references. It applies when you access 992d.net, contact us, open your account, or use supported account features in Indonesia where local law permits. We collect only the data needed to run the account flow, protect the

service, respond to your requests, and meet operational or legal duties. Payment names such as DANA, OVO, GoPay and QRIS may appear as context for transaction references, but this page is about privacy handling, not a promotion of any payment route.

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

PLAYER SUPPORT

Privacy Help And Contact Paths

If you need help with privacy matters, contact us through the route that matches your request. We keep the process direct so your account question reaches the right team without extra back...

Account privacy request Use this path when you want to ask about access, correction, deletion, or the data attached to your 99 2d account. Include your account name and a contact address we can use for verification.

Transaction reference question Choose this contact route when your privacy question involves a DANA, OVO, GoPay or QRIS reference shown in your account area. We check only the data needed to confirm the record.

Security concern Reach us quickly if you think your account data, login access, or device record has been exposed. We may ask for timing, device type and recent account activity to investigate safely.

PLATFORM TRUST SIGNALS

How We Keep Policy Review Clear

Our privacy wording is reviewed so it stays usable for you, not buried in legal clutter. We check the policy against live account flows, Indonesian service context and the data points you...

Account-flow review

We compare this policy with the steps you see when opening an account, signing in, checking the lobby, or asking for help. That keeps privacy wording aligned with real 99 2d screens.

Local context check

Because we serve Indonesia, we review references to DANA, OVO, GoPay and QRIS as account data context. We avoid implying payment handling beyond what the privacy policy needs to explain.

Plain-language editing

We write privacy points in direct English for Indonesia, with short sentences and clear reasons. You should not need a legal background to understand what data we collect and why.

Purpose mapping

Every data category in this policy is tied to an account purpose, such as access, safety, support, service records or legal duties. If a purpose changes, the policy review must address it.

Retention checks

We review how long account data is kept by looking at service needs, dispute handling, security records and legal requirements. When data is no longer needed, we aim to remove or reduce it.

Version discipline

When we update this Privacy Policy, we keep the page focused on what changed for your data. We avoid unrelated lobby claims so the policy remains a privacy document first.

SIDE BY SIDE

Consistency Across Our Policy Pages

Our legal pages should feel connected, but each one has its own job. This Privacy Policy stays focused on data handling while matching the same tone, structure and account-first wording elsewhere.

Privacy focus

This page explains personal data collection, use, sharing, retention and your choices. It does not replace account rules, promo terms, or lobby descriptions, even when those areas connect to privacy records.

Terms separation

Our terms page handles account conduct, service access and general obligations. This Privacy Policy only covers how data supports those flows, including identity, security, support and transaction reference handling.

Cookie alignment

Cookie wording should match this policy when it describes device signals, session tools and preference storage. We connect those points without turning the Privacy Policy into a technical tracking manual.

Promo record clarity

If you check the promo board, account records may show eligibility, viewing history or redemption status. This policy explains data use around that record, not the commercial terms behind it.

Support record match

Messages you send through support may include contact details, screenshots or account references. Our support wording and this Privacy Policy should match on why those records are kept.

Security wording

Security pages may describe account protection steps, while this page explains the data used for those steps. Keeping the split clear helps you understand both safety controls and privacy impact.

Local wording

Across our policy pages, Indonesia references should stay practical and accurate. When access depends on supported regions or local law, the same careful wording appears here and across related notices.

QUICK SIGNAL

Privacy Layout You Can Scan

We shape this page so privacy details are easy to find before you join. The layout highlights account data, choices, sharing rules and contact routes without pushing unrelated platform claims.

Clear opening summary The first section gives you the key privacy promise before the detail starts. You can see the account-first purpose, local Indonesia context and privacy scope without digging through long legal blocks.

Account data cues We call out the data types that matter most to your account, such as login details, profile records, device signals and support messages. Each cue connects to a clear service purpose.

Choice-focused wording Where choices are available, we explain them in practical terms: update details, contact support, manage preferences, or request access. The language is written so you know what action to take.

Sharing boundaries We describe when data may be shared with service providers, compliance partners or security tools. The layout keeps those boundaries visible so you can separate routine support from legal obligations.

Retention signals Retention points appear near the data they affect, not hidden at the end. You can see why account records may be kept and when we aim to reduce or remove them.

Contact placement Privacy contact routes are placed close to the policy details so you do not have to search. If you need account access help, correction, or deletion review, the next step is visible.

Privacy Questions Before You Join

We may collect account details, contact data, login records, device signals, support messages and transaction references. The exact data depends on what you choose to provide and which account features you use.

We use account data to create and manage your access, keep records accurate, respond to your requests, protect the service, review suspicious activity and meet duties that apply in supported regions.

Those names may appear in account records as transaction context when you use supported routes. We treat related references as personal data where they can be linked to your account.

Yes. Contact us through the privacy path and tell us what you want to access or correct. We may verify your account first so we do not disclose data to the wrong person.

We keep data for as long as needed for account service, security, dispute handling, legal duties and operational records. When data is no longer needed, we aim to delete, anonymise or reduce it.

We may share limited data with service providers, security partners, support tools, compliance reviewers or authorities when required. We share only what is needed for the purpose described in this Privacy Policy.

When we update this Privacy Policy, we revise the page so you can read the current approach. If a change needs your attention, we may use account messages or other contact routes.