Reference

Privacy Policy For Your gim99 Account

gim99 Privacy Policy explains what we collect when you open an account, access Live Baccarat Turbo or use DANA and QRIS, and how we use those details to…

Account dataWallet detailsCookie choicesAccess depends on local law
gim99 Privacy Policy For Your gim99 Account
HELP WHEN NEEDED

Privacy Questions Near Your Account Path

A clear contact route helps when a Privacy Policy question meets a real account issue. We ask you to contact our support path from the account area when login, phone verification or wallet status needs checking, and to include the payment reference rather than sending extra personal details. If you are in Bandung and QRIS status looks unclear, our team can use the receipt and account record to locate the request. Access and eligibility depends on local law, and we explain which policy step applies before handling a request.

Team online

Account contact

Use the support contact path connected to your gim99 account for a Privacy Policy question about phone verification, login records or a request to correct account details. Include your account contact and a short description so we can find the relevant record without asking for unrelated documents.

Wallet status

For DANA, OVO, GoPay or QRIS questions, send the payment reference and approximate time shown on your receipt. We use that narrow detail to check wallet status and explain how the Privacy Policy treats payment records, while you keep wallet passwords and security codes private.

Access request

If you want a copy, correction or removal request considered, contact us through the account support route and name the exact data involved. We may ask for account verification before acting, because the Privacy Policy requires us to protect your account from an unauthorised request.

DATA PRACTICE

What The Privacy Policy Does With Data

We keep the Privacy Policy practical by linking each data use to an account task you can recognise.

Account creation

When you open an account, we collect the details needed to create and maintain that account, then use the phone verification step to confirm access. The Privacy Policy explains the purpose of each required field, so you can distinguish account needs from optional preferences.

Payment records

A DANA, OVO, GoPay or QRIS reference can remain linked to an account record so we can match a receipt with its status. Bank transfer and virtual account references follow the same narrow purpose, helping support investigate a payment without viewing your wallet credentials.

Cookies

Cookies and similar browser storage can remember sign-in preferences, language choices and pages you have opened. You can manage them through your phone browser settings, although removing them may require another login. The Privacy Policy describes this device behaviour in plain terms.

Account security

We use account details, device signals and verification records to help detect unusual access and protect your account. These checks can lead to a request for confirmation before changes are made. Never share a password, wallet PIN or one-time security code with anyone.

Retention period

We retain different records for different periods rather than keeping everything indefinitely. Account, support and payment records may remain while needed for the stated service purpose, dispute handling or legal duties. When a record is no longer needed, our process addresses its deletion or anonymisation.

Changes and contact

You can ask us to correct account details, explain a data use or consider a deletion request through the support contact path. We verify the account before changing records, respond according to applicable requirements and publish Privacy Policy changes on this page when our practices change.

Privacy Policy Answers For gim99

These Privacy Policy answers address the searches we hear most often before account access: what data we collect, why wallet references appear in records, how cookies work on a phone and how to request a change. We keep the answers tied to actual account steps and local payment names. If your situation is different, use the support contact path and describe the specific record or access concern.

The gim99 Privacy Policy covers account creation, phone verification, sign-in records, device and cookie details, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks, your requests and policy changes.

We use phone verification to connect the person opening an account with the account access step and to reduce unauthorised changes. The Privacy Policy treats the verification record as an account-security detail. We do not ask you to send wallet passwords, PINs or one-time codes to support.

Yes. The Privacy Policy covers payment references and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those records to match a receipt, answer a status question and handle account-related payment checks.

Contact us through the support route connected to your account and state whether you want a copy, correction or explanation. Tell us which record is involved, such as a phone detail or QRIS reference. We may verify your account before processing the request under the Privacy Policy.

Cookies can remember sign-in preferences, language settings and recent page choices in your phone browser. If you clear them, you may need to sign in again. The Privacy Policy explains this use, and your browser settings let you remove or restrict cookies where those controls are available.

Retention depends on why a record exists and on applicable legal duties. Account, support and payment references may remain while needed for service, security, dispute handling or required records. The Privacy Policy does not treat every record alike, and we address deletion or anonymisation when it is no longer needed.

Account access and eligibility depends on local law. Where local law permits, we apply the Privacy Policy to the account and payment details used for your access path. If you are unsure, contact support before opening an account and ask about the specific access situation rather than sending extra personal data.