Reference

uno4d Privacy Policy for Indonesian Accounts

Our uno4d Privacy Policy shows what account, device and wallet details we collect, why we use them, and how you can ask for changes.

Clear data purposesWallet record detailsMobile access controlsContact request path
uno4d uno4d Privacy Policy for Indonesian Accounts
PRIVACY HELP ROUTE

Ask About Your Privacy Policy Request

You do not need to guess which route to use when a privacy question affects your account. Start from the signed-in account help area, describe the request in clear English, and include the relevant account detail without sending a password or wallet PIN. We use the same route for questions about mobile browser records, phone verification, payment references and access where local law permits.

Team online

Account help

Sign in, open account help and select the privacy request route when you want to ask about stored account details, phone verification records or a correction. Keeping the request inside your account helps us match it to the right profile without asking you to send a password.

Wallet receipt check

If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference appears in your request, share the receipt number and date only. We can then check the payment record connected to your account while you keep your wallet PIN and full login secret private.

Privacy contact

For access, correction, deletion or retention questions, use the privacy contact option in account help and explain the result you need. We may ask for a verification step before discussing personal data, so a request cannot be redirected to another person without an account check.

DATA CONTROL PRACTICE

Mobile Login and Data Controls at uno4d

We keep this policy practical by linking each data purpose to a familiar account action. Your phone verification supports account access checks; a mobile browser may create device and session records; and…

Account details

We may handle details you provide during account creation, including contact data used for phone verification. We use those details to identify the account, support sign-in checks and respond to privacy requests. Review your submitted details through account help if something needs correction.

Payment references

A payment reference can connect a DANA, OVO, GoPay or QRIS status to the correct account. Bank transfer and virtual account records may also appear when a receipt needs checking. We do not need your wallet PIN for a privacy or receipt request.

Cookies and sessions

Cookies and session records can help keep a signed-in mobile browser connected to the right account. They may also support security checks as you move from login toward the lobby. Your browser settings can control cookies, although changing them may affect account access.

Account security

We use account checks, phone verification and session signals to reduce the chance of another person reaching your personal data. Never place a password, wallet PIN or full verification code in a support message. Contact us promptly if a sign-in record looks unfamiliar.

Retention periods

We retain personal and payment records only for the period needed for account operation, security review, dispute handling or legal duties. The period can differ by record type and local requirement. You can ask why a particular record remains and receive the applicable explanation.

Changes to details

You can ask us to correct account details that are incomplete or inaccurate through the privacy contact route. Where local law permits, you may also ask about access, deletion or restricted use. We may verify your identity before making a change to protect your account.

Privacy Policy Answers for Your uno4d Account

These Privacy Policy answers focus on the searches you are most likely to make before opening or using an account in Indonesia. We cover collected data, wallet references, cookies, mobile sessions, correction requests and local access conditions. If your question is not listed, use the account help privacy route and include enough detail for us to locate the relevant record without sharing secret credentials.

The uno4d Privacy Policy covers account details, phone verification, device and session records, cookies, payment references, security handling, retention and privacy requests. It explains why we use each category and how to contact us about access, correction, deletion or another request where local law permits.

Phone verification helps us confirm that the person requesting account access or a data change is connected to the correct profile. It supports sign-in security and privacy request checks. We will not ask you to place your password, wallet PIN or full verification code in a message.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references may be connected with an account to check payment status or answer a receipt question. Bank transfer and virtual account records can be handled in the same practical way when support needs to trace a transaction.

A mobile browser may create account session, device and cookie records while you sign in and move toward the lobby. These records can support continuity and security checks. Your browser settings can control cookies, but changing them may affect sign-in or other account functions.

Open account help after signing in and choose the privacy contact route. Describe the detail that is inaccurate and the correction you want, without sending secret credentials. We may complete an account verification step before changing personal data, and timing depends on local law.

You can submit a deletion question through the privacy contact route. Where local law permits, we will assess the request and explain what can be removed. Some account, payment, security or dispute records may need to remain for legal duties or protection against misuse.

The policy is written for Indonesian account use, but access and eligibility depends on local law. Where local law permits, you can use the stated contact route to ask about your data rights. We may request location or account verification before giving a record-specific response.