Reference

Privacy Policy for Your senyumtoto Account

senyumtoto explains how we collect, use, protect and remove personal data connected with your account, including details linked to DANA, OVO, GoPay and QRIS activity.

Clear data purposesWallet record controlsMobile access detailsPrivacy request path
senyumtoto Privacy Policy for Your senyumtoto Account
PRIVACY CONTACT

Get Help With a Privacy Request

A clear contact path matters when you want to ask about personal data, correct an account detail or understand a wallet record.

Account support Use the account support path for access, correction or deletion questions.
Wallet record help For a DANA, OVO, GoPay or QRIS record, send the account identifier and the…
Policy questions Questions about this Privacy Policy can be raised through the policy contact route shown…
DATA PRACTICE

What We Do With Your Account Data

We organise personal data around specific account tasks rather than treating every detail as open-ended platform data.

Account details

When you open an account, we use the supplied phone number and related account details to create access credentials, send account messages and connect later support requests. A phone verification step helps us avoid changing or discussing data on an account that you do not control.

Login protection

Sign-in time, browser details and device signals may be recorded to protect your account from unusual access. If a login looks different from your normal path, we may ask for an account check before allowing sensitive changes, including phone or wallet record updates.

Payment matching

We keep payment references needed to match an account action with DANA, OVO, GoPay, QRIS, bank transfer or virtual account processing. We do not need your wallet PIN or one-time code for this matching, and you should never send either through support.

Cookies and devices

Cookies can keep a signed-in session, remember a selected page setting and help us understand whether a mobile browser is loading the correct account path. You can clear or restrict cookies in your browser, though some account functions may then require another sign-in.

Retention choices

We keep account, security and payment references only while they support account operation, dispute handling, fraud checks or a legal requirement. When a record no longer has one of those purposes, our process is to delete it or remove identifying links where practical.

Changes and requests

You may ask us to correct inaccurate personal data, explain a recorded purpose or consider deletion where applicable. Send the request through the policy contact path with enough account detail for verification; we may retain a minimal request record to show how it was handled.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the account and device questions we expect before registration. They explain why we request phone verification, how payment references are used and what steps apply when you want to change or remove personal data. If your situation is not covered, use the privacy contact route with your account identifier rather than sending wallet credentials.

It covers personal data connected with your account, including phone verification, login activity, device details, cookies, support messages and payment references. It also explains our purposes, retention approach, security checks and the path for correction, access or deletion requests where local law permits.

Phone verification helps us connect account access with the person who opened the account. We may use it before discussing private records or changing account details. It also helps us investigate an unusual login without asking you to disclose a wallet PIN or one-time code.

Yes. The Privacy Policy covers the payment references attached to account activity through DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes. We use references for matching and support checks, not for requesting your wallet password, PIN or one-time security code.

You can contact us through the privacy request path and ask what account data is held or request a correction. Include your registered phone number and a clear description of the change. We verify account ownership first, and the outcome depends on local law and any required record retention.

Cookies may keep your sign-in session, remember page settings and help the mobile browser load the correct account path. You can clear or restrict them in your browser settings. If cookies are blocked, you may need to sign in again or some account pages may not work as expected.

We retain records while they are needed for account access, security checks, payment matching, dispute handling or a legal requirement. After the relevant purpose ends, we aim to delete the record or remove identifying links where practical. Some request or transaction records may need a longer legal period.

Use the privacy contact route linked from our site or account support area and describe the concern clearly. Include your account identifier, the data involved and the action you want us to take. We may request an ownership check before discussing private details, and access depends on local law.