Reference

Privacy Policy for Your Wallet Data

madetoto keeps this Privacy Policy focused on the account details, device signals and wallet records needed to provide access in Indonesia.

Clear data purposesWallet record controlsAccount access choices
madetoto Privacy Policy for Your Wallet Data
ACCOUNT HELP

Wallet Status Questions Reach Our Team

A clear contact route helps you act on this Privacy Policy without sending sensitive details through a public channel. Use the account support path linked beside the cashier area when you need to ask about a DANA receipt, a QRIS reference, a login record or a correction to your profile. We will use the details already attached to your account to locate the request, and you should not send a password or wallet PIN.

Team online

Policy request

Ask us to explain a data field, the reason it is used or the account step connected with it. Include your account contact detail and the subject of your request so we can locate the correct record without asking you to disclose a password.

Wallet record

For a DANA, OVO, GoPay or QRIS question, share the transaction reference rather than a wallet PIN. Our team can compare the reference with the account status and explain which payment record is held for support and reconciliation.

Login concern

If a phone verification step or a familiar-device check blocks account access, contact us through the account help path near the cashier. We may ask for account identifiers to confirm ownership before discussing personal data or changing access details.

DATA PRACTICE

How Cookies and Account Security Work

We use this policy area to keep account handling understandable from the first phone verification through later wallet checks.

Account details

We use the contact details and verification responses you provide to create, secure and maintain your account. A phone verification step can connect a sign-in with the right account, while an incorrect detail may delay access until you request a correction.

Device signals

Your browser type, device path, session events and approximate technical details can help us identify repeated login failures or unusual access. We do not need the contents of your phone to perform these checks, and clearing cookies may start a new verification path.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be stored with the account status and support trail. We use those records to match a receipt, identify a failed step and answer a wallet question, not to request your wallet PIN.

Cookies

Cookies can keep a signed-in session working and help us understand whether a security step has already been completed. If you block or remove them, some account pages may ask for phone verification again before showing personal or payment-related details.

Retention

We keep account, security and transaction records only while they serve an operational need, a dispute, a security check or a legal duty. When a record is no longer needed for those purposes, our retention process removes it or separates it from direct account identification.

Changes and contact

You can ask us to correct an inaccurate profile field, explain a stored record or discuss a deletion request through the account support route. We may confirm ownership first, then tell you what can be changed and whether a legal or transaction duty requires continued retention.

Privacy Policy Questions About Your Account

These answers cover the searches we hear most often about the madetoto Privacy Policy, from phone verification to local wallet records. Read them before opening an account or use the support path beside the cashier when your question concerns a specific transaction or sign-in. We explain each request according to the account record involved and where local law permits.

The madetoto Privacy Policy covers account details, phone verification, login and device events, cookies, support messages and payment references. It explains why we use each category, how we protect access, how long records may remain and how you can ask about correction or removal.

Phone verification helps connect a sign-in with the account owner and can protect your profile when a new device or unusual login appears. We may retain the verification result and related security event, while you should keep passwords, wallet PINs and one-time codes private.

A DANA or QRIS transaction reference and status may be stored so we can match a receipt, investigate a failed cashier step or answer support. We do not need your wallet PIN for that work, and a reference is handled as account-linked payment data.

Yes. Contact us through the account support path and identify the field you believe is wrong, such as a phone detail or account name. We may confirm ownership before making a change, and some transaction or security records may need to remain for a defined duty.

On a mobile browser, cookies can keep your session active and help us recognise whether a security step has been completed. Removing or blocking them may sign you out or trigger phone verification again. The Privacy Policy explains these uses without requiring access to unrelated phone content.

Retention depends on the purpose of each record, such as account security, a wallet reconciliation, a dispute or a legal duty. We remove or separate records when that purpose ends where possible. Ask support about a specific record rather than sending payment credentials.

Our Privacy Policy is applied where local law permits, and access or eligibility depends on local law. If you are unsure about your position in Indonesia, check the applicable local requirements before opening or using an account. Support can explain our data process, not provide legal advice.