Reference

Open the bukti4d Privacy Policy

bukti4d Privacy Policy gives you a clear view of the account, phone, device, cookie and wallet details we handle when you use our services.

Account dataWallet recordsDevice choicesCookie controls
bukti4d Open the bukti4d Privacy Policy
POLICY CONTACT

Contact us about Privacy Policy

A clear contact path helps when you want to ask what a record means or request a change to your personal details. Tell us the account phone number, the relevant date and the subject of your request, without sending a wallet password or full payment credentials. Our support route can help with login records, wallet status references and policy questions, including requests from Surabaya.

Team online

Account request

For a copy, correction or deletion request under the Privacy Policy, contact our account support path with your registered phone number and the specific record you want us to check. We may ask for an account step to confirm that the request belongs to you.

Wallet record

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the date, amount reference and wallet name through the payment-status contact path. We use those details to locate the record without asking you to disclose a wallet password.

Policy request

Questions about cookies, device records or retention can be directed to our policy contact route. Include the page subject, your registered contact detail and the change you want considered; we will explain any identity check or legal reason affecting the request.

DATA PRACTICE

Browse how bukti4d handles your data

Privacy work is part of the account flow rather than a separate promise. We limit collection to details needed for sign-in, requested services, payment matching, security checks and support responses.

Account records

When you open an account, we use the details you submit and the phone verification step to create and protect that account. We may retain sign-in and change history so we can investigate an access question, connect a support request and identify unauthorised changes.

Payment matching

A wallet or bank reference helps us connect a payment request with the correct account and status. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear as selected rail names or references, while sensitive wallet credentials remain with the payment provider.

Device signals

Your browser, device type, operating system, IP address and sign-in time can help us identify unusual account activity. On mobile, these signals may change when you switch browser, clear site storage or move between a phone and another device.

Cookies

Cookies and similar storage can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage browser permissions, although turning off necessary storage may affect sign-in, policy access or the display of account status.

Retention period

We keep personal details only for the period needed for the stated account, payment, security, support or legal purpose. When a record is no longer needed, we remove it, anonymise it or restrict its use where a longer legal hold applies.

Change requests

You can ask us to access, correct or remove eligible personal details, or ask why a record is being used. We may verify your account first, then explain the result, any limits and the next step where local law permits.

Ask about your bukti4d Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or sending a request. We keep the wording practical: what we collect, why a payment reference appears, how device data behaves and what you can ask us to change. If your situation is not covered, use the policy contact path with the smallest useful set of account details.

The bukti4d Privacy Policy covers account details, phone verification, sign-in events, device and browser signals, cookies, support requests and payment references. It explains the purposes for using those details, retention approach, security checks and request options for account holders in Indonesia where local law permits.

Those wallet names may appear because a payment reference or status is needed to match your request with the correct account. We use the reference supplied for that purpose, not your wallet password. Bank transfer and virtual account references can be handled in the same limited way.

We may record device type, operating system, browser details, IP address, sign-in time and session signals. These details help us identify unusual account activity and diagnose page access. Changing from a mobile browser to desktop, clearing cookies or switching networks can change the signals we see.

Yes, you can request a correction by using the policy contact route and naming the account detail that appears wrong. Include your registered phone number and a short explanation. We may complete an account check before changing the record, and we will explain any restriction where local law permits.

We retain each category only while it serves an account, payment matching, security, support or legal purpose. A record may then be removed, anonymised or restricted. The precise period can depend on the record type and applicable law, so a retention question should identify the relevant account event.

Send a request through our policy contact path with your registered phone number, the categories you want to see and an approximate date range. We may verify that you control the account before responding. We will describe the available copy, timing and any lawful reason for limiting disclosure.

Yes. The policy can apply when you sign in from another phone, browser or desktop device. New device signals may trigger an account security check, while cookie settings may differ between devices. Access and eligibility depend on local law, and the same request route remains available.