Reference

Open gecko388 Privacy Policy Clearly

gecko388 Privacy Policy explains how we handle the details you provide before you enter the lobby, including account credentials, phone verification, device data and wallet references.

Account dataWallet referencesCookie choicesRequest access
Browse Our Lobby Read FAQ
gecko388 Open gecko388 Privacy Policy Clearly
CONTACT ROUTES

Ask Support About Your Privacy Policy

A clear contact route helps when you need to understand a record, correct an account detail or ask how a wallet reference was used. We keep privacy questions separate from general lobby requests so the right account context reaches the right handling path. Include your registered phone number and a short description, but do not send a password or full payment credential. Where local law permits, we can explain the next step for an access, correction, deletion or objection request.

Team online

Account request

Use the support route linked to your account when you want to ask about personal data connected with your gecko388 login. Include the registered phone number and request type; we may ask for an account step to confirm that the request comes from you.

Wallet question

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account reference, describe the transaction date and status without sharing a PIN. We use the reference to locate the relevant record and explain what data was handled.

Policy clarification

For a question about cookies, device records, retention or a change to this Privacy Policy, send the topic and your account contact through our support path. We will explain whether the request can be completed and what identity check is needed.

DATA PRACTICE

Check How gecko388 Handles Your Data

We apply the Privacy Policy to the account journey rather than treating data as a separate subject.

Account collection

When you open an account, we collect details needed to create and protect it, such as your contact information, login events and phone verification result. We do not ask you to place a wallet PIN in our support messages or account forms.

Payment references

DANA, OVO, GoPay and QRIS can return status or reference details through their payment flow. For bank transfer and virtual account requests, we use matching references to connect the status with your account and investigate a missing or pending record.

Cookie controls

Cookies may keep a sign-in session working, remember selected settings or help us understand page errors. You can manage browser cookie controls, but disabling necessary cookies may interrupt the account path or require you to sign in again.

Device protection

A mobile browser and desktop browser may send technical signals such as device type, browser details and login time. We use these signals to protect account access and investigate unusual activity, not to request sensitive credentials through an unverified message.

Record retention

We retain account, support and transaction records only as needed for the purpose collected, account security, dispute handling and applicable legal duties. Retention can differ by record type, so your request should identify the account detail or payment reference involved.

Your requests

You can contact us to ask about access, correction, deletion, restriction or objection where local law permits. We may verify your phone or account details before responding, and we will explain any reason a record must remain available.

Find Privacy Policy Answers Quickly

These Privacy Policy questions cover the account and wallet situations you are most likely to meet before using gecko388. We explain what information is involved, how to contact us and what happens when a request needs verification. If your question is not listed, use the support route with the smallest amount of personal detail needed to identify the issue.

It covers data connected with account creation, phone verification, sign-in activity, device use, cookies, support messages and payment references. It also explains why we use those records, how long they may remain and how you can ask about access or correction.

Yes, it explains how we handle status and reference details received during a DANA, OVO, GoPay or QRIS flow. The wallet provider may process separate data under its own terms. Do not send us your wallet PIN or full security credential.

We use your registered phone number for account creation, phone verification, account recovery steps and support identification. A phone check helps us distinguish an account request from an unverified message. We will not ask you to reveal a password in a support conversation.

You can submit an access request through the account support route where local law permits. Tell us which account detail or transaction reference you mean, and we may verify your registered phone number before explaining the available record and response process.

Send a correction or deletion request through support with your registered phone number and the specific record involved. We review the request under applicable requirements. Some security, dispute or legal records may need to remain for a stated period.

The policy explains cookies used for sign-in continuity, selected settings and technical error checks. You can adjust browser controls, though necessary cookie changes may interrupt your session. We recommend checking the policy again after changing browser or device settings.

The policy is available for you to read, while account access and eligibility depends on local law. If a local requirement affects a request, account step or data response, we will explain the relevant limitation through the support route.

Related Pages

gecko388 Indonesia Access guide Live Roulette Diamond About Us gecko388 Casino