Reference

Privacy Policy for gemini66 Accounts

The gemini66 Privacy Policy explains what we collect, why we use it and how you can ask about your account data before opening access to our Indonesia lobby.

Account clarityWallet contextCookie choicesContact route
gemini66 Privacy Policy for gemini66 Accounts
CONTACT YOUR WAY

Privacy Questions Reach Our Support

A clear contact path matters when you want to ask what your account record contains or why a wallet reference is connected to your profile. Our support route is available for Privacy Policy questions about collection, cookies, access, correction and deletion requests. Include the phone number or account identifier linked to your profile, but never send a password or wallet PIN. We may ask for an account step to confirm that the request comes from you before discussing personal data.

Team online

Live chat

Use the live chat route from your account when you need help locating a Privacy Policy answer, checking a data request or explaining a sign-in concern. We can connect the question with your phone verification record without asking you to post a password in the conversation.

Payment receipt

If your privacy question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, attach only the reference needed to identify the transaction. Remove wallet PINs, full passwords and unrelated personal details before sending a receipt for status checking.

Account request

For a copy, correction or removal request, tell us which account detail you mean and use the contact route connected with your gemini66 account. We may verify your phone before responding, helping keep another person from changing or receiving your private record.

SIX DATA CONTROLS

What We Do With Your Account Data

Privacy work is part of the account flow, not a separate promise shown only at registration.

Account details

We use the details you submit to create and maintain your account, send service messages and answer requests tied to your profile. A clear phone verification step helps us match a privacy request to the correct account before we reveal, correct or remove personal details.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be stored with a deposit or account event so we can match status information. Bank transfer and virtual account records serve the same administrative purpose. We do not need your wallet PIN to identify that reference.

Device signals

Your browser, device type, approximate connection location and session events can help us spot repeated failed sign-ins or an unusual account path. These signals also help us diagnose a mobile page that does not keep your login state, without treating them as a profile biography.

Cookies

Cookies can remember a session, preserve a selected language or help us understand which policy page brought you to a contact route. You can manage cookies through your browser, although limiting them may require you to verify your account again or may affect page continuity.

Retention

We keep personal records for as long as they support account administration, security checks, dispute handling or a legal requirement. When a record no longer has a valid purpose, our process is to remove it, anonymise it or restrict its use rather than keep it without reason.

Your request

You can ask what personal data we hold, request a correction, ask about processing or request removal where applicable. Send the request through live chat or your account contact route, describe the specific record and complete phone verification if we need to confirm identity.

Privacy Policy Answers Before Access

These Privacy Policy answers address the searches we hear before an Indonesian account is opened or a wallet is connected. They explain the practical route for account data, device records, cookies, payment references and requests. If your situation is not covered, use live chat with the account detail that needs attention and remember that access or eligibility depends on local law.

The gemini66 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records, how long we retain them and how to contact us.

Phone verification helps us create the correct account and reduce the chance that another person can access private details. We may use the same check before discussing a data copy, correction or removal request. Access or eligibility depends on local law, so verification does not change that condition.

Yes. The Privacy Policy covers payment references that help us match DANA, OVO, GoPay or QRIS activity with your account, along with bank transfer and virtual account records. These references support status checks and account administration; your wallet PIN and password should not be sent to support.

You can request a correction by using live chat or the contact route connected with your account. State which detail is wrong and what should replace it. We may ask for phone verification before making a change, because correcting one account record should not alter another person’s profile.

Cookies can help keep a browser session active, remember page settings and connect a policy visit with a support request. You can clear or limit them in your browser. If you do, the next visit may require another account check, and some page continuity may not work as expected.

We retain account, support, security and payment reference records while they have a service, security, dispute or legal purpose. Once that purpose ends, we aim to remove, anonymise or restrict the record. The exact period can depend on the type of record and the request involved.

Use live chat or the account contact route and ask for a copy of the personal data linked to your profile. Mention the relevant account step, such as phone verification or a QRIS receipt, without sending passwords or PINs. We may verify your identity before releasing private information.