Reference

semitoto Privacy Policy for Your Account

Lightning Roulette, Rooster Rumble and QRIS account records all need clear handling, so our Privacy Policy explains what semitoto collects, why we use it and how you can…

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

Open the Policy Before Account Access

semitoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide during account creation, including your contact details, phone verification result and selected account settings. It also covers technical records such as browser type, device session and security events used to protect access. When you use DANA, OVO, GoPay, QRIS,

1
bank transfer or a virtual account, we record the payment reference and status needed to match activity to your account; we do not need your wallet password. We use cookies for sign-in continuity, fraud checks and preference storage, and you can manage suitable browser settings before
2
opening the lobby. Records are retained only for the operational, dispute, security or legal purpose that requires them. Access to semitoto and any data request depends on local law. Our policy applies to account activity in Jakarta, Surabaya and elsewhere in Indonesia where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT THE DESK

Switch to Support for Privacy Requests

A direct support route helps when a Privacy Policy question affects your login, wallet status or account record.

HOW WE HANDLE DATA

Browse semitoto Data Controls Clearly

Privacy choices should be practical, not hidden behind broad statements. We separate account details, payment references, device signals and cookie preferences so our support team can address a precise request.

Data collection

We collect details you enter for account access, such as contact data and verification results, plus technical session signals. This lets us identify your profile, protect sign-in and answer a specific privacy request.

Cookie controls

Cookies help keep your browser session connected and remember selected settings. You can adjust browser cookie controls, although restricting necessary cookies may interrupt account access or require another sign-in.

Account security

Phone verification and device-session checks help us distinguish your account activity from an unfamiliar sign-in. Never send a password, wallet PIN or full payment credential through a support message.

Payment references

For DANA, OVO, GoPay, QRIS and bank rails, we use transaction references and status details to match a receipt with your account. The wallet credential itself is not needed for that check.

Retention controls

We keep records for the time needed for account operation, security checks, disputes or legal duties. When a record no longer serves that purpose, our handling follows the applicable retention process.

Change requests

You can ask us to correct account details, explain a data use or address a cookie concern through the account support contact. Include the requested change so we can verify and respond accurately.

Find Privacy Policy Answers Quickly

These Privacy Policy answers focus on the account questions you are most likely to ask before opening access. We explain the records connected with sign-in, device use and local wallets, along with the practical route for correction or review of a data request. If your situation is unusual, the account support contact can check the relevant record.

It covers account details, phone verification, device-session data, cookies, payment references and security events. It also explains why we use each category, how long records may remain and how to request a change.

Yes. The Privacy Policy covers the payment reference and status linked to DANA, OVO, GoPay or QRIS activity. We use those details to reconcile an account record, not to request your wallet PIN.

Phone verification helps connect an account request with the correct profile and supports access protection. We record its result for that account purpose, while any eligibility or access decision depends on local law.

Use the support contact in your account area and state which detail needs correction. Include the connected phone number and relevant record date; we verify the request before changing account data.

We may record browser type, device session and security events connected with sign-in. These signals help identify an unfamiliar access attempt, and they are handled under the Privacy Policy rather than used to collect wallet credentials.

Retention depends on the reason for keeping a record, such as account operation, security, a dispute or a legal duty. We remove or manage it through the applicable process when that reason ends.

Yes. Contact support through the account path with your cookie question or preference request. Browser controls can also restrict cookies, though necessary sign-in settings may then require another session.

semitoto Privacy Policy for Your Account

Switch to Support for Privacy Requests

Browse semitoto Data Controls Clearly

Data collection

Cookie controls

Account security

Payment references

Retention controls

Change requests

Find Privacy Policy Answers Quickly

01 What does the semitoto Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS activity?

03 Why does semitoto need phone verification?

04 How can I request a correction to my data?

05 What device data does the Privacy Policy mention?

06 How long does semitoto keep account records?

07 Can I ask about cookies in the Privacy Policy?

Related Pages