Reference

Privacy Policy for Your Account Path

mariwd uses this Privacy Policy to explain what account, device and wallet details we collect, why we use them and how you can ask about your data.

Clear data purposesWallet detail controlsPhone verification contextIndonesia access rules
mariwd Privacy Policy for Your Account Path
HELP WITH DATA

Where To Ask About Privacy Policy

A clear contact path matters when a login record, wallet reference or account detail needs checking.

Account help route Use the account help path when you need to ask about personal details, a…
Wallet status query For a DANA, OVO, GoPay or QRIS reference, share the date, amount and visible…
Correction request If your contact detail or account record is inaccurate, send a correction request through…
DATA PRACTICES

What We Handle And Why

Privacy depends on clear handling at each account stage, from the first phone check to a later request about stored details. We separate useful operational records from credentials you should never disclose.

Account details

We may handle the contact and verification details needed to identify your account and complete the account path. This can include a phone number, account identifier and access history, used to match your request with the correct record.

Device signals

When you open the lobby on a phone, tablet or desktop browser, we may receive device and connection signals such as browser type, session time and security markers. These help us recognise unusual access without asking for your password.

Cookies

Cookies or similar storage can keep a session working, remember a selected setting and help us understand whether an account page loads correctly. Your browser controls can manage these files, although some account functions may then need another sign-in.

Account security

Phone verification before account access helps us distinguish an account holder from an unauthorised attempt. We also use access records and security checks around wallet status, while our team will not ask you to reveal a password or wallet PIN.

Retention periods

We keep account, support and payment-reference records only for the period needed for the stated service, security or legal purpose. When a record no longer has a valid reason to remain, our handling process can remove or de-identify it.

Your requests

You can ask what personal details we hold, request a correction or ask whether deletion is available where local law permits. Send the request through account help, confirm ownership when asked and describe the exact record or policy choice you want addressed.

Privacy Policy Answers For mariwd

These Privacy Policy answers address the searches we expect before you open an account or return to an existing one. We focus on practical details: what is collected during phone verification, how DANA and QRIS references are treated, what cookies do on mobile and how to send a request about your personal data.

The mariwd Privacy Policy covers account details, phone verification, device signals, cookies, support requests and payment references. It explains why we use each category, how security checks operate and how you can ask about access, correction or deletion where local law permits.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, such as a visible status, date or transaction reference. We use those details to match an account query and investigate a status issue, not to request your wallet PIN.

Phone verification helps us confirm that the person requesting account access is linked to the correct account. It also supports security checks when you ask about stored data. We use the verification record for account and security purposes described in the Privacy Policy.

You can request a correction through the account help path. Tell us which contact detail or account record is inaccurate, then complete any ownership check we reasonably need. We will assess the request under the Privacy Policy and explain the result or next step.

Cookies or similar storage can keep your session active, remember a setting and help us identify loading problems on a mobile browser. Your browser can restrict them, but the Privacy Policy explains that some account pages may require another sign-in afterward.

We retain personal data for the period needed for the stated account, security, support or legal purpose. Payment references and access records may therefore remain after a session ends. The Privacy Policy allows you to ask what is held and whether removal is available.

Start with the account help route beside the cashier path and describe your request clearly. You may need to confirm account ownership before we discuss private details. Do not include a password, wallet PIN or full payment credential in your message.