Reference

buislot Privacy Policy for Your Account

The buislot Privacy Policy explains what we collect when you create an account, use the mobile lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet recordsCookie choicesContact requests
buislot buislot Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Near Your Account

A clear contact route helps you ask about the Privacy Policy without repeating your account history. Start from the support contact path linked in your account area, and include the email or phone detail connected to the request. We will use only the information needed to locate the record, confirm your identity, and respond about access, correction, deletion, or wallet-status data.

Team online

Account contact

Use the support contact path inside your account when you want to ask how the Privacy Policy applies to your phone verification, sign-in record, or device session. Include a short description so we can route the request without asking you to send wallet passwords or private payment credentials.

Payment record request

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the payment reference rather than a wallet password. We can check the stored status and explain which transaction details the Privacy Policy allows us to access, correct, or retain.

Access concern

If a new phone or browser shows an unexpected account session, contact us through the account support route before sharing further details. We may ask for a verification step, then review the session record and explain the security action under our Privacy Policy.

SECURITY PRACTICE

How We Apply This Policy

Privacy work is tied to practical account events rather than broad collection. We separate identity details from payment references where the process allows, restrict account actions by access…

Account details

We collect the details needed to open and maintain your account, including contact data and phone verification status.

Payment references

Our records for DANA, OVO, GoPay and QRIS normally identify a transaction through its reference, amount status, and account connection.

Cookies and sessions

Necessary cookies help keep your account signed in and preserve selected privacy choices.

Device security

We record practical security signals such as browser or device session details to identify unusual access.

Retention periods

We keep account, payment, and support records only for as long as needed for the stated service, security checks, dispute…

Changes and contact

You can ask us to correct inaccurate account details, explain stored data, or address a deletion request through the support…

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account and payment questions you may have before opening access. We keep the process tied to real records, such as a phone verification event, a QRIS reference, or a device session. If your question is not covered, use the account support contact path and tell us which part of the policy you need clarified.

The buislot Privacy Policy covers account contact details, phone verification status, sign-in and device-session records, cookie choices, support messages, and payment references. For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, we use the details needed to match status to your account.

No. Our Privacy Policy describes payment references and status checks, not storage of your DANA or OVO password. The same approach applies to GoPay and QRIS. If support needs to check a payment, send the transaction reference through the account contact path instead.

Use the support contact path inside your account and ask for a copy or explanation of the data connected to your account. We may confirm your phone or email first. This verification protects the record and lets us answer the request under the buislot Privacy Policy.

Yes, you can request a correction when an account contact detail, phone status, or payment reference appears inaccurate. Send the request through account support with the relevant record and a short explanation. We may ask for an identity check before changing information.

Cookies help maintain your signed-in session and remember privacy choices, so a mobile browser can return to the account path without losing the selected setting. Clearing cookies through your browser may sign you out and require phone verification before access resumes.

We retain payment and account records only for the service, security, dispute, and legal purposes described in the Privacy Policy. The period can depend on the record and where local law permits. After that need ends, we delete or separate direct identifiers where appropriate.

Yes. Account access and data processing depend on local law and the region connected to your request. If you are in Indonesia, use the account path available to you and contact support if a location or eligibility check prevents access or changes the data shown.