LEGAL REFERENCE

Privacy built into your account

bitung 4d keeps privacy close to the account journey: clear data use, visible consent points, and support paths before you enter the lobby. Open your account in seconds...

Data clarityConsent choicesAccount securityIndonesia support

See the Lobby Read FAQ

Our privacy posture for Indonesia

This Privacy Policy explains how we collect, use, store, share, and protect data connected with your bitung 4d account. It applies when you browse our brand home, open an account, enter the lobby, speak with support, receive service messages, or use account features tied to identity, security, and transaction checks. We use your data to keep access accurate, reduce fraud, maintain records,

and meet duties that apply in supported regions. Where local law permits, we may verify account details and transaction references linked to DANA, OVO, GoPay, and QRIS activity so your account flow stays consistent. We do not sell your personal data. We share limited records only with service partners, compliance advisers, technical vendors, or authorities when a lawful request requires it.

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

PLAYER SUPPORT

Privacy contact paths

When you need help with privacy, we keep the route simple and account-focused. Tell us what you want to access, correct, restrict...

TRUST MARKERS

Policy care signals

We write this policy for the way your bitung 4d account actually works, not as a loose legal template. Each privacy statement is checked against account signup, login, support, transaction references, and...

Named policy owner

Our privacy wording has an internal owner who tracks changes across account forms, cookies, support scripts, and security tools. That keeps the policy aligned with the data points you actually provide.

Change tracking

When we update privacy wording, we keep an internal change record covering what shifted and why. This helps us answer your questions without guessing from old account flow language.

Vendor checks

Before a service partner handles account records, we look at the purpose, access level, retention need, and security controls. Partners receive only what they need for the agreed service.

Support training

Our support team is trained to handle privacy requests with identity checks before discussing account records. This protects you from casual disclosure while keeping genuine requests moving.

Retention discipline

We keep account records only for active service, dispute handling, fraud prevention, compliance duties, or legal needs. When a record is no longer needed, we remove or de-identify it.

Security alignment

Privacy and security decisions are handled together, especially around login alerts, device signals, and wallet references. This helps us protect your account without collecting unrelated personal data.

Consistency across legal pages

Your privacy rights should not change because you opened another legal page on bitung 4d. We keep this Privacy Policy consistent with our terms, cookie notice, and account...

Terms alignment

Our terms explain account use, while this policy explains data handling. Where both pages mention verification, the privacy wording focuses on records collected and why they may be needed.

Cookie notice fit

The cookie notice covers browser storage and preference tools. This policy connects those settings to account privacy, service security, and how you can adjust optional tracking choices.

Account rules link

Account rules may describe identity checks and prohibited account sharing. This policy explains the related personal data, retention reasons, and safeguards used when those checks take place.

Promotion consent split

Promo terms explain campaign conditions, while this policy explains how we contact you about offers. You can ask us to change optional contact choices without closing your account.

Support script match

Support responses use the same privacy meanings as this page, including access, correction, restriction, and deletion requests. That keeps your request language consistent from page to inbox.

Regional wording

Access references use supported regions and where local law permits. We avoid broad promises because privacy rights, retention duties, and disclosure rules may vary by location.

Update cadence

When another legal page changes in a way that affects personal data, we check this policy too. That prevents account wording from drifting away from actual privacy practice.

Policy layout you can read fast

This page is designed so you can scan the privacy points that matter before opening your account. We use short sections, plain labels, and account-based examples...

Plain section labels

Every block uses a direct label so you can move from collection, use, sharing, retention, and rights without hunting through legal phrasing that hides the account impact.

Account examples

We connect privacy terms to familiar account actions, such as login, profile updates, support chat, device checks, and wallet references. That makes the policy easier to apply.

Rights placement

Your access, correction, deletion, and contact choices are placed near the support route, so you can move from reading the policy to sending a request quickly.

Short retention cues

Retention wording explains why certain records may stay active for service, disputes, fraud checks, or legal duties. We avoid vague storage language wherever a clearer reason fits.

Consent visibility

Optional contact and cookie choices are called out separately from account records needed for service. That helps you understand which choices are required and which can be adjusted.

Local context chips

DANA, OVO, GoPay, and QRIS appear as context chips because wallet references can relate to account verification. The chips are not a replacement for privacy wording.

Privacy questions before you join

We collect account details you provide, login records, device signals, support messages, and transaction references connected with your account. We use these records to operate access, security, service support, and lawful checks.

Wallet references may help us match account activity, resolve service questions, and check unusual patterns. We handle DANA, OVO, GoPay, and QRIS references as account data, not as public profile content.

Yes. Contact our privacy path with the account contact you used at bitung 4d. We may verify your identity first, then explain what records we hold and what limits may apply.

Send us the incorrect detail, the correction you want, and proof if needed. We will update eligible records or explain why a record must stay unchanged for security or compliance reasons.

We share limited data only when a partner helps operate security, support, hosting, analytics, verification, or required legal processes. Partners receive data for the service purpose, not for unrelated use.

Retention depends on the record type and purpose. We keep data while your account is active, while disputes or checks continue, or while legal duties require storage in supported regions.

Yes. You can ask us to adjust optional messages linked to promotions or account updates. Some service notices may still be sent when they are needed for security or account operation.