Reference

Privacy Policy for Your UH77 Account

Your UH77 Privacy Policy explains what we collect during account opening, how DANA, OVO, GoPay and QRIS records are handled, and how you can ask for a correction.

Account dataWallet recordsCookie choicesRequest access
UH77 Privacy Policy for Your UH77 Account
POLICY SUPPORT

Reach Us About Your Data Choices

A clear contact path matters when your account record needs attention. We direct Privacy Policy questions through the support route linked from your signed-in account, with enough detail for us to locate the correct account. Include your registered phone contact, request type and any wallet reference you want checked; never send a password or one-time code.

Team online

Account data request

Ask for access, correction or removal through the support channel connected to your UH77 account. We may confirm your registered phone contact before releasing or changing personal data.

Wallet record check

If a DANA, OVO, GoPay or QRIS record looks incorrect, include its reference and status. We compare the payment event with the account record before replying through the same support path.

Security concern

For a sign-in concern, contact support from the account area and describe the device path used. We can place the request beside the relevant account and security records for checking.

DATA PRACTICE

Security And Retention Inside UH77

We handle this policy area through defined account steps rather than vague promises. Phone verification, wallet matching and sign-in records help us separate your request from another account.

Account collection

We may collect your phone contact, sign-in details, device signals, support messages and payment references when you open or use an account. Each category supports a stated account or security purpose.

Cookie controls

Cookies can keep a browser session working and remember selected account settings. You can manage browser cookie controls, although switching them off may affect sign-in steps or saved preferences.

Sign-in security

Phone verification before account access helps us check that a request belongs to you. Do not share passwords or one-time codes, and contact support if a mobile session looks unfamiliar.

Retention periods

We keep records for as long as needed for the purpose collected, account servicing, payment reconciliation or a legal requirement. When a record is no longer needed, our process addresses its removal.

Your requests

You can request access, correction or deletion through the signed-in support route. Tell us which record concerns you, and we may verify account details before completing the request.

Device path

A mobile browser may create session and device records used to protect account access. If you change devices, explain that path in your request so we can check the correct sign-in event.

Questions About Privacy Policy

These Privacy Policy answers address the account and wallet questions you may search before opening an account. We keep the route practical: check the policy, prepare the relevant account or payment reference, then contact us through the support path available after sign-in. Access remains subject to local requirements.

The UH77 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS or bank transfers.

We may retain a payment reference, amount, status and time for DANA or QRIS so we can match the wallet event with your account, check a discrepancy and respond to a support request.

Yes. Send an access request through the signed-in support route, identify the account record you want, and complete any account check we require before sending data to the correct person.

Cookies can support browser sessions and selected settings. You can change cookie controls in your browser, but disabling them may interrupt sign-in, verification or saved account preferences.

Retention depends on the reason for collection, account servicing, payment reconciliation and legal duties. We address records for removal when the purpose or applicable requirement has ended.

Contact us through the account support route and describe the incorrect field, such as a phone contact or wallet reference. We may verify your account before applying or explaining a correction.

Our Privacy Policy explains data handling where local law permits. Account eligibility and available access depend on local law, so check the current access notice before creating or using an account.