Reference

sangkarbet Privacy Policy For Your Account

sangkarbet Privacy Policy explains how we handle the account, wallet and device data used when you open an account, sign in and move between the lobby and payment…

Account dataWallet checksCookie choicesMobile privacyContact path

Explore Our Lobby Read FAQ

What Your Privacy Policy Covers

sangkarbet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you provide during account creation, including your contact details and the verification step used before account access. It also covers records connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account when you choose one of those rails.

1
Device type, browser settings, sign-in time, security events and pages opened may be recorded to protect your account and keep the payment path consistent. We use this data for account operation, fraud checks, support replies and required record keeping, not for unrelated purposes. We may share
2
limited details with payment or technical partners only when needed for these tasks. Requests from Indonesian customers are handled according to applicable rules; access depends on local law and where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP DESK

Get Clear Answers About Your Data

A direct contact path helps when a privacy question appears beside a sign-in or wallet step.

HOW WE HANDLE DATA

Your Privacy Choices Stay Practical

Privacy works best when each data use has a clear reason and an identifiable account step. We separate ordinary sign-in records from payment references, limit staff access to operational needs, and use…

Account data

We collect the details needed to create and maintain your account, such as contact details, sign-in events and verification status. We do not need your DANA, OVO or GoPay password to connect a wallet reference with your account.

Payment references

A QRIS receipt, bank transfer reference or virtual account record can help us match a payment query. We keep the payment detail relevant to that task and do not treat it as permission to inspect unrelated wallet activity.

Cookies and devices

Cookies can keep a sign-in path working and remember security preferences. Device and browser signals help us identify unusual access across mobile and desktop; you can adjust cookie controls in your browser settings.

Account security

Before account access, phone verification may be required to confirm the contact route. We also record security events such as failed sign-ins and session changes so an unfamiliar device can be checked.

Retention period

We retain account, security and payment records only for the operational or legal period that applies to the record. When a retention need ends, the data is deleted, anonymised or placed beyond routine account use.

Changes and contact

You can ask us to correct inaccurate account details, explain a data use or clarify a cookie choice. Send the request through account support with enough detail for ownership checks, and we will respond through the contact route on file.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often before account creation or a wallet check. They explain what we collect, why a device or payment reference may appear, and how you can ask for a change. The answer for your account can depend on local law, the data involved and whether a security or payment record must be retained.

You are reading the sangkarbet Privacy Policy on the privacy-policy page. Keep this page bookmarked if you want to check how account, cookie, device and wallet data are handled before opening an account or completing phone verification.

We may collect contact details, account credentials, phone verification status, sign-in events, device signals, cookie settings and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account may also be recorded.

Device and browser details help us keep a mobile or desktop session secure and identify unusual sign-in behaviour. They can also help restore the correct account path after a session change, but they are handled for security and operation rather than unrelated profiling.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match a status question or receipt without requesting your wallet password.

Contact account support with the detail you believe is incorrect and the contact route used for sign-in. We may ask for phone verification or another ownership check before changing it, especially when the correction affects wallet status or account security.

You can send a deletion request through the privacy contact path. We will assess the request against account security, payment records and applicable retention duties. Where local law permits, data no longer needed for those purposes can be deleted or anonymised.

Yes. Your available rights, response process and any limits on deletion or access depend on local law. We still provide a clear route for questions, corrections and cookie choices, and we explain when a record must remain for security or payment handling.

sangkarbet Privacy Policy For Your Account

Get Clear Answers About Your Data

Your Privacy Choices Stay Practical

Account data

Payment references

Cookies and devices

Account security

Retention period

Changes and contact

Privacy Policy Answers For Indonesia

01 Where can I read the sangkarbet Privacy Policy?

02 What personal data does sangkarbet collect?

03 Why does Privacy Policy mention my device?

04 Does the Privacy Policy cover DANA and QRIS records?

05 How do I correct my sangkarbet account data?

06 Can I ask sangkarbet to delete my data?

07 Does access to my privacy rights depend on local law?

Related Pages