Reference

topcer33 Privacy Policy For Your Account

topcer33 Privacy Policy shows how we collect, use and protect the details connected with your account, from phone verification to DANA, OVO, GoPay or QRIS activity.

Account dataWallet recordsCookie choicesAccess requests
topcer33 topcer33 Privacy Policy For Your Account
CONTACT THE TEAM

Get Privacy Help Beside Wallet Status

A clear support route helps when a privacy question appears beside an account or wallet issue. Send your request through the signed-in account support path and describe the specific record, cookie choice or access concern. We may ask for the phone number linked to your account, but never ask you to send a password or full wallet PIN. For a receipt question involving QRIS or bank transfer, include the reference details rather than a full screenshot showing unrelated personal data.

Team online

Account support path

Open support from your signed-in account and select the privacy subject. We use the verified account path to match your request with the correct phone record without asking you to disclose a password.

Wallet receipt check

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and date. We can check the wallet status while limiting the personal details included in your message.

Access request

Ask us to view, correct or discuss stored account data through support. We confirm ownership first, then explain the next step and any record that cannot be changed immediately.

DATA HANDLING

Cookies, Devices And Account Security

Privacy choices work best when they match the way you actually access the account. We record limited device and browser signals to keep sessions consistent, identify unusual sign-in patterns and remember selected…

Phone verification

Before account access, we use the phone detail you provide to complete verification and connect the session to your account. If the number changes, contact support through the signed-in path so ownership can be checked.

Device signals

A mobile browser or desktop session may create technical records such as browser type, device settings and sign-in time. These signals help us investigate suspicious access without reading unrelated files on your device.

Cookie controls

Cookies can keep a session active, remember language or preserve a selected account setting. You can adjust browser controls, although blocking required cookies may interrupt sign-in or the move from account to lobby.

Wallet matching

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we use transaction references to match status with your account. We do not need your wallet PIN for that check.

Retention checks

We assess account, support and transaction records according to their purpose. A closed account request does not always remove a receipt or verification record immediately; we explain the reason and the remaining handling period.

Change requests

You can ask for a correction, access copy or deletion discussion through account support. Include the requested action and the phone detail linked to your account so we can verify identity before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we hear before an account is opened and when a wallet record needs checking. They explain the practical path for data access, cookie choices, account security and contact requests. Where a question concerns eligibility or service access, the answer remains subject to local law and the account details we can verify.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use each record, how long we may retain it and how to contact us.

We use your phone number to complete verification before account access, connect support requests with the correct account and help investigate unusual sign-in activity. If you request a correction, we use the verified account path rather than asking for your password or wallet PIN.

Yes. The Privacy Policy covers technical records created when you use a mobile browser or desktop, such as browser type, device settings and sign-in time. We use these signals for session continuity and account security, not to inspect unrelated content on your device.

We use the transaction reference, date, amount and status needed to match a DANA or QRIS activity with your account and resolve a receipt question. Send only those details through support; do not include a wallet PIN or unrelated personal data.

You can request access, correction or a deletion discussion through the signed-in account support path. We confirm ownership using your account details, clarify the requested record and explain whether a transaction or verification record must remain for an operational or legal reason.

You can change cookie settings in your browser and clear stored cookies from its privacy controls. Required cookies may still be needed for sign-in and account navigation. If a setting causes a session problem, contact support without sending your password.

Access depends on local law and the eligibility checks that apply to your account. Our Privacy Policy explains how related account and verification data is handled, while support can clarify a data request for an account in Indonesia, including Makassar.