Reference

buci4d Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your buci4d account, including phone verification, device access and wallet status.

Account clarityWallet dataDevice securityIndonesia access
buci4d buci4d Privacy Policy For Your Account
PRIVACY HELP PATH

Get Help With Your Privacy Policy

A clear contact route helps you ask what data we hold, why it is used or how an account record can be corrected. Start from the account help path when a phone verification record, wallet reference or sign-in detail needs attention. Include the account identifier and a short description, but do not send your password or a full payment credential. We use the details in your request to locate the relevant record and respond about this Privacy Policy rather than treating the message as a general lobby question.

Team online

Account request

Use the account help path to ask about your Privacy Policy rights, stored contact details or a correction. We may ask you to confirm the account phone number before discussing private records, so the request is connected to the right account.

Wallet question

If a DANA, OVO, GoPay or QRIS reference appears in your account history, mention the rail and date when asking about it. We check the transaction reference against the account record without asking you to reveal a wallet password or security code.

Access concern

For an unfamiliar mobile or desktop sign-in, contact account help with the approximate time and device path. We can review the access record, help secure the account and explain which data was used for the security check.

DATA HANDLING DETAILS

What We Do With Account Records

We separate practical account operations from the data choices explained in this Privacy Policy.

Account details

We use your account contact details to create access, complete phone verification and respond to requests about this Privacy Policy.

Device signals

When you sign in from an Android or iPhone browser, or from desktop, we may record device and connection signals…

Cookie choices

Browser storage can remember a session and selected settings so you do not repeat the same access step on every…

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may include a reference, amount status or timing needed to…

Retention timing

We keep account, security and transaction records for the period needed for the purpose described in this Privacy Policy, including…

Your requests

You may ask what personal data we hold, request a correction, ask about use or seek deletion where local law…

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions we expect you to ask before using buci4d. They explain the practical path for requesting access, correcting details, checking device records and asking about wallet references. If your situation falls outside these examples, use account help and describe the record or access step you want us to examine. We will use the minimum details needed to locate the request and access or eligibility depends on local law.

The buci4d Privacy Policy covers account details, phone verification, device and connection signals, cookie storage, support requests and payment references. It explains why we use each category, how we protect access and how you can ask about, correct or delete data where local law permits.

Phone verification connects an account request to the person seeking access and helps protect private records. We may use the verified phone step when you ask about your Privacy Policy rights, change account details or request information about a DANA, OVO, GoPay or QRIS reference.

Yes. The Privacy Policy covers payment references and status details returned through DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account reconciliation. We use these details to match an account request and resolve a status question, not to collect wallet passwords.

Use the account help path and state whether you want access, a correction or an explanation of use. Include your account identifier and the relevant record, such as a phone detail or device path. We may complete phone verification before discussing or changing private data.

When you sign in through an Android or iPhone browser, we may store device and connection signals for session continuity and security. Desktop sign-ins can create similar records. The Privacy Policy treats these as account-security data, and you can ask what is linked to your account.

We retain each record for the operational, security or legal period connected with its stated purpose. Payment references may remain while a status question or dispute is open. When retention is no longer needed, we remove the record or reduce its link to your account where applicable.

You can ask about deletion through account help, and we will assess the request under the Privacy Policy and applicable local requirements. Some records may need to remain for security, dispute handling or legal duties. We will explain the reason if the full request cannot be completed.