Reference

Privacy Policy For Your ringbet Account

Our ringbet Privacy Policy shows what we collect when you open an account, verify your phone, sign in from a mobile device, or select DANA and QRIS for…

Account data clarityDevice access detailsDANA and QRIS contextRequest changes directly
ringbet Privacy Policy For Your ringbet Account
HELP WITH REQUESTS

Get Clear Answers About Your Privacy

A privacy question should not get lost beside a wallet query, so we keep a direct route for account-data requests.

Account privacy contact Ask what account details we hold, why a field is needed, or how a…
Access request route Request a copy of personal details linked to your account through the privacy contact…
Correction and deletion Tell us which detail is incorrect or which request you want considered.
HOW WE HANDLE DATA

Privacy Controls Around Every Account Step

Privacy is applied at the points you can see: account creation, phone verification, mobile sign-in, wallet selection, and support contact.

Account details

We may collect your phone number, account identifiers, verification results, sign-in time, device type, and connection details.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, we use references and status details to match a…

Cookies and sessions

Cookies can keep your sign-in session working, remember selected settings, and support security checks.

Account protection

Phone verification and sign-in records help us check that an account request comes from the account holder.

Retention periods

We retain account, support, and transaction records only for the period needed for account operations, security checks, dispute handling, and…

Policy changes

If this Privacy Policy changes in a material way, we will place the updated wording on the privacy page and…

Answers Before You Open An Account

These Privacy Policy answers cover the searches we hear before account creation: what ringbet collects, how device and wallet records are used, and how to make a request. We keep the wording practical so you can decide what to share before completing phone verification or opening the lobby on your device.

It covers personal details connected with your account, including phone verification, sign-in records, device data, support messages, cookies, and payment references. It also explains retention, security checks, request rights, and the conditions that apply where local law permits access.

We use your phone number to create and identify your account, complete the clear phone verification step before account access, and help protect sign-ins. It also lets support locate the correct account when you ask about a session or wallet status.

Yes. The policy covers the payment reference, amount or status details needed to match DANA, QRIS, OVO, GoPay, bank transfer, or virtual account activity to your account. We do not need your wallet password or banking login for that matching process.

We may record device type, browser or mobile session details, connection data, sign-in time, and security events. On a phone, clearing cookies can end your session and remove saved choices; these records help us check unusual access without reading private files.

Use the privacy contact route shown on the signed-in account page, or the contact route on the privacy page if you cannot sign in. State that you want an account-data copy and include your registered phone detail for identity checking.

You can request a correction or ask us to consider deletion through the privacy contact route. We check the request first, then assess security, transaction, dispute, and legal needs. Some records may need to remain stored for those reasons.

The policy is written for Indonesian account access, including use of DANA, OVO, GoPay, QRIS, and local bank rails. Access and eligibility depends on local law, so you should check the rules that apply to your location before opening an account.