Reference

Open Your buas55 Privacy Policy

Our Privacy Policy explains how buas55 uses the details connected with your account, including phone verification, device access and wallet records for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount access choicesCookie controls
buas55 Open Your buas55 Privacy Policy
CONTACT OUR TEAM

Contact Us About Policy Access

A clear contact path helps when you want to ask about a record, correct an account detail or understand a wallet reference.

Account privacy request Ask us to explain, correct or update personal details connected with your account. Include your registered phone number and the specific field you want checked; we may verify account ownership before discussing any record.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, provide the date, amount reference shown in your account and wallet name. We use those identifiers to separate your request from another account without requesting your wallet PIN.
Access and cookie help If a privacy setting, cookie choice or account session behaves differently on mobile, tell us your device type and browser path. We can explain the relevant setting while keeping your password and one-time verification code private.
HOW DATA WORKS

Protect Your Account Data Clearly

We explain the practical controls behind this Privacy Policy so you can make informed choices before using account services. The sections below cover collection, cookies, security, retention, access requests and corrections.

Data we receive

We may receive your phone number, account details, sign-in events, device information and payment references. For example, a QRIS or bank transfer reference can help us connect a deposit question with the correct account record.

Cookie choices

Cookies and similar browser storage can keep a session active, remember a selected setting or help us understand whether a page loads correctly. You can adjust browser permissions, although changing them may require another login on your device.

Account security

Phone verification comes before account access, and we use session and device signals to identify unusual sign-in behaviour. We will not ask you to share a password, wallet PIN or one-time code through a privacy request.

Retention approach

We keep account, security and payment references for the period needed for the stated service, dispute and record purposes. When a record is no longer needed for those purposes, our handling follows applicable retention requirements.

Requesting access

You can ask what personal details are linked to your account by using the support route shown after sign-in. Include the relevant account phone number and request scope so we can verify ownership and return a focused response.

Correcting details

If your phone number, profile detail or account record appears wrong, tell us which value needs correction and why. We may compare the request with account and wallet references before changing a record or explaining why it remains stored.

Browse Privacy Policy Answers

These Privacy Policy answers address the account questions you are most likely to search before opening an account. They explain what we collect, how to request changes and what happens when you use a phone, mobile browser or Indonesian payment rail.

The buas55 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It also explains how we use, protect, retain and correct those records when you access account services where local law permits.

We may store payment references and status details for DANA, OVO, GoPay and QRIS, rather than your wallet PIN. These references help us match an account request, check a transaction status or answer a receipt question without needing your private wallet credentials.

Phone verification links account access to the number you provide and helps us distinguish your request from another account. It also supports security checks when a sign-in comes from a new mobile browser or when account details need to be changed.

Use the support path shown inside your account and state that you are making a Privacy Policy data request. Add your registered phone number, the records you want located and a suitable contact route; we may verify ownership before sharing account details.

Yes, you can ask us to correct an inaccurate phone number, profile detail or account record. Describe the incorrect value and the replacement clearly. We may check the request against account history or a DANA, QRIS or bank transfer reference.

Cookies can keep your session active and remember selected privacy settings in a mobile browser. If you block or clear them, you may need to sign in again or repeat phone verification. Your browser settings control these choices on your device.

Use the support contact route displayed in your signed-in account area and mention Privacy Policy in your request. Include only the details needed to locate the issue, such as your account phone number and payment reference; never send a password or one-time code.