Reference

Privacy Policy For Your Account

situs 4d Privacy Policy explains what we collect when you create an account, complete phone verification, sign in on mobile, or connect DANA and QRIS.

ACCOUNT DATACOOKIE CHOICESWALLET RECORDSCONTACT RIGHTS
Browse Our Lobby Read FAQ
situs 4d Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Account Access

A clear contact path matters when you want to understand a Privacy Policy entry or correct an account record. We ask you to contact us from the signed-in account where possible, because that lets us compare your request with the phone verification already attached to your profile. If you cannot sign in, use the public contact route and provide only the minimum details needed to locate the issue. Our policy questions stay separate from requests about Live Baccarat Table or wallet status.

Team online

Account Contact

Use the contact route in your account settings to ask about stored details, cookie choices, retention, or a correction. We may request a matching account step before changing data, so another person cannot alter your profile using only a displayed name.

Sign-In Assistance

If phone verification or sign-in blocks your request, contact us through the public support route and mention the device path you used, such as mobile browser or desktop browser. Do not send a password, wallet PIN, or full payment credential.

Wallet Records

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record, include the date, amount reference, and visible status only. We use those details to locate the record while avoiding unnecessary wallet credentials in a privacy request.

DATA PRACTICES

How We Apply This Privacy Policy

We apply this Privacy Policy through practical account controls rather than vague promises. Phone verification helps us connect a request to the right profile, device signals help us examine unusual sign-in activity…

Data We Receive

We may receive your account name, contact detail, phone verification result, sign-in time, device or browser signal, support message, and payment reference. We use these categories to operate account access, identify a request, check security, and respond to a wallet record question.

Cookies And Storage

Cookies or browser storage can keep a sign-in path consistent, remember a stated preference, and support security checks between pages. You can manage browser controls on your device; some account functions may require a necessary session cookie to remain available.

Account Security

We use phone verification, sign-in records, and device signals to help detect activity that does not match your account pattern. We do not ask you to place a password, wallet PIN, or full card credential inside a support message.

Retention Periods

We keep each data category only for the period needed for its stated purpose, account security, dispute handling, or a legal record where local law permits. You can ask us which category applies and why a particular record remains stored.

Corrections And Access

You may ask for a copy of account data linked to your profile or request a correction when a detail is inaccurate. Send the request from your signed-in account when possible; we may verify the phone attached to that account before responding.

Sharing Requests

We may use service partners to process technical, security, support, or payment-reference tasks, but a request remains tied to the purpose described here. Ask us which category was shared, the reason, and the contact route for follow-up.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions you may search before opening an account or connecting a local wallet. We keep the wording practical: what we collect, why phone verification matters, how cookies behave on mobile, and how to contact us about a record. The same terms apply when you browse from Indonesia where local law permits.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references. It also explains why we use each category, how retention works, and how you can request access or correction through the account contact route.

Phone verification helps us connect account access and privacy requests to the correct profile. If you ask us to change a stored detail, we may compare the request with that verification step. This reduces the chance of another person changing your account record.

Yes. It covers the transaction status, receipt reference, and account connection needed to identify a DANA or QRIS payment. We do not need your wallet password or PIN for that purpose. The same approach applies to OVO, GoPay, bank transfer, and virtual account references.

The policy describes necessary session cookies and browser storage used for sign-in continuity, security checks, and stated preferences. You can manage browser settings on your phone or desktop. Turning off a necessary session cookie may interrupt account access or require you to sign in again.

Use the contact route in your signed-in account and ask for the data linked to your profile. Include a clear request, not a password or wallet PIN. We may check the phone verification attached to the account before releasing or discussing personal records.

Yes. Send a correction request through account contact, identify the detail that is inaccurate, and provide the replacement wording where appropriate. We may verify your account step first. If the detail is tied to a payment reference, we may retain the original record for its stated purpose.

Start from account settings when you can sign in. If access is unavailable, use the public support route and share only the minimum details needed to locate your profile or request. Eligibility and account access depend on local law, and we will explain the next contact step.

Related Pages

situs 4d Indonesia LinkAja Min Deposit About Us Access guide Account information