Reference

Privacy Policy for gem188 Accounts

gem188 Privacy Policy explains how we collect, use and protect the details connected to your account, device and wallet activity.

Clear data purposesWallet reference checksRequest path included
gem188 Privacy Policy for gem188 Accounts
CONTACT THE TEAM

Privacy Questions Reach Support

A clear contact route helps when your Privacy Policy question involves a login, phone number or wallet reference.

Account privacy Send a message through our account support channel when you need to know which…
Wallet references If a DANA, OVO, GoPay or QRIS reference appears incorrectly, tell us the date…
Access requests For a copy, correction or deletion request, contact support using the details attached to…
DATA HANDLING

What We Do With Your Details

Our Privacy Policy separates information needed to operate your account from details used to answer your messages.

Account details

We use your account identifier, contact details and phone verification result to create and protect the profile you asked us to access. These fields also help support match a Privacy Policy request to the right account instead of disclosing details to another person.

Device records

When you sign in from a mobile browser or desktop, we may record device and session signals such as browser type, time and security events. This helps us review unfamiliar access and does not give support a reason to request your device passcode.

Cookies

Cookies and similar storage can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage browser storage, but removing it may require another login or affect the policy request flow.

Payment matching

Transaction references let us connect a DANA Fast Transfer, QRIS deposit, bank transfer or virtual account event with your account status. We use the minimum reference needed for matching and do not ask for your DANA, OVO or GoPay PIN.

Retention choices

We retain records for as long as they support account security, transaction checks, support history or a legal requirement. When a request can be completed sooner, we assess whether the related data can be removed or reduced under local rules.

Your requests

You can ask us to access, correct or clarify personal data through support. State the request plainly and use your linked account contact. We may verify your phone before sharing details, and we explain why a request cannot proceed when local law restricts it.

Privacy Policy Questions About gem188

These Privacy Policy answers cover the practical questions we hear before an account is opened or a wallet status is checked. We keep the wording specific to gem188, including phone verification, mobile access, transaction references and requests sent to support. If your situation is unusual, contact us through the account route so we can assess the details under local law.

The gem188 Privacy Policy covers account details, phone verification, device and login events, support messages, cookies and payment references. It explains why we use each category, who may need access for account operation, how retention is assessed and how you can ask for access or correction.

We use phone verification to connect account access and privacy requests to the correct person. It can help protect your profile when a sign-in looks unfamiliar or when you ask about stored data. We will not ask for your password, PIN or full wallet secret.

Yes. The Privacy Policy covers references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use a reference, date or status detail to match a transaction path, not your wallet PIN. Ask support if a displayed reference needs correction.

Contact support from the email or account details linked to your gem188 profile and state that you want an access request. Include the account identifier, not a password. We may complete phone verification first, then explain what can be provided and any limit that depends on local law.

You can ask us to correct inaccurate account or contact details through support. Describe the field that is wrong and provide the updated value through the linked account route. We may verify your phone before making the change, especially when it affects account access or wallet matching.

We keep information for the period needed for account security, transaction matching, support history or applicable legal duties. The period differs by record type. If you ask about retention, support can explain the relevant purpose and assess whether deletion or reduction is available where local law permits.

Yes. The Privacy Policy applies when you sign in through a mobile browser or desktop browser. Device and session signals may be recorded for access security, while cookies can support login settings. You can manage browser storage, although doing so may require another phone verification step.