Reference

gemoy88 Privacy Policy for Your Account

Our gemoy88 Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account recordsWallet activityCookie choicesSecurity requests
gemoy88 gemoy88 Privacy Policy for Your Account
PRIVACY CONTACT ROUTES

Get Privacy Help Near Your Wallet Path

A clear contact route helps when an account record or wallet reference needs checking.

Support chat Ask about a Privacy Policy request through the support chat shown in your account…
Contact form Send an account-data question through our contact form with your registered email and a…
Security route Report an unfamiliar device event or account change through the security contact path.
ACCOUNT DATA PRACTICE

How gemoy88 Handles Account Data

Our privacy process follows the account journey rather than treating every record alike. Registration details support account access, payment references support reconciliation, and device signals support security checks.

Collection

We collect details when you open an account, complete phone verification, sign in, contact support or use a wallet route. The requested fields are tied to the action being completed rather than gathered without a stated account purpose.

Cookie controls

Session cookies help keep your account connected while you move between pages. Browser settings let you clear or restrict cookies, although removing session data may require another sign-in before private account areas open.

Device security

We record practical signals such as device type, browser version, sign-in time and network indicators. These signals help us notice an unusual session without treating a device detail as your account password.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status with your account. We use transaction identifiers and status messages, not your private wallet login credentials.

Retention

Account and payment records remain available only as long as needed for security checks, support disputes, reconciliation and legal duties. When a retention reason ends, our process can remove or de-identify the relevant record.

Change requests

You can ask us to correct account details, explain a stored record or discuss deletion by contacting support. Include your registered email and request type; we verify ownership before changing private account data.

Privacy Policy Questions for Indonesian Accounts

These Privacy Policy answers focus on the account steps and local wallet records you are most likely to ask about before opening an account. We keep the route practical: identify the record, verify ownership, then explain the available action under local requirements.

It covers account details, phone verification, sign-in and device signals, cookie use, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

No. Our Privacy Policy describes storing transaction references and wallet status messages needed for reconciliation. Your DANA or OVO password and one-time security code should remain private and should never be sent to support.

Use the contact form linked from the support area and include your registered email plus the records you want checked. We verify account ownership first, then explain which data can be provided.

Yes, you can ask us to correct an inaccurate account or contact detail. Send the request through support with the relevant field identified; we may complete an ownership check before applying any change.

Device type, browser details, sign-in time and network indicators help us identify unusual account access. They support session security and are handled separately from passwords, wallet credentials and one-time codes.

We keep records for the period needed for account security, payment reconciliation, dispute handling and legal duties. After the relevant reason ends, records may be removed or de-identified under our retention process.

Start with the support chat or contact form shown in your account area. For an unfamiliar sign-in or device event, use the security route and provide your registered email without sharing any password.