Reference

Privacy terms for your account

Your account, wallet checks and device activity are covered by this Privacy Policy before you open the lobby.

Account dataPayment checksDevice controlsSupport access

Indonesia privacy scope and payments

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

A clear privacy record helps you understand what we store when you create an account, enter the lobby, use wallet rails or contact support. We collect only the details needed to run your account flow: login credentials, phone or email contact, device signals, session logs, payment

1
references and messages you send to us. When you use DANA, OVO, GoPay or QRIS, we keep the transaction reference, time stamp and status so your wallet history can be checked without exposing card-style data we do not need. Access to any account feature depends on
2
local law, and we may ask for extra account checks before processing a privacy request. If you are in Surabaya and switch from mobile to desktop, the same privacy controls follow your account.

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

CONTACT ROUTES

Reach us about your privacy

Privacy questions should reach a support path that can verify you safely before changing account data.

Live chat after login Use the chat bubble after signing in when you need a fast privacy check. We confirm your account session first, then help with data access, correction requests or device activity questions during 10:00-22:00 WIB.

Registered email request Send privacy requests from the email linked to your account so we can match the message to your profile. Include the account name, request type and any payment reference from DANA, OVO, GoPay or QRIS.

Account help form Open Account > Help > Privacy Request when you want a written trail inside the platform. The form helps us separate password issues, wallet record questions and personal data updates without mixing support topics.

ACCOUNT SAFETY

How we handle private data

Privacy protection is part of the account flow, not an extra page hidden away. We check login patterns, store payment references only for wallet reconciliation, and keep support messages linked to the…

Data we collect

We collect account details, contact fields, login time, device type, IP region and wallet references. These records help us keep your session available, answer account questions and match DANA, OVO, GoPay or QRIS activity to you.

Payment record handling

For payment rails, we store the reference number, method name, amount, time stamp and completion status. We use those records to reconcile Wallet > Transaction History and to respond when you ask about a privacy-related payment log.

Cookie and device use

Cookies remember your session, language choice and basic device settings so you do not repeat the same steps each visit. You can clear browser cookies, but you may need to sign in again afterward.

Security checks

Account > Security lets you update your password and review active device behaviour. If we see unusual access, we may pause sensitive privacy actions until you confirm ownership through your registered contact path.

Retention approach

We keep account and wallet records for as long as needed to run your account, resolve disputes and meet lawful record duties. Older support messages may be archived with limited access rather than kept in daily support queues.

Correction requests

If your phone, email or profile detail is wrong, send a correction request from the account help form. We may ask for one recent wallet reference or login detail before changing data tied to your identity.

Privacy questions before joining

These answers cover the privacy checks you may want to understand before opening an account or updating your profile. We focus on account data, payment references, device behaviour, support records and the steps you can take when something needs correction or removal.

We collect the account name, password, contact details, login records, device signals and support messages you provide. If you use wallet features, we also store transaction references needed to match your activity to your account.

Yes. We keep payment method names, reference numbers, time stamps and status results for DANA, OVO, GoPay and QRIS. These records support wallet history checks and privacy requests tied to transaction activity.

Open Profile > Privacy or contact support from your registered email. Tell us which detail is wrong, such as phone or email, and be ready to confirm account ownership before we make the change.

You can request access to account records through the help form after login. We verify your session first, then prepare relevant account, contact, wallet and support records where local law permits.

Cookies keep your session active, remember display settings and help us understand device access patterns. If you clear cookies on Chrome or Safari, the site may ask you to sign in again.

Support messages are limited to staff handling account, wallet or privacy cases. We keep them with the related ticket so your question can be answered without exposing the thread to teams that do not need it.

We keep privacy request records long enough to answer the request, show what action was taken and meet lawful record duties. After that, access may be limited or the record may be archived.

Privacy terms for your account

Reach us about your privacy

How we handle private data

Data we collect

Payment record handling

Cookie and device use

Security checks

Retention approach

Correction requests

Privacy questions before joining

01 What personal data does binggo4d collect when I open an account?

02 Does the policy cover DANA, OVO, GoPay and QRIS records?

03 How can I ask to update my account data?

04 Can I ask for a copy of my account records?

05 How does binggo4d use cookies on mobile and desktop?

06 Who can see my support messages?

07 How long do you keep my privacy request records?

Related Pages