Reference

velbett Privacy Policy for Your Account

velbett Privacy Policy explains how we use the account, wallet and device details connected with your access.

Account clarityWallet recordsDevice choicesContact path
velbett velbett Privacy Policy for Your Account
CONTACT ROUTES

Check Privacy Questions Through Account Help

A clear contact route helps when you want to ask about a record, correct an account detail or understand a wallet reference. Start with account help beside the cashier path and include the email or phone number linked to your account. We use that matching step to avoid discussing private records with the wrong person.

Team online

Account privacy

Send your privacy question through account help and include the registered contact detail. We can use that account step to locate the relevant record without asking you to share a password.

Wallet records

For a DANA, OVO, GoPay or QRIS question, attach the payment receipt reference rather than a wallet password. This gives our support team a focused path for checking the stored transaction record.

Access support

If the Privacy Policy page or account path does not load on mobile, tell us your device type and browser. We can separate an access issue from a request about personal data.

DATA PRACTICE

Explore How We Handle Account Data

We keep privacy work tied to practical account events rather than vague promises. The sections below explain what we collect, why cookies appear, how account security works, how long records may remain…

Collected details

We may record your contact details, phone verification result, sign-in time, device path and account actions. Payment references from DANA or QRIS help us match a status without storing a wallet password.

Cookies and storage

Cookies and similar storage can remember sign-in preferences, protect a session and measure page behaviour. You can adjust browser controls, though disabling them may affect the Privacy Policy or account path.

Account security

Phone verification, session checks and unusual-login signals help us protect your account. Never send a password or one-time code through support, even when asking about a wallet record.

Retention periods

We retain account, support and payment-reference records for the period needed for service, security, dispute handling and legal duties. The applicable period can vary with the record type and local law.

Data requests

You can ask us to access, correct or clarify personal data linked to your account. Include your registered contact detail and the specific record, such as a GoPay status or device event.

Policy contact

Privacy questions belong in the account-help route, with a payment receipt or account step when relevant. We may verify ownership before discussing records or applying a requested correction.

Browse Privacy Policy Answers for Indonesia

These answers address the searches we hear most often before an account is opened. Each response points back to the Privacy Policy, the account step involved and the local wallet or device detail that may appear in our records.

The velbett Privacy Policy covers account details, phone verification, sign-in events, device data, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank routes.

We use the phone verification result to confirm account access and help protect private records. It can also help us distinguish a genuine account request from an attempt to obtain another person’s data.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references may be used for receipt matching and status checks, while bank transfer and virtual account details can support reconciliation.

Use account help and identify the registered contact detail plus the record needing correction. A request could concern a phone number, device event or QRIS receipt reference, and ownership checks may apply.

Cookies may keep a sign-in session, remember selected settings and help protect the account path on mobile. Your browser controls can limit them, although some account or policy functions may then behave differently.

Retention depends on the record and the reason it was collected. Account, support and payment-reference data may remain for service, security, dispute handling and legal duties, subject to local law.

Yes, where local law permits. Send the request through account help with your registered contact detail and a clear scope, such as device events, wallet references or phone verification records, so we can locate it.