Reference

mata22 Privacy Policy, Clearly Explained

mata22 Privacy Policy shows what we collect during account creation, phone verification, wallet checks and mobile access, and why each detail is needed.

Account dataWallet recordsCookie choicesAccess requests
mata22 mata22 Privacy Policy, Clearly Explained
HELP PATHS

Privacy Questions Reach The Right Route

A clear contact path matters when a Privacy Policy question affects your account or wallet record. Start from the support route connected to your account area and include the phone number on file, the relevant date and the request you want us to check. For a QRIS or bank-transfer query, add the receipt reference without sending a full password or security code. If you are in Bandung or elsewhere in Indonesia, the same account path applies while access depends on local law.

Team online

Account data request

Use the account support path to ask what personal data we hold, why it is used or whether a stored detail needs correction. Include your registered phone number and a short description of the request; we may ask for an account step before discussing private records.

Wallet record check

For DANA, OVO, GoPay or QRIS records, send the transaction date, rail name and receipt reference through the cashier support path. We use those details to locate the record without asking you to share your wallet PIN, password or one-time security code.

Access and cookie help

If a mobile browser keeps returning you to login or a cookie choice is not saving, tell us the device type, browser and visible error. We can direct the request to the correct account route without asking for unrelated personal details.

HANDLING DETAILS

How We Apply This Privacy Policy

The practical parts of our Privacy Policy appear in the account actions you take: phone verification before account access, wallet status checks before a payment record is matched and device signals when…

Account collection

We collect account details when you enter them, including your phone number and verification response. A clear phone verification step helps us connect the right person to the right account before we discuss login records or wallet activity.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount and status record in the account flow. Bank transfer and virtual account records may also be matched to a receipt so a payment question can be checked accurately.

Cookie controls

Cookies can keep a session active, remember a selected language or help us identify a broken page on mobile. You can adjust cookie settings in your browser; removing them may require you to complete the login path again.

Device security

We may use device and browser signals to identify unusual sign-in patterns, such as a changed device or repeated failed access. We do not need your wallet PIN or password to assess that signal, and you should never send either through support.

Record retention

We keep personal and transaction records only for the period needed for account operation, security checks, dispute handling and applicable legal duties. When a record is no longer needed for those purposes, our retention process moves it toward deletion or de-identification.

Changes and contact

You can ask us to correct a detail, explain its use or request deletion where applicable by using the account support route. We may verify ownership first, then record the request, check any retention duty and reply with the available action.

Privacy Policy Answers For mata22

These Privacy Policy answers address the searches we expect before you create an account or continue using the site. They cover account data, wallet records, cookies, device access and requests for changes. If your question concerns a specific transaction or login, use the support route described above and share only the details needed to locate that record.

It covers account details, phone verification, device and browser signals, cookies, wallet references and support records. It also explains why we use those details for account access, security checks, payment matching and legal record needs, with access where local law permits.

We use your phone number to create and identify the account, complete phone verification before account access and help locate a support request. It should match the account path you use; never send your password, wallet PIN or one-time code.

Yes. The Privacy Policy covers payment references and status records created when you use DANA, OVO, GoPay or QRIS, plus bank transfer and virtual account records. We use them to match receipts and investigate wallet questions, not to request your private wallet credentials.

Cookies can maintain your session, save selected preferences and help us identify technical errors in the mobile browser path. You can remove or restrict them through browser settings, though you may then need to complete login and phone verification again.

You can request a correction through the account support route by stating the detail that appears wrong and the phone number linked to your account. We may verify ownership before changing it, then check whether the corrected record affects a wallet or security entry.

We retain records for account operation, security review, payment queries, dispute handling and applicable legal duties. The period depends on the record and its purpose. When those needs end, the record moves through deletion or de-identification according to our retention process.

You may ask for deletion through the account support route, and we will assess the request against account status, security needs, payment records and legal duties. Where a record must remain, we will explain the reason; access itself depends on local law.