Reference

Privacy Policy for bidikbet Accounts

The bidikbet Privacy Policy explains what account details we collect, why we use them, and how you can ask about access or changes.

Account dataWallet recordsCookie choicesAccess requests
bidikbet Privacy Policy for bidikbet Accounts
ASK ABOUT PRIVACY

Support Routes for Data Requests

A clear contact path helps when you need an answer about the Privacy Policy rather than a general account reply. Tell us which account step concerns you, such as phone verification, a QRIS receipt, a DANA reference or a login record, and provide only the details needed to locate it. We use the account contact route for identity checks before discussing private information. If access is unavailable, say so in your request and we will explain the next available path where local law permits.

Team online

Policy questions

Ask how the Privacy Policy applies to your account details, login history, cookies or payment reference. Include the email or phone contact connected to your account so we can locate the right record without asking you to send a password.

Correction requests

If your phone, contact detail or account record is inaccurate, tell us which field needs attention and why. We may request an account step or phone verification before changing information, so another person cannot alter your details through a casual message.

Access concerns

When a login attempt or wallet status stalls, describe the device path and the affected rail, such as GoPay, OVO or bank transfer. We use that context to separate an access issue from a Privacy Policy request and route the right response.

DATA HANDLING DETAIL

What We Do With Your Account Data

The Privacy Policy is designed around practical account events: opening access, confirming a phone, matching a wallet reference and responding to a request.

Collection

We collect details you enter during the account path, including contact information needed for phone verification.

Use

We use account and device details to provide access, check a login, connect a payment reference with your account and…

Cookies

Cookies may keep a session available, remember a selected setting or help us understand whether a sign-in path is working.

Security

Phone verification and login checks help us confirm that a Privacy Policy request comes from the account holder.

Retention

We retain a record while it serves the stated account, payment matching, dispute or legal purpose.

Your request

You can ask what personal data we hold, why it is used, how long it is kept, or how to…

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you are most likely to ask before opening access or sending a data request. They cover collection, payment references, cookies, phone verification, retention and corrections. If your question concerns a specific account event, mention the relevant rail or device path so our response can stay precise.

The bidikbet Privacy Policy covers account details, phone verification, login and device signals, cookies, wallet or bank transaction references, retention and requests about your data. It explains how we use those records for account access, payment matching, security and support, subject to local law.

Yes. The Privacy Policy includes references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity when those references are needed to match an account event. We use the reference for that operational purpose and do not publish your payment history.

Phone verification helps us connect the account to the contact detail you provided and helps protect private replies. If you ask about a login record, QRIS receipt or Privacy Policy request, we may use that verification step to check that the request comes from the account holder.

Cookies may support sign-in continuity, remember a selected setting and help us check whether an account path is working. You can adjust cookie controls in your browser. If you block some cookies, the site may ask you to sign in again or may not retain a preference.

You can contact us to request a correction to an account detail such as your phone or contact record. Identify the field and explain the issue. We may request account confirmation before making a change, and we assess the request where local law permits.

Retention depends on the record and its purpose. We keep information while it supports account administration, payment matching, dispute handling or a legal requirement. Ask about a particular login event, wallet reference or phone verification record and we will explain the relevant retention path.

Use our support contact path and state that your request concerns the Privacy Policy. Include the account contact detail and describe the record involved, such as a GoPay status or device login. Do not send your password; we will explain any identity check needed.