Reference

Privacy Policy For Your uber388 Account

uber388 Privacy Policy explains what account details we collect, why we use them and how you can ask about changes before opening an account.

Clear data purposesPhone verificationWallet record checksMobile browser access
uber388 Privacy Policy For Your uber388 Account
HELP WITH POLICY

Get Policy Help Near Account Access

A direct contact route helps when you need to understand a Privacy Policy point rather than search through unrelated account pages.

Policy questions Ask us which account details a particular Privacy Policy section covers. Include the email or phone reference connected to your account, but never send your password or one-time verification code through a support message.
Wallet records If a DANA, OVO, GoPay or QRIS status needs clarification, tell us the payment rail and reference shown in your account. We use that context to locate the relevant record and explain how the Privacy Policy applies.
Access concerns When a mobile sign-in or phone verification result looks unfamiliar, contact us through the account support path. We can help you identify the security step involved and direct a request to the right policy contact.
DATA HANDLING PRACTICE

How uber388 Handles Your Details

Privacy Policy choices matter most when they connect to actions you can recognise in your account.

Account details

We use the details you provide to create and maintain your account, send account-related messages and complete the phone verification step before access. Our Privacy Policy explains the purpose of each requested field so you can decide what to provide.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us identify the related account record. We use payment status for account servicing and support checks, not as a reason to collect unrelated personal details.

Cookies and devices

Cookies can keep your session active and help us recognise the browser path you chose on mobile or desktop. Device signals may support security checks, while your browser settings provide controls for some cookie activity.

Account security

Phone verification and sign-in signals help us spot an account access event that does not fit your usual pattern. If you see a mismatch, contact support promptly and avoid sharing passwords, wallet PINs or verification codes.

Retention choices

We keep records only for the operational, security or account purpose described in the Privacy Policy, subject to the period that purpose requires. A retention question can be sent through our contact path with the relevant account reference.

Changes and requests

You can ask us to explain a data use, correct an inaccurate account detail or clarify how a policy section applies. Include enough context for us to locate the record, and we will direct your request through the available account contact process.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and access questions you may have before joining uber388. We focus on practical records, including phone verification, mobile cookies, payment references and requests to change personal details. If your situation involves eligibility or access, that outcome depends on local law, so contact us with the account context you can safely provide.

The uber388 Privacy Policy explains what account, device, security and payment-reference data we handle, why we need it and how retention works. It also sets out how you can ask for clarification, correction or help with a record connected to your account.

Phone verification supports account access and helps us identify unusual sign-in activity. We use the result for account security and servicing, not as a reason to request your wallet PIN or password. Access or eligibility depends on local law.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. These records help us match a payment question with the correct account and explain a stalled wallet status.

Cookies can preserve your sign-in session and remember the browser path used to reach the lobby on a phone or desktop. Device signals may support security checks. Your browser settings offer controls for some cookies, while required session functions may still be needed.

You can contact us to ask about an inaccurate account detail or a data use you do not understand. Include your account reference and describe the requested change without sending a password or verification code. We will explain the available request process.

Retention depends on the purpose for which a record was collected, such as account access, payment status, security or support. Our Privacy Policy describes that approach rather than promising one period for every record. Ask support about the category relevant to your account.

Use the account support contact path and state that your question concerns the Privacy Policy. You can mention a phone verification event, QRIS reference, cookie setting or correction request. We will direct the matter to the relevant policy contact where local law permits.