Reference

Privacy Policy for Your ggwp99 Account

Your ggwp99 Privacy Policy explains what we collect when you create an account, verify your phone, open the lobby on mobile, or use DANA and QRIS for a…

Account dataDevice accessWallet recordsPolicy requests
ggwp99 Privacy Policy for Your ggwp99 Account
PRIVACY SUPPORT

Where to Send a Privacy Request

A clear support path helps you ask what we hold, why we use it, or how to correct an account detail. Start from your signed-in account support route and include the phone number connected to your profile, without sending a password or wallet PIN. We use the account context to locate the right record, while cashier-related questions stay connected to the payment reference that created them. Our support team can also explain a policy request when account access or a device session stalls.

Team online

Account support path

Use the signed-in account support path for a copy of personal details, a correction request or a question about phone verification. Include your account phone number and the subject of the request; we will ask for account checks before discussing private records.

Cashier record help

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, use the cashier support path and provide the relevant reference. We use that reference to separate your payment history from another account and to explain what we retain.

Device access check

If a privacy request follows an unfamiliar login on your phone or desktop, tell us the device path and approximate access time. We can review the session context, help secure the account and continue the request after verification.

DATA HANDLING

What We Do With Account Details

We handle personal details according to the purpose that brought them into the account flow: access, verification, wallet reconciliation, security or support.

Account details

We may hold your phone number, verification result, sign-in events and support messages to operate account access and answer your requests. We do not need your password in a support message, so keep passwords and wallet PINs out of any submitted text.

Payment references

When you use DANA, OVO, GoPay or QRIS, we may retain the payment reference, amount status and related account identifier needed to match a cashier event. Bank transfer and virtual account references may be handled in the same record-matching process.

Cookies and sessions

Cookies and similar session tools can remember that your browser has passed an account step, keep the requested page connected and help identify unusual sign-in behaviour. You can manage browser cookie controls, but changing them may interrupt account access or require another phone check.

Security checks

We use phone verification, sign-in history and device signals to reduce mistaken access to your account. If you move from a mobile browser to desktop, a new check may appear because the session context has changed; this is part of protecting your records.

Retention periods

We keep personal and payment records for the period needed for account security, support handling, transaction matching and applicable legal duties. When a record is no longer needed for those purposes, we remove it, restrict it or separate it from direct account access.

Changes and contact

You can ask us to correct inaccurate account details, explain a data use or provide an available copy through account support. Include the phone number linked to your profile and a clear request; we may verify ownership before making a change or sharing records.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you may have before opening access from Indonesia. We focus on the records created by phone verification, device sessions, wallet references and support contact, so you can choose the right request path without sending unnecessary personal details.

The ggwp99 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can request a correction or available copy.

We may collect your phone number, verification result, account activity, device and browser signals, support messages and payment references linked to your account. We use these details for access, security, transaction matching and support, not as a reason to request your password or wallet PIN.

Yes. The Privacy Policy covers the DANA, OVO, GoPay and QRIS references connected to your account, along with bank transfer and virtual account records. These details help us match a payment status and answer a cashier question without treating them as unrestricted wallet credentials.

Use the signed-in account support path and state whether you want a copy, correction or explanation of a data use. Add the phone number linked to your account, but do not include a password or wallet PIN. We may verify ownership before completing the request.

Cookies and session tools help keep your mobile browser connected after an account step and can support unusual-access checks. If you clear or block them, the lobby may ask you to sign in or verify your phone again. Browser cookie controls remain available on your device.

We retain records for account security, support handling, payment matching and applicable legal duties. The period can differ by record type and local requirement. When a record is no longer needed for those purposes, we remove it, restrict access or separate it from direct account use.

Yes. Send the question through account support and explain the access or data issue without sharing a password. Where local law permits, we will outline the available request path; if a local rule limits the response, we will state that limitation clearly.