Reference

Open cmd398 Privacy Policy Clearly

cmd398 Privacy Policy shows what account, device and wallet details we use when you move from phone verification to the lobby.

Clear data purposesWallet detail handlingPhone access checksContact route included
cmd398 Open cmd398 Privacy Policy Clearly
CONTACT ROUTES

Switch to Privacy Support When Needed

A direct support route helps when a Privacy Policy question concerns your login, wallet status or a payment receipt.

Account request Ask us to locate your account data by using the contact route connected to…
Wallet query For DANA, OVO, GoPay or QRIS records, include the payment reference and date rather…
Receipt status If a bank transfer or virtual account receipt is part of your request, attach…
DATA PRACTICES

Browse cmd398 Privacy Handling Details

Privacy depends on practical account controls, not vague promises. We separate login details, payment references, device signals and support messages so each request can be handled for its stated purpose.

Purpose first

We use phone, account and session details to provide access, verify requests, protect sign-in activity and answer support cases. A DANA or QRIS reference is handled for payment matching, not as a general profile label.

Cookies and sessions

Browser cookies and session markers help keep your sign-in active and remember the route from login to the lobby. You can manage browser permissions, though some account actions may then require another sign-in.

Device signals

A mobile browser and desktop browser may create separate security signals, such as session time and device type. We use these signals to identify unusual access and support account checks.

Account security

Phone verification comes before account access and may be requested again for a sensitive privacy change. Never send us your password, wallet PIN or one-time verification code in a message.

Record retention

We retain account, payment and support records for the period needed to operate the account, investigate disputes, protect against misuse and meet applicable duties. The period can differ by record type.

Change requests

You can ask us to access, correct or remove eligible personal details through the support route. State the request clearly, and we may verify your phone before making a change.

Browse Privacy Policy Questions

These Privacy Policy answers cover the account steps you are most likely to ask about before opening an account or contacting us. They explain wallet records, browser activity, phone checks, correction requests and local access in plain language. If your situation is different, use the privacy support route and describe the specific record or event you want us to locate.

It covers account details, phone verification, browser and device signals, wallet references, payment receipts and support messages collected while you access the service where local law permits.

Yes. The policy covers DANA and QRIS references used to match a payment event, along with OVO, GoPay, bank transfer and virtual account records connected to your account.

Phone verification helps us confirm account ownership before access and before discussing a private data request. It also helps separate your account from an unverified support message.

We use browser cookies and session markers to maintain sign-in and connect your mobile path to the lobby. Changing browser permissions can end a session or require another sign-in.

Yes. Send a clear correction request through the privacy support route, identify the detail that seems wrong, and complete any phone check needed to protect your account.

We keep payment and account records for the period needed for service, security, dispute handling and applicable duties. The period may differ for a QRIS receipt, bank record or support case.

Use the support route linked beside the cashier path and state whether you want access, correction or deletion of eligible data. Account verification may be required before we respond.