Reference

Open situs sandibet Privacy Policy clearly

Our Privacy Policy explains how we handle the account details behind DANA, OVO, GoPay and QRIS activity, including what we collect before account access and why.

Account clarityWallet contextDevice choicesContact path
situs sandibet Open situs sandibet Privacy Policy clearly
ASK ABOUT YOUR RECORD

Contact us about Privacy Policy requests

A direct support route gives you a practical way to ask about the Privacy Policy, an account record or a wallet reference.

Account help Use the account-help path when you want to ask how the Privacy Policy applies…
Wallet status For a DANA, OVO, GoPay or QRIS reference, include the transaction date and the…
Policy changes If a Privacy Policy section is unclear, send us the heading and your question…
HOW WE HANDLE DETAILS

Explore your Privacy Policy controls

We keep the Privacy Policy connected to actions you can actually take: check the account path before phone verification, use support for a data request, and review the wallet reference attached to…

Account data

We may hold your account name, phone number, verification status and relevant access records so we can create the account path and respond to account questions. We use those details for the stated service purpose rather than asking you to repeat private data in every support message.

Wallet references

Payment records can include a DANA, OVO, GoPay or QRIS reference, or details needed to match a bank transfer and virtual account request. These references help us check status and resolve mismatches without treating a wallet identifier as your account password.

Cookies and sessions

Cookies and similar session tools can remember an active account state, preserve navigation and help us see when a login flow breaks. You can manage browser settings on your device, although changing them may affect the way a Privacy Policy notice or account screen appears.

Account protection

We use phone verification before account access and may examine device or connection signals when a session looks unusual. Keep your password and one-time code private; support will not need either item to explain a data request or wallet status.

Retention approach

We retain records only for the operational, security, dispute and legal purposes described in the Privacy Policy. A payment reference may remain after a session ends when it is needed to reconcile a cashier event or answer an account-access question.

Changes and contact

You can ask us to correct account data, explain a stored record or clarify a policy change through account help. Tell us which field or section concerns you, and we will use the account details needed to verify the request before responding.

Find answers about Privacy Policy access

These Privacy Policy answers focus on the questions we expect you to ask before opening an account from Indonesia. They cover the data connected with phone verification, mobile sessions and local wallet references, plus the route for corrections or clarification. If your case involves a specific account event, use support with the smallest useful set of details.

It covers account details, phone verification, device and connection data, cookies, wallet references and support requests connected with your account. It also explains why we retain selected records, how we protect access and how you can ask for correction or clarification.

We use the phone number to create and verify the account path before access. It can also help us locate the correct account when you ask about a Privacy Policy request. Do not send your password or one-time code to support.

Yes. The policy covers payment references used to match a DANA, OVO, GoPay or QRIS event with your account. It can also apply to bank transfer and virtual account records needed for status checks, reconciliation or a disputed cashier request.

A mobile browser session may create device, browser and connection records that help maintain login state, identify an interrupted session or examine unusual account activity. The Privacy Policy explains the purpose of those records; browser cookie settings can affect session behaviour.

Yes. Send the account-help team the field that appears incorrect and the phone number linked to your account. We may verify your identity before making a change, and we will explain if a record must remain for security, dispute or legal reasons.

Contact support with the section heading, date you noticed the change and your question. We can explain the updated purpose, the affected account or wallet records and any available request path. Access remains subject to local law and the wording shown for your region.

The same policy principles apply when you open an account from Medan, while availability and eligibility depend on local law. Device, phone verification and wallet records are handled for the purposes described here, and support can clarify a location-specific access question.