Tell us what needs another look

How to send a correction

Write to [email protected]. Include the address of the page, the exact sentence or element you believe is wrong, and a current primary source when one is available. A direct vendor help page, platform policy, product documentation page, or reproducible navigation problem gives the editorial desk a clear starting point.

You do not need to provide personal information about a child. Please remove account identifiers, screenshots containing private viewing history, payment details, and device credentials. If a screenshot is essential to show a layout or accessibility issue, crop it to the relevant interface and obscure personal data before attaching it.

This site does not use a contact form. Email keeps the contact route explicit and avoids presenting a simulated submission or success message. Sending a report does not create a support contract or guarantee a particular response time, but it does place the issue in the editorial review path.

Issues we can investigate

Factual corrections include a feature statement that no longer matches official documentation, a supported device that changed, a source link that moved, or a description that exceeds what the cited page establishes. Sourcing corrections include a citation that does not support the nearby claim or an access date that needs renewal.

Disclosure concerns include an ownership statement that is unclear, a sponsored product link without the expected relationship markup, or wording that presents this StayBoba-operated publication as independent from WhitelistVideo. We also accept reports about broken navigation, missing alternative text, unreadable mobile layouts, keyboard focus, contrast, and content that is difficult to understand.

Product account help is different from an editorial correction. The same email address can receive the message, but include the product name and platform so it can be routed correctly. Never send a password, one-time code, full payment number, or a child's private activity record.

What happens during editorial review

First, we locate the generated record and the source set behind the page. We compare the disputed statement with the cited primary material and check whether a newer official page changes the conclusion. We also inspect nearby language because a sentence can be technically accurate while its heading or context creates a broader impression.

If a correction is warranted, we update the underlying record or deterministic template rather than patching only the published HTML. The page is regenerated, internal links and metadata are checked, and the content audit receives a new final-content hash. A changed factual claim also requires another fact-check. This process keeps the correction reproducible on later builds.

If the available evidence is inconclusive, we may narrow the statement or label the point as not documented. We do not fill a documentation gap with an assumption. A report may also reveal that a whole comparison needs a scheduled re-review rather than a one-line correction.

Useful details for faster review

A concise report can follow this order: page address, quoted statement, reason for concern, supporting source, and the date you checked it. For a visual or technical issue, add the device type, browser, approximate viewport size, and the steps that expose the problem. These details help us separate a content error from a route-specific rendering problem.

Before writing, you may want to read the editorial methodology and ownership disclosure. They explain why sources, limits, review dates, and relationships appear where they do. For the currently published product decision, return to the approved-channel options evaluation.