Reference

Privacy Policy for Your Indonesia Account

data sdy 6d Privacy Policy explains what we collect when you open an account, verify your phone, sign in from mobile or desktop, and use DANA, OVO, GoPay…

Account clarityWallet recordsCookie choicesAccess requests
data sdy 6d Privacy Policy for Your Indonesia Account
HELP WITH PRIVACY

Three Ways to Ask About Your Data

A clear support path matters when a login, wallet status or privacy request stalls. Use the account support route shown beside your signed-in account area and include the phone number linked to your profile, but never send a password or full payment credential. We use the details you provide to locate the correct record, check a receipt or explain a policy request. Requests are handled where local law permits and may require an account check before any data is disclosed.

Team online

Account access

If your phone verification does not match the account, tell us the affected login path and device type. We can check the account record without asking you to reveal a password, then explain which privacy step is needed before access can continue.

Wallet record

For a DANA, OVO, GoPay or QRIS receipt question, provide the account reference and transaction date shown in your history. We compare that reference with the wallet status and limit the response to details connected with your own account.

Privacy request

To ask for a copy, correction or eligible removal of personal data, state the request clearly through our account support path. We may confirm your phone verification first, because releasing account details without that check could expose your profile.

DATA HANDLING

Six Controls Behind This Privacy Policy

We keep this Privacy Policy practical by linking each data use to an account action.

Account details

When you create an account, we collect the contact details needed for access and phone verification. The same account record connects your casino and wallet activity, so a request about No Commission Baccarat or a wallet receipt can be checked against the correct profile.

Device signals

Our mobile browser path may record device type, browser version, session time and approximate connection data. These signals help us identify a sign-in that differs from your usual pattern; they are not a request for photos, contact lists or unrelated files on your device.

Cookies

Cookies can keep your session open, remember basic settings and measure which policy page was reached from an account link. You can clear or restrict cookies in your browser, although doing so may require another login or affect the way account pages load.

Payment records

We retain transaction references, status changes and verification results for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use these records to reconcile an account history and do not need your wallet PIN or banking password to check a receipt.

Account security

Phone verification is part of the account access check, while session and device signals help us investigate unusual sign-ins. If a withdrawal requires verification, we compare the request with the account record and payment reference before discussing its status with you.

Retention requests

We keep records only as long as needed for the stated account, security, payment or legal purpose, subject to local requirements. You can ask why a record remains, request a correction, or seek eligible removal; access depends on local law and identity checks.

Privacy Policy Answers for Account Holders

These Privacy Policy answers focus on the searches we hear around data sdy 6d: what is collected, why a phone check is needed, how wallet records are handled, and how you can request a change. Keep your account reference available when contacting us, and remember that requests are assessed where local law permits.

The data sdy 6d Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references and support requests. It explains why each category is used, how records are protected, when they may be retained, and how you can request access or correction.

Phone verification connects you to the correct account before we disclose account or wallet details. It also helps protect a mobile login from an unfamiliar device. We do not ask for your password, wallet PIN or banking password as part of this check.

Yes. Our Privacy Policy covers transaction references and status records linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those details to reconcile your account history, check a receipt and answer a wallet-status request.

When you sign in through a mobile browser or desktop browser, we may collect device type, browser version, session time and approximate connection data. These signals support account security and unusual-login checks; they do not give us access to unrelated files on your device.

Use the account support path and describe whether you want a copy, correction or eligible removal. Include your account reference and the phone number connected to your profile. We may complete a phone verification check before sharing or changing personal data.

We retain account, security and payment records for the period needed for their stated purpose and any applicable local requirement. You can ask why a record remains and request eligible removal. The result depends on local law and may require identity confirmation.

Yes. You can read this Privacy Policy before completing the account path, including the phone verification step. If you need clarification about cookies, wallet references or access requests, use the support route shown on our brand home before submitting personal details.