Privacy Policy

Privacy

Cricket99 Privacy Policy

This privacy policy explains how Cricket99.com.co handles public guidance, support links, login previews, payment help and user safety information.

Cricket99 safety checklist and account protection visual

Information You Should Not Enter Here

This website does not need your Cricket99 password, OTP, UPI PIN, wallet password or private banking credentials. The login fields shown in visual previews are not working credential collection forms.

If you need login reset, app access or payment help, use the support button and share only the details needed for that support case. Keep passwords and sensitive codes private.

Do not upload private documents or payment screenshots to unknown pages. If support asks for a screenshot, review it first and avoid exposing unrelated private codes.

Support Links And External Routing

Cricket99 support should feel simple for a mobile user. The public pages explain login, app, ID, payment and safety routes without asking visitors to type passwords into this website.

All external support buttons use a managed support path. That allows the support route to be updated without printing raw phone details across static pages, images or old cached content.

Users should still be careful. A managed support button does not mean every link on the internet is safe. If a route appears from an unknown source, check the safety page before entering account details.

Cookies, Analytics And Basic Site Data

Like most WordPress websites, the site may use technical cookies, performance tools, security tools or analytics to keep pages usable and understand basic traffic patterns.

Public page content is written to guide users. It is not a place to submit passwords, card details, OTP codes or private wallet information.

If a browser, plugin or cache stores page data, old pages may remain visible for a short time. Use the current support button on the live site when contact routing matters.

Payment And Screenshot Privacy

Payment help may require method, time, reference and status details. That is different from sharing sensitive PINs or wallet passwords.

When sharing a screenshot for support, check whether it contains unrelated private information. A useful screenshot shows the transaction status and reference while avoiding unnecessary exposure.

Never rely on payment details embedded in old images. Current support guidance should be used for payment questions.

How To Use This Information Safely

Read the section that matches your current issue before opening support. A user with a login problem should not start by sending payment screenshots, and a user with a payment question should not start by sharing a password. Keeping the issue clear protects the account and makes support easier to follow.

If a request feels rushed, pause before sending private details. Passwords, OTP codes, wallet PINs and unnecessary documents should not be shared through random pages or unknown contacts. Use the managed Cricket99 support path and explain the issue in plain language.

Mobile users should also check whether the problem is caused by device settings, app update, browser redirect, network change or an old saved link. These small details often decide whether the next step is login help, app help, ID support, payment support or safety guidance.

More Cricket99 Help

Cricket99 support

Use this for reset, account locked, app not opening and payment questions.

Privacy Policy FAQ

Does this website collect my Cricket99 password?

No. Do not enter or send passwords through this website.

Are raw contact details printed here?

No. Support uses a managed external path.

Can I share payment screenshots?

Only share what is needed through support and hide unrelated sensitive data.

Does this website host APK files?

No. App guidance is informational and support-routed.

What should I do if I shared private details by mistake?

Stop using that route and contact support for account safety help.

Support