Reference

lion777 Privacy Policy For Your Account

Our Privacy Policy explains how lion777 handles the details connected with your account, including phone verification, DANA and QRIS payment records, device access and support requests.

Account dataCookie choicesPayment recordsAccess requests
lion777.best page image
PRIVACY SUPPORT

Check Privacy Help Through Your Account

A clear support path helps when you want to ask what data we hold or why a payment record appears in your account.

Account data request Ask us to identify the account data connected with your verified phone number.
Wallet record question For DANA, OVO, GoPay or QRIS questions, share the transaction date and displayed status…
Policy correction path If a profile detail appears wrong, contact support from the signed-in account and describe…
DATA HANDLING

Browse How Cookies And Data Work

We treat privacy requests as account operations rather than a generic message. Our process connects the request to your sign-in details, checks the relevant record, and explains what can be changed, retained…

Data we receive

We may receive your phone number, verification details, sign-in events, device signals, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Cookie controls

Cookies can support sign-in continuity, security checks and page preferences. You can adjust browser cookie settings, though refusing some cookies may affect account access or require another verification step.

Account security

We use sign-in checks, phone verification and device signals to reduce account misuse. Keep your password and one-time codes private, and contact us promptly if an unfamiliar session appears.

Payment references

We keep transaction references needed to match wallet, QRIS, bank transfer or virtual account activity with your account. We do not need your wallet PIN to investigate a receipt or status.

Retention approach

We retain records for account support, security, payment reconciliation and legal duties for the period needed for those purposes. A request can ask us to explain the applicable retention reason.

Change or access request

Use the support path inside your account to request access, correction or removal where local law permits. Include the affected data type so we can route the request accurately.

Ask About Privacy Policy And Payments

These questions cover the points you are most likely to check before opening an account or sending a privacy request. Each answer relates to our Privacy Policy, account records and the local payment references shown in your account area.

It covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Our Privacy Policy explains that payment references may be used to match a DANA or QRIS transaction with the correct account, investigate a status question and support payment reconciliation.

Yes, send an access request through the signed-in account support path. We may verify your phone number or another account detail before explaining which records can be provided.

Contact us from your account and identify the detail that needs correction. We will explain the verification step and whether the requested change is available where local law permits.

Cookies can help maintain sign-in continuity, remember page preferences and support security checks. Browser controls let you adjust them, but some account steps may work differently afterward.

We keep data for account support, security, payment reconciliation and legal duties for the period needed for those purposes. You can ask support to explain the reason for a specific record.

Yes. Access or eligibility depends on local law. Our Privacy Policy explains data handling, but it does not override local requirements or determine whether account access is available in your area.