Reference

gg288 Privacy Policy For Your Account

Your account details, phone verification, wallet records and device activity are covered by the gg288 Privacy Policy.

Clear data purposesWallet record controlsPrivacy request pathDevice and cookie details
gg288 gg288 Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact route helps you resolve a privacy question without sending sensitive details through an unrelated message.

Account support route Use the support path beside account access when you need a copy, correction or explanation of data linked with your phone verification. We may ask you to confirm account details before discussing private records.
Wallet record request For a DANA, OVO, GoPay or QRIS record, send the receipt reference through the account support route. We check the status against the account record and avoid asking for your wallet password.
Device access concern If a login appears on an unfamiliar phone or browser, contact us through the account access path and identify the device session. We can explain the security check and the data connected with that request.
DATA PRACTICE

What We Do With Your Details

Our handling process follows the account actions you take rather than collecting data without a purpose.

Account details

We use your account and phone verification details to identify the correct profile, respond to a Privacy Policy request and protect account access. Please keep your password and one-time code private, including when contacting support.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to match a payment status with your account. We need the reference, not your wallet password or full banking login.

Cookies and devices

Cookies can keep your chosen session and help us detect unusual sign-in behaviour. On mobile, your browser may create a device record when you move from login to the lobby; clearing cookies can require another account check.

Account security

We may compare phone verification, sign-in time and device signals before discussing private account data. If you use a shared phone, sign out after checking your account and do not save access codes in the browser.

Retention periods

We keep account, support and payment records only for the period needed for the stated purpose, account administration or a legal requirement. A retention question can be sent through support with the relevant account or receipt reference.

Changes and requests

You can ask us to correct inaccurate account details, explain a data use or provide the route for a deletion request where local law permits. We verify the request first so another person cannot alter your profile.

Privacy Policy Questions About gg288

These answers address the Privacy Policy questions you may have before creating an account, checking a wallet record or contacting us about personal data. If your case involves a particular phone, device or receipt, include that reference through the account support route so we can keep the response specific.

The gg288 Privacy Policy covers account details, phone verification, login devices, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can request a correction or ask about retention.

Phone verification helps us connect you with the correct account and reduce the chance of another person accessing private records. We may use the verification result when handling a support request, but you should never send us your one-time code.

Yes. The policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes. We use those references to identify a transaction question without requesting your wallet password or banking login.

Use the support route connected with your account and state whether you want a copy, correction or explanation. Include the relevant phone number or receipt reference, but not your password. We may verify account ownership before handling the request.

Cookies can retain a session setting and help identify unusual device activity. When you move from login to the lobby on a phone, clearing browser cookies may remove that session and prompt another account check. Your browser settings control cookie removal.

We retain records for the period needed for the stated account, security, support or legal purpose. The exact period can depend on the record type and local requirements. Ask through support with your account reference if you need a retention explanation.

You can send a removal request through the account support route, and we will assess it where local law permits. Some records may need to remain for account security, transaction tracing or a legal requirement. We will explain the applicable outcome.