Reference

Open Privacy Controls for grosir188

grosir188 Privacy Policy explains what we collect when you create an account, check DANA or QRIS status, and move between Live Baccarat Table and the wider lobby.

Clear data purposesCookie choicesAccount access checksPayment record context
grosir188 Open Privacy Controls for grosir188
CONTACT PATHS

Reach Support About Privacy Questions

A direct support route helps when you want to ask about a record, correct an account detail or understand why a security check appears. Sign in first when you can, then use the support channel shown beside Account Wallet Help so we can match your request with the right account. If you cannot sign in, include the registered phone number without sending a password, wallet PIN or full payment credential.

Team online

Privacy request

Use the account support channel to ask what personal details we hold, why a field is needed, or how to request a correction. We may ask you to complete phone verification before discussing account-linked records, so another person cannot obtain your details.

Payment record query

For a DANA, OVO, GoPay or QRIS record, send the transaction date, amount and reference shown in your account rather than a wallet password. Our support team can connect the payment status with the correct account while limiting unnecessary financial details.

Access concern

If your mobile browser shows an unfamiliar sign-in or your account access stalls, contact support through the visible account route. Tell us the device type and approximate time, then change your password through the account path if you still have access.

DATA PRACTICE

Explore Our Data Handling Steps

Privacy choices work best when each step is visible. We separate account details from general browser signals, limit staff access according to their work, and use security events to investigate unusual sign-ins.

Account details

When you create an account, we may hold your name, phone number, login details and verification status. These fields support sign-in and account help. We do not ask you to place a wallet PIN or password in a support message.

Device signals

A mobile browser can send device type, browser version, approximate session time and security events. We use these signals to identify unusual access and keep your account path working, not to request unrelated content from your phone.

Cookies

Cookies can keep your session connected, remember a selected preference and help us see whether a page works correctly. You can adjust cookie settings in your browser, although blocking some cookies may interrupt sign-in or policy access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create a reference, status and time record. We use those details to match a cashier event with your account without storing a wallet PIN.

Account security

Phone verification, sign-in records and unusual-device checks help us protect account access. If you receive a prompt you did not expect, stop the session, change your password through the account path and contact support with the event time.

Changes and retention

You can ask us to correct inaccurate account details, explain a data use or remove eligible records through support. Some records may remain when needed for security, payment tracing or legal duties, and we will explain the reason when applicable.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the account questions you may search before opening access. We explain the practical route for data requests, cookies, device checks and local payment records, with support available through the account contact path. Where eligibility matters, access depends on local law.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains how to request corrections, ask about retention and contact us about your records.

We use your phone number to create and protect the account, complete phone verification and help support match a request with the correct account. If you contact us, do not send your password, wallet PIN or full payment credential in the message.

Yes. The Privacy Policy covers cookies used to keep a mobile browser session connected, remember selected settings and identify page errors. You can change cookie controls in your browser, but blocking needed cookies may interrupt sign-in or access to Account Wallet Help.

We may retain a payment reference, status, amount and time for DANA or QRIS activity so support can connect the cashier event with your account. These records help trace a status without requiring us to hold your wallet PIN.

Yes. Send a correction request through the support channel shown after sign-in, or explain that you need account help if sign-in is unavailable. We may request phone verification before changing account-linked data, and we will explain any record that cannot be changed.

We keep records for as long as needed for account support, security checks, payment tracing and legal duties. When a record is no longer needed, we remove or restrict it through our internal process, subject to any duty that requires continued retention.

Yes. Contact support through the account route and provide the device type and approximate sign-in time. Do not share a password or wallet PIN. If you still have access, change your password through the account path and follow any phone verification prompt.