Reference

Open The missav123 Privacy Policy Before Account Access

Our Privacy Policy explains how missav123 handles the details connected with your account, including phone verification, device access, and payment records from DANA or QRIS.

Clear data purposesDevice and cookie choicesAccount contact route
missav123 Open The missav123 Privacy Policy Before Account Access
CONTACT PATHS

Reach Us About Privacy Policy Requests

A clear contact path helps when your Privacy Policy question involves an account record, a phone number, or a wallet receipt. We ask you to use the account support route linked near the cashier area and include the email or phone detail connected with your request. That lets us locate the correct record without asking you to send a full payment credential. If you are in Makassar, the same online route applies from a phone or desktop browser, subject to local law.

Team online

Data request

Ask us to explain the personal data linked with your missav123 account. Include your account contact detail and the request type, such as access, correction, deletion, or a question about retention. We may verify account ownership before discussing any record.

Wallet record

For a DANA, OVO, GoPay, or QRIS privacy question, send the receipt reference rather than your wallet password or full security code. We use the reference to check the related account entry and limit the data shared during the reply.

Account access

When a phone verification or sign-in issue exposes a possible privacy concern, contact us through the account help path beside the cashier route. Tell us which device and browser you used, so we can separate an access problem from a data request.

DATA PRACTICES

Browse The Controls Behind This Privacy Policy

Privacy work is part of each account step, from the first phone verification to a later request about stored records.

Account data

We may handle your account contact details, phone verification result, sign-in history, device type, browser details, and requested account actions. The Privacy Policy ties each category to an operating purpose, so we do not treat every record as a general-purpose profile.

Cookie choices

Cookies can keep a session active, remember a selected setting, and help us understand whether a page request completed. Your browser controls whether cookies are accepted. Blocking some cookies may require another sign-in or affect the way a policy choice is remembered.

Phone verification

Before account access or a sensitive data reply, we may compare the request with the phone verification step on file. This check helps us avoid releasing account details to an unverified contact and supports a clearer record of who asked for the change.

Security signals

A new device, changed browser pattern, or repeated sign-in attempt can create a security signal. We use that signal to review the account request and may ask for an additional ownership check. We do not need your wallet password to assess a privacy enquiry.

Retention period

We keep records for the period needed to provide account support, reconcile a DANA or QRIS reference, address a dispute, meet a legal duty, or investigate security activity. When a record is no longer needed for those purposes, our handling follows the stated retention process.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. Send the request through the listed contact route with enough account context to identify you. We may preserve a request history so we can show how the change was handled.

Find Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions we expect you to ask before opening or using a missav123 account in Indonesia. They cover account records, cookies, payment references, device checks, correction requests, and contact steps. The answer for your situation can depend on the account evidence available and on local law.

It covers data connected with your account, phone verification, sign-in activity, device and browser access, cookies, support requests, and payment references. It also explains why we use those records, who may handle a request, how retention works, and how you can ask for access or correction.

Yes. The policy includes payment references linked with an account, such as a DANA receipt or QRIS status. We use the reference to reconcile an account action or answer a support request. Do not send a wallet password, full security code, or unrelated personal details.

You can request a correction when an account detail is inaccurate or no longer current. Use the listed contact route and identify the record you want changed. We may verify phone ownership or another account detail first, then keep a request history showing how the correction was handled.

On a mobile browser, cookies may remember your session and a policy choice. Your browser settings control acceptance. If cookies are blocked or cleared, you may need to sign in again, and a page may not remember the setting you selected during your previous visit.

Device and phone checks help us distinguish your account request from an unauthorised attempt. A new browser, unusual sign-in pattern, or sensitive data enquiry may require an ownership check. The purpose is account protection and request accuracy, not a request for your wallet password.

Retention depends on the record and its purpose. A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference may be kept while needed for account support, reconciliation, disputes, security checks, or legal duties. The policy explains the applicable retention approach for your request.

Use the account support route linked near the cashier area and state that your request concerns the Privacy Policy. Include your account contact detail and a short description of the issue. We may ask for ownership confirmation before sharing, changing, or removing account-linked data.