Reference

visi4d Privacy Policy for Your Account

The visi4d Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and request account help.

Clear data purposesWallet record contextAccount access rightsCookie choices
visi4d visi4d Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Policy Help Directly

A clear contact route matters when a data request and an account issue arrive together.

Policy questions Open support chat from the login screen and ask about collection, cookies, retention or…
Wallet records For a DANA, OVO, GoPay or QRIS reference, send the relevant receipt number rather…
Correction requests Ask support to correct account details after phone verification.
DATA PRACTICES

How visi4d Handles Policy Requests

We separate account protection from ordinary service records so a Privacy Policy request can be checked without exposing another account.

Account data

We collect details such as your phone number and verification result to create an account and confirm that a request comes from the correct account holder.

Cookie settings

Cookies can support login continuity, security checks and page preferences. Your browser controls can remove or restrict them, although some account steps may then need repeating.

Device signals

A mobile or desktop login may create a security record such as device and session details. We use those signals to spot unusual access and protect your account.

Wallet evidence

Payment references from QRIS, DANA, OVO, GoPay, bank transfer or a virtual account help us reconcile a request. We do not need your wallet password for that check.

Retention timing

We keep records only for the period needed for account service, security checks, dispute handling or applicable legal duties. The exact period can depend on the record type.

Your requests

You can ask about access, correction or eligible deletion through support chat. We verify the account first, then explain any legal or security reason a request cannot be completed.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect before access: what data is collected, why wallet references appear, how cookies work and where to send a request. If your situation involves a specific payment receipt or phone change, use the support route above so we can check the correct account record.

It covers account details, phone verification, device and session records, cookies, support messages, wallet references, retention and your available requests for access or correction.

When you use DANA or QRIS, we may keep a transaction reference to match payment status with your account. We do not need your wallet password to perform that check.

No. Our Privacy Policy describes wallet references and payment status records, not wallet passwords. If support needs evidence, provide the relevant OVO or GoPay receipt reference only.

Open support chat from the login or cashier path and request account data under the Privacy Policy. We first verify your phone and account details before preparing an eligible response.

Yes. Send a correction request through support chat after phone verification. We may ask for the account step that confirms the change belongs to you.

Cookies may keep a session active and support security checks or preferences. You can restrict them in your browser, but login and verification steps may need to run again.

The same account data process applies in Semarang and across supported Indonesian access areas. Account access or eligibility depends on local law, including where local law permits.