Reference

bigo4d Privacy Policy for Indonesian Accounts

Our Privacy Policy explains how bigo4d handles your account details, device signals, cookies and wallet records when you use the lobby.

Clear data purposesWallet record controlsPhone verification contextCookie choices

Explore Our Lobby Read FAQ

How Wallet Data Enters Our Policy

bigo4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your Privacy Policy rights apply to details collected during account creation, login, wallet checks and support conversations. When you choose DANA, OVO, GoPay or QRIS, we receive transaction references and status details needed to match a cashier event with your account; we do not need your

1
wallet password. Bank transfer and virtual account records can include a bank reference, amount and timestamp. We may also record device type, browser path and failed login events to protect account access. Data handling and eligibility depend on local law, and some services may be unavailable
2
where local law does not permit them. The policy applies to bigo4d pages, the mobile browser path and related account contact routes.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

POLICY HELP ROUTES

Where To Ask About Privacy Policy

A direct support route helps when you want to question a record, correct an account detail or ask how a cookie works.

Support chat Use the support chat for a Privacy Policy question about login records, cookies or a DANA, OVO, GoPay or QRIS transaction reference.

Account contact form The signed-in contact form lets us connect a correction or data request to your account without asking you to place private credentials in a message.

Payment status path For a wallet record concern, provide the payment date, rail name and reference shown in your receipt so our support team can trace the correct event.

HANDLING DETAILS

What Our Privacy Policy Covers

We keep the policy practical by connecting each data use to an account action you can recognise.

Account records

We use your account name, phone detail and verification state to identify the correct account during login checks, support replies and requests to amend stored details.

Device signals

Browser type, device path and failed login events may be recorded to spot unusual access. These signals help us investigate an account without requesting your password.

Cookie choices

Cookies can keep a session active and remember selected page settings. You can manage browser cookie controls, though changing them may require another login on mobile.

Wallet matching

DANA, OVO, GoPay and QRIS references help us match a cashier status with your account. We use the reference and status, not your wallet PIN.

Retention periods

We retain a record only for the operational, safety or legal purpose connected with it. A request can ask which category applies and whether removal is available.

Change requests

Ask us to correct, explain or restrict a data use through the signed-in contact form. Include the affected account step, but keep passwords and wallet credentials private.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the account and wallet questions you may search before opening an account. We keep the route specific: identify the record, use the support channel connected to your account and follow any local-law condition that applies to your request or access.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect the right person to an account and reduces mistaken access during support or login checks. We use the verification state for that account purpose, where local law permits.

No. We may receive a payment reference, status and timestamp for a wallet event, but you should never send a DANA, OVO, GoPay or QRIS PIN to our support team.

Sign in, open the account contact form and describe the stored detail you want corrected. Add your registered phone number and the relevant account step, without including a password or wallet credential.

Cookies can support a signed-in session and retain selected page settings on your mobile browser. You can adjust browser controls, although disabling cookies may send you through login again.

Retention depends on why the record exists, such as account support, payment matching, security checks or a local legal requirement. Contact us to ask which category applies to your record.

Yes. Use support chat or the signed-in contact form and state your location and request. Account access and eligibility depends on local law, including where local law permits the service.

bigo4d Privacy Policy for Indonesian Accounts

Where To Ask About Privacy Policy

What Our Privacy Policy Covers

Account records

Device signals

Cookie choices

Wallet matching

Retention periods

Change requests

Privacy Policy Questions Before Account Access

01 What does the bigo4d Privacy Policy cover?

02 Why does bigo4d collect phone verification details?

03 Does the Privacy Policy include wallet PINs?

04 How can I request a correction under the Privacy Policy?

05 How does bigo4d use cookies on my phone?

06 How long does bigo4d keep account data?

07 Can I ask about Privacy Policy access from Indonesia?

Related Pages