Reference

Privacy Policy for Your vegeta9 Account

Our Privacy Policy explains how vegeta9 handles the details linked to your account, including phone verification, DANA or QRIS payment records, device signals and support messages.

Account dataWallet recordsCookie choicesPolicy requests
vegeta9 Privacy Policy for Your vegeta9 Account
CONTACT PATHS

Get Privacy Help Near Account Access

A clear contact path matters when a privacy question appears beside a login or wallet issue. Use our available support channel from the account area and describe the exact request, such as a phone correction, cookie question or DANA receipt reference. We may ask you to confirm account details before discussing personal data. If you are in Bandung and a wallet status is still pending, include the payment rail, device type and time shown on your screen so we can locate the relevant record.

Team online

Account contact

Send a privacy request from the account contact route and include the email or phone number attached to your vegeta9 profile. We use those details to locate the right record without asking you to send a password.

Wallet evidence

For a DANA, OVO, GoPay or QRIS question, attach the payment reference rather than a full wallet password or security code. This gives our support team a useful status trail while limiting unnecessary exposure.

Access concern

If your login or phone verification appears unusual, tell us the device and browser path you used. We can review the security event and explain the next account step without revealing protected access details.

HANDLING YOUR DATA

What We Do With Account Details

We keep privacy work tied to identifiable account events rather than vague collection. That means separating contact details, wallet references, device signals and support conversations by their operational…

Account creation

When you open an account, we use your phone number and verification result to establish access and reduce mistaken account…

Payment matching

A wallet or bank reference can show which transaction belongs to your account, while the payment provider remains responsible for…

Device signals

Your browser, operating system and connection details may be recorded when you move from a mobile lobby to desktop access.

Cookie choices

Cookies and similar storage can keep a session active, remember selected settings and help us detect access problems.

Retention practice

We keep personal details only for the account, security, support or legal purpose that requires them.

Change requests

Ask us to correct an inaccurate phone detail, clarify a stored payment reference or explain a data use through the…

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the practical questions you may have before opening an account or asking for a data change. We explain the account step, wallet references, cookies, device records and contact process in plain English. If your situation depends on a specific local requirement, access depends on local law and we will handle the request using the applicable rule.

The vegeta9 Privacy Policy covers account details, phone verification, payment references, device signals, cookies and support messages. It also explains why we use those records, how we protect access, how long records may remain and how you can request a correction or clarification.

We may store a transaction reference and status connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use that detail to match your account, investigate a receipt question and handle support; your wallet password and security code should not be sent to us.

Yes. Use the available account contact route and state which detail is wrong, such as a phone number or email address. We may request an account check before changing anything, and any correction or removal request is handled where local law permits.

Our Privacy Policy treats cookies and similar storage as tools for session access, selected settings and security checks. You can adjust permissions in your browser. Blocking required storage may affect the login path, payment status display or form used to send a privacy request.

We may record device and browser signals, such as operating system, browser type and unusual sign-in patterns. These details help us protect your account when you move between a mobile browser and desktop access; they are handled separately from your password.

Retention depends on why a record exists. Account, payment, security and support details may remain while needed for those purposes or for legal and dispute handling. When the reason ends, we delete, anonymise or restrict routine use of the record where appropriate.

Send the request through the available account support contact route and describe the data or policy point clearly. Include your account email or phone reference, but never your password or wallet security code. We may verify account ownership before responding with protected details.