Reference

Privacy Policy for vespatogel Accounts

Our Privacy Policy explains how vespatogel handles the details connected to your account, including phone verification, DANA and QRIS activity, device access, and support requests.

Phone verificationWallet recordsCookie choicesAccount requests
vespatogel Privacy Policy for vespatogel Accounts
REQUEST HELP

Three Ways To Ask About Privacy

A clear contact path matters when you want to understand or change a record. Start from the support route shown inside your account, especially if a phone verification, wallet receipt, or device…

Account privacy request Use the support route inside your account to ask what personal details we hold, why they are used, or which account step created the record.
Wallet record question For DANA, OVO, GoPay, QRIS, or bank transfer questions, include the payment reference and date so we can separate wallet status from unrelated account data.
Device access concern If a phone or browser sign-in looks unfamiliar, contact us through account support promptly. We can check the session context and explain the security step attached to it.
DATA CONTROLS

Cookies, Devices, And Account Protection

We handle privacy through ordinary account controls rather than hidden settings. A login on mobile or desktop can create technical records used to keep the session working, while cookies help remember selected…

Account details

We use your phone number and submitted account details to complete verification, connect you with the correct account, and respond to a privacy request without exposing another person’s records.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer, or virtual account reference helps us trace a status question. We do not need your wallet password to investigate that record.

Cookie choices

Cookies may keep a session active or remember a preference on your browser. You can adjust browser controls, although removing them may require another sign-in or reset selected settings.

Device records

We may record device type, browser details, and connection signals around account access. These checks help us identify unusual sign-ins without treating your device as a permanent identity.

Retention decisions

We keep personal records only for the account, security, support, dispute, or legal purpose that requires them. When that purpose ends, we assess deletion, anonymisation, or restricted storage.

Change requests

Ask us to correct an account detail through support, using the account step and contact method already connected to you. We may verify ownership before making a change.

Privacy Policy Answers For Your Account

These questions address the privacy points most relevant before you open an account or use the lobby from Indonesia. Each answer relates to our Privacy Policy, from wallet records and cookies to access, correction, deletion, and the support route used for verification.

It covers account details, phone verification, payment references, support messages, cookies, device signals, retention, and the circumstances in which we may share data with a service provider.

We use your phone number to complete the account access step, connect support with the right record, and help identify an account request. We do not need your wallet password for this process.

Yes. The Privacy Policy covers payment references and wallet status connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account steps, while the payment partner may apply separate terms.

You can request access through the support route inside your account. Include the relevant phone or account detail, and we may verify ownership before explaining the records connected with you.

Contact account support with the detail you believe is inaccurate and the account step where it appears. We will check the request, confirm ownership where needed, and update the record when appropriate.

We retain data for the account, security, support, dispute, or legal purpose requiring it. After that purpose ends, we assess deletion, anonymisation, or restricted storage under applicable requirements.

Yes. Mobile and desktop access may create browser, device, cookie, and session records. These details help maintain sign-in and identify unusual access, and they remain subject to the same policy controls.