Reference

Open the dg77 Privacy Policy

The dg77 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse Live Baccarat Prestige or use DANA, OVO, GoPay…

Account dataWallet statusCookie choicesSupport requests
dg77 Open the dg77 Privacy Policy
CONTACT ROUTES

Ask about Privacy Policy access

A direct question about the Privacy Policy should include the account detail or data purpose you are asking about, without sending a wallet PIN or password. We route account, cookie and payment-record questions through the support contact shown inside your signed-in account, so the request can be matched to the right profile. If login or wallet status stalls, start with the account help path beside the cashier area and mention the relevant DANA, OVO, GoPay, QRIS or bank transfer reference.

Team online

Account message

Use the support contact displayed after sign-in to ask which account details we hold, why they are used, or how a Privacy Policy request is progressing. We may ask for an account identifier, but never ask you to share a password, PIN or full wallet secret.

Cashier context

For a payment-record question, include the date, amount shown in your account and the rail used, such as QRIS, DANA or bank transfer. This gives our support team a practical reference without requiring you to expose complete card, wallet or banking credentials.

Access help

If you cannot reach the account contact because login is stalled, use the visible support route on the access page and describe the device path you took. We use that detail to separate a privacy request from a sign-in or wallet-status issue.

DATA PRACTICE

Protect your dg77 account data

Privacy at dg77 is handled through practical controls rather than broad promises. We separate account access, payment matching and support handling, then keep the Privacy Policy available so you can check the…

Account creation

When you open an account, we collect the details needed to create and protect that profile. Clear phone verification comes before account access, helping us connect the correct person to the sign-in event without treating a device alone as proof of identity.

Device signals

A mobile browser can send technical signals such as device type, browser details and access time. We use these signals to maintain a working account session and spot unusual sign-in patterns; they do not replace the account step or phone verification.

Payment records

A DANA, OVO, GoPay or QRIS status can create a transaction reference linked to your account. Bank transfer, virtual account and Bank BCA Deposit records may also be retained to reconcile a cashier event, answer disputes and show the correct status.

Cookies

Cookies can keep a session active, remember a language or region choice and help us understand which account page failed to load. You can manage cookie settings through your browser, although restricting essential cookies may interrupt sign-in or Privacy Policy access.

Retention

We retain account, security and transaction records only for the period needed for the stated purpose, account support and applicable legal requirements. When a record is no longer needed, our handling process removes it or separates it from direct account identification.

Change requests

You can ask us to correct account details, explain a data purpose or address a deletion request through the signed-in support contact. Include the specific record and account identifier; we verify the request before making a change, where local law permits.

Search Privacy Policy answers

These Privacy Policy answers focus on the searches we hear before an account is opened or a wallet is connected. We keep the wording practical: what we collect, how a request is checked, what happens on a mobile device and where Indonesian payment references appear. If your case is different, use the account support route described above.

The dg77 Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support requests. It explains why we use each category, how access is controlled and how you can ask about correction, deletion or a data-purpose question where local law permits.

We may store a payment reference, status and account link for DANA, OVO, GoPay or QRIS transactions. We use those records to match a cashier event and answer a status question. Do not send us your wallet PIN, password or complete secret credential.

Phone verification helps connect a Privacy Policy request to the correct account before we discuss personal records. If you ask about a profile, cookie setting or payment reference, we may request an account identifier and another check rather than relying on an unverified message.

When you use a mobile browser, we may receive device type, browser details, access time and technical session signals. These details help keep the account path working and identify unusual sign-in activity. They are handled separately from the content of your personal request.

Use the support contact shown inside your signed-in account and name the exact record you want corrected. We verify that the request comes from the account holder, then assess correction or deletion under the Privacy Policy and applicable local requirements.

We keep account, security and payment records for the period needed for their stated purpose, support handling and applicable legal requirements. A DANA, QRIS, bank transfer or virtual account reference may remain while a transaction question or account obligation is still open.

Start with the support contact displayed after sign-in, or use the access-page route if login is unavailable. Mention Indonesia, your account identifier and the data category involved, such as cookies or QRIS status. Service access and eligibility depends on local law.