Reference

Privacy Policy For Your vm789 Account

Our Privacy Policy explains what we collect when you open a vm789 account, use DANA, OVO, GoPay or QRIS, and access the lobby from your phone or desktop.

Clear data purposesWallet record detailDirect privacy contact
vm789 Privacy Policy For Your vm789 Account
CONTACT PATH

Privacy Help For Account Questions

A clear contact path helps when your privacy question sits beside a login or wallet issue.

Account access If you cannot complete phone verification or recognise a sign-in device, contact our support route with the account identifier and approximate access time. We use those details to locate the relevant security record without asking you to disclose your password.
Wallet record For a privacy question about DANA, OVO, GoPay or QRIS, include the payment rail and reference shown in your account. We can explain which transaction details we hold and separate a payment-status question from a request to change personal data.
Data request To request access, correction or deletion where available, state the exact account detail concerned and the action you want. We may ask for account verification before responding so another person cannot obtain or alter your private records.
DATA PRACTICE

What We Do With Your Account Data

Privacy depends on practical handling, not a broad promise. We separate account access checks from wallet references, record security events for investigation and use cookies or similar tools to keep your session…

Account details

We may hold your name or chosen account label, phone number, email address and phone verification result. These details connect you to the correct account and help us respond to a data request. Keep them current so an access check does not point to an old contact.

Device signals

When you sign in from a phone, tablet or desktop, we may record browser, device and session signals. This helps us spot an unfamiliar login and protect the path into the lobby. These signals are handled as security records rather than as a public profile.

Cookies

Cookies and related storage can remember a session state, language choice or security step. You can manage browser permissions, but blocking necessary storage may interrupt login or phone verification. We do not describe optional cookie use as a requirement for unrelated account activity.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference, amount, status and time record. We use that trail to match the correct account and investigate a receipt question, while sensitive wallet credentials remain outside our request for support.

Retention period

We keep records only for as long as needed for the stated account, security, dispute or legal purpose. The period can differ between a phone verification event, a cookie session and a payment reference. Ask us about a specific record and we will explain its applicable retention position.

Security requests

If you suspect another device has entered your account, contact us promptly, change your password and complete any requested verification. Tell us the device type and access time rather than sharing credentials. We can review the security trail and explain the next account-protection step.

Privacy Policy Questions For vm789

These Privacy Policy answers address the searches we expect before an account is opened or a wallet is connected. We keep the language direct: you can ask what data we hold, why a device or payment reference appears, and how to request a correction. Where access is discussed, it depends on local law.

The vm789 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. It also explains purposes, retention, security checks and the contact route for data requests.

We use the phone verification record to connect account access to the correct contact and help identify unusual sign-ins. It can also support an account recovery or privacy request. We do not ask you to send a password, wallet PIN or complete payment credential through support.

Yes. The Privacy Policy covers references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account requests. A reference may include the rail, status, time and account match needed to trace a payment question or investigate a dispute.

Contact our support route and identify the account phone number or email, then ask for a copy of the personal data connected to your account. We may verify ownership before responding. Be specific if you want login records, cookie details, phone checks or wallet references included.

You can ask us to correct an inaccurate account detail by naming the field and supplying the replacement value. We may confirm your identity before making a change. Records needed for security, dispute handling or legal duties may remain while the relevant purpose still applies.

There is no single period for every record. A session cookie, device security event, phone verification result and DANA or QRIS payment reference can follow different retention needs. Ask about the specific record through support, and we will explain whether it remains and why.

Use our support contact path for questions about Privacy Policy access, account data or wallet records. Include your account identifier and the subject of the request, without passwords or wallet credentials. Service access depends on local law, and we respond through the available account-support route.