Reference

cubit4d Privacy Policy for Your Indonesia Account

Your account details, wallet references and device choices are covered clearly in the cubit4d Privacy Policy.

Account dataWallet referencesCookie choicesAccess requests
cubit4d cubit4d Privacy Policy for Your Indonesia Account
HELP PATH

Where To Ask About Your Account Data

A clear support route helps when a privacy request and a wallet status appear together.

Account privacy request Use the support path inside your account to ask for a copy, correction or…
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, point us to the…
Access and deletion query Ask us through the same account support route when you want to discuss access…
ACCOUNT SAFETY

Account Security Beyond The Payment Screen

Privacy controls work best when account habits are clear. We describe how data moves from phone verification to the account record, how cookies support the site path, and…

Data handling

We use phone, account and transaction details for stated account purposes, including verification and status matching.

Cookies

Cookies can help keep your account path and selected settings working between pages.

Phone verification

A clear phone verification step helps connect the right person to an account before account access.

Account protection

We limit account-data access to the systems and people handling the relevant task.

Data retention

We retain records for as long as their purpose, account handling needs or applicable requirements call for.

Changing your details

Request a correction through the account support route and tell us which field is wrong.

Privacy Policy Questions From cubit4d Accounts

These Privacy Policy answers address the account questions you are most likely to ask before creating an account or checking a wallet status. We keep the wording practical: what we collect, why it matters, how to request a change and what access depends on in Indonesia.

It covers account details, phone verification, cookie use, device activity connected to the site, payment references and support requests. It also explains purposes, retention, security controls and ways to request changes.

We may collect the phone number and account details needed for creation and verification. If you use DANA, OVO, GoPay or QRIS, we may also handle the related transaction reference and status.

The Privacy Policy does not require us to receive your wallet password to match a payment reference. Do not send wallet credentials through support; use the account path and provide only the requested record details.

Use the support route inside your account and ask for an access request. We may confirm account ownership before providing data, and the available action depends on local law and the record involved.

Yes. Tell us which account field is inaccurate through the account support route. We may request a phone or ownership check, then assess the correction against the record and applicable requirements.

Retention varies by purpose and record type. Verification, cashier references and support correspondence may follow different periods, and we keep each only while account handling or applicable requirements call for it.

Access and eligibility depends on local law. Check the current Privacy Policy and account prompts for your location, and contact support if you need clarification before submitting personal or payment details.