Reference

Open metasui Privacy Policy With Clarity

metasui Privacy Policy shows how we collect, use and protect the details connected with your account, including phone verification, login activity and wallet records.

Account dataCookie choicesWallet recordsPolicy contact
metasui Open metasui Privacy Policy With Clarity
ASK ABOUT PRIVACY

Contact metasui About Your Privacy Policy

A clear contact route matters when you want to change an account detail or ask why a record appears in your Privacy Policy history.

Account support Use the support route from your logged-in account when you need a copy of…
Wallet record help If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share the transaction date…
Security contact Tell us promptly if you suspect an unrecognised login or a change you did…
CONTROL YOUR RECORDS

Browse Privacy Controls Inside Your Account

Your Privacy Policy choices connect to practical account actions rather than a separate device application.

Data collected

We may hold contact details, phone verification status, login events, device signals and payment references needed to operate your account. The Privacy Policy explains why each category is used and which details are not required for ordinary browsing.

Cookie settings

Cookies and similar browser storage can keep sessions working, remember selected settings and help us detect unusual access. Your browser controls let you remove them, although clearing session data may sign you out of the account.

Account security

Phone verification, session checks and device signals help connect access to your account. If the login path looks unusual, we may pause a request while confirming ownership. We will not ask for your password or wallet PIN.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be retained to reconcile account activity and resolve a status question. We use the reference for that purpose, not as permission to access your wallet.

Retention timing

We keep different records for different periods, based on account operations, security checks and legal duties. The Privacy Policy describes the retention approach, and support can explain the relevant category when you ask about a specific record.

Change requests

Ask us to correct contact details, access a copy of eligible records or raise a deletion request where local law permits. Include the account email or phone, and we will confirm ownership before sending private account material.

Find Answers About Privacy Policy Access

These Privacy Policy answers address the account questions you are most likely to have before opening access. We keep the wording practical: what we collect, why wallet references appear, how cookies work, and how you can contact us. If your question concerns a particular login or transaction, use the account support route so we can check the correct record.

The metasui Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references, retention and your request options. It also explains how we respond to access, correction and deletion questions where local law permits.

Those wallet names can appear because we record a payment reference when you use DANA, OVO, GoPay or QRIS for an account transaction. The reference helps us match status and support checks; it does not give us your wallet PIN.

Contact account support from the login path and identify the email or phone linked to your account. State that your request concerns the Privacy Policy and account data. We confirm ownership first, then explain which records can be provided under local law.

Yes. Send the correction request through account support with the affected email, phone or profile detail. We may ask you to complete phone verification before changing it, because an unverified change could redirect account access or payment status messages.

On mobile, cookies and session storage can keep your login path connected while you move from the lobby to account settings. You can clear them in your browser controls. After clearing, you may need to verify your phone and sign in again.

Retention depends on the record type and the operational, security or legal reason for keeping it. Payment references and login events may follow different periods. The Privacy Policy sets out the approach, and support can address a specific record category.

Use the account support channel for a data, cookie, login or wallet-record concern. Include only safe details such as the account contact and transaction reference. Do not send a password, one-time code or payment PIN. Access depends on local law.