Reference

fusototo Legal Terms For Your Account

fusototo Legal terms explain who may access your account, how we handle records connected with DANA, OVO, GoPay and QRIS, and where local law permits access to our…

Account conditionsData requestsWallet recordsLocal-law access
fusototo fusototo Legal Terms For Your Account
CONTACT ROUTES

Three Ways To Raise A Legal Question

A clear contact route helps you resolve a Legal concern without sending private account details into the wrong place.

Account access Use the account help path for phone verification, login records or an access question. We check the account identifier first and ask only for details needed to handle that Legal request.
Wallet record Choose the wallet contact path when a DANA, OVO, GoPay or QRIS receipt needs matching. Include the payment reference and date, while keeping passwords and one-time codes private.
Rights request Send a clear request to correct, access or remove personal records where applicable. Tell us which account detail is concerned, and we will use the account contact route to respond.
DATA PRACTICES

How We Apply The Legal Policy

Legal handling is tied to practical account events rather than broad statements. We use records to verify account ownership, trace a wallet status and protect access to the lobby.

Account data

We connect account records with the identifier used during registration so a Legal request reaches the correct account. Phone verification may be required before we disclose or change private details.

Cookies

Cookies can keep session settings available while you move between account pages. You can manage browser permissions, but changing them may affect login continuity or required page functions.

Account security

We treat passwords, verification codes and wallet references as private account material. Do not place them in a request; our contact path can confirm ownership without asking for your secret credentials.

Record retention

We retain account, payment and access records for the period needed for the stated purpose or applicable rules. A Legal request can ask which record is held and why it remains.

Correction path

If your name, phone detail or account record is inaccurate, identify the field and provide the account identifier through the account route. We may request evidence before making a change.

Policy contact

For a Legal question about data, cookies, access or retention, use the rights request route and describe one issue per message. This helps us send a focused response to you.

Answers Before You Open An Account

These Legal answers cover the questions you may have before opening an account from Indonesia. They explain access, data handling, payment records and contact steps in plain terms, so you know what to prepare before phone verification or a policy request.

It covers account access, phone verification, cookies, data handling, payment records, retention and requests to correct or remove personal details where applicable. Access depends on local law.

Access is available where local law permits. Check the account access conditions before opening an account, and do not proceed if local rules make the service unavailable to you.

Phone verification helps us connect a request with the correct account before discussing private records. It may be required for access questions, account changes or a payment-status enquiry.

We may retain DANA and QRIS references to match a receipt with an account action and resolve a status question. Keep your payment reference available, but never send passwords or one-time codes.

Use the rights request route, name the exact field to change and include your account identifier. We may ask for account evidence before correcting a record or confirming the result.

Retention depends on the purpose of each record and applicable local rules. You can ask which account, access or payment record is held, why it remains, and whether a request applies.

Use the account, wallet or rights contact route that matches your issue. Describe the single concern clearly, include a reference when relevant, and keep sensitive credentials out of your message.