Reference

botak bet Privacy Policy For Your Account

Our Privacy Policy explains how we handle the account details connected with Live Roulette, Lucky Fortune Cat and wallet access on your phone.

Account clarityWallet data careMobile access control
botak bet botak bet Privacy Policy For Your Account
REQUEST ROUTES

Account Help For Privacy Requests

A clear contact path matters when you want to ask about the Privacy Policy or the records attached to your account.

Policy questions Send your Privacy Policy question through the account support route.
Data corrections Ask us to correct an account detail when your phone verification record or contact…
Wallet references For a DANA, OVO, GoPay or QRIS record question, provide the payment reference and…
SIX DATA CONTROLS

Six Data Controls For Your Account

We handle this policy area through practical controls rather than broad promises. Account details are separated from ordinary browsing records where our systems allow, payment references are used for the relevant wallet…

Account details

When you open an account, we use the submitted contact details and phone verification result to create and protect your account record. We do not need unrelated profile details for this step.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a requested wallet action. The Privacy Policy explains why each reference may be retained.

Cookies

Cookies and similar device records can keep a session working, remember selected settings and help us detect unusual access. Your browser controls can manage cookies, though some account functions may change.

Account security

Phone verification and account checks help us distinguish your request from an unauthorised change. We may ask for matching details before discussing records or updating access information.

Retention period

We retain personal records for the operational, dispute and legal period connected with their purpose. When that period ends, records are deleted, anonymised or securely restricted where appropriate.

Your requests

You can ask what eligible data we hold, request a correction or ask about deletion through the account support route. We explain any required identity check and any legal reason for limits.

Privacy Policy Questions For botak bet

These answers address the Privacy Policy questions most often raised before account access. They cover the records created during phone verification, mobile browsing and local wallet steps, along with the practical route for asking us to explain or change eligible data.

It covers account details, phone verification, device and browser records, cookies, payment references and support requests connected with our pages and account areas. It also explains retention, disclosures and your request options.

We use phone verification to create an account record, protect account access and check that a data change comes from the right person. The Privacy Policy describes the purpose and handling of that record.

Yes. It covers payment references linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use those references to connect a requested wallet action with the correct account record.

Our systems may record technical details such as browser type, device signals, session activity and security events. These records help keep mobile account access working and identify unusual activity, as explained in the policy.

Use the support contact route in your account area and describe the specific request. Include your account identifier, then complete any identity check we reasonably need before locating or changing eligible records.

Retention depends on the purpose of the record, unresolved account or payment matters and legal duties where local law permits. After the relevant period, we delete, anonymise or restrict the record.

Yes. You can use the listed support contact route to ask about data handling before opening an account. Do not send payment credentials; a general question usually needs no wallet or identity details.