Reference

super33 Privacy Policy For Your Account

super33 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay, QRIS or bank transfer.

Clear data purposesWallet activity contextDevice access choicesContact and change requests
super33 super33 Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Policy Help Beside Your Account

A clear contact route matters when a privacy question appears during login, phone verification or a wallet status check. We ask you to include the account identifier you used and a short description of the request, without sending a full password or secret security code. That lets us locate the right record while reducing unnecessary exposure. If your question starts beside a QRIS or DANA cashier step, keep the payment reference available so we can separate an access issue from a transaction-status question.

Team online

Account request

Use the account support path when you want to ask what personal data is linked to your login, phone verification or device session. We may ask for a matching account detail before responding, so your request is handled against the correct super33 record.

Wallet privacy

For DANA, OVO, GoPay or QRIS questions, share the payment reference and wallet name rather than a password or full private credential. We use those details to trace the relevant status record and explain what payment data is retained.

Access correction

If your name, phone detail or account record needs correction, contact us through the same support route and describe the requested change. We may verify ownership before editing the record, especially when the request affects account access or bank transfer matching.

DATA PRACTICES

Inside super33 Privacy Handling

Privacy work is part of the account flow rather than a separate promise shown only on this page.

Account data

We may hold details you provide during account creation, including contact data used for phone verification.

Device signals

A mobile browser or desktop session can provide technical signals such as browser type, approximate session timing and security events.

Cookies

Cookies and similar storage can remember session choices, support account continuity and help us understand whether a page request completed.

Payment records

A DANA, OVO, GoPay or QRIS reference can be connected to your account status so we can identify a pending…

Retention choices

We retain account, security and payment records for the period needed to provide access, resolve disputes, prevent misuse or meet…

Policy requests

You can ask for access, correction, deletion or clarification through our support path.

Privacy Policy Questions About super33

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account or returning from a mobile device. We keep the wording practical: what data is used, why a payment reference appears, how cookies work, and what route to take when you want a change. Access depends on local law and the terms that apply to your location.

The super33 Privacy Policy covers data connected with account creation, phone verification, login activity, device signals, cookies, support messages and payment references. It explains why we use those records for access, security, payment matching and legal duties, plus how you can request access or correction.

Yes. The Privacy Policy includes payment references and status details returned during DANA, OVO, GoPay or QRIS steps. We use them to match a transaction with your account and investigate a pending status. Do not send your password or private wallet credential when asking for help.

Phone verification helps us confirm that an account request belongs to the person controlling the contact detail. It can support login recovery, account protection and privacy requests. We may ask for a matching account detail before changing personal data or discussing records connected with your account.

You can request a correction through the account support path. State which detail is wrong and provide the account identifier used for sign-in. We may verify ownership before making the change, especially when the detail is also used to match QRIS, wallet or bank transfer records.

We keep records for as long as they support account access, security checks, payment reconciliation, dispute handling or applicable legal duties. Retention depends on the record type. When the purpose ends, we remove the record or separate it from direct account identity where practical.

Yes. Your mobile browser settings let you clear or restrict cookies and similar storage. This can end an active session, remove saved preferences or require another login. The Privacy Policy explains that technical session data may still be needed for security and account continuity.

Use the support path linked with your account and describe whether you want access, correction, deletion or clarification. Include a safe account identifier and, for a payment question, the transaction reference. Access and eligibility depend on local law, and we may verify ownership before replying.