Reference

cmt777 Privacy Policy For Your Account

cmt777 Privacy Policy explains how we handle the details linked to your account, including phone verification, device access and DANA, OVO, GoPay or QRIS records.

Account dataWallet recordsCookie choicesPolicy requests
cmt777 cmt777 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route matters when you want to understand a data record or change an account detail. Start from the support area linked to your signed-in account, include the phone number or case detail we can match, and avoid sending wallet passwords or one-time codes. For a payment question, the cashier-status path helps us identify whether the record relates to DANA, OVO, GoPay, QRIS or a bank transfer.

Team online

Account support

Use the support path inside your account for a Privacy Policy question, correction request or access enquiry. Include the account phone number and the subject of your request so we can check the relevant record without asking you to disclose a password or verification code.

Cashier status

If your request concerns a DANA, OVO, GoPay or QRIS reference, send the transaction date, amount shown in your account and status label through the cashier support path. We use those details to locate the record while keeping wallet login credentials outside the request.

Policy request

For a copy, correction or deletion question, mention Privacy Policy and describe the exact data involved. We may ask you to complete phone verification before discussing account-linked details, because the request must come from the person connected to the account.

HANDLING PRACTICE

How cmt777 Handles Six Data Areas

We apply the Privacy Policy to practical account events rather than treating every record the same way.

Account details

We use your phone number and account credentials to identify the account you are trying to access. Phone verification can be required before we disclose account-linked details or complete a requested change, helping prevent another person from acting on your account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries may appear as reference data around a cashier action. We use status, timing and account matching details to investigate a record; we do not need your wallet password for that check.

Device signals

When you move from mobile login into the lobby, we may process browser, device and session signals needed to keep the connection active and spot unusual sign-in behaviour. These signals support account protection and are not a public profile about you.

Cookies

Cookies can remember a selected setting, maintain a session or help us assess whether a page loads correctly. You can manage cookie behaviour through your browser settings, although switching some cookies off may affect the account path or policy display.

Retention

We keep account, support and payment-reference records for the period needed to operate the requested service, resolve disputes and meet applicable legal duties. When a record is no longer needed for those purposes, our handling follows deletion or restriction rules available where local law permits.

Change requests

You can ask us to correct inaccurate account data, explain a record, restrict a use or remove data where the applicable rules allow it. Send the request through account support, complete any identity check requested, and tell us which record needs attention.

Privacy Policy Questions About cmt777

These answers focus on the requests we most often need to handle around account access, wallet references, cookies and data changes. Read the full Privacy Policy before opening an account, then use the support route when a question depends on your specific record or where local law permits a different request.

It covers account and phone verification details, sign-in and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, data requests and contact steps.

Our payment-reference checks use account matching, status and transaction details rather than your wallet password. Never send a wallet password or one-time code through support. If a record is unclear, provide the visible status and date shown in your account.

You can ask for an account-data copy through the support path connected with your signed-in account. State that the request concerns the Privacy Policy, identify the account phone number, and complete phone verification if we need to confirm the requester.

Send a correction request through account support and name the exact field or record that appears wrong. We may ask for phone verification before changing account-linked information. Requests are assessed under the rules that apply where local law permits.

Browser, device and session signals can help keep your mobile or desktop login connected and flag unusual access. They support account security and troubleshooting around the lobby path. They are handled as operational data, not displayed as a public profile.

Your browser settings usually let you remove or restrict cookies. Some cookies keep a session active or preserve a selected setting, so disabling them may change how account access or the policy page works. Contact support if a cookie choice causes an error.

We retain records for the operational, dispute-handling or legal period that applies to the specific record. This can differ between account details, support messages and DANA, OVO, GoPay or QRIS references. Ask support about a particular record and its applicable request options.