Reference

super33 Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use, store and protect the details connected with your super33 account, including phone verification, wallet activity and device access.

Account clarityWallet recordsDevice choicesCookie controls
super33 super33 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Privacy Policy

A direct support request gives you a practical way to ask how this Privacy Policy applies to your account. Tell us which account detail, wallet reference, device record or cookie setting you want clarified, and include only the details needed to locate your request. We use the account and cashier paths to separate payment-status questions from privacy requests, so a receipt connected with QRIS or DANA can be checked without sending your full payment credentials.

Team online

Account path

Use the account help route when you want to ask about phone verification, sign-in records or the personal details attached to your super33 account. We may ask you to confirm account ownership before discussing or changing any private record.

Cashier path

For a privacy question involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, use the cashier support path and identify the relevant transaction date. We can then separate a receipt lookup from a request about stored personal data.

Policy request

Send a clear request when you want a copy, correction or removal assessment for data linked to your account. Include your registered contact detail and the result you seek; we will check the request under this Privacy Policy and local requirements.

DATA HANDLING

How super33 Applies This Policy

We apply this Privacy Policy at the points where account data is created or used, rather than treating privacy as a separate page with no operational link.

Account data

We may collect your account contact details, phone verification result, login history and messages you send to support. We use these records to provide the requested account service, answer privacy questions and identify which account a correction or access request concerns.

Wallet references

A DANA, OVO, GoPay or QRIS payment may create a reference, amount, status and timing record linked to your account activity. Bank transfer and virtual account records can serve the same tracing purpose, while sensitive payment credentials remain outside the details we need for support.

Device signals

When you sign in from a phone or desktop, we may record technical signals such as browser type, operating system, session time and security events. These signals help us protect account access and investigate a disputed login without using them for unrelated profile decisions.

Cookies

Cookies can keep the account path working, remember a session and help us understand whether a page request completed. You can manage cookies through your browser settings, though blocking necessary cookies may affect sign-in, phone verification or the route back to this Privacy Policy.

Retention

We keep account, support and transaction records for as long as needed for the stated service, security checks, dispute handling or legal duties. Retention can differ by record type, so a request to remove data is assessed against the reason that record must remain available.

Your request

You can ask what personal data we hold, request a correction, ask about deletion or question a particular use through the account help route. We may verify your identity before responding, and access or eligibility depends on local law and the rules that apply to your request.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, wallet and device questions you are most likely to have before opening an account. We keep the answers practical: they explain where a record comes from, why it is used and which support route to take. If your situation is specific, include the relevant account step or payment reference when you contact us.

The super33 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use those records for account access, security, wallet-status checks and requests about your data, with access depending on local law.

Phone verification helps connect an account request with the person trying to access it and helps us respond to privacy requests safely. We may use the verification result during sign-in or account support, but we do not treat it as permission to use your details for unrelated purposes.

Yes. The Privacy Policy includes payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These records can show a status, timing or receipt reference needed for account support, while the cashier path should not require your full payment credentials.

You can request a correction through the account help route by stating which detail is wrong and what it should say. We may ask you to confirm account ownership before making a change, then assess the request against this Privacy Policy and any applicable local requirement.

Send a data access request through account support with your registered contact detail and a clear description of the records you want, such as login events, wallet references or support messages. We verify the requester first, then respond according to this Privacy Policy and local law.

We retain different records for different periods because account details, security events, support messages and transaction references serve different purposes. We keep them while needed for the service, dispute handling, security or legal duties, and we assess removal requests against those reasons.

You can manage cookies through your browser settings on a phone or desktop. Necessary cookies may be required for sign-in, phone verification and the account path, so blocking them can affect those steps. This Privacy Policy explains their role and where to ask for clarification.