Reference

Dragon Tiger privacy at cogil69

Dragon Tiger, Rocket Crash, Super Bingo and QRIS wallet steps create account records, and this Privacy Policy explains how we collect, use and protect those records when you…

Account data rulesCookie choicesDANA OVO QRIS recordsPrivacy contact paths
cogil69 Dragon Tiger privacy at cogil69
CONTACT ROUTES

Reach us about privacy requests

A privacy request should not feel hidden behind the lobby. We keep clear contact paths for account data questions, cookie concerns and correction requests tied to…

Live chat Use the chat bubble after login for privacy questions tied to an active account.
Email request Send privacy requests through the contact form linked in your account menu.
Account menu Open Account > Privacy > Data request when you want to correct profile details…
ACCOUNT SAFETY

Account controls behind the lobby

Privacy is part of the account flow, not a separate promise on paper. We collect only the data needed to register you, keep sessions working, process wallet activity and keep the lobby…

Registration data

When you open an account, we collect the name, phone, email and login details needed to identify the profile. We use those records for access checks, support replies and account recovery only where the request matches ownership.

Device and session logs

We record device type, browser, IP region and login time to help detect unusual access. If you see a device you do not recognise, open Account > Security > Active sessions and close it there.

Payment references

DANA, OVO, GoPay and QRIS activity creates transaction references, timestamps and account matching records. We use these to confirm deposits, process withdrawals and answer payment privacy questions without exposing full wallet credentials in support chat.

Cookies and browser storage

Cookies keep your login session active, remember language choices and help us measure page errors. You can clear them in your browser settings, though you may need to log in again after clearing local storage.

Retention checks

We keep account and payment records only as long as needed for operations, dispute checks, security monitoring or legal duties. When a record no longer has a valid purpose, we remove it or reduce it.

Correction requests

If your phone, email or profile detail is wrong, contact us before using another account. We verify ownership, update the record where allowed, and tell you if a payment partner must also refresh its data.

Privacy questions before you join

These answers cover the privacy points we get asked about before and after account opening. Use them to understand what we collect, why we ask for it, how payment records are handled and how you can contact us. If your question involves your own account, we will verify ownership before discussing personal records.

We collect registration details such as name, phone, email, username and security credentials. We also create login, device and wallet records when you access the lobby or use DANA, OVO, GoPay or QRIS.

We use payment references to match deposits, process withdrawals, handle account questions and check unusual activity. The record normally includes a timestamp, amount, method and matching reference, not your full wallet login credentials.

You can contact us about deletion through Account > Privacy > Data request or the contact form. Some records may need to stay for security, dispute checks or legal duties before they can be removed.

Cookies help keep your session active, remember basic settings and measure page errors while you move through Slots, Dragon Tiger or other lobby areas. You can clear cookies in your browser, then log in again.

We share limited records only when needed for account operation, payment processing, fraud checks, hosting or support tools. We do not sell your personal data, and partner access is limited to the purpose involved.

Start from Account > Privacy > Data request, then choose the detail you want corrected. We verify ownership through your current login, registered contact path or a recent wallet reference before changing the record.

We may record the new device type, browser, IP region and login time. If the access looks unusual, we may ask for extra verification before allowing changes to privacy settings or payment records.