Reference

tugu66 Privacy Policy for Clear Account Choices

Your account, device and wallet details receive a clear explanation in the tugu66 Privacy Policy, so you can decide what to share before opening access.

Account data explainedWallet records describedYour contact path
tugu66 tugu66 Privacy Policy for Clear Account Choices
HELP WITH DATA

Support for Privacy Policy Requests

A clear support route helps when your Privacy Policy question concerns a login record, phone check or wallet status.

Account questions Ask us to clarify which account details support phone verification or login checks.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the relevant…
Policy changes If our Privacy Policy wording changes or you want to ask about a data…
DATA HANDLING

How tugu66 Handles Your Policy Choices

We keep the Privacy Policy practical by linking each data point to an account action you can recognise.

Account details

We use the details you submit during account opening and phone verification to create access, respond to account requests and connect your profile with the correct payment status. We do not need your wallet password for these checks.

Device signals

When you move from login to the lobby on a mobile browser, device and session signals can help us identify unusual access. These checks support account security and are handled as part of the Privacy Policy rather than used as a public profile.

Cookies

Cookies can keep essential page functions working between login, policy pages and the lobby. Your browser settings control some cookie choices, while disabling necessary cookies may affect account access or the way policy content is displayed.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us match a wallet status or receipt query to your account. Bank transfer and virtual account references may be handled in the same way, without storing a wallet password.

Retention timing

We retain account, device and payment records for the period needed for the stated account, security or legal purpose. When a record is no longer needed for that purpose, our handling follows the applicable deletion or retention process.

Changes and contact

You can ask about the data connected with your account, request a correction or question a policy change through our support path. Include your account identifier, but never send a password, wallet PIN or one-time verification code.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep the wording tied to real steps such as phone verification, mobile login, payment receipt matching and policy contact. If your situation depends on a local rule, access or eligibility depends on local law and our support route can explain the available process where local law permits.

It covers account details, phone verification, device signals, cookies, payment references and contact requests connected with your access. The Privacy Policy also explains retention, security handling and how to ask about correction or access to data linked with your account.

Phone verification helps connect the account step with the person requesting access and supports login checks. We use the result for account handling and security, not as a reason to request your password, wallet PIN or one-time code.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. These references help us match a receipt or wallet status question with the correct account.

We may handle device and session signals from the mobile browser to identify unusual access and protect the account. The policy treats these signals as security data, and they are not displayed as a public profile or used to request wallet credentials.

You can contact us through the support path beside the cashier area and request a correction. Include the account identifier and explain the inaccurate detail, but leave out passwords, wallet PINs and one-time verification codes.

We keep payment references for the operational, security or legal period connected with the transaction and account request. When that reason ends, handling follows the applicable retention or deletion process described by the Privacy Policy.

Use the support contact path shown with the policy and describe the wording or data choice you want clarified. We can explain the change, identify the relevant account process and state whether access depends on local law.