Reference

Privacy Policy For Your gl100 Account

Our Privacy Policy explains what data gl100 uses when you open an account, sign in, check wallet status or contact account support.

Account dataDevice choicesWallet recordsYour access rights
gl100 Privacy Policy For Your gl100 Account
ACCOUNT HELP PATH

Get Privacy Policy Help Near Wallet Support

A clear contact path helps when a Privacy Policy question affects your account or wallet record.

Account questions Ask us through the signed-in support path when you need to understand the personal…
Wallet records For a DANA, OVO, GoPay or QRIS record, include the visible reference and approximate…
Correction requests If your account detail is inaccurate, send the requested correction through account support and…
DATA HANDLING PRACTICE

What We Do With Your Privacy Data

Our Privacy Policy follows the practical path your data takes from account creation to support.

Account collection

We collect the details you enter during the account path, including contact data needed for phone verification. We use those fields to identify your profile, provide account access and connect support requests with the correct record, rather than requesting unrelated personal details.

Device signals

When you move from mobile login to the lobby, we may process device, browser and session signals. These details help identify unusual access, keep a session working and investigate login failures. They do not replace the account details needed for verification.

Cookies

Cookies can remember a signed-in session, language choice or selected page state. You can manage browser cookie settings, although restricting them may interrupt account access or require another login. Our Privacy Policy explains why these small files are used on the site.

Payment references

We record the payment route and reference needed to check a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event. We do not need your wallet PIN or full password for a status request, and you should never place those secrets in a support message.

Account security

Phone verification, session checks and limited staff access help protect your profile. If you notice an unfamiliar login, change the relevant account credential and contact us through the signed-in support route. We use the resulting details to assess the security event.

Retention requests

We keep records only for the operational, dispute or legal reasons described in the Privacy Policy. You can ask which data is held, request a correction or ask about deletion through support. Some records may remain where a legal or security need requires continued retention.

Privacy Policy Questions About gl100

These Privacy Policy answers address the account questions you are most likely to have before opening access. We keep the wording tied to actual steps: phone verification, mobile sessions, payment references, cookies, retention and contact requests. Where a right or access condition depends on the rules that apply to you, we explain that clearly and ask you to use the account support path for a record-specific response.

The gl100 Privacy Policy covers data collected during account creation, phone verification, sign-in, device access, wallet status checks and support contact. It also explains cookies, payment references, security use, retention and the ways you can request access, correction or removal.

We use your phone number to create and identify your account, complete the required phone verification step and help protect sign-in sessions. If you ask about account data, we may use that number to confirm that the request belongs to you.

Yes. The Privacy Policy covers the payment route and reference connected with DANA, OVO, GoPay and QRIS events, as well as bank transfer or virtual account records when used. We use these details for status checks, reconciliation, support and required record keeping.

You can ask for access to the personal data connected with your gl100 account through the signed-in support path. Tell us the account phone number and the request you are making. We may complete an identity check before releasing account-specific records.

Send a correction request through account support and identify the field that is wrong. We compare the request with your account record and may ask for phone verification. If the change affects a payment reference, include the visible reference but omit wallet secrets.

We retain account, security and payment records for the operational, dispute or legal reasons described in the Privacy Policy. Retention can differ by record type. You can ask support what applies to a particular record and whether deletion is available under the applicable rules.

Yes. Use the account support route to ask about cookies, browser sessions or device signals linked with your access. We can explain the purpose of the data and the available request path. Restricting cookies may require another login or interrupt account access.