Reference

calo22 Privacy Policy for Indonesia

Our Privacy Policy explains what we collect when you open a calo22 account, sign in on mobile, browse Live Blackjack Elite or use DANA and QRIS.

Account clarityWallet dataCookie choicesPolicy contact
calo22 calo22 Privacy Policy for Indonesia
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A direct support route helps when you want to understand the Privacy Policy rather than guess what a setting means.

Account support Use the support area after login for a Privacy Policy question. Include your account contact detail and request type so we can check the correct record, especially when a DANA, OVO, GoPay or QRIS reference is involved.
Access questions If account access stalls during phone verification, tell us which step appeared and what device you used. We can explain the relevant data purpose without asking for your password or a full wallet credential.
Request follow-up For a correction or removal request, identify the information concerned and the account contact used to open it. We may ask for a safe account check before changing records connected with payment status.
DATA HANDLING

Know What Privacy Controls Cover

The way we handle data is set out in our Privacy Policy so you can connect each control with a real account action.

Account records

We use the details supplied during account opening to create and maintain your profile, complete phone verification and respond to account requests. If a contact detail changes, ask us to correct the record through the account support route.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference, amount and status record. We use that trail to match a cashier event, investigate a mismatch and keep financial records accurate.

Cookies and sessions

Cookies can remember a sign-in session, language choice or security state on your device. You can manage cookie permissions in your browser, although changing them may require another login before account pages open.

Security signals

We may assess device, browser, sign-in time and network signals to spot unusual account activity. These checks help us protect your access; they are not a request for your wallet password or private payment PIN.

Retention periods

We keep records only for the period needed for the stated account, security, support or payment purpose, subject to legal duties. Ask through support which category applies to your record and why it may still be retained.

Your requests

You can ask what personal data we hold, request a correction, question a use or seek deletion where local law permits. We may verify ownership through your account contact before making a change or sharing account-specific details.

Answers Before You Open Your Account

These Privacy Policy answers address the searches we hear most often from people considering calo22 in Indonesia. They cover account creation, wallet references, device activity, cookies, access requests and policy contact. If your situation is different, use the support area after login and describe the exact account step or data category involved. We will use that context to explain the relevant section without turning a general question into a request for sensitive credentials.

The calo22 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, game-page activity and payment references. It also explains retention, security measures and how you can ask for access, correction or deletion where local law permits.

We use your phone number for account creation, verification and account-related contact. It can help us identify the correct profile when you ask about a DANA, OVO, GoPay or QRIS status. We do not need your wallet PIN to handle that request.

Yes. The policy covers references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These may include a payment reference, status and timing so we can match your account request. Wallet credentials remain with the relevant payment service.

We may collect browser type, device details, sign-in time, network signals and security events connected with your session. This helps protect account access and investigate unusual activity. The policy explains the purpose, and you can ask support about a specific device record.

Open the account support area and state which detail needs changing, such as a contact record or profile field. We may confirm ownership using your account contact before editing it. This route also lets you ask why a particular field is retained.

You can submit a removal request through account support. We assess it under the Privacy Policy and applicable local requirements, because some security, transaction or legal records may need to remain for a defined period. We will explain the result and its reason.

Use the cookie and site-permission controls in your mobile browser to allow, block or clear cookies. Removing session cookies may sign you out and require phone verification again. The Privacy Policy explains which cookie purposes support access and how to ask us about them.