Reference

Privacy Policy for Your cinasuper Account

Our Privacy Policy explains how we use information connected with your cinasuper account, including phone verification, sign-in activity and wallet status.

Clear data purposesWallet record contextAccount request path
cinasuper Privacy Policy for Your cinasuper Account
REQUEST HELP

Privacy Questions Follow Your Account Path

A clear support request helps us locate the right account record without asking you to send unnecessary details.

Account access If phone verification prevents you from reaching your account, contact support through the account…
Wallet records For a DANA, OVO, GoPay or QRIS reference, include the payment name, date and…
Data request Ask directly for access, correction or deletion guidance through our support route.
DATA HANDLING DETAILS

What We Protect Across Your Sessions

Privacy starts with knowing which account actions create records and why those records matter.

Account details

We use the details needed to create and maintain your account, including contact information used for phone verification.

Cookies and sessions

Cookies and similar session tools can remember an active sign-in, preserve requested settings and help us understand whether a page…

Account security

Phone verification is an account-security step before access, so we may retain evidence that a verification attempt occurred.

Payment references

A payment record may show a method such as QRIS, DANA or bank transfer, together with an amount reference and…

Retention choices

We keep information only for the period needed for the stated account, security, support or legal purpose.

Policy changes

When this Privacy Policy changes, we update this page so you can compare the current wording with your account needs.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account questions you are most likely to ask before opening or accessing cinasuper. They cover the information collected during sign-in, the handling of local wallet references, device sessions, cookies, retention and requests for changes. If your situation is not covered, send support a direct question without including passwords or private wallet credentials.

It covers information connected with your account, including phone verification, sign-in activity, device sessions, support messages, cookies and payment references. The policy explains why we use those records, how we protect account access and how you can ask for access, correction or deletion guidance.

Yes. The Privacy Policy covers the account-side references connected with DANA, OVO, GoPay and QRIS activity, such as a method name, processing status or transaction reference. The relevant wallet provider has separate rules, so its own privacy terms also apply to provider-held information.

We may collect the contact detail used for phone verification, sign-in events, device and browser information, session data and support history. We use these categories to provide account access, identify security concerns and answer a Privacy Policy request. You should never send us your password or wallet PIN.

You can ask support to correct inaccurate account information, explain a stored record or provide deletion guidance. We may verify that you control the account before acting. Some records may remain where they are needed for security, transaction support or a legal obligation, and we will explain that reason.

The policy applies when you access the account from a mobile browser, tablet or desktop. A device may create technical session and security records that differ from another device. If an unfamiliar device appears during access, contact support through the account path and change your sign-in credentials.

We retain each category for the period needed for its stated account, security, support or legal purpose. The exact period can depend on the record and applicable rules. You can ask support which category applies to your request and why a record cannot be removed immediately.

Use the support path available on the cinasuper site and identify your question as a Privacy Policy request. You can ask about phone verification, cookies, device sessions or wallet references before creating an account. Access or eligibility depends on local law, so include your Indonesia region only when relevant.