Reference

olahbet Privacy Policy for Your Account Data

olahbet Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account clarityWallet recordsCookie choicesSecurity steps
olahbet olahbet Privacy Policy for Your Account Data
PRIVACY CONTACT

Three Ways To Ask About Privacy

A direct support route helps when you need to understand a Privacy Policy request rather than guess which account screen to use.

Account help route Use the account help route for a Privacy Policy question about your name, phone…
Wallet status check For DANA, OVO, GoPay or QRIS records, share the transaction date, amount and reference…
Access recovery path If a privacy request follows a stalled login, tell us which device and sign-in…
DATA HANDLING

Six Practical Privacy Controls

We handle privacy through account actions you can recognise: the phone check before access, wallet references linked to a transaction, device signals used for security and a request path for corrections.

Account details

When you create an account, we may collect your name, phone number and verification details so we can distinguish your account from another person’s request. We use the information for access, account support and security checks, not as a reason to request your password.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and time record. Bank transfer and virtual account records follow the same purpose: matching activity, checking a disputed status and protecting the account without storing your private wallet password.

Device signals

Your phone or browser may send device type, browser version, connection details and security signals when you sign in. We use these signals to notice unusual access and protect the account; they do not replace the identity details required for a privacy request.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage cookies through your browser settings, although turning some off may affect sign-in continuity or the way your Privacy Policy request form works.

Retention periods

We retain account, security and payment records only for the period needed for the stated purpose, account protection, dispute handling or a legal duty. When a request concerns deletion, we explain which records can be removed and which must remain for those reasons.

Change requests

To correct a phone number, ask for a copy of your data or question a retention decision, contact us through the signed-in help route. We may confirm ownership first, then record the request, check the relevant account data and reply through the contact attached to it.

Privacy Policy Questions About olahbet

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the wording practical: what we collect, why a device or wallet reference appears in our records, how to request a change and what happens when local rules affect access. If your situation is specific, use the account help route and avoid sending passwords or one-time codes.

It covers account details, phone verification, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual accounts. It also explains why we use those records, how long some must remain and how you can ask about access or correction.

We may collect the name, phone number and verification details you provide, plus sign-in and security records created by your device or browser. We use these details to provide account access, respond to privacy requests and reduce the chance of another person entering your account.

Yes. A DANA or QRIS payment can create a reference, amount, time and status record linked to your account. We use that record to match the transaction, investigate a status question and protect the account. We do not need your private wallet password for that process.

Use the signed-in account help route and describe the correction, such as an outdated phone number. Include the contact attached to your account and enough detail to locate the record. We may confirm ownership before changing anything, then respond through the contact already associated with your account.

Cookies can maintain your sign-in session and remember page settings, while device and browser signals help us identify unusual access. You can manage cookies in your browser. If you disable certain cookies, the account session or Privacy Policy request form may not work as expected.

We keep records for the period needed for the purpose stated in the Privacy Policy, including account security, payment matching, disputes or a legal duty. If you ask about deletion, we explain whether the specific record can be removed or must remain for one of those reasons.

Yes, you can contact us with a question about the records connected to your account. Access depends on local law, and where local law permits we can explain available access, correction or deletion steps after confirming that you control the account.