Reference

Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between Lightning Roulette, Aviator and Basketball Betting.

DANA data scopeOVO wallet checksGoPay and QRIS recordsCookie choices
dreamply77 Privacy Policy for Your Account Data
CONTACT ROUTES

Privacy Contacts for Account Data Requests

Fast privacy support matters when your account, wallet, or device record needs attention. We handle privacy messages through live chat, email, and WhatsApp so you can choose the channel that matches the…

Live chat privacy desk Use live chat from 09:00 to 01:00 WIB for quick privacy questions, cookie concerns, or account data checks. Start from the help icon, then choose Privacy Request so your message reaches the right queue.
Email for data records Send deeper requests to [email protected] with your account email, requested change, and payment rail used recently. We answer with the steps needed for access, correction, deletion, or export checks.
WhatsApp identity check WhatsApp support can help confirm whether a privacy request is yours before we act. We may ask for a masked phone number, recent QRIS reference, and device type, not your password.
ACCOUNT CARE

Data Care Across Lightning Roulette Sessions

Privacy work is part of our account flow, not an afterthought. We separate account data, wallet records, cookie choices, and support messages so each request can be checked without exposing unrelated details.

Registration data

When you create an account, we collect details needed to identify your profile, protect login access, and contact you about privacy requests. We do not ask for your DANA, OVO, GoPay, or QRIS PIN.

Wallet records

DANA, OVO, GoPay and QRIS activity creates transaction references, timestamps, amount fields, and account matching checks. We use those records to verify wallet actions, handle disputes, and respond to data access requests.

Cookie controls

Cookies help remember session status, language choice, and device checks. On mobile browser, open Account > Privacy > Cookie Choices to adjust non-essential cookies without closing your current account session.

Device security logs

We record device type, browser, IP signal, login time, and session status to detect unusual access. You can check Account > Security > Active Sessions and ask support to close a device you do not recognize.

Retention periods

Account and wallet records are kept only as long as needed for payment checks, legal duties, dispute handling, and security analysis. When retention ends, we delete or anonymise records where our systems allow it.

Correction requests

If your name, phone number, or email is wrong, contact us before your next wallet action. We confirm ownership first, then update records so future DANA, OVO, GoPay, or QRIS checks match.

Privacy Policy Questions Before You Join

Your privacy questions usually start before you open an account, especially if you plan to use a local wallet or log in from more than one device. The answers below explain what we collect, why we keep it, how to contact us, and what you can request under this Privacy Policy.

We collect registration details, login records, device signals, and contact data needed to run your account. If you use DANA, OVO, GoPay, or QRIS, we also store transaction references linked to that wallet activity.

Yes. The policy covers the payment records we receive or create when you use those rails, including timestamps, reference codes, matching status, and support messages. We do not collect your wallet PIN or app password.

You can request correction, deletion, or access by live chat or email. We verify account ownership first, then explain what can be changed, what must be kept for records, and what depends on local law.

Cookies help keep your session active, remember language choice, and support security checks. On mobile browser, go to Account > Privacy > Cookie Choices to adjust optional cookies while required session cookies remain active.

Only assigned support, risk, and account teams can access identity check records for work that requires it. We limit access by role, keep internal logs, and avoid sharing personal data inside unrelated support conversations.

We keep game session and wallet records for payment checks, account safety, dispute handling, and legal duties. After the needed period ends, records are deleted or anonymised where the system and applicable rules allow.

Access signals may show a different region, so extra checks can apply. Eligibility depends on local law and is available only where local law permits, which means some account actions may be restricted.