Reference

tso777 Privacy Policy For Your Account

tso777 Privacy Policy explains what we collect when you open an account, sign in, use the lobby or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet recordsCookie choicesSecurity requests
tso777 tso777 Privacy Policy For Your Account
CONTACT ROUTES

Where To Send A Privacy Request

A clear support route helps you act on this Privacy Policy without searching through unrelated account pages.

Account support path Use the signed-in account support path for a Privacy Policy request about your profile…
Wallet record help For a DANA, OVO, GoPay or QRIS privacy question, attach the relevant receipt reference…
Access trouble If account access stalls before you can reach support, use the site contact route…
DATA HANDLING

What We Do With Your Account Details

Privacy Policy choices matter most when they match the way an account actually works. We connect phone verification, sign-in events and transaction references so we can review an unusual access attempt or…

Collection purpose

We collect account contact details, phone verification results, sign-in timestamps and device signals to provide account access and detect activity that does not match your normal session. A request about collection can be sent through the account support path.

Cookie controls

Cookies can support sign-in continuity, security checks and page settings on your device. You can manage browser cookie controls, although removing some cookies may affect account access or require another sign-in when you return.

Account security

We use phone verification before account access and examine sign-in context when activity looks unusual. Keep your password and one-time codes private; support will not need those secrets to handle a Privacy Policy request.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create references such as amount, time, status and account link. We use these references to check receipts and wallet status, not to request your private wallet password.

Retention approach

We keep account, security and transaction records for as long as needed for account operation, fraud checks, dispute handling or legal duties. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Change requests

You can ask us to correct inaccurate account data, explain its use or request deletion where applicable. Send the request through support with your registered contact detail; we may verify ownership before changing or removing a record.

Privacy Policy Answers For tso777

These Privacy Policy answers focus on the account, device and wallet questions you are most likely to ask before opening or using an account. They explain the practical route for access, correction and contact requests without turning the page into a general lobby description. If your question is not covered, send it through the account support path with enough detail for us to locate the relevant record.

The tso777 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and transaction references. It applies when you browse the site, enter the lobby or contact us about DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm account access and connect a request to the correct account. It also supports security checks when sign-in context changes. We do not ask you to place a password or one-time code in a support message.

Yes. The Privacy Policy covers references linked to QRIS, DANA, OVO and GoPay activity, such as a status, time, receipt reference or account connection. These details help us investigate a payment question without requesting your private wallet credentials.

Use the account support path and describe whether you want access to a record or correction of an account detail. Include your registered email or phone detail, but leave out passwords and one-time codes. We may verify ownership before responding.

You can send a deletion request through support, and we will assess which records can be removed. Some account, security or transaction records may need to remain for operational, dispute or legal reasons. Any access decision depends on local law.

Cookies can keep your session active, support security checks and remember page settings on mobile or desktop. Browser controls let you remove or restrict them, but doing so may require another sign-in or affect parts of the account path.

Contact us through the account support path as soon as you notice an unfamiliar sign-in, naming the approximate time and device if known. Do not send your password. We use the account and device context to investigate the security concern.