Reference

Legal rules for your uber388 account

uber388 sets out its Legal position in plain English, covering account access, identity checks, payment records and requests about your personal data.

Indonesia accessPhone verificationPolicy accessWallet records
Browse Our Lobby Read FAQ
uber388 Legal rules for your uber388 account
CLEAR CONTACT ROUTES

Get help with Legal questions

Legal questions should reach the route that matches the issue, so we separate account access, wallet records and data requests.

Account access If phone verification or login blocks your Legal access, use the account support route beside the cashier path. Tell us whether the issue concerns registration, a locked session or an eligibility question, and we will direct the request to the relevant account check.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference through the support path shown in your account. We can check status details without asking for your wallet password, card PIN or one-time security code.
Data requests To ask about stored account data, cookies, retention or a correction, identify the registered phone number and describe the change clearly. We may ask for an account check before discussing personal records, so the request reaches the right account holder.
HOW WE HANDLE DATA

Your Legal controls and account records

We handle Legal matters through practical account controls rather than broad promises. Phone verification helps connect an account request to the right person, while payment references help us separate DANA, OVO, GoPay…

Data handling

We use account details to manage access, identity checks, payment matching and Legal requests. A request should include only the details needed to locate your record. We do not need your wallet password, PIN or one-time code to discuss a payment reference.

Cookie use

Cookies can keep a session connected to the correct account and help the policy page open from your login path. If cookie settings interrupt access, record the device behaviour and contact support so we can separate a browser issue from an account restriction.

Account security

Phone verification is an account step before access is completed. Keep your login details private and never send a one-time code through support. When account details and payment references do not align, we may pause the request until the account check is clear.

Record retention

Payment and account records may be kept for the period needed to handle account access, disputes, security checks and Legal duties. Ask through the account support route if you need the retention reason for a particular record or payment reference.

Correction requests

If your registered phone details or another account record is inaccurate, describe the specific field that needs changing. We may request verification before applying an update, helping prevent a third party from altering the account or redirecting a payment record.

Policy contact

Use the support contact displayed in your account when you need a Legal explanation, access clarification or data response. Include the policy topic, registered phone number and any relevant reference, but leave out passwords, PINs and one-time security codes.

Answers before you open an account

These Legal answers address the questions we expect before an Indonesian account is opened or a policy request is sent. They explain local access, account verification, payment records, cookies, data changes and contact steps without replacing the law that applies to your location. Read them with the policy wording in your account area, and contact support when your circumstances need a specific response.

Access depends on local law. You should confirm that using the service is permitted where you are located before opening an account or entering the lobby. Our account path includes phone verification, and support can explain the account step without deciding whether local law permits your access.

Phone verification connects the account to the contact detail supplied during registration and helps us handle Legal requests with the correct account holder. It can also affect access when a login or payment record does not match. Never send your one-time code to support.

Yes. Send a request through the support contact shown in your account and identify the registered phone number. We can explain the account, payment and cookie records connected to your request, subject to the checks and limits that apply under local law.

Describe the exact record that needs correction, such as a registered phone detail, and send the request through the account support route. We may verify your identity before changing it. This protects your account from an unauthorised person redirecting access or payment records.

DANA and QRIS references are treated as payment records linked to an account request. We may use the reference to check status or match an entry, but we do not need your wallet password, PIN or one-time code. Contact support if a record appears unfamiliar.

Retention depends on the purpose of the record, such as account access, payment matching, security checks or a dispute. Ask support about a specific account or payment reference and we will explain the applicable reason and next step where local law permits.

Check the policy pages through your account area and use the support contact displayed beside the account and cashier paths. Include the policy topic and registered phone number. We can explain a changed section, access condition or data process without requesting confidential wallet credentials.

Related Pages

uber388 Indonesia FAQ bsislot88 bolacash88 uber388 Casino