Reference

Legal access starts with clear terms

suma55 keeps Legal details close to the account path, so you can check access conditions, wallet handling and data choices before opening an account.

Account termsWallet clarityData choicesLocal-law access
suma55 Legal access starts with clear terms
POLICY HELP ROUTES

Find the right Legal contact path

A clear contact route helps you resolve a Legal question without sending payment details to the wrong place. We separate account access, wallet status and data requests so your message reaches the relevant policy path. Use the support link beside the cashier when a receipt or transaction status needs context, and include the account phone number only through the requested field. We can then match the issue to the correct record while keeping the conversation tied to the terms that apply in Indonesia.

Team online

Account terms

For a question about phone verification, account access or local eligibility, use the account support path and state which Legal wording is unclear. We will point you to the relevant clause and explain the next account step where local law permits.

Wallet records

When DANA, OVO, GoPay or QRIS status needs checking, open the support route beside the cashier and keep the payment receipt reference ready. We use that reference to connect your question with the correct transaction record and policy condition.

Data requests

For a request about stored account details, cookies or a policy change, use the data contact route shown on this page. Tell us what you want changed or clarified, and we will explain the verification needed before handling the request.

HOW WE HANDLE DATA

Your Legal choices stay visible

We treat Legal as an operating process, not a footer label. Account records are used to manage access, phone verification and policy requests, while payment references help us investigate a wallet question…

Data handling

We use the account details needed for access, verification and Legal support. When you ask about a record, we first confirm the account context, then explain why that detail is held and how it relates to the policy question.

Cookies

Cookies can keep the Legal page, account path and selected session state working across a mobile browser. Our policy wording explains their role, so you can ask us to clarify a cookie choice before relying on the account path.

Account security

Phone verification is part of the account access check, and sensitive policy changes may require confirmation through the account path. Do not send a password or wallet PIN in a support message; use the requested verification field instead.

Record retention

We retain account and transaction records according to the policy needs explained in our Legal wording. If you ask how long a particular record is kept, identify the record type and we will explain the applicable retention position.

Who to contact

The support route beside the cashier is suitable for wallet records, while the data contact route is intended for cookies, account details and policy wording. Choosing the matching path helps us avoid moving sensitive information between unrelated requests.

Requesting changes

You can ask us to correct account details or clarify a Legal condition through the relevant contact path. We may request account verification before changing a record, and we will explain any limit that depends on local law.

Answers to suma55 Legal searches

These Legal answers cover the questions that usually matter before account access: which terms apply, how local eligibility is handled, what happens to account and wallet records, and where to request a change. We keep the answers tied to actual suma55 steps, including phone verification, the mobile browser path and the support route beside the cashier. If your situation is unusual, send the specific clause and account context through the matching contact path.

The suma55 Legal page covers account creation, phone verification, access conditions, wallet records, cookies, account security, retention and policy requests. It is the place to check the terms that apply before you use the account path, with access depending on local law.

Access depends on local law and your location. We do not replace local rules with a general statement, so check whether access is permitted for you before opening an account. The Legal wording explains the account condition and verification step that apply.

These payment names appear because a wallet or QRIS record can be relevant to a Legal question about a cashier transaction. They do not change the policy terms. If status needs checking, use the support route beside the cashier and provide the requested reference.

Phone verification is part of the account access process. We use it to connect the account request with the correct account record and to protect policy changes from unauthorised requests. The exact access position still depends on local law and the terms shown.

Use the data contact route and describe the account detail you want corrected or the policy wording you want clarified. We may ask for account verification before making a change, because the request must come from the person connected to that record.

Our Legal wording explains that cookies can support page operation, session continuity and the mobile browser account path. If you want clarification about a cookie choice or its purpose, contact us through the data route before relying on that setting.

Send the question through the support path that matches the subject: account access for verification or eligibility, the cashier route for wallet records, or the data route for cookies and stored details. Include the clause or screen wording so we can answer precisely.