Reference

Privacy Policy For Your 22crown Account

22crown Privacy Policy shows how we handle the details linked to your account, including phone verification, device access and wallet activity through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
22crown Privacy Policy For Your 22crown Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you control your account data without searching through unrelated pages.

Policy contact route Send a request through the contact route shown with this Privacy Policy when you…
Account support path If your phone verification or sign-in record is incorrect, start from the account support…
Cashier record check For a payment reference, include the wallet or bank rail used and the account…
SECURITY PRACTICE

How We Handle Account Data

Privacy work is tied to practical account controls rather than a broad statement.

Data collection

We collect details needed to open and protect your account, including a phone number, verification status, sign-in events and selected…

Cookie controls

Cookies can keep your session active, remember selected settings and help us spot unusual access.

Account security

Phone verification is checked before account access and before certain account changes.

Retention periods

We retain account, security and payment-reference records only while they serve the stated account, support or legal purpose.

Change requests

You can ask us to correct inaccurate account details, explain a record or request deletion where local law permits.

Privacy contact

For a privacy request, use the contact route attached to this policy and describe the account step involved.

Privacy Policy Questions Answered

These Privacy Policy answers focus on the account questions you are most likely to have before opening or using 22crown. We cover phone verification, wallet references, mobile cookies, deletion requests and access that depends on local law. If your question concerns a specific DANA, OVO, GoPay, QRIS or bank transfer record, use the policy contact route and identify the account step involved.

It covers account details, phone verification, sign-in events, device signals, cookies, support records and payment references. It explains why we use each category, how long we retain it, how we protect it and how you can request access, correction or deletion where local law permits.

No. Our Privacy Policy describes payment references used to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity to your account. We do not ask for or store your wallet password. Do not send passwords or one-time codes through a support request.

We use phone verification to confirm account ownership before access and selected account changes. The result can also help us investigate unusual sign-in activity. If the phone detail is wrong, use the account support path and be ready to confirm ownership before we discuss or change it.

Yes. Use the contact route attached to this Privacy Policy and state whether you want a copy, correction or explanation. We may request account verification before responding. A deletion request may be limited when a security, transaction or legal record must remain.

Cookies can maintain a mobile session, remember settings and help identify unusual access. Your browser can clear or restrict them, but you may need to sign in again. The Privacy Policy remains reachable from the account area after you return to the mobile lobby.

We keep each category only while it supports account operation, security, support or a valid legal purpose. Account and payment-reference records may therefore have different periods. When the relevant purpose ends, we remove, anonymise or restrict the record through our internal process.

Yes. Certain access, deletion and data-handling requests depend on local law. We assess the request against the applicable rules for your account context, explain any limit, and still provide the policy contact route so you can ask for clarification.