Reference

to80 Privacy Policy for Your Account

Our Privacy Policy explains how to80 handles the details connected with your account, mobile browser, wallet status and support requests.

Account clarityWallet checksCookie choicesSecure access
Browse Our Lobby Read FAQ
to80 to80 Privacy Policy for Your Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact path matters when you want to know what we hold or why a wallet reference appears in your account. Start from the signed-in support route and include the phone or account identifier linked to your request. We may ask for a payment reference, but we will not ask you to send a password or a full wallet security code. Requests from Indonesia are handled in the same account context used for DANA, OVO, GoPay and QRIS status checks.

Team online

Account support

Use the support path after signing in when your question concerns a phone number, login event, device record or account detail. We can locate the relevant record more accurately when you include the account identifier and the date of the event you are asking about.

Wallet receipt

For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference and selected rail rather than a wallet password. We use those limited details to trace a receipt or status link without asking you to expose the full contents of your wallet.

Access request

If you want a copy, correction or removal request, state the action clearly through account support. We may confirm ownership with the phone verification step before changing records, so another person cannot redirect your account history or device access.

DATA PRACTICE

How We Handle Six Privacy Areas

Our handling process follows the account actions you take rather than treating every visit the same way.

Account data

When you open an account, we record the contact and verification details needed to create that account and protect later sign-ins. Your chosen account identifier helps us connect support questions, wallet references and access requests without asking you to repeat the full history each time.

Cookie controls

Cookies and similar browser records can help retain a login state, remember a selected language or detect an unusual sign-in pattern. On a mobile browser, you can clear site data through browser settings; clearing it may sign you out and remove saved preferences.

Payment references

We retain a reference for a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event so a receipt can be matched to your account. The reference is used for status checks and reconciliation, not as permission to view your separate wallet balance.

Account security

Phone verification before account access helps us distinguish you from someone attempting to use your details. We also use sign-in and device signals to identify unusual activity. Never send a password or complete wallet security code through support, even when asking about privacy.

Retention periods

We keep records only for as long as they serve the purpose explained here, support an open account, resolve a payment question or meet a legal requirement. When a record no longer has a valid purpose, our handling process moves it toward deletion or anonymisation.

Changes and requests

You can ask us to correct an inaccurate contact detail, explain a data use or provide an account-related copy through support. We may need ownership confirmation, and some records can remain where local law permits retention for security, payment matching or dispute handling.

Privacy Policy Questions for to80

These answers address the searches we hear most often about the to80 Privacy Policy. They focus on account records, mobile access, payment references and requests made from Indonesia. If your situation involves a specific DANA, OVO, GoPay or QRIS event, include its reference through the account support route so we can connect the answer to the correct record.

The to80 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access and how you can ask about, correct or remove eligible records.

Phone verification helps connect the person requesting account access with the correct account record. We may use the result when handling a privacy request or unusual sign-in. It does not give us access to your separate DANA, OVO, GoPay or QRIS wallet.

Yes. The Privacy Policy covers the payment reference, selected rail, amount status and account link needed to match a DANA or QRIS event. We do not need your wallet password. Send only the receipt reference through support when asking about a payment record.

Use the signed-in account support path and ask for a copy of your account data. Include your account identifier and the email or phone detail attached to it. We may confirm ownership before responding, and the result depends on local law.

You can ask us to correct an inaccurate contact detail, verification result or account reference through support. Explain what appears wrong and what should replace it. We may retain the original event where local law permits it for security or payment matching.

On a mobile browser, cookies can retain a sign-in state, save a preference or help identify unusual access. You can clear them through your browser settings. After clearing site data, you may need to complete the account login and phone verification steps again.

Send a removal request through account support and identify the records or account concerned. We first confirm ownership, then check whether any record must remain for payment reconciliation, account security or a legal requirement. Where local law permits, eligible data is removed or anonymised.

Related Pages

to80 Indonesia About Us ilegal4d Account information FAQ