LEGAL REFERENCE

Privacy built for Indonesia accounts

43 2d brings live tables, slot rooms and sportsbook markets into one account flow, and this Privacy Policy explains how we handle your data while you open, browse...

Indonesia privacyAccount dataLobby privacyQRIS context
Tour the Lobby Read FAQ
43 2d Privacy built for Indonesia accounts

How this policy applies

This Privacy Policy describes how 43 2d collects, uses, stores and shares data connected with your account, site access, device activity, support requests and payment references. It applies when you use 432d.app, open an account, contact us, adjust account settings or interact with lobby features where local law permits. We may process contact details, login records, device signals, transaction references and conversation

history so we can operate the account flow, reduce misuse, respond to your requests and meet duties that apply in supported regions. We do not sell your personal data. When DANA, OVO, GoPay or QRIS appear in the account area, related privacy handling may include reference IDs, timestamps and status updates needed to confirm the action.

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

24/7 SUPPORT

Contact paths for privacy requests

If you want to ask about your data, correct account details or raise a privacy concern, contact us through the channel that fits your case. We respond using the same direct tone...

Privacy mailbox Email us with the account name, contact detail and the privacy request you want handled. We use that message to verify the request, route it internally and reply with the next practical step.
Account support chat Use chat when your privacy question is tied to a live account session. We can confirm basic identity points, check recent account events and explain which data is needed for follow-up.
Escalation request Ask for escalation when a privacy matter needs a deeper check, such as access logs, correction history or payment reference records. We keep the request focused on data handling, not promo or lobby questions.
PLATFORM TRUST SIGNALS

Policy checks we keep visible

Our privacy wording is written for you, not hidden behind legal fog. We keep the policy aligned with the account journey, from first page load through lobby access, payment references, support contact...

Plain-language drafting

We write privacy terms in direct English for Indonesia, so you can see what data is collected, why it is used and how to contact us without decoding formal legal phrasing.

Account-flow alignment

The policy follows the same path you take on 43 2d: open an account, verify details, enter the lobby, use support and manage references tied to account activity.

Regional wording

Where access depends on local rules, we use supported-regions wording and avoid promises that do not fit every location. That keeps the privacy posture realistic for Indonesia-facing account flows.

Payment reference clarity

We separate wallet or QRIS references from broader personal data. That helps you understand why DANA, OVO, GoPay or QRIS status details may appear in account records.

Limited sharing stance

We share data only when needed for service operation, security checks, payment reference handling, support work or legal duties. We do not sell your personal data to outside marketers.

Update discipline

When policy language changes, we aim to keep the reason visible and the wording practical. You should be able to read the updated section and understand what changed.

Consistent privacy across our pages

This page sits beside other 43 2d policy pages, but it has one job: explain privacy handling. We keep its structure consistent so you can move between account...

Privacy PolicyThis page explains data collection, use, storage, sharing and your request paths. It is the main place to understand how personal data moves through your 43 2d account flow.
Terms pageAccount terms explain access rules and service use. When those terms mention account records, this Privacy Policy explains how related data is handled and protected.
Promo termsPromo terms may mention eligibility checks or account status. This Privacy Policy explains the data side, including why certain account details may be used to confirm eligibility.
Cookie wordingCookie wording focuses on browser storage and site signals. This Privacy Policy connects those signals to wider account handling, security checks and preference management.
Support scriptsSupport responses should match this policy when privacy questions appear. If you ask about access, correction or deletion, our answer should point back to these privacy routes.
Payment referencesWallet and QRIS pages may show status labels or reference IDs. This Privacy Policy explains why those records exist and how they relate to account safety and service checks.
Account closureClosure wording explains how you can ask to end account access. This Privacy Policy explains what data may be kept, removed or retained for required operational reasons.
SERVICE CONTEXT

Privacy cues on every account page

We design privacy cues to stay close to the actions that create data. That means consent prompts, account fields, security labels and support links appear where you need them, not buried away from the...

01
Clear consent prompts When a step needs consent or confirmation, we aim to show it near the action. You should not have to search through unrelated lobby content to understand that privacy choice.
02
Short field labels Account fields use practical labels, so you can tell why we ask for a contact detail or verification point. Clear labels reduce mistakes and help support handle corrections faster.
03
Session security cues Login and session areas display security wording tied to privacy handling. These cues help you understand that device signals and access records support account protection and misuse checks.
04
Wallet context chips DANA, OVO, GoPay and QRIS labels may appear as context chips beside account actions. Their purpose is to show the reference path, not to expose unnecessary personal data.
05
Request access points Privacy request links stay close to account and support areas. If you want data access, correction or deletion help, you can reach the right path without browsing unrelated pages.
06
Change visibility When policy wording changes, we aim to make the page date and updated section easy to spot. That helps you decide whether the change affects your account choices.

Privacy questions before you join

We may collect contact details, account identifiers, login records, device signals, support messages and payment reference data. We use these details to operate your account, protect access, respond to requests and meet duties in supported regions.

Device and login data helps us recognise account access patterns, reduce misuse and keep sessions stable. We use it for privacy and security purposes, not to sell your personal data to outside marketers.

When those options appear, we may store reference IDs, timestamps, status labels and related account links. These records help match your account action with the wallet or QRIS flow and answer privacy-related support questions.

Yes. Contact us with the detail you believe is wrong and the account reference we can verify. We will check the request, confirm what can be changed and explain any records that must remain unchanged.

You can request deletion through our privacy contact path. We will assess the account, remove data where allowed and explain if certain records must be kept for security, dispute handling or legal duties.

We share data only when needed for service operation, support, security checks, payment reference handling or duties that apply where local law permits. We do not sell your personal data to outside marketers.

We aim to keep updates visible on this page through clear wording and date cues. If a change affects how your account data is handled, we will present it in practical language you can act on.