We publish a correction whenever we identify a factual error in an Omellody page. That includes pricing that became inaccurate after a product changed plans, a feature list that drifted from reality, an outdated security claim, a misattributed quote, or a broken structured-data element that affected how a page was presented. We do not silently rewrite reviews.
Our corrections standard
Confirm the fact
We corroborate the claim against a primary source โ vendor documentation, an audit, a regulator filing, or a test we can reproduce.
Fix the page
We update the affected copy, the relevant structured data, and any related comparison or hub pages that echoed the error.
Log it here
We add an entry to this public log with the date, the page, the change, and the type (major correction, clarification, or routine update).
Credit the reporter
Where a reader or researcher reported the issue and agrees, we credit them in the entry.
Correction types
- Major correction โ a factual error that could have changed a reader's decision. Flagged with a visible "Correction" note on the affected page.
- Clarification โ a statement that was technically accurate but could be misread. Rewritten for clarity, logged here.
- Routine update โ price changes, feature additions, or deprecations in the normal quarterly cycle. Logged without a correction note when the original was accurate at the time of publication.
Report an error
Seen something that looks wrong? Email our editorial team through the contact page. We read every message and respond to anything that looks like a factual issue within two business days. Include a link to the page, the specific claim, and, if possible, the primary source we should consider.
Recent corrections
May 10, 2026
Update
LifeLock by Norton โ underwriter disclosure added
Added the underwriter name to the identity theft insurance terms section. The coverage amount and per-incident limits were unchanged; the clarification only made the underwriting carrier visible on the product page.
- Page
- LifeLock by Norton review
- Reason
- New disclosure requirement added to the identity theft protection research rubric.
April 22, 2026
Clarification
NordVPN Dark Web Monitor coverage
Clarified the scope of Dark Web Monitor Pro. The earlier wording could be read to imply unlimited monitored identifiers; we updated the page to specify the current per-plan caps disclosed by NordVPN, matching the help-center documentation.
- Page
- NordVPN review
- Reason
- Reader reported ambiguity; verified against vendor help article.
April 8, 2026
Major Correction
TurboTax โ state filing price at checkout
An earlier version of the review listed the state filing price at its pre-season promotional level after the promotion had ended. We re-ran a full checkout trace from a single W-2 scenario, updated the price table, and added a note to the pricing section explaining that state filing prices change during tax season.
- Page
- TurboTax review
- Reason
- Post-promotion price drift; confirmed by fresh checkout walkthrough.
March 29, 2026
Update
Bitwarden โ added latest audit reference
Added a reference to the most recent publicly disclosed Bitwarden security audit and updated the "Audit & Transparency" evidence in the review. Scores were unchanged.
- Page
- Bitwarden review
- Reason
- New audit publication in category research cycle.
March 14, 2026
Update
YNAB โ annual plan price refresh
Updated the annual plan price in the pricing section and the comparison table after YNAB refreshed its pricing page. Free-trial terms were unchanged.
- Page
- YNAB review
- Reason
- Routine quarterly re-evaluation.
February 19, 2026
Clarification
Aura โ family plan child coverage
Clarified which child-monitoring features are included on the standard family plan versus the top tier. The original wording could be read to imply both tiers included advanced child SSN monitoring; only the top tier does.
- Page
- Aura review
- Reason
- Cross-check against vendor plan comparison page.
Historical corrections
Corrections older than six months are retained in our internal editorial archive. Readers who need to reference an older correction can request the entry through the contact page; we will send the archived version along with the page it applied to.
Related