Reference

mashoki Privacy Policy for Your Account

Our Privacy Policy explains what account, device and wallet details we collect when you open mashoki, sign in, or contact support.

Account dataWallet detailsDevice controlsPolicy requests
mashoki mashoki Privacy Policy for Your Account
REQUEST ROUTES

Three Ways to Ask About Privacy

A clear contact route matters when a name, phone number, or payment reference needs correcting.

Account request Use the support path in your account area to ask for a copy, correction…
Payment reference If your request concerns DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account…
Access concern When a sign-in or device event looks unfamiliar, contact account support through the available…
DATA PRACTICES

What We Do With Your Account Data

We keep the Privacy Policy practical by linking each data use to an account task: sign-in, identity checks, wallet matching, fraud detection, or a request from you.

Account records

We use your submitted contact details and verification responses to create and protect your account. The phone or email connected to sign-in can also help us confirm that a privacy request comes from the account holder.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we record references needed to match a payment with your account. We do not need your wallet PIN, card password, or banking login to perform that match.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, language settings, and security checks. You can clear or restrict them through your browser, although doing so may require you to verify your account again.

Device security

We record practical security signals such as device type, browser version, sign-in time, and session events. These signals help us spot unusual account access without treating a device record as a payment credential.

Retention periods

We keep account, payment-reference, and security records while they serve account operation, dispute handling, security checks, or legal duties. When a record is no longer needed, we delete it or remove details that identify you.

Your changes

You may ask us to access, correct, or delete eligible personal details through the account support route. Include the relevant account contact and a short description of the change so we can respond to the right record.

Privacy Policy Answers for mashoki

These Privacy Policy answers cover the account questions Indonesian customers usually ask before opening an account. We explain the data connected to sign-in, wallet checks, cookies, device activity, retention, and access requests in plain terms. If your situation is not listed, use the account support route and include only the details needed to locate your record.

The mashoki Privacy Policy covers details you submit for an account, sign-in and verification records, device and session signals, cookies, payment references, support messages, and retention. It explains why we use each category and how you can request access, correction, or deletion where applicable.

No. Our Privacy Policy does not require us to store your DANA, OVO, GoPay, or QRIS PIN. We use a payment reference, amount, date, and account connection to match a transaction. Never send a wallet PIN, banking password, or one-time security code in a support request.

Device type, browser version, sign-in time, and session events help us protect your account and investigate unfamiliar access. These signals can also keep the account page working across mobile and desktop. They are security and session records, not your wallet password or banking login.

Use the account support path and identify the phone number or email connected to your mashoki account. State whether you want a copy or correction, then name the relevant record. We may ask for account verification before releasing or changing personal details.

We retain payment references only while they support account operation, transaction matching, dispute handling, security checks, or legal duties. This can include DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records. When the purpose ends, we delete or anonymise the record.

Yes. Your browser settings let you clear or restrict cookies and similar session tools. After that change, you may need to sign in or complete a phone verification step again. Some account functions may not work as intended when essential session cookies are blocked.

Our Privacy Policy explains data handling, while account access and eligibility depend on local law. If a local rule affects access from Indonesia, we apply the relevant requirement to the account process. You can still contact support to ask how a specific data request is handled.