Reference

gecko666 Privacy Policy for Indonesian Accounts

Our Privacy Policy gives you a clear view of how gecko666 handles account details, phone verification, device activity and payment status before you open the lobby.

Account data explainedWallet status clarifiedAccess requests available
gecko666 gecko666 Privacy Policy for Indonesian Accounts
POLICY HELP

Where to Ask About Your Privacy Policy

A privacy question should not require a long search through the lobby. We provide a direct support route from the account area so you can ask about a stored detail, a phone check, a device record or a payment reference. Include the email or phone connected to your account, but never send a wallet password or full payment credential. We may ask for an account check before changing or disclosing personal data.

Team online

Account support chat

Use the support chat inside your account when you need to ask what personal data is attached to your login, why a phone check appears, or how to request a correction. We use the account path to reduce mistaken disclosures and keep the request connected to the right record.

Payment privacy request

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment date, reference and visible status through support. We check the account record without asking you to reveal a wallet password, card secret or one-time security code.

Account closure path

If you want to close your account or ask us to stop using optional contact details, begin in the account support area. We verify the request, explain any records that must remain for a dispute or legal duty, and confirm the action through your registered contact.

SECURITY PRACTICE

How We Handle Account Privacy

Privacy controls work best when they match the steps you actually take. We separate account identity, device access and payment status so a support request can be checked without exposing unrelated details.

Account details

We use your contact details and phone verification result to create, maintain and protect the account you control. They also help us send account notices and respond to a privacy request. We do not treat a support message as permission to reveal another person’s account data.

Payment records

For DANA, OVO, GoPay and QRIS, we keep the rail name, reference and status needed to match an account action. Bank transfer and virtual account records are handled in the same way. Wallet credentials are not requested in our support process.

Device signals

Your browser and device may provide sign-in time, session details and security signals when you open the lobby. We use these details to identify unusual account access and investigate a reported session. They are not used as a substitute for your phone verification.

Cookies

Necessary cookies can keep your account session active and remember security choices between pages. Optional storage may support preferences or measurement where enabled. Your browser settings can remove or restrict cookies, but signing in again may be required after that change.

Retention approach

We keep personal data only while it supports account operation, security, payment matching, dispute handling or a legal requirement. When a record is no longer needed, we remove it or separate it from your account where practical. A closure request does not erase required records immediately.

Change requests

You can ask to see, correct or delete eligible account data through support chat. Tell us which detail is wrong and use the registered contact so we can confirm control. Where local law permits, we will explain the result, including any reason a record must remain.

Privacy Policy Questions for gecko666

These answers cover the privacy points you are most likely to check before opening an account. They focus on the data connected to login, phone verification, device use and Indonesian payment rails, rather than describing unrelated lobby functions. If your question concerns a specific record, contact us from the account support path so we can check your details safely.

The gecko666 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains how to request access, correction or eligible deletion, and how we handle records that must remain for security, disputes or legal duties.

No. Our Privacy Policy describes payment status and reference handling, not collection of your DANA or OVO password. For GoPay, QRIS, bank transfer and virtual account activity, we use the transaction details needed to match an account action and investigate a support question.

Phone verification helps confirm that you control the contact connected to the account before access or a privacy change is completed. It also helps us reduce mistaken disclosures during support. We may request the registered contact again when you ask to view, correct or close an account.

Open the account support area and send a privacy request using your registered email or phone. State whether you want access, correction or eligible deletion. We check account control first, then explain the available result and any records that must remain under applicable local requirements.

We keep data while it is needed for account access, security checks, payment matching, support, disputes or a legal requirement. The exact period can depend on the record and the request. After that need ends, we remove the data or separate it from direct account identification where practical.

You can restrict or remove cookies through your browser controls. Necessary storage may still be required for sign-in, session continuity and security checks, so refusing it can require repeated login or prevent some account actions. Optional storage can be managed separately where those controls are provided.

The same Privacy Policy explains data handling for Indonesian account access, including connections from Semarang and other locations. Eligibility and access depends on local law. If a local rule affects your account or request, we will use the support path to explain the applicable limitation.