Policies | Cric BatBall

What this hub covers

The main rules, disclosures, and support standards behind the public site

This page is designed as a policy index for visitors who want more than short footer links. It explains where Cric BatBall sets out the rules for platform use, how match-entry timing is described, what broad disclaimer limits apply, how support and grievances are handled, and how privacy, cookies, accessibility, and data security are addressed on the current site.

Policy Guide explains the full policy set in simple language and points users to the right official page
Terms explains who may use the site, what conduct is expected, and what service limits apply
Privacy, cookies, and data security explain different parts of the information-handling picture
Disclaimer explains what the current public site does not guarantee or offer
Responsible Play, Accessibility, Community Guidelines, and Grievance explain safety, conduct, inclusion, and escalation

Current public policy position

Current public model and disclosures

The current published site presents free participation and recognition-based outcomes only. It does not present deposits, wagering, or cash prizes on these pages. It also states that Cric BatBall is an independent fan platform and does not claim official affiliation with IPL, BCCI, TATA IPL, or any franchise.

Important context: match entry on Cric BatBall is described as opening only around the real fixture window, and player selection is described as following the official playing XI rather than advance speculation.

Policy pages

What each page is designed to explain

Each page below has a different role. Together, they explain the current Cric BatBall platform more clearly than a short legal footer alone can do.

Policy Guide Explains the full Cric BatBall policy set in plain language, including what the platform is, what users can do, what rules apply, and why the official policy pages still control if there is a conflict. Terms Explains who may use the site, how match access is framed, what conduct is prohibited, what service limits apply, and how Cric BatBall describes its current free-participation model. Privacy Explains what information may be received, how it may be used, when it may be shared, how long it may be retained, and how visitors can request help with privacy issues. Cookies Explains how cookies and similar browser storage may support sessions, preferences, measurement, and security, along with the visitor controls that may affect those tools. Data Security Explains Cric BatBall's security approach in practical terms, including access discipline, monitoring, incident handling, user responsibilities, and the limits of any security programme. Disclaimer Explains the limits of public information, service availability, third-party references, and why the current site should not be treated as offering money, redeemable rewards, or official league affiliation. Responsible Play Explains adult-only participation, the difference between free play and healthy play, warning signs that suggest taking a break, and when to seek help or step back. Accessibility Explains the practical accessibility goals for Cric BatBall, where barriers may still exist, how feedback should be submitted, and why the page should not be read as a blanket compliance certification unless explicitly stated. Community Guidelines Explains respectful behavior, fair-play expectations, moderation logic, reporting routes, and the kind of conduct that can lead to warnings, restrictions, or review. Grievance Explains the formal escalation route for complaints or unresolved issues that need documented review beyond normal support.

How these pages connect

Each policy answers a different practical question a visitor may have

Can I use the site? Start with the Policy Guide, Terms, Responsible Play, and How to Play to understand eligibility, live-entry timing, and the current free-participation model.

What information is involved? Read Privacy for information use, Cookies for browser-level tools, and Data Security for the protection and incident-response side of the same picture.

What is not promised? Read the Disclaimer to understand the limits around information accuracy, service availability, third-party references, and the absence of cash or real-world value items on the current public site.

What if I face a problem? Use Accessibility for usability barriers, Community Guidelines for conduct expectations, and Grievance if the matter needs a more formal documented escalation.

What if the platform changes later? Check the update dates and the relevant policy page again, because any new participation model, new data practice, or new support process should be reflected in the public policy set.

Why these explanations are longer

The policy set is meant to reduce guesswork, not just satisfy a footer requirement

Cric BatBall's policy pages are written to explain the real operating model in plain language. That means the pages should tell visitors what is currently live, what is not promised, where support fits in, and how different issues should be routed instead of relying on vague legal wording alone.

Policy Guide turns the policy set into an easier plain-language explanation
Terms explains the use rules and service limits behind the public site
Privacy, Cookies, and Data Security explain different layers of information handling
Disclaimer explains what is informational, what may change, and what is not offered on the public site
Support-related pages explain help channels, inclusion standards, conduct rules, and escalation routes
The full policy set should evolve when the product model or operational practices materially change

How to use this policy set

Start with the page that matches the question you actually have

Before using the site Read the Policy Guide, Terms, Responsible Play, and How It Works pages to understand eligibility, match timing, and the current free-participation model.

If privacy matters most Read Privacy, Cookies, and Data Security together, because they explain different parts of the same information-handling picture.

If you want the limits first Read the Disclaimer to understand what Cric BatBall does not guarantee and what is not being offered on the current public site.

If you face a barrier Read Accessibility for usability issues, Community Guidelines for conduct issues, and Grievance if the issue needs a formal escalation path.

If features change later Use the updated dates on each page and the public disclosures in the policy set to understand what has changed and whether the participation model has been revised.

Future changes

New features should bring new disclosures

If Cric BatBall later adds paid entry, prizes of value, deeper account systems, additional analytics tools, or regulated features, the policy pages should be updated before or at launch. That includes updating the terms, privacy, cookies, security, and disclosure language instead of leaving old assumptions in place.

New data practices should appear in Privacy and Cookies
New technical controls or vendors should be reflected in Data Security where material
New participation formats should be explained in Terms and Responsible Play
Any major operational change should be paired with a new visible update date