Reference

Privacy Policy For Your gtr77 Account

gtr77 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, check DANA or QRIS status, and contact our account help…

Account dataWallet recordsCookie choicesPhone verification
gtr77 Privacy Policy For Your gtr77 Account
HELP WITH YOUR DATA

Privacy Questions Along The Account Path

A clear contact path matters when a privacy request is connected to a stalled login or wallet status. From your gtr77 account, use the account help route and describe the request in plain English, including the phone number linked to your account and the relevant DANA, OVO, GoPay, or QRIS reference. We use those details to locate the right record without asking you to send a wallet PIN. If you cannot access the account, explain that in your request so we can check identity before discussing personal data.

Team online

Account access

For a data request after a failed sign-in, use the account help route shown with your account controls. Include your registered phone number and state whether you need access, correction, or deletion. We check identity before revealing account details.

Wallet records

If a DANA, OVO, GoPay, or QRIS reference appears incorrectly, send the date, rail name, and visible transaction reference through account help. We can compare that record with the account history while keeping your wallet PIN and private credential out of the request.

Policy requests

For questions about cookies, retention, sharing, or a copy of your data, describe the exact Privacy Policy point you mean. We will direct the request to the relevant support path and may ask for phone verification before making a change.

OUR DATA HANDLING

Inside gtr77 Privacy Controls

We handle Privacy Policy requests as account operations, not as a general sales conversation. Sign-in details help us protect access, device signals help us identify unusual sessions, and payment references help us…

Account data

We collect details you provide during account opening, including contact information and phone verification data. Sign-in records help us confirm that a request comes from the account holder. We use this information for access control and privacy requests, not for unrelated account creation.

Cookie settings

Cookies can preserve required session settings when you move from login to the lobby on a mobile browser. Optional cookie choices can be adjusted through the available browser controls. Removing necessary cookies may require another sign-in before account access continues.

Device signals

When you open the account from a phone or desktop, we may record limited device and session signals to detect unusual access. These signals help us investigate a disputed login without treating your device model as proof of identity on its own.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account can be matched to your account activity. We use the reference and status needed for reconciliation, while wallet credentials remain with the relevant payment service.

Retention checks

We review stored records against their purpose: account security, payment matching, support handling, or a duty that applies where local law permits. If a record is no longer needed and no duty requires it, we assess it for removal or de-identification.

Change requests

You can ask us to correct inaccurate account data, explain a processing purpose, provide eligible records, or remove data where applicable. Send the request through account help with enough detail to locate it; phone verification may be required before action.

Privacy Policy Questions About gtr77

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the practical steps for access, correction, cookies, payment references, and deletion without asking you to share sensitive wallet credentials. Eligibility depends on local law, including whether access is available in your Indonesian region.

The gtr77 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, payment references, support requests, retention, and permitted data sharing. It also explains how you can request access, correction, clarification, or deletion of eligible personal data.

Yes. The Privacy Policy covers payment references and status information connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use those details to match an account record, while your wallet PIN stays with the payment service.

Use the account help route and state that you are making a Privacy Policy data request. Add your registered phone number, the record you need, and the reason for the request. We may complete phone verification before providing account-linked information.

You can request a correction when your account information is inaccurate or incomplete. Send the existing detail, the corrected detail, and your registered phone number through account help. We check the request against the account before changing the record.

Our Privacy Policy explains that necessary cookies can keep a mobile browser session working between login and account pages. Browser controls may let you adjust optional cookies. Clearing required cookies can end the session, so you may need to sign in again.

We retain records only while they serve account security, payment matching, support handling, accounting, or a legal duty where local law permits. Retention depends on the record and purpose. We assess older data for removal or de-identification when no need remains.

You can ask for deletion of eligible personal data through account help. Tell us which record you mean and include the registered phone number. We assess the request under the Privacy Policy and applicable local law, since some records may need to remain for security or legal duties.