Reference

sesetoto Privacy Policy for Your Account

Our Privacy Policy explains what sesetoto collects when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record clarityAccount access controlsPolicy request path
sesetoto sesetoto Privacy Policy for Your Account
CONTACT DATA HELP

Get help with a privacy request

A clear contact route helps when you want to ask about account data, correct a detail or question a wallet record. We keep privacy requests separate from general lobby questions, while our account support path can still connect your request to the right transaction or sign-in event. Send the relevant account detail without sharing your password.

Team online

Account contact path

Use the contact option attached to your account area and state that your request concerns the Privacy Policy. We can then locate the correct account record without asking for your password.

Cashier record question

For DANA, OVO, GoPay or QRIS references, include the transaction date and wallet name. We use those details to distinguish a payment query from a request to change personal data.

Access concern

If a new phone or sign-in event appears unfamiliar, contact us through the account help path beside the cashier area. We may ask for account verification before discussing protected details.

DATA CONTROL POINTS

Six ways we handle your data

Privacy work is part of the account flow, from the first phone verification to a later request to correct or remove information.

Account details

We use your phone number and account details to create access, complete phone verification and connect your requests to the correct account. Please keep those details accurate so we can respond safely.

Device signals

A mobile browser or desktop session may provide device and connection signals that help us recognise unusual sign-ins. We use them for access protection, not as a substitute for your account choices.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage browser cookie controls, though some account steps may then need repeating.

Wallet records

DANA, OVO, GoPay, QRIS and bank references help us match an account action with the correct transaction. We retain the reference needed for status checks, disputes and account security.

Retention

We keep personal data only as long as needed for the stated purpose, account protection, dispute handling or legal duties. When retention is no longer needed, we remove or de-identify records where practical.

Change requests

You can ask us to access, correct or clarify personal data through the account contact path. We may verify ownership first, then explain what can be changed and any reason a record must remain.

Privacy Policy questions for Indonesia

These answers address the questions we expect you to ask before opening an account or sending a data request. They cover account access, wallet references, browser behaviour, retention and the steps we take to confirm that a request comes from the account owner.

It covers account details, phone verification, device signals, cookies, wallet references and support records created when you use our services. It also explains your access, correction and data request options.

We use your phone number to create and protect account access, complete the required verification step and connect support requests to the correct account. Keep it current and never share your password.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references for status checks, account support and disputes.

You can contact us through the account privacy path and request access to personal data connected with your account. We may verify ownership before releasing protected details or transaction-linked records.

Send a correction request through the account contact path and identify the field that needs changing. We may confirm your identity, update eligible details and explain why certain transaction records cannot be altered.

Yes. It explains how cookies support sign-in sessions, settings and page performance on a mobile browser or desktop. Browser controls can remove them, but you may need to repeat account steps.

Retention depends on the purpose of each record, including account security, dispute handling and legal duties. When a record is no longer needed, we remove or de-identify it where practical.