Reference

ultra33 Privacy Policy for Your Account

The ultra33 Privacy Policy explains what we collect when you open an account, verify your phone, browse from a mobile browser or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesPhone verification
ultra33 ultra33 Privacy Policy for Your Account
REQUEST ROUTES

Where Privacy Policy Questions Go

A clear contact route helps you ask about the Privacy Policy without placing sensitive wallet details in the wrong message.

Account data request Use the support route inside your account to ask what personal details we hold under the Privacy Policy. We may ask you to confirm the phone number linked to the account before discussing account-specific records.
Wallet reference check If a DANA, OVO, GoPay or QRIS reference needs clarification, send the transaction reference rather than a wallet password. We use the reference to locate the related cashier record and explain its status.
Access and correction For a correction, deletion request or question about local availability, contact us through the account support path. Access to ultra33 depends on local law, and we may need phone verification before changing personal details.
HANDLING YOUR RECORDS

What We Do With Account Details

The Privacy Policy is applied during ordinary account steps, not only after a support question. We separate contact details, technical logs and cashier references so each record has a practical purpose.

Account creation

When you open an account, we collect the details needed to create your profile and send account notices. Phone verification happens before account access, helping us connect the verified number with the correct account record.

Cashier references

A payment reference can show that a DANA, OVO, GoPay, QRIS, bank transfer or virtual account action belongs to your account. We use this record for matching, status checks and replies about a cashier enquiry.

Device activity

When you use a mobile browser, we may record browser type, operating details, connection data and session times. These entries help us investigate unusual access and explain why a phone verification step appeared.

Cookies

Cookies and similar storage can keep a session active, remember basic choices and help us understand which account page was opened. You can manage cookies through your browser settings, although some account functions may then need another login.

Account protection

We use phone verification, session checks and access logs to reduce unauthorised account activity. Never send a password or complete wallet credential in a support message; our team uses account references and verification steps instead.

Retention and requests

We retain records for as long as needed for account operation, dispute handling, security checks and legal duties. You can ask for access, correction or deletion through support, subject to identity checks and any required retention period.

Privacy Policy Answers for ultra33

These Privacy Policy answers address the searches we most often expect before an account is opened. They cover the data behind phone verification, mobile sessions, wallet references, cookies and requests for access or correction. If your question concerns a particular account record, use the support route shown after login and avoid sending passwords or complete wallet credentials.

The ultra33 Privacy Policy covers account details, phone verification, device and session records, cookies, cashier references and support messages. It explains why we use each type of data, how long records may be retained and how you can request access or correction.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS actions, plus bank transfer and virtual account references. We use those references to match an account action, check status and respond to a cashier question.

Phone verification connects an account request with the phone number supplied during registration and helps reduce unauthorised access. Under the Privacy Policy, we retain the verification status and related account record for security, support handling and required legal purposes.

When you use a mobile browser or desktop browser, we may record browser type, session time, connection details and technical device information. The Privacy Policy allows us to use these entries for login checks, security investigation and account support.

You can request access to, or correction of, personal details through the account support route. We may first confirm your phone number and account identity. The Privacy Policy allows exceptions where keeping a record is required for security, disputes or law.

Send a deletion request through the support path shown in your account, stating which details you want removed. We verify the request before acting. Some records may remain under the Privacy Policy when needed for legal duties, security checks or unresolved payment matters.

Yes. Access to ultra33 depends on local law, and the Privacy Policy applies where local law permits. If a local rule affects account access or data handling, we may limit an account action and explain the available support path.