Reference

Privacy Policy For Your mata788 Account

mata788 Privacy Policy shows how we handle your account details, phone verification, cookies and wallet references when you access our service.

Clear data purposesWallet record contextAccount request pathLocal-law wording
mata788 Privacy Policy For Your mata788 Account
CONTACT ROUTES

Privacy Requests From Your Account

A clear contact route helps you act on the Privacy Policy without sending sensitive details to an unknown address. Start from the support path connected to your mata788 account, state the request clearly, and include the relevant login contact or payment reference only when asked. We can use that context to locate the correct record, check whether a phone verification step is pending, and explain the next action. The same route works from a mobile browser in Yogyakarta or from a desktop session.

Team online

Data access request

Ask us to identify the personal details connected with your account through the account support path. Include your registered contact detail, but do not send a password, wallet PIN or full bank credentials. We will use the verification step to confirm the request belongs to you.

Correction request

If your contact detail or account record needs a change, describe the specific field and the reason through support. We may ask for phone verification before making an adjustment, so a request cannot be applied to the wrong account or an unverified session.

Wallet record help

For a DANA, OVO, GoPay or QRIS reference, attach the receipt detail requested by support rather than sharing wallet credentials. We can then match the reference with the account record, explain its status and keep the payment discussion within the privacy process.

DATA PRACTICE

What Our Privacy Controls Cover

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

Account data

We may handle your name, contact detail, login identifiers and verification result so we can connect an account request with the correct profile. If you ask what we hold, we may verify your identity first, then describe the records covered by your Privacy Policy request.

Cookies and browser use

Cookies can keep a session recognised, remember a privacy choice or help us understand an error on a mobile browser. You can review cookie controls in your browser settings, although changing them may affect login continuity or the way an account page loads.

Login protection

Phone verification is used before account access where the security step is required. We also consider sign-in and device signals when checking unusual access. Never send a password or wallet PIN through support; we will not need those credentials to handle a policy request.

Payment references

A DANA, OVO, GoPay or QRIS reference can appear in an account record when you ask us to check wallet status. We use the minimum reference needed to locate the transaction context and do not treat a receipt image as permission to access your wallet.

Retention approach

We keep records for as long as they support the stated account, security or support purpose, or for a period required by applicable rules. When a record is no longer needed, our handling follows the retention process described in the Privacy Policy.

Policy changes

If our data practices change, we update this Privacy Policy and show the revised date or wording on the policy page. Check the page before opening a new account or sending a support request, especially when access or eligibility depends on local law.

Privacy Policy Questions For mata788

These Privacy Policy answers focus on the account steps and local wallet references you are most likely to ask about before opening an account. If your question concerns a record not covered here, use the account support path and describe the specific data or request. We will keep the response tied to your account and the applicable local rules.

The mata788 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your routes for access, correction and other requests.

Phone verification helps us connect account access with the contact detail you provided and helps prevent a request from being applied to the wrong profile. The Privacy Policy explains this use, along with the security records created when you complete that account step.

Yes. A DANA or QRIS receipt reference may be handled when you ask support to check an account-linked payment status. Send only the detail requested, never a wallet PIN or password, and use the account support path so the reference stays connected to the correct request.

Open the support route connected to your account and name the exact field that needs correction. We may request phone verification before changing it. The Privacy Policy allows us to confirm ownership first so another person cannot alter your contact or login record.

You can ask through account support which cookie purpose relates to your session, privacy choice or page error. Browser settings also let you manage cookies on mobile or desktop. Turning some off may affect login continuity, as explained by the Privacy Policy.

We retain personal data while it supports the stated account, security or support purpose, and longer only where an applicable legal requirement calls for it. The exact period can depend on the record type, so request a retention explanation through account support.

Yes. Account access and eligibility depends on local law, and some data handling may apply where local law permits. Our Privacy Policy describes the information used for account and security steps, while the policy page remains the place to check current wording.