Reference

Privacy Policy for Your mahtoto Account

mahtoto Privacy Policy explains how we handle the account, device and wallet details connected to your access.

Account dataCookie choicesWallet recordsPrivacy requests
mahtoto Privacy Policy for Your mahtoto Account
PRIVACY HELP

Get Privacy Answers Near Your Account

A clear support route helps you ask about Privacy Policy matters without repeating your account story. From the account area, describe the issue, name the relevant wallet status, and include the date or reference shown in your cashier record. We can then separate a cookie question from a DANA, OVO, GoPay or QRIS status question. For access concerns, mention whether you used a mobile browser or desktop so we can point you to the right policy step.

Team online

Account support path

Use the support route connected to your account when you want to ask what data is held, why phone verification appears, or which policy step applies to your access.

Wallet status context

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share only the visible reference and status; never place a wallet password or security code in your message.

Device access detail

Tell us whether the request came from a mobile browser or desktop session, then describe the page path from login to the lobby so privacy support can respond with relevant steps.

DATA HANDLING

What We Do With Your Account Data

We keep Privacy Policy practice tied to the way your account actually works. Phone verification helps connect access to the correct account, while device and cookie signals help remember settings and detect…

Account details

We use the phone number and account details you submit to identify your profile, complete the stated access step, and respond to a Privacy Policy request connected with that profile.

Cookies and settings

Cookies and similar device signals can remember your chosen settings and help us understand a failed session. You can ask support about these signals before changing browser permissions.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used as payment references, not as a request for your private wallet password or security code.

Account security

Phone verification and session checks help us distinguish your account access from an unusual device change. If a sign-in path looks different, contact support before sharing any document.

Retention requests

When you ask how long a record is kept, we assess the account detail, payment reference or support message involved and explain the applicable retention reason through the account path.

Policy changes

If this Privacy Policy changes, we place the updated wording on the policy page. You can ask which part changed and request help understanding its effect on your account.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the searches we expect before you open an account. They cover the data connected with phone verification, mobile access, cookies, wallet references and requests made through support. If your situation involves a payment record or a device change, keep the visible reference ready and avoid sending passwords, wallet codes or unrelated documents.

The mahtoto Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references. It explains why those details may be used, how they relate to access, and how you can ask about a record through the account support path.

Yes. Privacy Policy treatment includes the visible transaction reference and status connected with DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We use these details to match a cashier event, not to request your wallet password.

Phone verification connects the access step with your account and helps us respond to account-specific privacy requests. If the verification screen appears on your mobile browser or desktop session, follow the stated account path and contact support if the step does not match your details.

You can ask what account, device, cookie, support or payment-reference data relates to your profile. Send the request through the account support path with the visible reference where relevant, but leave out wallet passwords, security codes and unrelated personal documents.

Cookies and related device signals may remember settings and help us identify a broken or unusual session from mobile or desktop. Your browser controls can affect them, while support can explain the relevant Privacy Policy wording before you change those settings.

You can request clarification, correction or removal where the applicable Privacy Policy and legal requirements allow it. Tell us which record is affected, such as a phone detail or payment reference, and we will explain the next account support step.

Yes. Access and eligibility depends on local law, and where local law permits, the Privacy Policy explains the data needed for account operation and security. If your location or account status creates uncertainty, ask support before providing additional details.