Reference

Privacy Policy for sensasional77 Accounts

sensasional77 Privacy Policy explains how we handle the details you provide when you open an account, verify your phone, access Live Roulette Grand or use DANA and QRIS.

Clear data purposesWallet details handledPhone verification explainedCookie choices available
sensasional77 Privacy Policy for sensasional77 Accounts
ACCOUNT HELP ROUTE

Where To Ask About Privacy Policy

A direct support route helps when you want to understand a Privacy Policy entry rather than guess from a payment screen.

Account support Use the account support channel shown after login for Privacy Policy questions about your name, phone verification, login history or a correction request. Include the email or phone linked to your account, but never send your password or a complete wallet PIN. We use the account path to locate the relevant record.
Payment clarification If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, send the payment reference through the support route in your account. We can explain which payment detail we received and why it was needed, while the payment provider remains responsible for its own processing.
Privacy request For a copy, correction or removal request under the Privacy Policy, identify the account and describe the action you want us to take. We may verify ownership before responding. That step protects your records from a request made by someone using your device or an unrelated contact address.
DATA HANDLING DETAILS

What We Do With Your Account Data

Privacy depends on practical handling, so we describe the points you can check inside our account flow.

Account details

When you open an account, we use the details you submit to create access and connect your phone verification step. We do not need your wallet PIN for this process. Check your account record through support if your phone number or other submitted detail is no longer accurate.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference, amount and status record so we can match the account step. Bank transfer and virtual account records serve the same purpose. The payment provider handles its own data under its separate privacy terms.

Cookies and devices

Cookies and device signals can keep a session working, remember a selected setting and help us spot unusual access. On mobile, you can manage browser permissions through device settings; changing them may require another login or remove saved preferences from the account path.

Account security

Phone verification and login checks help us confirm that an account request comes from the person who controls the registered contact. Keep your password private and sign out on shared devices. If a login looks unfamiliar, contact account support and mention the time and device involved.

Retention choices

We keep account, support and payment records only for the period needed for access, reconciliation, dispute handling or a requirement that applies where local law permits. When a record no longer serves one of those purposes, our handling process moves it toward deletion or de-identification.

Your requests

You can ask what personal data we hold, request a correction, ask about deletion or raise a concern about cookie use. Send the request through the account support route with enough detail to identify the record. We verify ownership before making a change or releasing account data.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account steps Indonesian customers are most likely to question. We explain what happens around phone verification, local wallet references, mobile sessions and requests for access or correction. If your circumstances are different, contact us through the account support path and include the relevant transaction or login detail. Any access or eligibility point depends on local law and is handled where local law permits.

The sensasional77 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each type of data, how we protect account access and how you can ask for access, correction or deletion through the support route.

Phone verification helps us confirm control of the contact linked to your account before access or an account change. It also helps support locate the correct record when login stalls. We do not ask you to disclose a wallet PIN, and you should keep verification codes private.

Yes. The Privacy Policy covers payment references and status details we receive when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. The relevant provider may separately process your information under its own terms, which you should read alongside our policy.

Use the account support channel shown after login and state that you are making a Privacy Policy data request. Tell us whether you want access, a correction or deletion. We may verify account ownership before responding, and you should not include your password or wallet PIN.

Our Privacy Policy covers cookies and device signals used for session continuity, selected settings and security checks. You can change browser permissions through your phone settings. That choice may sign you out, remove saved preferences or require another verification step when you return.

We retain account, support and payment records only as long as needed for access, reconciliation, dispute handling or a requirement that applies where local law permits. The exact period can depend on the record type. Ask support which retention reason applies to a specific account detail.

Yes. Contact us through the account support path and describe the decision, the affected account step and any related receipt or login time. We may request ownership checks before discussing personal data. We will assess the request under the Privacy Policy and local rules that apply.