Reference

bar77 Privacy Policy for Your Account

bar77 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use wallet rails such as DANA, OVO, GoPay…

Account detailsWallet recordsCookie choicesAccess requests
bar77 bar77 Privacy Policy for Your Account
PRIVACY HELP PATH

Check Privacy Help Before Contacting Us

A clear support route helps you control your personal details without sending sensitive material through an unverified channel. Start from the support link shown in your account area and describe the Privacy Policy question, the affected account step and the action you want us to take. We may ask for account identifiers, but we will not ask for your wallet password or banking login. Keep payment receipts available when your request concerns DANA, QRIS or a bank transfer record.

Team online

Account access

Use the support link beside the account area when you need to ask about sign-in records, phone verification or a device appearing in your access history. We will explain the checks needed to locate your account without requesting your DANA, OVO or GoPay password.

Wallet record query

For a Privacy Policy question about a cashier record, include the payment rail, date and reference shown on your receipt. DANA, QRIS, bank transfer and virtual account references help us find the correct record while keeping unrelated wallet details out of the request.

Change request

Ask through the account support path if you want to correct a contact detail, question a cookie setting or request access to stored data. We may verify ownership before making a change, so keep the account phone available and do not send a wallet PIN.

DATA HANDLING STEPS

Browse bar77 Data Handling Steps

Our Privacy Policy is applied through ordinary account and device controls rather than hidden settings.

Collection

We collect account details when you open an account or complete phone verification, then add sign-in, device and session records as you use the service. Browsing Baccarat, kungdomtoto or other lobby areas can create technical logs used to keep the requested page available.

Payment references

A DANA, OVO, GoPay or QRIS receipt may contain a reference, amount and time that help us match an account event. Bank transfer and virtual account records serve the same checking purpose. We do not need your wallet password or bank login to perform that match.

Cookies

Cookies can keep your session, remember a selected language or help us understand whether the Privacy Policy link opened correctly. You can adjust cookie controls in your browser, although blocking required cookies may sign you out or prevent account pages from loading.

Account security

Phone verification, sign-in records and device signals help us check that an account request comes from the account holder. If a new phone or desktop behaves unexpectedly, support may ask you to repeat an account step before discussing stored details.

Retention

We keep account, payment and support records for the period needed to operate the account, resolve a receipt question or meet a legal requirement. When a record is no longer needed, we remove it or separate it from direct account identifiers where practical.

Your request

Send a data access, correction or deletion question through the support path linked inside your account. Tell us which detail or record you mean, such as a phone number or QRIS reference. We verify ownership first, then explain the available action and timing.

Browse Privacy Policy Answers for bar77

These Privacy Policy answers cover the account questions Indonesian customers usually raise before opening an account. We keep the wording practical: what is collected, how wallet references are used, how a phone or desktop is recognised, and how to ask for a copy or correction. If your situation is not covered, use the support path inside your account and include only the details needed to locate the request.

It covers account and contact details, phone verification, sign-in and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, access requests, corrections and deletion options where local law permits.

Phone verification helps us connect the account request with the person seeking access and reduces mistaken or unauthorised changes. We record the verification result and related access event, not your wallet password. If verification fails, use the account support path rather than sending a PIN.

No. We may retain a DANA or QRIS payment reference, time and status so we can match a receipt with the correct account. We do not need your wallet password or banking login for that check. Never include those credentials in a support request.

Device and sign-in signals help us keep your account session working and identify unusual access from a phone or desktop. Cookies can remember session settings and policy choices. You can adjust optional cookies in your browser, while required cookies may be needed for account pages.

Yes, where local law permits. Use the support link in your account and specify the data request, such as contact details, sign-in history or a payment reference. We verify account ownership before responding, then explain what can be supplied and any applicable limits.

Send a correction request through the account support path and identify the affected field, such as your phone number or contact detail. We may request a verification step before changing it. A receipt reference from GoPay, OVO or bank transfer can help locate the right record.

We retain records for as long as they are needed for account operation, payment matching, support questions, disputes or legal requirements. After that period, we remove or de-identify them where practical. If you ask about a specific record, include its account step or reference.