Reference

mataramtoto Privacy Policy For Your Account

Our Privacy Policy explains how mataramtoto handles the details you provide when opening an account, signing in, and using DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record clarityPhone verification contextPolicy contact path
mataramtoto mataramtoto Privacy Policy For Your Account
CONTACT OPTIONS

Ask About Your Stored Account Data

A direct support request helps us connect your Privacy Policy question with the correct account record. Tell us which account step, wallet reference or device session concerns you, and we can explain the handling route without asking you to post private details publicly. If you are in Medan, the same online support path applies as it does elsewhere in Indonesia, where local law permits.

Team online

Account access request

Use our account support channel when you want to ask what personal details are linked to your account. Include your registered phone number only through the secure contact route, and we can direct the request to the correct verification step.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, send the date, amount reference and wallet name through support rather than sharing a full credential. We use those details to locate the relevant payment record while keeping your request focused.

Policy clarification

If a Privacy Policy paragraph is unclear, ask us to explain the purpose in plain English. A support message about cookies, device access or retention can be handled separately from a cashier or account-status question.

DATA PRACTICES

Six Practical Privacy Commitments

Privacy becomes easier to assess when each practice is tied to an account action. We separate contact details from payment references, limit account access through phone verification, and use device signals to…

Account details

When you open an account, we handle the details needed for account access and communication. Phone verification is part of that path, so we can distinguish a genuine access request from an unrelated attempt to use your account.

Payment references

DANA, OVO, GoPay and QRIS references help us match a cashier event with your account. We focus support on the reference, status and account step rather than asking you to send a wallet password or private security code.

Cookies

Cookies may keep your sign-in session, language setting or page state available while you move between account areas. You can manage cookies through your browser controls, although changing them may affect how the Privacy Policy page or account path behaves.

Device security

We may record device, browser and sign-in signals to help identify unusual access. If you move from a mobile browser to desktop, those signals can help us ask for an additional account check before access continues.

Retention choices

We retain a record for as long as its stated account, support, security or legal purpose requires. When that purpose ends, we assess whether the record can be removed, shortened or kept only in a form that no longer identifies your account.

Change requests

To request correction, access or deletion where available, contact support with your registered account detail and the change you want. We verify control of the account first, then explain any timing or legal reason that affects the request.

Privacy Policy Questions About mataramtoto

These Privacy Policy answers address the account and wallet questions we hear most often. They explain what to send, how we connect records to your account, and what can affect a request. If your situation is different, contact support with the smallest useful detail and we will guide the next policy step where local law permits.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security checks and how you can request access or correction.

Phone verification links an access request to the account detail you supplied and helps us identify an unusual sign-in. It is part of the account-security process, not a request for your wallet password. We use the verification record for the stated access and security purpose.

Yes. The Privacy Policy includes references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. A reference can help us check a receipt or wallet status, but you should never send a private wallet code through an open message.

Contact our account support route with your registered phone number and a precise request, such as access to account details or correction of a device record. We verify account control before acting, then explain the available response and any legal condition that applies.

On a mobile browser, cookies may preserve sign-in continuity, language settings and page state as you move through account areas. Your browser controls can clear or restrict them. If you do so, the next login may require another account check or page preference selection.

You can submit a deletion request through support, and we will check which records can be removed under the Privacy Policy. Some account, security, support or payment references may need to remain for a stated purpose or legal requirement where local law permits.

Use the account support channel and describe the concern in plain English, such as cookies, retention, phone verification or a wallet reference. Avoid sending passwords or full payment credentials. We will confirm the request path after checking that you control the account.