Reference

Privacy Policy For Your sofabet Account

Our Privacy Policy explains how we collect, use and protect the details connected with your sofabet account, including phone verification, device access and wallet status.

Account dataDevice choicesWallet checksPolicy access
sofabet Privacy Policy For Your sofabet Account
CONTACT OUR TEAM

Ask About Data, Login Or Wallet Records

A clear contact route matters when a privacy question is tied to your account.

Account privacy request Use the account support path to ask what personal details are linked to your…
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears in your account history, send…
Access and device help When a new phone or browser changes your login path, contact us through the…
HOW WE HANDLE IT

Check The Details Behind Our Privacy Policy

The Privacy Policy is designed around the information your account actually creates: sign-in activity, verification steps, device sessions, wallet status and messages sent to support.

Account data use

We use your phone and account details to create access, complete phone verification and keep the correct profile connected to…

Cookies and sessions

Cookies and device storage help remember a session, load the right account state and reduce repeated login confusion.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we handle the reference and status information needed to…

Security events

We keep records such as failed access attempts, verification events and device changes to help protect your account.

Retention choices

We retain information only for the period needed for account operation, security investigations, payment reconciliation, dispute handling or legal duties.

Change or access request

You can ask for access, correction or deletion by using the support route connected with your account.

Find Answers About sofabet Privacy Policy

These Privacy Policy answers focus on the account actions you are most likely to question before access. We cover phone verification, device cookies, local wallet references, deletion requests and the route for contacting us. If your situation is specific, use the account support path and describe the record or event you want us to check.

The sofabet Privacy Policy covers account details, phone verification, device sessions, cookies, security records, support messages and payment status references. It explains why we use each category, how long we may retain it and how you can request access, correction or deletion where local law permits.

We use phone verification to connect account access with the correct person and reduce mistaken or unauthorised logins. The verification result becomes part of the account security record. We do not ask you to send a one-time code through support when you contact us.

Yes. The Privacy Policy covers the payment reference and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions. These details help match an account event with a transaction without requiring your password or private verification code.

Cookies and similar storage help maintain your login session, remember account state and load the appropriate policy version. Clearing them can sign you out or require phone verification again. Your browser settings control removal, but some account access steps may then appear again.

You can use the account support path to ask which personal data we hold and how it is used. Include the account phone number and identify the request clearly. We may verify your identity first, and the response depends on local law and applicable record duties.

Yes, you can request a correction or deletion through account support. Tell us which detail is inaccurate or which record you want removed. Where local law permits, we will process the request, although security, dispute, payment or legal records may need to remain.

Contact us through the support route available inside your account and describe the Privacy Policy concern in clear terms. For a wallet record, include its date and visible reference; for a device issue, include the browser or phone change. Never include a password or one-time code.