Reference

gim33 Privacy Policy For Indonesia

Your gim33 Privacy Policy page explains what we collect, why we use it and how you can ask us to update or remove eligible details.

Clear data purposesWallet record contextCookie choicesAccount request path

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

gim33 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy describes how we receive, use, store and disclose details connected with your gim33 account. That can include contact details, login events, device signals, verification results, support messages and transaction references. When you select DANA, OVO, GoPay or QRIS, we may retain the payment

1
status and reference needed to match your account activity, while the wallet provider handles its own records under its terms. Bank transfer and virtual account references can be handled in the same way. We use these records to maintain account security, answer requests and resolve payment
2
mismatches. Access or eligibility depends on local law, and any request that conflicts with a legal retention duty may need to remain stored for the required period.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY SUPPORT

How To Ask About Your Data

A clear support route helps you check a privacy matter without repeating your account story across several places.

Account privacy request Sign in to your account and send a privacy request through the displayed support route. Tell us whether you need access, correction or deletion of eligible details, and we may ask for an account step to confirm that the request is yours.

Wallet record check For DANA, OVO, GoPay or QRIS questions, include the transaction reference and approximate date rather than your wallet password. We can compare the reference with our account record and explain what we retain for payment matching.

Login or device concern If your phone, browser or session looks unfamiliar, contact us through the policy support path and describe the device event. We can review account access signals, help secure the session and keep the privacy request attached to your account.

DATA PRACTICES

How We Handle Account Privacy

We keep this policy practical by linking each privacy question to a real account action: a login, a cookie setting, a wallet reference or a support request.

Account details

We may use your submitted account details to create, maintain and protect access. Phone verification can be part of the account path before entry, and the related result helps us identify the correct account when you ask for a data copy or correction.

Device and session data

A mobile browser and a desktop browser can produce different session signals, such as device type, language, time and security events. We use those signals to detect unusual access and investigate a privacy concern without needing the contents of your personal device.

Cookies and storage

Cookies or similar storage can remember a session choice and support account security. Your browser settings let you clear or restrict them, although doing so may require another login. Our policy route explains how to ask which cookie purpose relates to your visit.

Payment references

For a QRIS scan, DANA status or bank transfer, we may retain a reference, amount status and timestamp needed to reconcile the account record. We do not need your wallet PIN for that check, and you should never send one in a support message.

Retention decisions

We keep records only for the purposes described in this policy and for periods shaped by account, security or legal needs. A deletion request may not remove a payment or verification record immediately when a rule requires us to preserve it.

Changing your details

Ask us to correct an inaccurate phone detail, contact record or account reference through the policy support path. We may verify the request against your account step before making a change, helping prevent another person from altering your privacy record.

Privacy Policy Answers For gim33

These Privacy Policy answers address the searches we hear most often about account records, wallets, cookies and access. If your situation is different, use the policy support route with a short description and the relevant account reference. Please do not include a password, wallet PIN or full payment credential in your message.

The gim33 Privacy Policy explains how we handle account details, phone verification, device signals, cookies, support messages and payment references. It also describes your route to request access, correction or deletion where local law permits, while some records may remain subject to legal retention duties.

We can receive details you submit during the account path, including contact and verification details, plus technical events such as browser type, login time and security signals. If you use DANA, OVO, GoPay or QRIS, we may also receive a transaction reference and status.

DANA and QRIS create payment events that need to be matched with the right account. We may retain a reference, status and timestamp for that purpose, but your wallet PIN belongs with the payment provider. The same approach can apply to OVO, GoPay and bank transfer records.

Yes, send an access request through the support route displayed on the policy page or inside your signed-in account. State the account identifier and the records you want to understand. We may ask for a verification step before releasing details connected with your account.

Use the same policy support path and describe the inaccurate field, such as a phone detail or contact record. Include the correct value only when necessary. We may compare the request with your account step before changing the record, so another person cannot edit it.

The period depends on the type of record and the reason it was collected. Login events may support account security, while DANA, QRIS, OVO, GoPay, bank transfer and verification references may need longer retention for reconciliation or legal duties.

Sign in and use the privacy support route shown in your account when possible. If you cannot sign in, use the contact path displayed on the Privacy Policy page and provide a short description plus an account reference. Never send a password or wallet PIN.

gim33 Privacy Policy For Indonesia

How To Ask About Your Data

How We Handle Account Privacy

Account details

Device and session data

Cookies and storage

Payment references

Retention decisions

Changing your details

Privacy Policy Answers For gim33

01 What is the gim33 Privacy Policy about?

02 What data can gim33 collect when I open an account?

03 Why does the Privacy Policy mention DANA and QRIS?

04 Can I request a copy of my gim33 account data?

05 How do I ask gim33 to correct my personal details?

06 How long does gim33 keep payment or login records?

07 How can I contact gim33 about a privacy concern?

Related Pages