Reference

mari wd Privacy Policy Explained Clearly

The mari wd Privacy Policy explains what account, device and payment details we collect, why we use them and how you can ask about them.

Account dataWallet recordsCookie choicesPhone verification
mari wd mari wd Privacy Policy Explained Clearly
CONTACT OUR TEAM

Get Privacy Policy Help Before You Act

A direct support path helps you resolve a privacy question without guessing which account screen to use. Tell us whether your question concerns phone verification, a wallet reference, a cookie choice or a request about stored details. We ask you to contact us through the support route shown on the mari wd site and include the account contact detail that helps us locate the request. Do not send a password or full payment credentials. We may need to verify account ownership before discussing personal data.

Team online

Account questions

If you want to ask how the Privacy Policy applies to your account, contact support from the account help path. Include your registered contact detail and a short description of the record you want us to check, such as phone verification or a sign-in event.

Wallet records

For a DANA, OVO, GoPay or QRIS question, share the payment date, rail name and reference shown in your account. We can use that information to locate a status record without asking you to disclose a wallet password or private security code.

Data requests

To ask about correction, access or removal of personal details, state the request plainly through our support contact route. We may ask for an account check first, then explain what can be changed under the Privacy Policy and where local law permits.

DATA HANDLING

What We Do With Privacy Policy Requests

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We use details such as your contact information and phone verification result to create and maintain your account. The same records help us match a sign-in request to the correct account and respond when you ask about account data under this Privacy Policy.

Payment references

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may receive a reference, amount status and related timing record. These details help us trace the requested payment action without storing your wallet password.

Device sessions

Your browser or mobile session may provide device and connection signals used to recognise repeated access and identify unusual activity. We use these signals for account protection and troubleshooting, not as a substitute for the phone verification step.

Cookie choices

Cookies can support sign-in flow, page settings and session continuity. You can manage available cookie controls through your browser or the site prompt, although restricting some cookies may affect the way account pages or the lobby load.

Retention period

We keep personal data for as long as needed for the purpose described, account support, security checks or an applicable legal requirement. When a record is no longer needed, our handling follows the retention and deletion process available to us.

Change requests

You can ask us to explain, correct or remove personal details by using the support route and completing any ownership check. Whether we can fulfil a request depends on local law, the record involved and any continuing account or legal need.

Privacy Policy Answers For mari wd

These Privacy Policy answers address the account and wallet questions you may have before opening an account or when checking an existing record. We describe the practical route for requesting help, changing details and understanding device or cookie data. If your situation is not covered here, contact us through the support path shown on the site. We can ask for a simple ownership check before discussing information linked to your account.

The mari wd Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains why we use these records and how to ask about them.

Phone verification helps connect you with the correct account and supports account protection during sign-in or an account change. We may use the verification result when handling a Privacy Policy request, but you should never send your password or security code through support.

Yes. The Privacy Policy covers payment references and status details created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These records help us trace the requested account action, while sensitive wallet credentials remain outside a support message.

Use the support contact route shown on the mari wd site and ask for access to your personal data. Include your registered contact detail and the scope of your request. We may verify account ownership first, then explain the available response under local law.

You can request a correction through support by identifying the account detail that appears inaccurate and stating the replacement clearly. We may ask for an ownership check before changing it. The available action depends on local law and the purpose for retaining the record.

On a mobile browser, cookies may support sign-in, session continuity and selected page settings. You can adjust available controls through the browser or site prompt. Restricting cookies may change how account pages load, but it does not remove the need for phone verification.

We keep personal data for the period needed for its stated purpose, account support, security checks or an applicable legal requirement. The period can differ by record, such as a phone verification result or QRIS payment reference. Contact us to ask about a specific record.