Reference

Open with clear Legal boundaries

timun merah explains the Legal conditions behind account access, wallet records and policy requests before you enter the lobby.

Account termsData handlingLocal-law accessPolicy contacts
timun merah Open with clear Legal boundaries
CONTACT ROUTES

Switch to the right Legal contact route

A clear contact path helps you resolve a policy question without sending account details through an unrelated channel.

Account policy route Open the support path after signing in and select the Legal subject that matches your request. We use the account phone number to locate the correct record, then explain the relevant access or policy step without asking you to share a wallet password.
Wallet record query For a DANA, OVO, GoPay or QRIS record, include the payment reference and approximate date rather than sending secret wallet credentials. We can check the account-side status and tell you which Legal process applies to a correction or clarification.
Access question If Indonesia Secure Login 510 stops at phone verification, contact us through the account support route and describe the screen step. Eligibility depends on local law, so our reply will separate a technical access issue from a jurisdiction condition.
DATA PRACTICE

Browse how Legal data duties work

Our policy handling follows the practical record trail created when you verify a phone number, sign in, request account help or use a payment route.

Account details

We use your account and phone-verification details to identify the correct record when you ask about Legal access. Keeping the phone number current helps us distinguish your request from another account and reduces confusion during a policy response.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect a receipt to an account-side status. We do not need your wallet password for that check, and you should never place secret credentials in a support message.

Cookie controls

Cookies may preserve sign-in continuity and device preferences while you move through a policy page. You can manage browser cookie settings on your device, but clearing them may require a fresh phone-verification step before account access.

Security handling

We keep account assistance tied to the signed-in route and phone verification rather than accepting an unsupported identity claim. If a sign-in attempt looks inconsistent, we may ask for an additional account check before discussing private records.

Retention requests

If you want to ask how long a particular account or payment reference is retained, send the request through the Legal support route. Include the record type and date so we can address the right policy category.

Change requests

For a correction to your name, phone number or account record, contact us from the account route and describe the requested change. We may need phone verification before applying an update, especially where payment history is involved.

Check Legal answers for your account

These Legal answers address the questions we expect before an Indonesian account is opened or a policy request is sent. They cover eligibility, records, cookies, contact steps and account changes, with payment examples such as DANA and QRIS where they affect the request. If your situation is not covered, use the account support route.

Legal covers the account conditions, data handling, payment records, access rules and contact process that apply to timun merah. Eligibility depends on local law. Read the policy terms before phone verification, and contact us through the signed-in support route if a clause needs clarification.

Access or eligibility depends on local law and your location. Our account path uses Indonesia Secure Login 510 with phone verification before access. If the verification step stops, contact support from the available account route so we can separate a technical issue from a local-law condition.

The policy can cover account-side records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. For a record question, provide the reference and approximate date through support. Do not send wallet passwords or private security codes with your request.

Sign in, open the policy contact route and describe the exact correction, such as a phone number or name update. We may ask for phone verification before changing the record. Where local law permits, we will explain any extra evidence needed for the request.

Yes. Our Legal policy explains that cookies may help preserve sign-in continuity and device preferences. You can adjust cookie settings in your browser. Clearing them can remove saved continuity, so a later visit may require another sign-in or phone-verification step.

Use the support path inside your account and choose the Legal or access subject. Include your account phone number and a short description of the screen or clause involved. We will use that route to discuss the relevant record without requesting secret wallet credentials.

Retention can depend on the record type, the account request and local legal requirements, so we do not state one period for every case. Ask through the Legal support route with the record date and category, and we will explain the applicable retention basis where local law permits.