Reference

Privacy Policy For Your gesit777 Account

gesit777 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move from mobile login into the lobby.

Account accessWallet detailsDevice controlsPolicy requests
gesit777 Privacy Policy For Your gesit777 Account
REQUEST A RESPONSE

Get Policy Help Beside Account Support

A clear request path helps when you want to ask about a record, correct an account detail or understand a wallet reference.

Account request Ask about the personal details linked to your account through the account support path. Include your registered phone or email, describe the Privacy Policy question, and we can direct the request to the right handling team.
Wallet record For a DANA, OVO, GoPay or QRIS record, provide the date, reference and wallet name rather than a password or security code. This gives us enough context to check a status without exposing unnecessary payment credentials.
Access concern If a phone verification step or mobile login does not match your account, use the account help route before sending another document. We may ask for account ownership details so a privacy request reaches the correct account holder.
DATA HANDLING DETAILS

What Our Privacy Process Covers

The practical choices below show how we handle the policy area from first registration through later account requests.

Account details

We may hold the name, phone number, email address and verification status you provide during account creation. These details help us connect a login to one account and respond to a Privacy Policy request without mixing your records with another account.

Wallet references

Payment records can include a DANA, OVO, GoPay or QRIS reference, amount status and related receipt details. We use these records to match a wallet event or bank transfer, not to request your wallet password or private security code.

Cookies and sessions

Cookies can keep a signed-in session, remember a language choice or help identify an interrupted account step. You can manage browser cookie controls, although changing them may require another login before you reach the mobile lobby.

Device security

Browser type, device signals and login timing may be checked for unusual access patterns. If a new phone behaves differently from your usual device, we may pause an account step and request phone verification before access continues.

Retention requests

We keep records only for the period needed for the stated account, payment or security purpose, subject to legal requirements. Ask us which category applies to your record, and we can explain the retention reason and available next step.

Changes and contact

You can ask us to correct an inaccurate detail, explain a data use or provide a copy where the law allows. Send the request through account support with your registered contact detail; never include a wallet PIN or login password.

Privacy Policy Questions Before Account Access

These answers focus on the questions you may search before creating an account or checking a wallet record. They explain the account step, device checks, cookies, payment references and request route in plain terms. If a situation is not covered, contact support with the registered detail connected to your account.

It covers account details, phone verification, wallet references, cookies, device signals, security checks, retention and requests connected to your use of the service. The policy applies to Indonesian access where local law permits, and any eligibility decision depends on local law.

Phone verification helps us connect the login to the account you opened and identify unusual access. If you change devices or a login pattern differs, we may ask you to complete that step before account access continues.

Yes. A DANA or QRIS transaction may create a reference, status and receipt record so we can match the wallet event. Similar records can apply to OVO, GoPay, bank transfer and virtual account activity.

The policy can cover browser type, device signals and login timing used to identify unusual account access. We do not need your wallet PIN for this check. A new mobile device may trigger phone verification before you return to the lobby.

You can request a correction through the account support path. Include the registered phone or email, name the detail that appears wrong, and explain the requested change. We may confirm account ownership before changing the record.

Cookies may keep your session active, remember a language choice or help restore an interrupted account step. You can adjust browser controls, but removing cookies may sign you out and require another login before mobile access.

Send a retention question through account support using the contact detail registered to your account. Tell us which record you mean, such as a QRIS receipt or phone verification event, and we will explain the applicable purpose and next step.