Reference

gempa 77 Privacy Policy For Your Account

gempa 77 Privacy Policy explains how we collect, use and protect the account details connected with your lobby access and wallet activity.

Account clarityWallet recordsCookie choices
gempa 77 gempa 77 Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Questions Reach The Account Desk

A clear contact route helps you resolve a privacy question without repeating your account story. When you contact us, include the phone number linked to your account, the subject of your request and any relevant wallet reference; do not send a password or full payment credentials. We use those details to locate the correct record and respond about access, correction, deletion or cookie choices. Requests connected with a stalled wallet status can be directed through the same account support path.

Team online

Privacy request

Send an account privacy request through our support contact path with your registered phone number and the change you want. We may ask for an account step that confirms you are the person making the request before discussing personal records.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the date, amount reference and wallet name without sending secret credentials. We compare the record with your account status and explain what can be corrected.

Login access help

A login or phone-verification problem can affect your privacy request. Tell us which device path you used, such as mobile browser or desktop browser, so we can separate an access issue from the data question itself.

DATA HANDLING STEPS

Six Practical Controls In Our Privacy Policy

We handle privacy through account steps you can recognise rather than vague promises. Phone verification helps us distinguish an account holder from an unrelated request, while device and…

Account data

We may hold the account name or identifier, registered phone number, verification result and login history needed to manage access.

Device signals

Browser type, device path and security events can help us assess a login that looks unusual.

Cookie choices

Cookies can keep a session working, remember selected site settings and help us understand technical errors.

Wallet references

A payment record may show a rail such as QRIS, DANA, OVO or GoPay, plus a reference used to match…

Retention checks

We keep account, security and transaction records for as long as needed for service operation, dispute handling or applicable legal…

Change requests

You can ask us to correct an outdated phone detail, clarify a record or request deletion where permitted.

Privacy Policy Answers For gempa 77

These Privacy Policy answers cover the account and wallet questions you are most likely to ask before opening an account or contacting us. We keep each answer tied to the records, devices and payment references used on our Indonesia service. If your situation is not listed, use the privacy contact path with the smallest useful set of account details.

It covers data connected with your account, phone verification, browser or device access, support messages, cookies and wallet status records. It also explains why we use these records, how long operational needs may require them and how you can request a correction or other available action.

These payment names help explain the type of wallet or payment reference that may appear beside your account activity. We use a reference to check status and resolve a mismatch, but you should never send a wallet PIN, password or secret credential in a support request.

Contact our privacy support path using the phone number linked to your account and state that you want an account data request. We may ask you to complete phone verification or another account check before we discuss records containing personal details.

You can ask us to correct an outdated phone detail or another inaccurate account field. Describe the existing record and the requested correction clearly. Because a phone number controls account access, we may verify your identity before applying the change.

Cookies can support a working login session, remember browser settings and help identify technical errors on a mobile browser. Your browser controls can restrict them, but changing those settings may interrupt account access or remove a saved preference.

Retention depends on the purpose of each record, such as account operation, security checks, payment reconciliation, dispute handling or legal duties. We do not promise one period for every field. You can ask us which category applies to your request.

Yes. Available access, correction, deletion or restriction options depend on local law and the nature of the record. Where local law permits, we will assess your request, confirm the account connection and explain the next step through our support route.