Reference

Terms & Conditions for Your uber77 Account

uber77 Terms & Conditions set the rules for opening an account, using the lobby and moving funds through DANA, OVO, GoPay or QRIS.

Account access rulesWallet verificationPolicy change noticesIndonesia access wording
uber77 Terms & Conditions for Your uber77 Account
POLICY HELP PATHS

Where to Ask About Account Terms

A clear support route helps when a clause affects your login, wallet status or account request. Start from the support link beside your account and include the email or phone number attached to the profile, the payment rail involved and the time of the event. Our team can explain the applicable Terms & Conditions, point you to the relevant clause and tell you which receipt or account step is needed. Do not send a password or one-time code in a support message.

Team online

Account access

Use the account support path if your phone verification does not complete or a device session is refused. Share the registered contact detail and device type; we can direct you to the account clause without asking for your password.

Wallet status

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment receipt and reference time through the support contact route. We use those details to explain a pending status under the Terms & Conditions.

Policy requests

Ask through the policy contact form when you need a copy of your account details, a correction or clarification of a clause. Include the request type and registered contact so we can match it to the correct account.

ACCOUNT CONTROL DETAILS

How We Handle Rules, Data and Cookies

We apply these Terms & Conditions through account checks rather than hidden steps. Your phone verification supports account access, while session controls help us identify unusual sign-ins across mobile and desktop devices.

Data handling

We use account, contact and transaction details to operate the agreed service, check requests and respond to support. A data request should come from the registered contact route so we can connect it to the right account.

Cookie choices

Cookies can keep a session connected and remember selected settings on your device. Your browser controls can remove them, although clearing session cookies may require you to complete phone verification again before account access.

Account security

Keep your password private, use your own phone and sign out on shared devices. If a mobile or desktop session looks unfamiliar, contact support promptly and mention the device path so we can explain the applicable account rule.

Retention records

We keep account, payment and support records only as long as needed for service operation, dispute handling or legal duties. The retention period can differ by record type; support can explain the request path for a specific category.

Policy changes

When a material clause changes, we place the new wording and effective date on the Terms & Conditions page. Check that page before using the account again, because continued access after the effective date may apply the revised wording.

Correction requests

If your name, phone detail or another account field is wrong, contact us through the policy route with the correction requested. We may ask for a verification step before changing records tied to wallet or account access.

Terms & Conditions Questions Before Account Access

These answers cover the clauses you are most likely to check before opening an account or using a local wallet. We keep the practical route visible: read the current Terms & Conditions, complete the requested account step, and contact support when a payment record, device session or personal detail needs review under the policy.

They cover account creation, phone verification, login conduct, wallet transactions, device access, policy changes, data handling and support requests. The current wording on this page applies to your use of the account, while access remains subject to local law and any stated eligibility condition.

Yes. Account and lobby access depends on local law. We may restrict access or request an additional check where a legal or operational requirement applies. Read the current Terms & Conditions for the relevant wording, and contact support if your location or account status is unclear.

Those local rails may be shown as available choices, subject to the account and transaction conditions. Use a wallet or bank detail that matches the requested account check, keep the receipt, and contact support if a DANA, OVO, GoPay or QRIS status stays pending.

Phone verification connects account access to the contact detail you provide and helps us handle unusual login or wallet requests. Complete the step on your own device, keep the number current, and use support if verification fails instead of creating duplicate account details.

You can use the available mobile or desktop path, but each session still follows the same Terms & Conditions. Sign out on shared devices, protect your password and report an unfamiliar session with its device type so support can explain the next account step.

Send the request through the policy contact route using the registered phone or email, state the field that needs correction and include the relevant account detail. We may ask for verification before changing information connected to wallet records or account access.

Check the policy page for the revised wording and effective date first. If a clause remains unclear, use the support link or policy contact form and identify the section title. Include your registered contact detail, but never send your password or one-time code.