Reference

Open bar99 Privacy Policy Clearly

Your account details, wallet records and device access deserve a clear Privacy Policy, so we explain what bar99 collects and why.

Account detailsWallet recordsCookie choicesContact requests
bar99 Open bar99 Privacy Policy Clearly
CONTACT ROUTES

Contact Us About Privacy Policy

A clear contact route matters when a Privacy Policy question affects your account or wallet record.

Privacy request Send a Privacy Policy question through the support contact path and state whether you…
Wallet record If a DANA, OVO, GoPay or QRIS entry looks incorrect, include the payment reference…
Account access When Privacy Policy access is blocked by a sign-in issue, tell us which device…
DATA PRACTICES

See How We Handle Your Data

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We use the details you provide during account creation and phone verification to establish your account record, respond to requests and connect the correct wallet status. Keep your phone number current so we can handle an access or data question accurately.

Cookies

Cookies can remember selected settings and help us understand whether a sign-in session is working. You can manage available cookie choices through the site controls. Changing those choices may affect convenience, but it does not erase the account records covered by this Privacy Policy.

Account security

We use sign-in events, device signals and phone verification status to help protect account access. Never send us a password, PIN or one-time security code in a contact request. If access looks unusual, contact us before changing wallet details.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained to match a cashier event with your account and resolve a status question. We do not need your full wallet credential to locate a payment record.

Retention period

We keep personal details for the time needed to provide account access, protect the service, resolve disputes or meet a legal requirement. When a purpose ends, we remove or anonymise the relevant record according to the retention rules in this Privacy Policy.

Change requests

You can ask us to correct inaccurate details, explain a data use or remove eligible records through the support route. Include your account phone number and request type; we may verify account ownership before making a change.

Find Answers About Privacy Policy

These Privacy Policy answers address the account questions you are most likely to have before opening bar99. We explain the records connected with phone verification, wallet activity, cookies, device access and contact requests in plain English for Indonesia. If your situation is not covered, use the support path with the smallest useful set of account details, and do not include passwords or complete wallet credentials.

The bar99 Privacy Policy covers account details, phone verification, sign-in and device signals, cookie settings, wallet references and contact requests. It also explains why we retain certain records, how we protect account access and how you can ask for access, correction or removal where local law permits.

We use phone verification details to connect an account request with the correct account and help protect the sign-in path. The verification status can also help us investigate an access problem. We do not ask you to place a password or one-time code inside a support message.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account requests. We use those references to match a wallet event with your account and handle a status question without needing your full wallet credential.

You can contact us through the privacy support route to ask what account data we hold. Include the phone number linked to your account and state that you want an access request. We may verify ownership first, and the response depends on local law and applicable retention duties.

Send a correction request through the support contact path, identify the inaccurate detail and provide the replacement value. For example, you may flag a phone number or wallet reference. We may confirm account ownership before changing the record and will explain any limit under local law.

We retain personal data while it supports account access, security checks, payment record matching, dispute handling or a legal requirement. The relevant retention period can differ by record type. When the purpose ends, we remove or anonymise the data as described in the Privacy Policy.

Use the support path for questions about cookies, sign-in sessions or device signals, and mention whether you used a mobile browser or another device path. Cookie controls manage selected settings, while device checks help protect access. Eligibility and access depend on local law.