Reference

laju22 Privacy Policy for Your Account

Our laju22 Privacy Policy shows what we collect when you open an account, sign in, browse Live Baccarat Gold or check wallet status through DANA and QRIS.

Account data explainedWallet records coveredCookie choices includedPrivacy requests welcomed
laju22 laju22 Privacy Policy for Your Account
REQUEST HELP

Contact Paths for Privacy Requests

A clear contact route matters when a privacy request affects your account or wallet history.

Account support path Use the support route inside your signed-in account for a privacy request.
Cashier-linked contact If your request concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, use…
Access troubleshooting When a privacy page or account request does not load on mobile, tell us…
DATA HANDLING

How Cookies and Account Security Work

Our privacy process follows the same account path you use from phone verification to the lobby.

Account data

We use your submitted account details to create and maintain your profile, complete phone verification and respond to privacy requests.

Cookie controls

Essential cookies help keep your session active while you move from login to a privacy request.

Sign-in protection

We use phone verification, session checks and device-related signals to reduce unauthorised account access.

Payment references

A QRIS receipt, bank transfer record or virtual account reference helps us reconcile activity without storing your private wallet password.

Retention choices

We keep personal records only for as long as needed for account operation, payment reconciliation, fraud prevention, dispute handling and…

Changes and requests

You can ask to access, correct or delete eligible personal data through the signed-in support path.

Privacy Policy Questions for Indonesia Access

These Privacy Policy answers cover the practical questions we expect before you open an account or ask us to change existing records. We focus on the data connected with login, mobile browsing, local wallet references and support requests. If your question involves eligibility, remember that access depends on local law; our contact path can explain the account process without asking for unnecessary private details.

The laju22 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains access, correction, deletion and security requests for eligible records.

We use the phone number attached to your account for verification, sign-in protection and request matching. If you ask us to change or disclose personal data, confirming that number helps prevent another person from receiving details about your account or wallet activity.

Yes. The Privacy Policy includes cookies, session records and device signals created when you browse on a phone or desktop. These details help keep your login active and diagnose a page issue, including a problem moving from the lobby to a privacy request.

We may retain transaction references, receipt details and status records needed to match DANA or QRIS activity with your account. We do not ask for or need your wallet PIN. Bank transfer and virtual account references can be handled in the same account-support process.

Open the signed-in account support path and state whether you want access, correction or deletion of a specific record. Include your account contact and a clear description. We may complete phone verification first, then explain any record that must remain for payment or legal reasons.

You can submit a deletion request through account support. We assess each record separately because some details may be needed for payment reconciliation, security, disputes or legal duties. Where local law permits, we remove eligible data after the required checks are complete.

Use the privacy contact path inside your account, or the support route beside the cashier when your question concerns a wallet receipt. Describe the issue without sharing a password or PIN. If you cannot sign in, provide the affected contact and device path so we can locate the request safely.