Corrections, logged in public.

1. Why this page exists

The leapbuzz site carries claims, dates, statistics, and platform-feature references that buyers and readers use to make decisions. We take those claims seriously enough to verify them on publish and to log every correction in public when one is needed. A correction policy that lives only in the editor's inbox is not a policy.

2. How to file a correction request

Email [email protected] with three things:

1. The exact page URL where the claim appears.
2. The specific claim, quoted verbatim from the page.
3. The source you believe contradicts it (primary publisher and date if available).

Primary-source flags (regulator publications, platform-vendor official documentation, academic research) get prioritised. Anonymous flags are read but slower to action because we cannot follow up for clarification.

3. What happens next

1. Within two weeks: a senior practitioner reads the flag, verifies the claim against primary sources, and replies. If the claim is verifiably wrong, we update the page, post a dated entry in the public log on this page, and bump dateModified in the JSON-LD on the corrected page.
2. If the claim is correct as published: we reply with the source and reasoning. No public log entry is created in that case.

Note on timing: new-business enquiries through /contact get a reply within one business day. Corrections, privacy requests, and other editorial / legal enquiries are reviewed on a two-week cadence because they need primary-source verification, not a sales response.

4. The verification standard

We act on claims that are demonstrably wrong against a primary source. We do not action subjective disagreements with our stance or interpretation. The bar is factual accuracy, not editorial alignment.

Primary sources we use to verify:

• Regulator publications (.gov,.gov.sg,.gov.au,.gc.ca, EU bodies)
• Platform-vendor official documentation (support.google.com, business.facebook.com, etc.)
• Academic publishers (arXiv, ACM, peer-reviewed journals)
• Named research firms (McKinsey, Forrester, Gartner, IDC, Bain, eMarketer)
• Industry bodies (IMDA, IAB chapters, MRC)

5. Types of correction we make

6. Public correction log

Every applied correction is logged below with date, page URL, original claim, corrected claim, and source. The log is permanent: corrections do not get scrubbed once posted.

7. What we will not correct

Opinion, voice register, and brand positioning are editorial decisions, not factual claims. We do not action requests to:

• Soften tone or remove italic accents
• Drop named-competitor references or pivot positioning
• Remove a stance because it conflicts with a reader's view
• Add hedges to a position the reader disagrees with

If the request is about editorial direction rather than factual accuracy, the right page is the editorial policy.

8. Anonymous requests

We read anonymous flags, but they take longer to action because we cannot follow up for clarification. If you would prefer not to share your identity in the public log, say so in the email and we will action the correction without naming the source.