Reference

gecko303 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a gecko303 account, move through the lobby, or check DANA, OVO, GoPay and QRIS status.

Account clarityWallet contextDevice awarenessPrivacy requests
Explore Our Lobby Read FAQ
gecko303 gecko303 Privacy Policy For Your Account
REQUEST A RESPONSE

Privacy Help Beside Your Account Path

A privacy question should not leave you searching through the lobby. Start from your signed-in account help route and include the email or phone detail attached to your account, plus the relevant wallet reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to find the right record without asking you to send a password or full wallet credential.

Team online

Account help route

Use the help path after login for questions about the personal details attached to your gecko303 account. We can locate the correct record from your account contact detail and explain the next privacy step without requesting your password.

Wallet status check

For a privacy question linked to DANA, OVO, GoPay or QRIS, include the payment reference shown in your account. We use the reference to separate transaction status from sensitive wallet credentials and keep the request focused.

Access correction

If your account contact detail is no longer correct, tell us through the same support path before requesting a record change. We may ask for an account check so another person cannot alter your privacy details.

HOW WE HANDLE DATA

Account Security From Login To Lobby

Privacy protection follows the same path you use to enter the account and reach the lobby. We separate account credentials from wallet references, watch for unusual device or browser activity, and keep…

Account details

We use your submitted contact and verification details to create, secure and maintain your account. Before changing sensitive account data, we may compare the request with the account path already on record so a third party cannot redirect access.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account flows can create references, statuses and receipt details. We use these records to match an account request with a payment event, while wallet passwords remain outside our account process.

Device signals

Your browser, device type, session details and security events may be recorded when you sign in. On mobile, these signals help us recognise an unusual login; on desktop, they support the same account check without requiring a separate app.

Cookies and storage

We use necessary cookies or browser storage for session continuity, security checks and page settings. You can clear or restrict them in your browser or device controls, but the account may ask you to authenticate again after that change.

Retention approach

We keep personal and account records for the period needed to operate the account, address payment or security questions, resolve disputes and meet legal duties. When a record is no longer needed for those purposes, we remove or separate it where practical.

Change request

To ask for access, correction or removal of personal data, use the signed-in help route and describe the record involved. We may verify account ownership first, then explain what can be changed and whether another retention duty applies.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers cover the questions we expect before you open an account or continue using the account path. They explain how gecko303 treats identity details, device signals and local payment references, while keeping access language clear for Indonesian customers. If your situation is not listed, use the account help route with the detail you want us to check.

The gecko303 Privacy Policy covers personal details, account verification, login activity, device signals, cookies, wallet references and support records. It also explains retention, security handling and requests for access or correction when you use the account path where local law permits.

No. Our Privacy Policy distinguishes wallet credentials from account records. We may receive a DANA or GoPay payment reference, status or receipt detail needed to match an account event, but you should not send a wallet password through support or any account form.

We collect limited device, browser and session signals to protect login access, identify unusual activity and diagnose a page or account issue. The same approach applies whether you use a mobile browser from Yogyakarta or a desktop device elsewhere in Indonesia.

Open the signed-in account help route and ask for access to your personal data under the Privacy Policy. Include the contact detail attached to the account and describe the record you want. We may verify ownership before preparing a response.

Yes. Send a correction request through the account help route and identify the field that is wrong, such as a contact detail or verification record. We may ask for an account check, then update the record where the request is valid and permitted.

We retain records for account security, payment questions, dispute handling and legal duties for as long as those purposes require. The period can differ by record type. When no valid purpose remains, we remove or separate the data where practical.

Use the support route inside your signed-in account and describe the privacy issue clearly. For DANA, OVO, GoPay or QRIS questions, include the visible payment reference rather than wallet credentials. Account access and eligibility depend on local law.

Related Pages

gecko303 Indonesia About Us gecko303 Casino Access guide FAQ