Reference

6r6r Privacy Policy for Your Account

Our 6r6r Privacy Policy explains how we handle account details, device signals and payment records when you open the lobby from Indonesia, including from Denpasar.

Account dataWallet recordsDevice choicesPolicy access
6r6r 6r6r Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Personal Data

A clear support path helps you ask about the Privacy Policy without explaining your whole account history from the start. Begin with the support route shown after sign-in and include the email or phone detail linked to your account, plus the relevant receipt or status screen. We can then direct your request to the right data or account check.

Team online

Account data request

Use the account support route to ask what personal data is linked to your profile. Include your verified phone detail so we can distinguish your request from another account.

Wallet record query

For DANA, OVO, GoPay or QRIS records, share the payment reference shown in your account. We use that detail to locate the relevant wallet status without asking for your full history.

Policy clarification

If a Privacy Policy passage is unclear, contact us through the same support route and name the section. We can explain how it relates to login, device checks or account security.

DEVICE SECURITY

How Device And Account Data Is Handled

The policy is practical at each point where your account creates a record, from the first phone check to a later sign-in on mobile or desktop.

Data we receive

We may receive account details you submit, phone verification results, sign-in records, device signals and payment references. Browsing a room such as Ways of Qilin can also create technical session data.

Cookies and sessions

Cookies and similar session tools help keep your sign-in active and remember essential account choices. You can review browser controls, while changing them may affect the path back to your account.

Account protection

Phone verification and device signals help us identify unusual sign-in activity. Never send a password or one-time code through support; use the account route when you need a security check.

Retention choices

We retain records only for the period needed for account operation, security checks, payment reconciliation or a lawful request. The Privacy Policy explains the purpose behind each retention category.

Who receives data

We limit access to data to the people and service processes needed for account support, security or payment status checks. DANA, OVO, GoPay and QRIS references are handled for their stated account purpose.

Requesting a change

You can ask us to correct an inaccurate account detail or clarify how a record is used. Send the request through support with your verified phone detail and the specific field to check.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the account actions you are most likely to take before opening access: phone verification, mobile sign-in, wallet checks and a request to change personal data. If your question is not listed, use the support route connected to your account and quote the relevant policy section.

It covers account details, phone verification, device and session signals, cookies, payment references and support requests. It also explains why we use each category and how you can ask about its handling.

Yes. The policy covers payment references connected with DANA, OVO, GoPay and QRIS, including records used to match a wallet status or receipt with your account.

Phone verification links account access to the contact detail you provide and helps us investigate unusual sign-ins. It may also help support identify the correct account during a data request.

We may record device type, browser signals, session timing and related security events. These details help protect account access whether you sign in from a mobile browser or a desktop.

Use the support route shown in your account and identify the field you want checked. Include your verified phone detail, but do not send a password or one-time security code.

Retention depends on the purpose of the record, such as account operation, payment reconciliation, security review or a lawful request. The Privacy Policy describes the relevant purpose and retention approach.

Yes. Send that question through account support and refer to the Privacy Policy section involved. We can explain which internal or payment-related process needs the data for your request.