Reference

Privacy Policy That Keeps Your Account Clear

Your cuan805 Privacy Policy puts account data, cookie choices, and DANA, OVO, GoPay, QRIS records in plain view before you open your account; from Bandung or anywhere access…

Account data useDANA recordsOVO recordsGoPay and QRIS logsCookie controls
cuan805 Privacy Policy That Keeps Your Account Clear
PRIVACY HELP

Reach Us About Your Privacy

Privacy questions should reach the team that can check account records, not a public comment box.

Live chat after login Open your account menu, choose Help, then select Privacy Request. Chat works well for cookie questions, device access checks, and requests tied to recent DANA, OVO, GoPay, or QRIS activity.
Email privacy desk Send privacy requests to [email protected] with your account name and registered contact. We use email for data access, correction, and deletion requests because it gives you a dated written trail.
WhatsApp identity check Use the WhatsApp link shown inside your account for quick verification questions. We may ask for your registered phone, last login device, and payment rail used before we discuss account data.
DATA CONTROL

Control Your Data Inside cuan805

We handle privacy through account steps you can see. Registration collects the details needed to create your wallet profile, payments add transaction references, and gameplay adds session records for security and dispute…

Account data collected

When you open an account, we collect your name field, contact detail, password hash, device type, and login records. These items let us protect access and answer privacy requests tied to your profile.

Payment record handling

DANA, OVO, GoPay, and QRIS activity creates references inside your wallet history. We keep the payment rail name, time, amount, and status so you can ask about a transaction without exposing full wallet credentials.

Cookie choices

Cookies remember language, session state, and security signals on your phone browser. You can clear cookies through your browser settings, but doing so may require a fresh login and device check.

Device security logs

New device access may trigger extra checks, especially after a password reset or payment dispute. We record device and IP signals to spot account takeover attempts and protect your privacy request history.

Retention period checks

Some records stay while your account remains active, while payment and dispute records may be kept longer where required. When you ask for deletion, we separate removable data from records we must retain.

Correction requests

If your contact detail or profile field is wrong, contact us through logged-in chat or [email protected]. We verify your identity first, then update eligible data and confirm the change by message.

Privacy Answers Before You Open Account

These answers explain how the policy works when you share data with us, use a local wallet, change devices, or ask for a copy of your records. If your question touches account ownership, payment tracing, or deletion, contact us through a logged-in channel so we can confirm it is really you before acting.

We collect the fields needed to create and protect your account, such as contact detail, password hash, device type, login time, and wallet activity. We use those records for access, payments, support, and security checks.

Yes. We record payment rail, transaction time, amount, status, and reference code where available. We do not need your full wallet password, and we ask you not to send private wallet screenshots unless support requests a masked proof.

Email [email protected] or use logged-in chat under Help and Privacy Request. We verify your registered contact, then prepare eligible account, wallet, and access records in a format our team can safely share.

You can request correction through live chat after login or by email. We may ask for your registered contact, last login device, and recent payment rail so we do not change data for the wrong account.

Device and IP records help us detect unusual access, investigate account disputes, and protect privacy requests from impersonation. These logs also help confirm whether a login came from your usual phone browser or a new device.

We keep records for as long as needed to operate your account, handle disputes, trace payments, and meet duties that apply where access is permitted. Deletion requests are checked against those needs before we remove data.

Only the support and account teams that need the request can see it. We limit access to your case details, keep the request linked to your account, and use identity checks before making privacy changes.