Reference

Privacy Policy for Your sea33 Account

sea33 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and device access.

Account dataWallet detailsCookie choicesContact path
sea33 Privacy Policy for Your sea33 Account
HELP WITH DATA

Privacy Questions Reach Our Support Desk

A direct support route helps when your Privacy Policy question involves an account step, wallet reference or device sign-in.

Account request Use the account support path for a Privacy Policy request about your phone verification…
Wallet query If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, include…
Device help For cookie or device questions, tell us whether you used a mobile browser or…
DATA HANDLING

What We Do With Your Personal Data

Privacy Policy choices matter most when they match real account events. We connect a phone verification step with your account, record wallet references needed for payment status, and…

Account details

We may use your name, phone contact, sign-in data and account activity to open and maintain your profile.

Payment records

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us match a payment status to your account.

Cookies

Cookies can keep a sign-in session, remember a selected setting and support security checks.

Account security

We use sign-in events, device details and phone verification to spot access that does not fit your account pattern.

Retention

We retain account and transaction records only for the period needed for account operation, dispute handling, security checks or a…

Data requests

You can ask for a copy, correction or deletion of personal details through the support desk.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the questions we hear before an account is opened or a wallet is connected. They explain what to send to support, what happens on a mobile browser and why payment references appear in an account record. If your situation is not covered, use the support path with the smallest amount of personal detail needed to locate your account. Access depends on local law.

The sea33 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, payment references and support messages. It also explains retention and how to request access, correction or deletion. The policy applies to your use of our pages where local law permits.

Phone verification helps us confirm that an account request belongs to you and helps protect account access from unusual sign-ins. It may also support a data request when you ask us to change or disclose personal details connected with your account.

Our Privacy Policy treats DANA, OVO, GoPay and QRIS references as payment-status records, not as a request for your wallet PIN. Do not send a PIN, password or full banking credential to support. We need only the account and transaction details needed to trace a query.

Cookies can keep your sign-in session, save a setting and help with security checks on a mobile browser. You can clear them through the browser settings on your phone. After clearing storage, you may need to sign in again or complete phone verification.

Yes. Send a request through the account support path with the phone or email linked to your account and state that you want a data copy. We may verify your identity before responding, and the available scope depends on local law and record requirements.

Contact the support desk and identify the account detail that needs correction, such as a phone contact or profile entry. We compare the request with your account and may ask for a verification step. Payment and security records can have separate correction limits.

You can ask us to delete personal details through the support path. We assess the request against account security, payment reconciliation, dispute handling and legal record duties. Where local law permits deletion, we remove or separate the applicable data and explain any record that must remain.