Reference

Privacy Policy for Your Account

gcr77 Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Blackjack Turbo or use DANA and QRIS.

Clear collection reasonsWallet record controlsPhone verification contextPolicy request path

Explore Our Lobby Read FAQ

How Our Privacy Policy Applies

gcr77 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers account registration, phone verification, lobby activity, payment references and support requests. When you choose DANA, OVO, GoPay or QRIS, we retain the transaction reference and status needed to match your account record; we do not need your wallet password to show whether

1
a request is pending or completed. Bank transfer and virtual account records may include a bank reference, including a Mandiri transfer reference, so our payment team can investigate a mismatch. We use data for account access, security checks, policy administration and requested support. Access depends on
2
local law, and where local law permits, you may ask us to explain, correct or remove eligible data through the account support route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

POLICY HELP ROUTES

Ask About Privacy Policy Changes

A clear request path helps you resolve a data question without sending wallet credentials through chat.

Account support route Use the support path inside your account for a Privacy Policy question, a correction request or a data access request. Include your account identifier and the relevant date, but never send your DANA, OVO, GoPay or QRIS password.

Sign-in assistance If phone verification blocks account access, select the support option shown beside the sign-in step. We use the details you provide to check the account record and can ask for a verification detail before discussing private data.

Payment record check For a missing QRIS receipt, an OVO status question or a Mandiri bank transfer reference, contact support from the account path and attach the transaction reference only. This lets us check the payment record without requesting your wallet login.

DATA HANDLING DETAILS

What We Do With Policy Data

Privacy controls work best when each account step has a defined data purpose. We separate login details from payment references, use device signals to identify unusual access, and keep policy requests tied…

Account records

We collect details you enter during account opening, including contact data and phone verification status. That record helps us identify your account, send access messages and respond to a Privacy Policy request without confusing it with another account.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and processing time in your account history. We use those fields to match a receipt or investigate a failed step, not to request your wallet password.

Cookies and devices

Cookies can remember your session and selected account path, while device signals can help identify an unusual sign-in. On mobile, clearing site data may remove session recognition and require phone verification again before account access.

Account security

We may compare sign-in details, phone verification and device activity when an access pattern looks unusual. If a check is required, follow the account prompt and share only the requested verification detail through the secure support path.

Data retention

We keep account, payment and support records for as long as needed for the purpose collected, security checks and required account administration. When a record is no longer needed, we remove or separate it where our process and local law allow.

Changes and requests

You can ask us to correct an inaccurate contact detail, explain a payment reference or provide eligible account data. Submit the request after sign-in so we can confirm account ownership before changing or disclosing private records.

Privacy Policy Answers for gcr77

These Privacy Policy answers focus on the account and wallet questions you may search before opening an account. We keep the steps practical: identify the record, use the correct support route and provide only the details needed for a secure response.

The gcr77 Privacy Policy covers account details, phone verification, cookies, device signals, lobby activity, payment references and support requests. It explains why we use each category, how we protect account access and how you can ask about correction, access or eligible removal.

Yes. The Privacy Policy explains that DANA and QRIS activity may create a transaction reference, status and time in your account record. We use those details to match receipts and investigate payment issues, while your wallet password remains outside our request.

Sign in, open the account support route and request the specific data category you want us to check. Name the account record, date or payment reference where possible. We may confirm phone verification or another account detail before responding to protect your private data.

You can ask for a correction through the support path shown after sign-in. Tell us which account field is inaccurate and what should replace it. We may request an account ownership check before changing contact data connected with phone verification or wallet records.

Cookies can keep your session and account route recognised on a mobile browser. If you clear site data, the next sign-in may require phone verification again. Our Privacy Policy treats cookies as access and session tools, not as a reason to request wallet credentials.

We retain payment references for the period needed to match account activity, handle support questions, apply security checks and complete required account administration. When retention is no longer needed, we remove or separate the record where our process and local law allow.

Use the support route inside your account and describe the access, correction or eligible removal request. If sign-in is unavailable, use the support link on the sign-in route. Access depends on local law, so we confirm the request and account ownership first.

Privacy Policy for Your Account

Ask About Privacy Policy Changes

What We Do With Policy Data

Account records

Payment references

Cookies and devices

Account security

Data retention

Changes and requests

Privacy Policy Answers for gcr77

01 What does the gcr77 Privacy Policy cover?

02 Does the Privacy Policy explain DANA and QRIS data?

03 How can I request my gcr77 account data?

04 Can I correct a wrong phone or account detail?

05 How does the Privacy Policy treat cookies on mobile?

06 How long does gcr77 keep payment references?

07 Where can I ask about Privacy Policy access rights?

Related Pages