Reference

Privacy Policy For Every Account Step

yuhu 4d Privacy Policy explains how we handle details linked to your account, device, wallet status and visits to our pages.

Account dataWallet recordsDevice accessCookie choices
yuhu 4d Privacy Policy For Every Account Step
CONTACT ROUTES

Privacy Help Beside Your Account Path

A direct request is easier to resolve when it includes the account step and the data concern.

Account privacy request Tell us which account detail you want to access, correct or remove.
Wallet record check If a DANA, OVO, GoPay or QRIS record looks incorrect, send the transaction reference…
Device access concern When a phone or computer session looks unfamiliar, contact us from the account help…
DATA CONTROL POINTS

Six Ways We Handle Privacy Details

Privacy work is not separate from the account journey; it appears when you log in, select a wallet, change a device or ask for help.

Data you provide

We receive details you enter for account creation, phone verification and support.

Cookie settings

Cookies can remember a session, language choice and basic page state on your device.

Account security

Phone verification helps us check account access before private details are discussed.

Payment records

A payment reference, selected rail and status can remain connected to your account for reconciliation.

Retention choices

We retain account and transaction details for the period needed to operate the account, handle disputes and meet applicable obligations.

Change requests

You can ask us to correct an inaccurate detail, explain how a record is used or request deletion where applicable.

Answers About Your Privacy Policy

These Privacy Policy answers cover the searches we expect before an account is opened or a wallet is connected. We keep the replies practical: what we collect, why a record appears, how you request a change and what happens when a device or payment status needs checking. If your situation is not listed, use the account support path.

The yuhu 4d Privacy Policy covers account details, phone verification, device sessions, cookies, payment references and support messages. It explains why we use each category, how long records may remain and how you can ask for access, correction, explanation or deletion where applicable.

We record a DANA or QRIS reference so a receipt can be matched to the correct account and status. That record helps us investigate a missing update without requesting unnecessary wallet credentials. We use the reference for account and payment handling, not for unrelated contact.

Send a data access request through the account support path and identify the registered phone number or account detail involved. We may ask for an ownership check before replying. The response can include stored profile fields, session details and transaction references covered by the Privacy Policy.

Yes, you can ask us to correct an inaccurate phone or wallet detail through account support. State which field is wrong and provide the updated value only in the secure request path. We may verify ownership before making a change, especially where DANA, OVO or GoPay records are involved.

The Privacy Policy explains that cookies can keep your login session, language choice and page state available. Browser controls let you restrict or remove them. If you disable required cookies, you may need to verify your phone again or repeat the account path on that device.

We keep payment references and related account records while they are needed for reconciliation, dispute handling, account security or applicable obligations. This can include bank transfer and virtual account details. When the purpose ends, we review the record for deletion or de-identification under our process.

You can request deletion through account support, and we will assess which records can be removed. Some details may need to remain for security, transaction reconciliation or applicable obligations. Access and eligibility depends on local law, so our reply will explain any limit that applies.