Privacy Policy

This page explains what information Cric BatBall may receive, how that information may be used or shared, how long it may be retained, and what routes are available if a visitor wants to ask questions, request corrections, or raise a privacy concern.

Last updated: March 12, 2026 Support email: knowmore@cricbatball.com Scope: public site and support interactions

What this policy covers

This policy applies to information connected with Cric BatBall's public pages, support contact, policy requests, grievance submissions, and any account or participation services made available under the same platform framework.

It is intended to explain the current public privacy position in straightforward language so visitors can understand what kinds of information may be involved before they contact support or use site features.

Information you provide directly

Contact details submitted through forms, email, or support messages
Account details or identifiers used to provide access if account services are enabled
Messages, screenshots, attachments, or supporting documents shared for support or grievance review
Any correction request, complaint detail, or follow-up information you choose to provide

Information generated through site use

Cric BatBall may receive browser, device, session, IP-address, referral, or page-interaction information needed for site delivery, security review, troubleshooting, and general improvement of the user experience.

This kind of data is often created automatically when a website is loaded and can help explain whether a page failed, whether traffic appears suspicious, or which parts of the site need operational improvement.

Support, grievance, and policy records

If you contact Cric BatBall about privacy, accessibility, conduct, support, or a grievance, the platform may retain the communication thread and supporting records so the matter can be reviewed and resolved with context.

That may include timestamps, reply history, attachments, and internal notes that help the platform understand what was reported and how the matter was handled.

Privacy in practice

Most privacy questions come down to purpose, access, and retention

Why information is collected Usually to run the site, respond to support requests, investigate problems, preserve context for policy review, and keep the platform secure and accountable.

Who may access it Access should be limited to people, teams, or service providers who need the information for operational, support, security, or legal reasons.

How long it may remain Different records may be retained for different periods depending on whether they are needed for routine support, technical troubleshooting, security review, or dispute handling.

When the explanation changes If Cric BatBall introduces new account tools, new vendors, or new participation features, the privacy explanation should be updated to reflect that broader data picture.

How to make a privacy request

Clear requests are easier to review and resolve properly

Use the support email and clearly say whether you want access, correction, deletion, clarification, or complaint review
Identify the email address, account, support thread, or page interaction involved so Cric BatBall can locate the right records
Be prepared for reasonable verification if the request affects personal or account-linked information
Response timing may vary depending on the complexity of the issue and whether other legal or security considerations apply

How information may be used

Privacy on Cric BatBall is tied to operations, support, safety, and accountability

Cric BatBall may use information to run the site, respond to visitors, review policy issues, maintain platform integrity, and keep a record of communications where that is reasonably necessary. The goal of this page is to explain those uses in plain language instead of leaving them implied.

Operational use Needed to deliver pages, maintain continuity, support logins or sessions where relevant, and keep basic site functions running properly.

Support use Needed to respond to questions, review screenshots or attachments, and understand what happened in a support or policy-related conversation.

Safety and review Needed to investigate misuse, preserve records where appropriate, and protect the platform, its users, and its support processes.

Communication Needed to send direct replies, confirm receipt of a request, or notify users about material changes where such communication is appropriate.

When information may be shared

Sharing should be limited to legitimate operational, legal, or protective reasons

Information may be processed by service providers that support hosting, email, analytics, or other operational tools used by the platform
Information may be disclosed where required by law, legal process, or a valid government request
Information may be used in connection with investigating fraud, abuse, security concerns, or user-safety issues
If the business structure or service operations materially change, related records may be transferred as part of that change subject to applicable law and updated notice

Retention and user requests

Records may be kept for as long as they are reasonably needed

Cric BatBall may retain information for platform operations, support history, security review, dispute handling, and lawful obligations for as long as that purpose reasonably requires. Retention periods can differ based on the type of record and why it was created.

Use the published support email for questions, correction requests, or deletion-related requests
Include enough detail to identify the account, email thread, page, or communication involved
Cric BatBall may ask for reasonable verification before acting on a request that affects account or personal information
Some records may need to be retained for security, legal, or dispute-resolution reasons even after a broader deletion request

Cookies, age limits, third-party links, and updates

Cric BatBall's Cookies page explains browser storage and similar tracking tools, while the Data Security page explains the platform's broader protection approach. This site is intended for adults aged 18 and above and should not knowingly target children. Third-party links or embedded tools may have their own privacy practices, which visitors should review independently.

The privacy page should be read as part of the full policy set rather than as a stand-alone promise about every technical detail. The broader picture is spread across Privacy, Cookies, Data Security, and the relevant support or grievance routes.

If a serious privacy issue remains unresolved: use the grievance route so the issue can receive a more formal documented review.