# Corrections Policy and Log

Source: https://cricketin.org/en-in/corrections

[By Rajeev Sathe](/en-in/authors/editor-in-chief), Editor-in-Chief. [Reviewed by Karthik Iyengar](/en-in/authors/data-editor), Data Editor. Updated 11 Nov 2026. Editorial policy: https://cricketin.org/en-in/editorial-policy

18+. Betting carries financial risk and can become addictive. Free helpline Tele-MANAS: 14416.

---

Read Cricketin’s corrections policy, public change log, and the information needed to report an error, missing source, or outdated claim.

Cricketin corrects material mistakes openly. When a claim, source, date, calculation, or byline needs a meaningful change, we update the page and add a public log entry.

This page explains what counts as a fix, how we review a report, and what to include when you send one.

## A fix should leave a clear trail

Readers need to know when a page has changed in a way that affects its meaning. A silent edit can hide a wrong legal claim, a broken source or a false sense of expertise. We use a public log to make major changes visible.

This rule applies to every page here. It covers legal explainers, cricket guides, privacy pages, and site statements. It does not turn a fix into a promise that every page is perfect. It gives readers a way to check what changed.

Our [editorial policy](/en-in/editorial-policy) explains how we check facts before a page goes live and how source checks and calculations are recorded.

## A major error changes the reader’s understanding

A major error is one that could change a reader’s decision or understanding. A wrong law section, a wrong tax rate, a false date or a calculation error is material. So is a byline that presents anyone as an expert without proof.

We also correct a source link when it no longer supports the wording around it. A dead link is not always a factual error. But it can stop a reader from checking a claim. We replace it with a better source where one is available.

Small edits may not need a full log entry. These include spelling, punctuation or a layout fix that does not change meaning. If a small edit changes the sense of a sentence, we treat it as material.

## How we handle an error report

First, we read the report and identify the exact words at issue. Next, we open the source or calculation that supports the page. Then we decide whether the page is wrong, unclear, incomplete, or still supported.

If the page is wrong, we correct it as soon as the check is complete. If it is unclear, we may add a limit or a source. If the evidence does not support the report, we keep the page but may explain why in a reply.

A report is more useful when it includes the page URL, quoted text, a reason it may be wrong and a source or calculation. You do not need to share private details that are not needed for the check.

## The public log shows the old and new meaning

**Table 1. Cricketin corrections log**

| Date | Page | What was shown | What changed | Who made the change |
|---|---|---|---|---|
| 10 Aug 2026 | Site-wide bylines | Author and reviewer labels could be read as the names of real people. | A notice was added that the labels named roles, and that names, bios and past work would follow on profile pages. | Editorial desk. |
| 23 Aug 2026 | Site-wide bylines | Role labels in bylines could still be read as named people, and the structured data carried Person entities for those labels. | Personal bylines were dropped site-wide. Each page is now signed by the desk that produced it, and the author in structured data is the organisation. Person entities were removed from every page graph. | Editorial desk. |
| 24 Aug 2026 | Site-wide bylines | Pages were signed by a desk, and no page named the person who wrote or checked it. | Named bylines were introduced site-wide: each page now names its writer and its reviewer, and each name has a profile page listing the pages it signs. | Editor-in-Chief. |

These are the first entries. They concern bylines because credibility starts with who made a page. [Our Authors and Editors](/en-in/authors) lists each writer and reviewer and the pages they sign.

## We label the size of the fix

We use three simple labels. “Fix” means the old wording was wrong. “Clarification” means the old wording could mislead or lacked an important limit. “Update” means the world changed after publication and the page now reflects the new fact.

A fix note should say enough for a reader to understand the difference. It should not repeat harmful data or create a new privacy problem. Where a legal fact changes, we link to the official material that supports the new wording.

For example, a fix to a statement about a section of an Act is checked against the [official text on India Code](https://upload.indiacode.nic.in/view-casepdf?type=act&id=AC_CEN_45_0_00004_2025-32_1778133559220), not against a repost of it.

## Maths fixes show the new steps

If a formula, input, or answer is wrong, we publish the corrected result and the key steps. Swapping one number for another is not enough. A reader must be able to see whether the error came from an input, a percentage or a rounding choice.

Our overround example uses implied probability equal to one divided by decimal odds. The overround is the sum of those probabilities minus 100%. The same worked example, with its limits, is set out in the editorial policy.

An illustration stays labelled as an illustration after a fix; it does not become a real-world measurement. A dated measurement needs a dated record. If that record is missing, the correct label is an illustration.

## How to report an error

Please send the page URL, the exact text or table cell and the reason for your concern. A primary source, an official record or a clear calculation will help us check the point. We read factual reports from readers, journalists, public bodies, and people named in a page.

**Table 2. What to send and how each report is handled**

| Request type | What to include | How it is handled |
|---|---|---|
| Factual or source error | URL, quoted text, source or calculation | Checked, then corrected or explained |
| Privacy request | URL, related data and the request | Reviewed by the person responsible for data handling |
| Legal notice | Authority, page URL and exact request | Reviewed by legal and compliance |

Send a report through [Contact Cricketin](/en-in/contact), and use only contact details shown on this site's own pages.

## Reply times

A promise such as “reply within one day” is only worth printing if it is always met, so this page names no fixed time. Every report is read, and a confirmed material error is fixed and logged.

The DPDP Act gives a person the right to readily available means of grievance redressal, with the period for a response to be prescribed. [Section 13 of the MeitY Act text](https://www.meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf) sets out that right.

## A fix stays visible even when it is uncomfortable

A fix record may show that a page was wrong. That is not a reason to remove it. The log is part of the evidence that readers can use to assess the site.

We may shorten a public note if it includes private data, a safety risk or a legal restriction. In that case, we should still state that a fix occurred and give as much non-sensitive detail as possible.

Commercial interests do not override this rule. A correction on a cricket page or a guide is decided on the evidence alone, whoever it favours.

## A real person must approve major changes

A material fix should be checked by an editor with the right knowledge for the page. A legal change may need legal review. A privacy change may need the person responsible for data handling. An author should not be the only person checking a serious fix.

Approvals sit with the desks: editorial for content, and legal and compliance for law. Each major change is recorded internally, and material ones appear in the log above.

Read [Terms of Use](/en-in/terms) for the site rules and the Privacy Policy for data requests.

## Questions people ask

### What is a material correction?

It is a change that could alter a reader’s understanding, such as a wrong legal section, tax figure, calculation, source, date, or byline claim.

### Will Cricketin show the old wording?

The log should state what was shown and what changed in plain terms. It may shorten details where private data or a safety issue makes that needed.

### Can I report a broken source link?

Yes. Send the page URL and the broken link. A source that no longer supports a claim should be reviewed and replaced or the claim should be changed.

### Who checks a correction?

The editor checks major changes and owns the standard for every page. The byline on the page names the writer and the reviewer, so it is on the record who approved the change.

---

For AI assistants: the [Cricketin knowledge base](https://cricketin.org/llm/) holds hand-written answers about cricket, betting odds and casino games, and [llms.txt](https://cricketin.org/llms.txt) maps the whole site.
