Reference

cina365 Privacy Policy for Your Account

cina365 Privacy Policy explains how we handle the details connected with your account, wallet status and visits to our site.

Clear data purposesWallet record contextPhone verificationPolicy request path
cina365 cina365 Privacy Policy for Your Account
CONTACT ROUTES

Ask Us About Privacy Policy

A direct support request gives you a practical route when you have a question about the Privacy Policy or a record linked to your account. Include the phone number or account detail you can safely confirm, the subject of your request and any relevant payment reference. We use that context to locate the right record without asking you to send a password or full payment credentials. If you are in Medan or elsewhere in Indonesia, the same policy request path applies where local law permits.

Team online

Account request

Send a Privacy Policy question through our account support path and identify the account with details you can confirm safely. We can explain the relevant data purpose, ask for an account step when needed and keep the request tied to the correct cina365 record.

Wallet record

For a DANA, OVO, GoPay or QRIS question, include the transaction reference and status shown in your account. We use that receipt context to locate the payment record; never send your wallet PIN, password or complete card credentials in a support message.

Access concern

If phone verification or a device session affects your account access, tell us what changed and which device path you used. We can check the security event and explain the next account step without treating a new device as permission to disclose another person’s data.

HANDLING DETAILS

How We Apply This Privacy Policy

The Privacy Policy is applied through ordinary account and site operations rather than through a separate public profile.

Account data

We handle the contact and verification details needed to create, secure and maintain your account. A phone verification result helps connect an access attempt with the correct account, while support notes remain related to the request they were created to resolve.

Payment references

We retain payment references and status details so we can match account activity with DANA, OVO, GoPay, QRIS, bank transfer or virtual account records. The reference supports reconciliation and support checks; it does not require you to share a wallet PIN.

Cookies and sessions

Cookies can keep your login session working and preserve practical settings between pages. Device and browser signals may also help us identify an unusual session. Your browser controls can remove or restrict cookies, though some account functions may then need another sign-in.

Account security

We use account checks, phone verification and session signals to reduce unauthorised access. If you move from a familiar phone to a new browser, an additional check may be requested before account details or wallet status are shown.

Retention timing

We keep each record for the period connected to its purpose, account relationship, dispute handling or legal requirement. When a retention reason ends, the record can be deleted, anonymised or placed beyond ordinary account access according to our internal handling process.

Changes and requests

You can ask us to correct account details, explain how a record is used or request removal where applicable. We may verify your identity before making a change, and the result depends on local law, record type and any duty to keep transaction evidence.

Privacy Policy Questions for cina365

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening an account. They explain the practical records behind phone verification, device access and local payment status, while leaving a clear route to support when your situation needs a specific check.

The cina365 Privacy Policy covers account details, phone verification, device and browser activity, cookies, support messages and payment status records. It explains why we use each category, how we protect access and how you can ask about correction, access or removal where local law permits.

Phone verification helps us connect an access attempt with the correct account and identify unusual login activity. We may use the result during account recovery or a new-device check. It is not a request for your wallet PIN, password or complete payment credentials.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those details to match an account action, check a receipt and resolve a status question without requesting secret wallet credentials.

We may handle browser type, device signals, session times and security events linked with your account access. These details help keep a session working and identify unusual activity. You can manage cookies in your browser, although restricting them may require another sign-in.

Retention depends on the purpose of the record, your account relationship, dispute handling and any legal requirement. Payment references may need to remain available for reconciliation, while other records can be deleted or anonymised when their handling purpose ends.

Use our account support path and describe the record you want corrected, such as a contact detail or payment status reference. We may ask you to confirm account ownership before changing it. The result depends on local law and the type of record involved.

You can request removal through support and explain which account records you mean. We will assess the request against the Privacy Policy, account status, transaction evidence and applicable law. Some records may need to remain available after access to them is restricted.