Reference

Privacy Policy for Your ggt108 Account

Our Privacy Policy explains how ggt108 handles the account, wallet and device data you provide when you open an account or enter the lobby.

Account clarityWallet recordsDevice controlsPolicy requests
ggt108 Privacy Policy for Your ggt108 Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact route matters when you want to know what data we hold or why a record appears beside your account.

Account support path Open the support area from your signed-in account and ask about a data record…
Payment record help If a wallet reference looks unfamiliar, send the payment date, rail name and visible…
Privacy request For access, correction or deletion questions, state the request clearly and use the contact…
DATA PRACTICE

How We Handle Account Data

Our handling process follows the practical journey from account creation to a support reply. We separate account details from payment references where our operations allow, use device signals to help identify unusual…

Account details

When you open an account, we handle details such as your phone contact and verification status to create access and connect your requests to the right record. We do not need your wallet password to check a payment reference or answer a policy question.

Device signals

A mobile browser or desktop session can provide device and access signals, such as session activity and browser characteristics. We use these signals to help protect sign-in flow and investigate unusual access, not to read unrelated content on your device.

Cookies

Cookies and similar session tools help keep your account path working between sign-in, the lobby and a payment status screen. Your browser controls whether some cookies are stored, although changing them can affect account access or the way a page remembers your session.

Account security

Phone verification and sign-in checks help us connect an access request to your account. Never send a login code, wallet password or full payment credential in a support message; we only need the limited details required to locate the relevant record.

Retention process

We retain account, access and payment-reference records for as long as needed for the stated service purpose or applicable requirements. When a record is no longer needed, our process removes it, anonymises it or restricts further use where that is appropriate.

Change requests

You can ask us to access, correct or remove personal data through the account support path. Include the record concerned and a safe contact detail; we may confirm account ownership before acting, then reply with the outcome or explain any restriction.

Privacy Policy Answers for ggt108

These common Privacy Policy questions focus on the records you create through account access, mobile sessions and local payment references. If your question is not listed, use the support path in your signed-in account and describe the specific record, date or access step you want us to check.

The ggt108 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we handle each category and how to request access or correction.

No. Our Privacy Policy separates the payment reference needed to match an event from your wallet password or private credential. If you ask about a DANA or QRIS status, send the visible reference and date through support; do not send a password or sign-in code.

Phone verification helps connect an account access request to the person who created the account and helps us respond to account-related requests. We record the verification status and related account details for that purpose, subject to this Privacy Policy and where local law permits.

Yes, you can request access to personal data connected with your account through the signed-in support path. Tell us which record you mean, such as account details, device access or a GoPay payment reference. We may confirm account ownership before preparing a response.

Send a correction request through the account support area and identify the inaccurate field or payment reference. For example, you can point to a phone detail or bank transfer record that does not match your account. We will check the source and explain the next step.

We keep account, access and payment-reference data for the period needed for the stated operational purpose or applicable requirements. After that period, we remove, anonymise or restrict the record where appropriate. A retention question can be sent through the privacy contact route.

The policy is written for the account and wallet flow used in Indonesia, including DANA, OVO, GoPay and QRIS references. Account access depends on local law and is available where local law permits. Your support request is handled through the contact path shown in your account.