Reference

Open cod303 With Clear Privacy Choices

cod303 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account accessWallet recordsCookie choicesContact requests
cod303 Open cod303 With Clear Privacy Choices
CONTACT DATA CARE

Ask About Account Data and QRIS

A clear contact path helps you resolve a privacy question without repeating your account story.

Account request Use the contact route shown in your account area to ask what personal details…
Wallet record For DANA, OVO or GoPay references, include the relevant transaction date and wallet name…
Access concern If login or account access stalls, describe the device path and the last completed…
HOW WE HANDLE DATA

Explore Security Behind Your Account Path

We keep this policy practical by linking each data category to a visible account action. Phone verification helps us check ownership, device signals help us investigate unusual access, and wallet references help…

Account details

We may handle the details you provide for account creation, including contact information used during phone verification. We use those details for account access and related requests, not as a reason to collect unrelated personal material from your device.

Payment references

A DANA, QRIS, bank transfer or virtual account record can contain a reference, amount status and time needed to investigate a receipt. We use the reference for the payment question you raise, while your wallet credentials remain outside our account form.

Cookies and devices

Cookies and device signals can help keep your session connected while you switch from login to the lobby. On mobile, they may help us identify a returning browser; you can manage browser cookie controls, though changing them may affect account access.

Security checks

We may compare login details, phone verification and device activity when an account access pattern needs checking. This supports account protection around areas such as Domino QQ VIP Table without asking you to reveal a password in a contact request.

Retention periods

We retain account, security and transaction records only for the period needed for the stated account, safety or legal purpose. The period can differ by record type, so a request about retention should identify the account area and record you mean.

Changes and requests

You can ask us to correct account details, explain a data use or review a suitable deletion request through the contact path in your account area. We may verify ownership first, then reply with the action available under local requirements.

Browse cod303 Privacy Policy Answers

These Privacy Policy answers cover the account and wallet questions you are most likely to have before opening access. They explain phone verification, cookies, payment references, deletion requests and local eligibility in plain terms. If your case involves a specific receipt or device, use the contact route in your account area so we can assess the right record.

It covers account details, phone verification, login and device signals, cookies, wallet references, security checks, retention and requests about your records. It also explains how we handle questions linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us connect an account request with the person seeking access and helps protect account records from an unverified contact. We may use the verification result when you ask about login, correction, wallet status or another Privacy Policy matter.

Yes. The policy covers payment references such as a DANA receipt or QRIS status record when those details are connected to an account question. We use the reference to investigate the stated issue and may request account verification before discussing personal transaction data.

Use the contact route displayed in your account area and state which detail is incorrect, such as a phone number or account identifier. We may verify ownership before making a change, then explain whether the correction can be completed for that record.

You can send a deletion request through the account contact path. We first check ownership and identify the records involved. Some account, security or transaction data may need to remain for a stated legal or operational period, and we will explain the result.

Cookies can keep a mobile browser connected between phone verification, login and the lobby. You can adjust cookie controls in your browser, but refusing some cookies may interrupt account access or require another verification step. The policy explains the purpose of each relevant data use.

Our data practices are described for the account journey, but account access and eligibility depends on local law. Where local law permits, you can use the stated contact path for a policy question; check the rules applying to your location before opening or using an account.