Grievance process

Grievance Process

If a user believes an issue was not handled adequately through normal support channels, this page explains when the grievance route should be used, what information to include, how Cric BatBall may review the issue, and what a formal response process may look like.

Last updated: March 12, 2026 Primary email: knowmore@cricbatball.com Use after normal support where possible

What this page covers

This page covers formal grievances relating to Cric BatBall's platform, support, policies, conduct, security, accessibility, or unresolved operational issues. It is designed for matters that need documented review rather than routine clarification.

When to use a grievance

Use this route when a matter remains unresolved after normal support, when the issue is serious enough to require formal handling, or when you need Cric BatBall to review a complaint with supporting records and a clear written response.

What to include

  • Your full name and contact information
  • The page, feature, or match context involved
  • A clear description of the concern and relevant dates
  • Any screenshot, reference number, or prior support thread

Target response timing

Cric BatBall aims to acknowledge grievance submissions within about 3 business days where practical and to provide an investigation response within about 15 business days where possible. Complex matters may require more time depending on the records or technical review involved.

Common grievance categories

Formal review can apply to more than one type of issue

  • Account-access or identity-related concerns
  • Privacy, security, or information-handling concerns
  • Accessibility barriers that remain unresolved after initial support
  • Community conduct, harassment, or moderation concerns
  • Disputes about published rules, support handling, or platform communication
How review may work

A formal grievance should move through clear review stages

Acknowledgement Cric BatBall confirms receipt and checks whether the complaint is clear enough to review.
Information check The platform may ask for screenshots, dates, prior support threads, or other documents that help establish the facts.
Investigation Relevant records, policies, communications, or technical details may be reviewed so the issue can be assessed with context.
Response A written outcome may include clarification, corrective action, further questions, or notice that additional time is required.
Possible outcomes

A grievance response may clarify, correct, restrict, or escalate

  • A policy explanation or clarification where the issue comes from misunderstanding rather than platform error
  • A correction to content, communication, or account handling where the issue is validated
  • A moderation or access decision where misuse, risk, or conduct concerns are confirmed
  • A request for more time if the matter depends on deeper technical or historical review
Submission advice

The strongest grievance submissions are factual, specific, and documented

Explain what happened, when it happened, what earlier response was received if any, and what outcome you are seeking. Send grievance-related communication to knowmore@cricbatball.com with a clear subject line such as "Grievance - privacy concern" or "Grievance - support handling."

Practical point: routine questions should go through normal support first, but urgent security or serious user-safety concerns should be raised immediately with as much detail as possible.