Reference

Privacy Policy For Your ultra33 Account

The ultra33 Privacy Policy explains what we collect when you open an account, sign in, use a mobile device or connect DANA, OVO, GoPay and QRIS.

Account recordsWallet activityCookie choicesContact requests
ultra33 Privacy Policy For Your ultra33 Account
CONTACT THE POLICY TEAM

Privacy Questions From Login To Wallet

A clear contact route matters when a Privacy Policy question appears beside an account or wallet action.

Account access If your phone verification or sign-in record looks incorrect, contact us through the account…
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the…
Privacy request To ask for access, correction or deletion, write from the contact detail attached to…
HOW WE HANDLE RECORDS

Inside ultra33 Data And Cookie Controls

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We use the contact details you provide to create your account, complete phone verification and respond to account messages. Before access is changed, we may compare the request with the account record so another person cannot alter your profile through a simple message.

Device signals

When you sign in on a phone, tablet or desktop browser, we may record device, browser and session signals linked to that access event. These signals help us examine an unfamiliar login; they are not a request for your device password or private files.

Cookie choices

Cookies can keep a session active, remember a page setting or show whether a policy page opens correctly. Your browser lets you delete or block cookies, although removing session cookies may require you to sign in again before opening account pages.

Wallet matching

A DANA, OVO, GoPay or QRIS status may be paired with an account reference so we can distinguish a pending record from a completed one. Bank transfer and virtual account references serve the same matching purpose without requiring us to store your wallet PIN.

Retention timing

We retain account, support and transaction records for the time needed to provide the requested service, investigate a dispute, protect account access or meet a legal duty. When a stated purpose ends and no duty remains, the record can be removed or placed beyond routine use.

Change requests

You can ask us to access, correct or remove eligible personal details by using the policy contact route. Include the account email or phone detail, the requested change and a brief reason; we may verify ownership before completing the request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the questions we expect before you open an account or connect a local wallet. They cover the data behind account access, mobile use, payment matching and contact requests. If your situation is not listed, use the account support route and refer to the exact record or policy point you want us to check.

The ultra33 Privacy Policy covers contact details, phone verification records, sign-in events, device signals, support messages and payment references. We use them for account access, security checks, wallet matching and support. You can ask us to access or correct eligible details where local law permits.

Our Privacy Policy does not ask you to send a wallet PIN through support. DANA, OVO, GoPay and QRIS may appear as payment status or reference details connected with your account, while your private wallet credential should remain with the relevant wallet service.

Device and browser signals help us identify an unusual sign-in, keep a session working and investigate an account access question. The Privacy Policy treats these as security and session records; we do not ask for your device password or access to private files.

Use the support contact displayed inside your account and state the detail that needs correction, such as a phone number or contact email. Include the account reference where possible. We may confirm ownership before editing the record, and the request depends on local law.

On a mobile browser, cookies can keep your session active and help us see whether a policy page loads correctly. You can block or remove them through browser settings. If session cookies are removed, you may need to complete account sign-in again.

You can submit a removal request through the policy contact route, using the email or phone detail attached to your account. We assess the request under local law. Some account, payment or support records may remain when needed for security, disputes or a legal duty.

Our support route inside the account area can receive a Privacy Policy question about access, correction, cookies, retention or wallet records. Give us the relevant account detail and avoid passwords or PINs. We will explain the next step and any ownership check required.