Reference

Open the tanjung4d Privacy Policy

The tanjung4d Privacy Policy explains what we collect when you create an account, sign in from a phone, browse VIP Baccarat or rocketslot, and use DANA, OVO, GoPay…

Account dataWallet referencesDevice accessPolicy requests
tanjung4d Open the tanjung4d Privacy Policy
CONTACT ROUTES

Check your Privacy Policy contact path

A clear contact route helps you ask about personal data without exposing account details in a public message.

Account data request Use the signed-in support path to ask which account details we hold or to…
Wallet reference check When a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction code…
Access correction route If your phone verification or device record needs correction, contact us from the account…
DATA PRACTICE

Explore the Privacy Policy safeguards

We handle privacy as an account operation, not as a separate page with vague promises. Our process connects collection, access, correction and deletion requests to the records created by your account journey.

Account data collected

We may collect your name, phone number, account identifier, sign-in history, device details and records needed to operate your profile. When you browse VIP Baccarat, top1totologin or Fish Hunter, activity records may help us keep sessions working and investigate account questions.

Cookie activity

Cookies and related browser signals can keep a signed-in session connected, remember selected page settings and help us identify repeated access from one device. You can adjust browser cookie controls, although turning them off may affect account access and policy request handling.

Account security

Phone verification is an account step before access, and device signals can be checked when a login looks unusual. Never send a wallet password through support. For DANA, OVO, GoPay or QRIS questions, share only the payment reference requested for matching.

Retention periods

We keep personal and transaction records for the operational, security or legal period connected to their purpose. A completed account action does not always remove a record immediately, because payment references or access logs may still be needed for a documented request.

Correction requests

You can ask us to correct inaccurate account data through the signed-in contact route. State the field that is wrong and the replacement value, then complete any ownership check we request. We record the request so the correction can be traced to your account.

Policy questions

For questions about how the Privacy Policy applies to a phone, browser, wallet reference or lobby session, contact account support with a precise example. We answer from the relevant record and may explain why a data field is required for access.

Ask about tanjung4d Privacy Policy

These Privacy Policy answers address the account and device questions we expect from Indonesian customers before they open an account. They cover collection, wallet references, cookies, access requests and correction steps. Where a request requires identity confirmation, we explain that step through the private account contact route rather than asking you to post personal details in an open channel.

The tanjung4d Privacy Policy covers personal data collected during account creation, phone verification, sign-in, lobby access and payment matching. It explains device signals, cookies, retention, correction requests and contact routes. Access to the service depends on local law, including for Indonesian account holders.

We use your phone number to create and identify the account, complete phone verification and help protect sign-in access. It can also help us locate a support request. We do not need your DANA, OVO, GoPay or QRIS wallet password for account assistance.

Yes. The Privacy Policy covers payment references received when you use DANA, OVO, GoPay or QRIS, along with bank transfer and virtual account references. We use those codes to match an account action or investigate status, without requesting full wallet credentials.

You can request a correction through the signed-in account support path. Name the field that needs changing and provide the accurate value. We may ask you to complete phone or account verification before making the update, so an unknown person cannot alter your profile.

Cookies may keep your session connected, retain page preferences and help us recognise repeated browser access. You can change cookie settings in your browser. If essential cookies are blocked, sign-in, phone verification or a Privacy Policy request may not work as expected.

We retain personal, access and transaction records for the operational, security or legal period connected to their purpose. The exact period can differ by record type. You can ask support about a specific record, and we will explain the applicable retention reason.

Sign in, open the account support route and describe your Privacy Policy question with your account identifier or linked phone number. For a wallet issue, add the relevant payment reference only. We may confirm ownership before sharing, correcting or discussing personal data.