Reference

Open musa303 Privacy Policy Before Account Access

musa303 Privacy Policy explains how we collect, use, store and update data connected with your account, including wallet records from DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
musa303 Open musa303 Privacy Policy Before Account Access
CONTACT ROUTES

Open the Policy Contact Path

Privacy questions should reach the team that can match your request to the correct account record. We keep the contact route close to login and wallet support, so you can send a precise request without sharing credentials in an open message.

Team online

Account data desk

Use the account support link when you need a copy of data connected with your login, a correction to contact details, or clarification about a verification record.

Wallet record help

For DANA, OVO, GoPay or QRIS data questions, include the relevant date and payment reference. Do not send your password or full wallet PIN with the request.

Policy change requests

Ask us to update, restrict or remove eligible data through the support contact shown after account access. We may check account ownership before making a change.

CONTROL DETAILS

Switch On Clear Data Controls

We handle Privacy Policy requests through practical account checks rather than broad promises. Your request is reviewed against the relevant login, device session or payment reference, and we tell you when a…

Data collection

We collect account details, verification status, sign-in events and payment references needed to operate the requested account path. We avoid asking for unrelated data when a support request can be answered without it.

Cookie choices

Cookies can remember session state and selected preferences. You can review cookie controls in your browser settings, although blocking necessary cookies may interrupt login or account-request screens.

Account security

We use login checks, session records and account ownership checks before discussing sensitive data. Keep your password private and contact us if a sign-in or wallet record looks unfamiliar.

Retention period

We keep records while they support account administration, payment reconciliation, security checks, dispute handling or legal duties. When a record is no longer needed, our retention process removes or separates it.

Requesting changes

You can ask for access, correction or deletion of eligible account data through the account support path. Include the email or phone linked to your account so we can locate the right record.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references help us trace a submitted payment status. We use those details for matching and support, not for requesting your wallet PIN.

Browse Privacy Policy Questions

These Privacy Policy answers cover the account and wallet questions you are most likely to check before opening access. If your case involves a particular record, send the relevant date, device path or payment reference through the support contact.

It covers account details, verification records, sign-in activity, device data, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use account and device records to confirm access, protect sessions, match support requests, investigate wallet status and keep login screens working across mobile browsers and desktop devices.

Yes. Send an access request through the account support path and identify the linked phone or email. We may verify account ownership before releasing data connected with your request.

Contact us through the policy support route with the incorrect field and the replacement detail. We check the account record first, then update eligible data or explain why a record must remain unchanged.

We use payment references and status details to match a submitted wallet action and answer receipt questions. We do not need your wallet PIN or password for this support process.

Necessary cookies can retain a login session and selected choices. Your browser can block or clear them, but doing so may require another login or interrupt a Privacy Policy request.

It means account access, data handling and any related request are subject to the rules that apply in your location. Eligibility depends on local law, so check the policy before proceeding.