Reference

dreamply77 Privacy Policy for Your Account

The dreamply77 Privacy Policy explains how we handle the account, device and wallet data connected with Live Dealer Lobby, Rocket Crash and other lobby areas.

Account dataWallet recordsPrivacy requestsDevice controls
dreamply77 dreamply77 Privacy Policy for Your Account
PRIVACY CONTACTS

Get Privacy Help Near Wallet Status

A clear contact path matters when your account data or payment record needs attention.

Account data request Ask us to confirm the account details linked to your phone verification.
Wallet record check For DANA, OVO, GoPay or QRIS questions, mention the transaction reference and approximate date.
Access correction If a login, device detail or account contact appears incorrect, tell us which field…
DATA HANDLING

How We Handle Your Account Data

Privacy controls work best when they match the way you actually use an account. We separate account access, wallet records and device signals, then use each only for the stated operational purpose.

Account details

We handle details such as your phone number, account identifier and verification status to create, maintain and protect access. We do not need your password in a privacy request, so keep it out of every message.

Wallet references

A DANA, OVO, GoPay or QRIS receipt can contain a reference, amount and status needed to match an account event. We use that payment context for checks rather than requesting unrelated wallet contents.

Cookies and devices

Cookies and device signals help remember a session, detect unusual login behaviour and keep the mobile path consistent. Clearing browser data can remove saved session details and may require phone verification again.

Account security

Phone verification is an account safeguard before access or selected changes. We may compare login and device events when a request involves account recovery, wallet status or an unfamiliar browser.

Retention periods

We retain account, security and payment references only for the period needed for the stated purpose, account records and applicable legal duties. When a period ends, records are removed or handled in a restricted form.

Changes and contact

To request a correction, copy or deletion of eligible data, use the account support contact and identify the affected record. We verify ownership first, then explain any limits required by local law.

Privacy Policy Questions for Indonesia Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. They cover the data tied to login, phone verification, cookies and local payment records, with access handled where local law permits.

It covers account details, phone verification, login and device events, cookies, wallet references and support requests connected with your use of the service. Payment examples include DANA, OVO, GoPay and QRIS.

We use phone verification to confirm account ownership before access or selected account changes. It can also help us examine an unfamiliar device or a wallet-status question without requesting your password.

Yes. The policy covers payment references, status and related account records for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity needed for a payment check.

You can ask through the account support contact for a copy of eligible data linked to your account. Include your account identifier, complete phone verification if requested and avoid sending passwords.

Cookies can retain a session and support device checks when you move from login to the lobby on a mobile browser. Clearing them may sign you out and prompt phone verification again.

Send a correction or deletion request through the account support contact, naming the affected record. We verify ownership and explain any retention needed for account security, payment records or local law.

Yes. Privacy requests, account access and any available deletion may depend on local law. We apply the stated request path for Indonesian access where local law permits and explain restrictions clearly.