Reference

laku toto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, browse Super Sic Bo or check a football market, and…

Account dataWallet recordsCookie choicesAccess requests
laku toto laku toto Privacy Policy for Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path matters when you want to understand a record or correct an account detail. We direct privacy questions through the support route connected to your account, with the relevant login or wallet context attached where possible. You can ask about a payment reference, a phone-verification record or a cookie choice without explaining your question repeatedly. Requests are handled subject to identity checks and where local law permits.

Team online

Account privacy request

Use the support path beside your account area to ask what personal details are linked to your login. We may request account identifiers before discussing records.

Wallet record question

Mention DANA, OVO, GoPay or QRIS and include the transaction reference when asking about payment data. This helps us locate the correct status record.

Correction or deletion

Tell us which detail needs changing or removal, such as an old phone number or device record. We assess the request against account security and local law.

DATA PRACTICES

Six Checks Behind Your Privacy Controls

We keep this policy practical by linking each privacy question to an account action you can recognise.

Account details

We handle the contact and verification details you provide when opening an account or changing access settings. These details support sign-in checks and replies to your privacy requests.

Device activity

A mobile browser or desktop session can create technical records such as device type, browser version and sign-in time. We use them to examine account access concerns.

Cookie settings

Cookies can keep a session working and remember selected settings. Your browser provides controls for clearing or restricting them, although some account functions may then require another sign-in.

Payment references

DANA and QRIS status checks may include a reference, amount status and time received. We use these details to match a payment question without asking for your wallet password.

Retention checks

We assess account, access and transaction records for the period needed for operations, security or legal duties. When a request can be completed, we remove or amend eligible details.

Request identity

Before releasing, correcting or removing personal data, we may confirm your account through the registered phone or another account step. This protects your records from an unrelated request.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the points you are most likely to check before opening an account or contacting us. They cover the data connected with login, mobile access, cookies, local wallets and requests to see or change your records. If your situation is not listed, use the account support route and include enough detail for us to find the relevant record.

It covers account details, phone verification, sign-in activity, device and browser records, cookies, game or market activity, payment references and privacy requests connected with your account.

Yes. The policy covers references and status details created during DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, but not your private wallet password.

Use the support route linked to your account and ask for an access request. Include your registered phone detail when possible; we may verify your identity before responding.

Yes. Send a correction request through account support and identify the old detail. We check the request against phone verification, account security and where local law permits.

Device type, browser version and sign-in time can help us check whether an account access event matches your normal mobile or desktop session.

Cookies can support your session and remember settings. You can clear or restrict them in your browser, though the next account visit may require another sign-in.

We retain records for the operational, security or legal purpose that applies. When that purpose ends, we assess whether eligible details can be removed or amended.