Reference

Legal Rules For Your berkawantoto Account

berkawantoto sets out its Legal position in plain language so you can understand account access, data handling and policy requests before opening an account.

Account accessData requestsLocal-law checksWallet records
berkawantoto Legal Rules For Your berkawantoto Account
POLICY HELP PATHS

Get Legal Help With Account Records

A clear contact route matters when a Legal question concerns your account rather than a general page. We ask you to begin from the account support path so our team can connect the request with the correct registration and payment record. Include only the details needed to identify the issue, and do not send a wallet password or one-time verification code. This keeps a policy request focused while we check access, account status or a transaction reference.

Team online

Account access

If your Legal question concerns phone verification or account entry, use the account support path and provide your registered phone number. We can then check whether the request is an eligibility matter, a missing account step or a local-law access question.

Wallet record

For a Legal request about DANA, OVO, GoPay or QRIS records, include the payment reference and approximate time. We use those details to locate the matching account entry without asking you to share a wallet password or verification code.

Policy change

When you want to question, correct or update a policy record, contact us through the same account support route. State the exact request, such as data correction or access clarification, so the response addresses Legal rather than a separate lobby matter.

DATA HANDLING PRACTICE

How We Manage Legal Requests

Legal handling covers more than the wording on this page. We separate account credentials from ordinary support messages, use transaction references to trace wallet activity and keep access decisions tied to the…

Account data

We use registration details, including the phone number linked to your account, to match a Legal request with the right record. Providing consistent details helps us avoid changing information on the wrong account or disclosing account data to another person.

Cookie settings

Cookies can support a remembered session and device behaviour during account access. You can manage them through your browser settings, although removing some cookies may require you to repeat an account step before the lobby can open.

Account security

Phone verification is an account-security step used before access where required. We do not ask for your wallet password or one-time code in a Legal support request. Keep those details private and use the registered account route when asking for help.

Record retention

We retain account and transaction records for the period needed to operate the account, answer a Legal request and meet applicable local requirements. A payment reference from DANA or bank transfer may therefore remain linked to its account record.

Who handles requests

Our account support team handles questions about policy wording, access checks, data corrections and record status. Starting from your account path gives the team the context needed to separate a Legal request from a lobby or wallet display issue.

Change requests

To request a correction or policy-related change, identify the account detail involved and explain the change in clear English. We may ask for a registered phone number or payment reference before discussing account data or applying an update.

Legal Answers Before Account Access

These Legal answers address the questions we expect before an Indonesian account is opened or a policy request is sent. They explain how local-law wording, registration details, cookies, security checks and payment records connect. If your situation needs an account-specific decision, use the support path with the registered details requested for that case.

Our Legal policy covers account access, eligibility wording, data handling, cookies, account security, record retention and requests to correct or discuss account information. It also explains how payment references from DANA, OVO, GoPay, QRIS or bank transfer may be matched to your account.

Yes. Access depends on local law, so registration and account functions are not presented as available in every location. You must provide accurate details and complete any requested phone verification, but those steps do not replace the local-law condition.

Use the account support path and describe the exact record you want corrected. Include your registered phone number when requested, but never send a wallet password or one-time code. We use the request details to locate the relevant account entry.

Payment references help us connect a transaction with the correct account and respond to a Legal question about status or ownership. This can include a DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference supplied during account activity.

You can manage cookies through your browser settings. Some cookies support session continuity or device behaviour, so removing them may require another account step. Cookie choices do not remove the need to follow access checks where local law permits.

Start with the account support path and state whether the concern involves access, data correction, cookies, security or a payment record. The team may request your registered phone number, account email or transaction reference to identify the correct case.

Yes. We may update policy wording when an applicable rule or operating requirement changes. If a change affects access, we may pause a feature while checking the relevant details. Check this Legal page before using the account after a policy update.