Reference

gempa77 Privacy Policy for Your Account

gempa77 Privacy Policy gives you a clear view of the account, wallet and device details we use when you open an account and access the lobby.

Account clarityWallet data contextCookie choicesRequest changes
Explore Our Lobby Read FAQ
gempa77 gempa77 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Privacy

A direct support route helps you resolve a privacy question without posting account details in a public message. Use the support channel shown inside your signed-in account for a request about stored details, a wallet reference or a device record. If you cannot sign in, use the account access route displayed on gempa77 and state that your request concerns the Privacy Policy. Include only the details needed to locate your account, because sending extra personal data can slow a secure check.

Team online

Account privacy desk

Ask our account support team which details are linked to your profile, including phone verification records and login-device signals. We may ask you to confirm account ownership before discussing private data or applying a correction.

Wallet reference check

For a DANA, OVO, GoPay or QRIS privacy question, share the visible transaction reference through the account support channel. We use that reference to locate status data without asking you to send a wallet password or PIN.

Privacy change request

Request access, correction or removal review through the privacy contact path shown in your account area. Tell us what should change and why; we will explain any identity check or legal reason affecting the request.

DATA PRACTICES

How We Apply This Policy

We apply the Privacy Policy to practical account events rather than treating every detail alike.

Account details

We collect details you provide when opening an account, such as contact data and phone verification results. We use them to create the account record, help you sign in and respond when you ask us to correct or access those details.

Wallet references

A DANA, OVO, GoPay or QRIS event can leave a reference, amount status and time in account records. Bank transfer and virtual account references serve a similar matching purpose. We do not need your wallet PIN to investigate a status question.

Cookies and devices

Cookies can remember a signed-in session and basic preferences, while device signals help identify an unusual login. On a mobile browser, clearing cookies may sign you out and remove saved settings; you can then sign in again through the normal account path.

Account security

We use phone verification, sign-in checks and account activity signals to reduce unauthorised access. If a login looks unusual, we may pause a sensitive account request until ownership is confirmed. Never send a password, wallet PIN or one-time code in support messages.

Retention periods

We keep account, payment-reference and support records only for the period needed for account operation, dispute handling, security checks or a legal duty. When a record no longer serves one of those purposes, our handling process moves it toward deletion or anonymisation.

Your requests

You may ask what personal details we hold, request a correction or ask about deletion through the privacy contact path. We may verify your identity first, and we will explain if a record must remain because of security, dispute or legal requirements.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions we expect before you open an account or connect a wallet. They cover the details behind phone verification, mobile access, cookies, payment references and correction requests. If your situation is different, contact us through the secure account support path and describe the specific record you want us to check.

It covers account details, phone verification, login and device signals, cookies, support messages, wallet references and retention. It also explains your routes to request access, correction or deletion. The policy applies to these handling activities when you use the account path where local law permits.

DANA and QRIS can return a transaction reference, status and timestamp needed to match a wallet event to your account. We use those records to investigate payment status and account questions. We do not ask for your wallet PIN, password or one-time security code.

Yes. The Privacy Policy covers OVO and GoPay references in the same way as DANA and QRIS references. We may retain the visible status and matching details connected to your account activity, while the wallet provider remains responsible for its own separate data practices.

You can request access or correction through the privacy contact path shown inside your account support area. Tell us which detail appears wrong or which record you want to see. We may first confirm account ownership before sharing or changing private account data.

Cookies can keep your mobile-browser session connected and remember basic settings. If you clear them, you may be signed out and need to complete the normal phone or account login step again. The Privacy Policy explains how cookie-related data supports access and preferences.

We retain account, wallet-reference and support records for the period needed for account operation, security checks, dispute handling or a legal duty. The period can differ by record type. You may ask support why a particular record remains and whether deletion is available.

Use the privacy contact route displayed in your signed-in account. If you cannot access the account, use the account support route shown on gempa77 and state that the matter concerns the Privacy Policy. Share the minimum details needed for us to locate and verify your request.

Related Pages

gempa77 Indonesia Badminton Indonesia Open Bet Access guide GoPay Fast Transfer About Us