Reference

uci33 Privacy Policy, Made Clear

Our uci33 Privacy Policy shows what we collect when you create an account, sign in from a mobile browser, or use DANA and QRIS at the cashier.

Account dataWallet recordsCookie choicesIndonesia access
uci33 uci33 Privacy Policy, Made Clear
HELP WITH DATA

Request Privacy Help From Your Account

A clear support path matters when a Privacy Policy question concerns your own account. Start from the signed-in account help route and tell us whether you need a copy, correction, deletion request or explanation of a wallet record. In Jakarta and across Indonesia, we use the account details you provide to locate the right record without asking you to send a wallet password. Access questions remain subject to local law.

Team online

Account help route

Open account help after signing in and describe the Privacy Policy request in plain language. Include the email or phone detail attached to your account so we can match the request without exposing another person’s records.

Wallet status check

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and date rather than a wallet password. We use those details to trace a pending status, duplicate record or receipt mismatch linked to your account.

Data change request

Ask us to correct an account detail through the same support route. We may verify your signed-in session or request an account step before changing personal data, helping prevent an unknown person from altering your record.

RECORDS AND CONTROL

What We Handle Behind Your Login

Privacy work continues beyond the first account form. We separate information needed to identify your account from signals used to keep a session working on a phone or…

Account details

We may handle the name, contact detail and verification status you submit during account creation or access.

Device signals

A mobile browser or desktop session can provide device and connection signals such as browser type, time and security events.

Cookie controls

Cookies can remember a session choice and help us understand whether a page request belongs to an active account.

Account security

We use sign-in checks and phone verification details to reduce unauthorised account access. Never send a wallet password through support.

Retention decisions

We keep records only while they support the stated account, payment or legal purpose, then remove or de-identify them when…

Policy changes

If this Privacy Policy changes in a material way, we will place the updated wording where you can read it…

Privacy Policy Answers for uci33

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover access, wallet records, cookies, corrections and deletion requests without turning a personal data question into a general service explanation. If your situation is not listed, use the account help route with the relevant reference and we will assess the request under the policy and local law.

The uci33 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It applies when you create or use an account and when DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity is matched to your record.

We need selected account details to create your account, confirm phone access, answer requests and connect a payment reference with the correct record. We collect only what supports that purpose. Service access depends on local law, and eligibility is handled where local law permits.

No. The Privacy Policy does not require us to store your DANA, OVO, GoPay or QRIS wallet password. We may retain a transaction reference, amount, status and time so we can check a receipt or account mismatch without requesting secret wallet credentials.

Sign in, open the account help route and request a correction. State the field that is wrong and provide the account contact detail used during verification. We may complete an account check before changing it, so another person cannot edit your record.

You can submit a deletion request through account help. We will assess which records can be removed and which must remain for an account, payment or legal purpose. A QRIS receipt reference and a marketing preference may not follow the same outcome.

Cookies can retain a sign-in state, remember a consent choice and help connect a browser request with an active account. You can adjust them in your mobile or desktop browser. Disabling necessary cookies may prevent sign-in or access to the policy page.

Use the signed-in account help route and describe the request, such as access, correction, deletion or wallet-record clarification. Include a transaction reference when relevant, but never send a wallet password. We will review the request under this policy and local law.