Reference

Open sel toto Privacy Policy with clarity

Our sel toto Privacy Policy explains what we collect when you create an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice accessYour privacy choices
sel toto Open sel toto Privacy Policy with clarity
CONTACT ROUTES

Check your privacy contact path

A clear support route matters when a privacy question sits beside an account or wallet issue. We keep privacy requests connected to the same account path used for login and cashier status, so you can identify the relevant transaction or device without sending sensitive details through an unrelated channel. If you are in Medan or elsewhere in Indonesia, use the support link shown on the site and include your registered phone number only when requested. Access depends on local law.

Team online

Privacy request

Use the site support route to ask what account, device or wallet records we hold. We may ask you to confirm your registered phone number before discussing personal data, so a request reaches the correct account.

Wallet record query

For a DANA, OVO, GoPay or QRIS reference, include the date and payment status shown in your account. We use those details to locate the relevant record without asking you to send a wallet password or full security code.

Access correction

If your name, phone detail or device access record needs correction, tell us through the privacy contact path. We can request an account step or phone verification before making a change that could affect your login.

DATA PRACTICE

Explore how we protect your records

We handle this policy area through practical account controls rather than broad promises. Login events, phone verification and wallet references are separated by purpose so support can investigate a status question without…

Account collection

We request a phone number and account details to create access, complete phone verification and connect your activity to the correct profile. We do not need your wallet password for that account step, and you should never send it to support.

Cookie controls

Cookies can retain a session choice, language setting or security check on your browser. Clearing them may sign you out or require phone verification again. Your browser controls let you remove or block them, subject to the account functions that need these checks.

Login security

We use login events, device signals and phone verification to identify unusual account access. If a new phone or browser triggers a check, complete the requested account step rather than sharing a code with another person.

Retention timing

Account, payment reference and support records remain available only as long as needed for the stated service, security review, dispute handling or legal duty. When a record no longer has a valid purpose, our handling process moves it toward removal or further restriction.

Your data request

You can ask which personal records relate to your account, request a correction, or ask a question about processing through the privacy contact route. We may verify your identity with your registered phone number before responding or changing a record.

Policy contact

Send privacy questions through the support link connected to your account and state whether the issue concerns login, device access, DANA, OVO, GoPay, QRIS or another payment reference. This gives our team a focused starting point for the request.

Browse sel toto Privacy Policy answers

These Privacy Policy answers address the account questions you are most likely to have before opening access. We explain the records linked to phone verification, wallet status, browser use and support requests in plain terms. If your situation is not covered, use the privacy contact route and mention the account step or payment reference involved. Where local law permits, we can assess requests connected with your personal data.

The sel toto Privacy Policy covers account details, phone verification, login events, device and browser signals, cookies, wallet references, support requests and retention. It explains why we use each type of record, how we protect account access and how you can ask about or correct connected data.

Yes. The Privacy Policy covers payment references and status records created when you use DANA, OVO, GoPay or QRIS. We use these details to match an account action with the correct wallet rail. We do not ask you to provide a wallet password through support.

Phone verification helps connect an account to the person completing the access step and helps us detect unusual login activity. It may be requested again after a browser or device change. Keep verification codes private and enter them only in the account path shown on the site.

You can contact us through the privacy support route and ask which personal records relate to your account. Include your registered phone number only when requested. We may verify the request before responding, helping prevent someone else from receiving account, device or wallet details.

Send a correction request through the site support path and describe the account field, device record or payment reference that appears wrong. We may ask you to complete phone verification before changing it. Where local law permits, we assess the request against account security and legal duties.

We retain account, payment reference and support records for the period needed to operate access, protect the account, handle a dispute or meet a legal duty. The exact period can depend on the record and applicable law. Ask through the privacy route if you need a record-specific explanation.

You can manage or remove cookies through your browser settings. Cookies may retain a session choice, language setting or security check, so clearing them can sign you out or require phone verification again. The Privacy Policy explains this browser use, while your device controls let you adjust it.