Reference

chery55 Privacy Policy for Your Account

Our Privacy Policy explains how chery55 handles the details connected with your account, from phone verification to wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet checksCookie choicesContact requests
chery55 chery55 Privacy Policy for Your Account
PRIVACY HELP PATH

Where to Ask About Privacy

A clear support route matters when a privacy request and a wallet record meet in the same account.

Account help path Send a privacy request from the signed-in account help path so we can connect your message with the correct phone verification record. For a DANA, OVO, GoPay or QRIS question, add the transaction reference and the date shown in your account.
Payment receipt check If a payment receipt contains the wrong account detail, tell us which field needs correction and attach only the relevant reference. We can check the wallet status or bank transfer record without asking for your wallet password, PIN or full banking credentials.
Privacy request status After you request access, correction or deletion, keep the request details for follow-up in the same support path. We may ask for a matching account step, such as phone verification, before discussing personal data linked to chery55.
DATA CONTROL DETAILS

Cookies, Security and Retention

Our handling of personal data follows the account journey rather than a single broad collection step.

Account details

We use your phone number and account settings to create access, complete the clear phone verification step and send account-related responses. You can ask us to correct a detail when your name, phone record or other submitted account field no longer matches your request.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain reference data and status rather than wallet passwords. This lets us match a receipt, investigate a stalled status and answer which account record was involved.

Mobile cookies

A mobile browser can store session cookies that support sign-in continuity and selected settings. You can clear cookies through your browser controls, although clearing them may sign you out and require the phone verification step again.

Security records

We record practical security signals such as sign-in time, device changes and failed access attempts. These records help us detect account misuse and confirm that a privacy request comes from the person connected with the account.

Retention period

We keep account, payment and support records for the period needed to operate the service, resolve disputes, protect access or meet a legal requirement. When a record is no longer needed, we remove it or make it no longer linked to you.

Request changes

You may ask for a copy, correction, restriction or deletion of personal data through the signed-in help path. We assess the request against account security and legal duties, then explain any detail we must retain and why.

Privacy Policy Answers for chery55

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep each answer tied to a real step, such as phone verification, a mobile cookie, a QRIS reference or a request made through the account help path. If your situation is not covered, contact us through that same path where local law permits.

The chery55 Privacy Policy covers personal data connected with your account, sign-in activity, device cookies, support messages and payment references. It explains why we use each category, how we protect account access, when records are removed and how you can request a copy or correction.

We may collect your phone number, account settings, phone verification status, sign-in records, device signals and messages sent through support. We use these details to provide access, protect the account and answer your request. We do not need your DANA, OVO or GoPay password.

Yes. The Privacy Policy covers payment references and status connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those details to match a receipt or investigate a stalled status, not to collect your wallet PIN.

Sign in, open the account help path and state that you are making a Privacy Policy data request. Ask for a copy, correction, restriction or deletion, and include the relevant account phone number. We may complete a phone verification check before releasing personal data.

We use session cookies on your browser to maintain sign-in continuity and remember selected settings. Your mobile browser controls can clear them, but clearing cookies may end the session and require phone verification again. The Privacy Policy explains how cookie records relate to account access.

We retain account, payment and support records only while they serve an operational, security, dispute or legal purpose. Once that purpose ends, we remove or anonymise the record where practical. A deletion request may not remove details that a legal or security duty requires us to keep.

Yes. Use the signed-in account help path and identify the field you believe is wrong, such as a phone record or payment reference. Do not send a wallet password or PIN. We check the request against the account and explain the correction outcome where local law permits.