Reference

unsurtoto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an unsurtoto account, enter the lobby, or check a wallet status.

Account dataDevice choicesWallet recordsPolicy requests
unsurtoto unsurtoto Privacy Policy for Your Account
CONTACT ROUTES

Choose a Privacy Policy Contact Path

A clear contact path helps you resolve a privacy question without repeating your account story. Start from the account help route when a phone verification record looks wrong, use the wallet-status route when a DANA or QRIS reference needs checking, or send a policy request when you want to ask about access, correction or removal. We use the details already attached to your account to reduce confusion.

Team online

Account access

Use the account help route for a Privacy Policy question about phone verification, login records or a device that no longer appears familiar. We may confirm account details before discussing private records.

Wallet reference

For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, include the receipt reference and approximate date. We check the payment record without asking for your wallet PIN.

Data request

Ask for a copy, correction or deletion through our policy contact path. Tell us which account detail or cookie record concerns you, and we will use account verification before changing private data.

DATA HANDLING

Browse How We Handle Privacy Requests

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

Account details

When you open an account, we collect the details needed to create and verify it. We use your phone verification record to connect an access request with the account you are asking us to discuss.

Device records

A phone or desktop may provide browser, session and device signals during login. We use those signals for account protection and access checks, not as a substitute for your requested privacy contact.

Cookie choices

Cookies can retain language, session and preference settings. Your browser controls whether optional cookies remain, while necessary session cookies may be required to keep an account page open.

Payment references

DANA, OVO, GoPay and QRIS may create receipt or status references connected to an account action. We use those references to check a record, and we do not request your wallet PIN.

Retention checks

We retain records only for the period needed for account security, payment tracing, dispute handling or a legal request. When a record no longer serves that purpose, our process reviews it for removal.

Request verification

Before sharing or changing private data, we may ask you to confirm account ownership through the account access details already held. This prevents a third party from requesting your records.

Find Privacy Policy Answers for unsurtoto

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening an account. If your situation is different, use the relevant contact path and describe the record, device or payment reference involved. Where eligibility is discussed, access depends on local law.

It covers account creation, phone verification, login and device records, cookie choices, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use phone verification to connect an access request with the correct account and to reduce mistaken or unauthorised account discussions. We may verify ownership before sharing, correcting or removing related records.

Yes. The policy covers browser, session and device signals created when you use a phone or desktop. These signals support login checks and account protection, while cookie choices remain controlled by your browser.

We handle receipt and status references linked to account activity so we can check a payment record. We do not ask for your DANA or QRIS wallet PIN, and wallet data remains subject to the policy.

Yes. Send a policy request naming the account detail, device record or payment reference involved. We may confirm account ownership first, then assess the request under applicable law and our retention duties.

Retention depends on the purpose: account protection, payment tracing, dispute handling or a legal request. When a record is no longer needed for those purposes, our process reviews it for removal.

Use the account help route for access records, the wallet-status route for payment references, or the policy contact path for copying, correction or removal. Include only the details needed to identify your request.