Reference

uni4d Privacy Policy For Your Account

The uni4d Privacy Policy explains what account details we collect, why we use them, and how you can request access or changes.

Account dataWallet recordsCookie choicesAccess requests
Browse Our Lobby Read FAQ
uni4d uni4d Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Near Account Support

A clear contact route matters when your account record or wallet reference needs attention.

Account request Use the account support path to ask about stored profile details, phone verification records, or a correction to your account data. We may request an account identifier before sharing private details, so your request reaches the right record.
Wallet record For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, send the payment reference and status shown in your account. We use those details to locate the relevant transaction record without asking you to repeat unrelated account information.
Access concern If a privacy request follows an unusual login, tell us whether it came from a mobile browser or desktop device and when it happened. We can use the account security trail to check the event before discussing changes or disclosure.
HANDLING DETAILS

How We Keep Privacy Requests Clear

We keep this policy practical by linking each privacy question to a real account action. Phone verification helps us distinguish an account holder from an unverified request, while device and session records…

Account details

We may collect details needed to create and maintain your account, including contact data and phone verification status. We use those details to identify the correct account, respond to your request, and prevent one person from changing another person’s record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account action can create a reference, status, and timing record. We use this narrow payment context to match account activity, check an incomplete step, and answer a wallet query.

Cookies

Cookies and similar session tools can remember a sign-in state, support security checks, and show the correct account path. We do not treat a cookie as a substitute for your account consent, and you can ask us which cookie category relates to your visit.

Device security

When you move from phone login to the lobby, or use a desktop browser, technical signals may record the session, browser, and security event. We use these signals to investigate access concerns rather than to infer unrelated personal traits.

Retention timing

We keep account, support, and payment records only for the period needed for the stated purpose, account checks, dispute handling, security work, or legal duties. When a retention need ends, we handle removal or restriction according to applicable law.

Your request

You can ask what personal data we hold, request a correction, ask about use, or raise a lawful objection through account support. We may verify your phone or account details first, then explain the result and any legal reason for a limitation.

Privacy Policy Answers For uni4d

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder before opening an account or contacting us. We explain the records connected to login, payment status, cookies, device access, and privacy requests in direct terms. If your situation needs a local-law assessment, use the account support path with the relevant reference.

The Privacy Policy covers account details, phone verification, support messages, cookie activity, device and session signals, and payment references. It explains why we use each category, how retention works, and how you can request access or correction where local law permits.

Phone verification helps us connect a request to the correct account and reduce unauthorised changes. We may use the verification status when you ask to update profile data, discuss a wallet reference, or access information linked to your account.

Yes. The Privacy Policy covers the account-side records created when you select DANA, OVO, GoPay, QRIS, bank transfer, or virtual account. These can include a reference, status, timing, and selected rail, used to check an incomplete payment step.

When you sign in through a mobile browser or desktop browser, we may record technical session and security signals such as browser context and access events. We use them to maintain account security and investigate unusual access, not to collect unrelated personal details.

Contact us through the account support path and state whether you want access, correction, restriction, or another privacy action. Include the account identifier or relevant payment reference where suitable. We may verify your phone before processing the request.

We retain information for the period needed to operate the account, check payment disputes, respond to support, protect access, or meet legal duties. The period can differ by record type. We then handle deletion or restriction where local law permits.

Yes. Ask support to identify the cookie or session category connected with your visit. Cookies may support sign-in continuity and security checks. Your browser also provides controls, although changing them can affect the account path or session behaviour.

Related Pages

uni4d Indonesia Account information Access guide About Us FAQ