Reference

Privacy Policy for Your gecko slot Account

gecko slot Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Clear data purposesWallet record controlsPhone verificationCookie choices
gecko slot Privacy Policy for Your gecko slot Account
CONTACT PATHS

Where to Ask About Privacy Policy

A clear contact path helps you act on this Privacy Policy without searching through the lobby. We handle privacy questions alongside account and wallet assistance, so you can identify the relevant record when a phone verification detail, QRIS receipt or payment status needs checking. Contact us through the account help route shown on gecko slot, include the email or phone detail attached to your account, and describe the request you want us to assess. We may ask for account verification before discussing personal data.

Team online

Account help

Use the account help path when you want to ask how your phone number, login record or account identifier is used under this Privacy Policy. Include the affected account detail so we can locate the correct record without asking you to send a full payment password or security code.

Wallet record check

Choose the wallet assistance path when your question concerns DANA, OVO, GoPay or QRIS data. We can review the receipt or status reference you provide, while keeping payment credentials and one-time verification codes out of your message.

Privacy request

Send a direct Privacy Policy request when you want access, correction or deletion assessed. Tell us which information you mean and how we can verify the account holder. We respond according to the applicable process and local law.

DATA HANDLING

What We Do With Account Data

Privacy Policy decisions are tied to specific account actions rather than broad collection for its own sake.

Account creation

When you open an account, we collect the details needed to create and protect that account, including the phone verification…

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create transaction references in our records.

Device signals

Your browser, operating system, approximate technical connection details and session events can help us keep account access working on a…

Cookies

Cookies and similar storage can remember session choices and help us understand whether a page request worked.

Account security

We use phone verification and account checks to reduce the chance that personal details are disclosed to the wrong person.

Retention requests

We keep records only for the period needed for account operation, security, dispute handling or a legal requirement that applies…

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account, device and wallet questions you are most likely to have before opening or continuing an account. We keep the answers tied to gecko slot records and the payment rails shown in our Indonesian account flow. If your situation is different, use the contact path above and identify the specific record you want us to check.

It covers account details, phone verification, device and session data, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction, deletion and retention where local law permits.

Phone verification helps us connect an account request to the correct account holder before access is provided. It also gives our support team a matching step when you ask about login or personal data. Never send your verification code in a support message.

Yes. The Privacy Policy includes transaction references and status details needed to investigate a QRIS, DANA, OVO, GoPay, bank transfer or virtual account question. We use the reference to check the account record and do not need your wallet password or PIN.

You can request correction by using the account help route and naming the detail that appears wrong. Include the account email or phone detail needed for matching, but do not include a password or one-time code. We assess the request under applicable local law.

Cookies can keep your session active and remember necessary page settings on mobile or desktop. Browser controls let you restrict or remove them. If you block essential storage, login continuity or access to account pages may not work as expected.

Retention depends on why the record exists, such as account operation, security, dispute handling or a legal requirement. Ask us about a particular record rather than a general category. We assess requests to remove or limit retention where local law permits.

You can open this Privacy Policy from the same mobile or desktop account path used to reach the lobby, including from Jakarta, subject to access that depends on local law. If the page or account route does not load, contact account help with your device details.