Reference

cinapaten Privacy Policy for Your Account

Our Privacy Policy explains how we use the details connected with your cinapaten account, including phone verification, mobile-browser access and wallet records from DANA or QRIS.

Clear data purposesWallet record contextRequest paths
cinapaten cinapaten Privacy Policy for Your Account
HELP WITH DATA

Privacy Questions Near Account Help

A clear contact path matters when you want to ask about your Privacy Policy rights or an account record. Start from account help if you are already signed in, and include the phone detail connected with your profile so we can locate the correct record. If you are checking a DANA, GoPay or QRIS reference, keep the receipt details ready; we use them to separate a payment-status question from a personal-data request.

Team online

Account help

Ask about stored account details through the account-help route after signing in. We may ask for the phone verification detail linked to your profile before discussing private records.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the relevant receipt reference. This helps us check the correct transaction without exposing another account.

Privacy request

Use the privacy contact route shown with this policy to ask for access, correction or clarification. Tell us which record concerns you and how we should respond.

DATA PRACTICES

How We Handle Your Privacy Choices

We connect each privacy decision to a practical account step rather than asking for details without a purpose.

Account details

We use your account and phone-verification details to identify your profile, provide requested access and respond to account questions. We do not need unrelated personal details to show a game category.

Payment references

A DANA, OVO, GoPay or QRIS reference, or a bank-transfer and virtual-account receipt, may be retained to match payment status and resolve an account query.

Cookies

Cookies can keep essential account steps working across a mobile browser or desktop session. They may also help us understand security events, while non-essential choices remain subject to your settings.

Account security

We examine sign-in time, device type and verification events when an account needs protection. If activity appears unusual, we may request an account step before discussing private data.

Retention

We retain personal and payment records for the period needed to provide the requested service, address security matters or meet applicable legal duties, then assess whether continued storage is needed.

Your requests

You can ask for a copy, correction or clarification of personal records through the privacy route. Include your account identifier and request type so we can handle the right data.

Privacy Policy Answers for cinapaten

These Privacy Policy answers address the searches we hear most often about account records, local wallets, cookies and access. If your situation is not covered, use the stated privacy contact route and describe the account step or payment reference involved.

It covers account details, phone verification, device and session records, cookies, payment references, security checks, retention and requests to access or correct personal data.

Phone verification helps us connect an account request with the correct profile and protect private records. We may use it before discussing wallet status or changing account details.

Yes. The policy explains that DANA, OVO, GoPay and QRIS references may be used to match a payment status or receipt with your account.

Cookies can support essential sign-in and account movement in your mobile browser. They may also help identify security events, subject to the choices available in your browser settings.

You can request access to personal records through the privacy contact route. Include your account identifier and the records you want checked so we can handle the request accurately.

Send a correction request through the privacy route and identify the detail that needs changing. We may ask for an account step before updating or discussing private information.

We keep records for operational, security or legal needs, then assess whether storage is still required. Payment receipts and verification events may need separate retention for account checks.