Reference

belanja4d Privacy Policy For Your Account

belanja4d Privacy Policy shows how we handle the account details, device signals and wallet records connected with your access.

Clear data purposesWallet record controlsPhone verification contextMobile access details

Browse Our Lobby Read FAQ

How Our Privacy Policy Applies

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

Our Privacy Policy covers data you provide during account opening, including your phone number and details needed to check account access. It also covers technical records from your browser or mobile device, such as login time, session activity and cookie choices. When you use DANA, OVO,

1
GoPay, QRIS, bank transfer or a virtual account, we retain the transaction reference needed to match wallet status, payment receipts and account requests. We use these records to operate access, investigate stalled wallet status and protect the account from unusual login attempts. We do not describe
2
access as available everywhere: eligibility depends on local law, and our handling follows the account route shown to you. If you disagree with a policy change, contact support before continuing to use the account.

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

CONTACT ROUTES

Privacy Help Beside Your Account Path

A privacy question should not disappear inside a general payment request. Use the support chat linked from your account when you need to ask about a phone record, cookie choice or wallet…

Account support chat Ask us to locate the Privacy Policy section connected with your account, explain a stored phone detail, or clarify why a DANA or QRIS reference appears in a support response.

Wallet record request For OVO, GoPay, bank transfer or virtual account records, send the payment reference through the account support route so we can check status without requesting your wallet password.

Correction contact If your account detail is inaccurate, contact us from the signed-in device path and state the field to change; we may ask for phone verification before processing the request.

DATA PRACTICE

What We Keep And Why

We keep this Privacy Policy practical by tying each data use to an account action. Login, phone verification, mobile device signals and payment references help us recognise a legitimate session and resolve…

Account data

We use the phone number and account details you submit to identify your account, complete phone verification and respond to a request about access, correction or removal.

Device signals

When you move from mobile login to the lobby, we may record browser, device and session signals to detect unusual access and help restore the correct account path.

Cookie choices

Cookies can keep a session active and remember a selected preference. Your browser settings can restrict cookies, although changing them may affect the way policy choices are retained.

Wallet references

DANA, OVO, GoPay and QRIS references help us match a receipt or wallet status with the correct account. We do not ask for your wallet password through support.

Retention checks

We retain account, session and transaction records only for the operational, dispute and protection purposes connected with the account route, then assess whether continued storage is needed.

Your request

To request a copy, correction or removal of personal data, contact support from your account path. We may verify your phone before confirming the request or sharing account details.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions you may search before opening access. We keep the route specific: check your account area, use the support contact shown there, and remember that eligibility depends on local law.

It covers account details, phone verification, device and session signals, cookie choices, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use your phone number to create and identify the account, complete the phone verification step and protect access when a login or data request appears unusual.

Yes. It covers browser, device and session signals created when you use the mobile path from login to the lobby, helping us recognise a legitimate session and investigate access issues.

We retain the reference needed to match a DANA or QRIS receipt with your account and check wallet status. Do not send wallet passwords or one-time codes to support.

Yes. Contact us through the signed-in support route, name the record or field involved, and complete phone verification if requested. We will explain the available correction or access step.

Send a removal request through account support. We first verify that you control the account, then explain which records can be removed and which may need retention for disputes or protection.

Access depends on local law. Where local law permits, the policy applies to the account route shown to you; if access is unavailable, contact support for the relevant account-data question.

belanja4d Privacy Policy For Your Account

Privacy Help Beside Your Account Path

What We Keep And Why

Account data

Device signals

Cookie choices

Wallet references

Retention checks

Your request

Privacy Policy Answers For Indonesia

01 What does the belanja4d Privacy Policy cover?

02 Why does belanja4d need my phone number?

03 Does the Privacy Policy cover mobile devices?

04 How are DANA and QRIS records handled?

05 Can I request a copy or correction of my data?

06 How do I ask belanja4d to remove account data?

07 Does eligibility change how this Privacy Policy works?

Related Pages