Corrections Policy

Send the page URL, the incorrect statement, and a better primary source if you have one via /contact/. Material errors that affect scores, prices, availability, testing status, fabricated hours-tested implications, or who-should-not-buy guidance are prioritized over cosmetic typos.

Prefer primary sources. Confirmed errors update the page and the source register. When a change would reasonably affect a purchase decision, we note it on the page update label or a short corrections note rather than silent rewrite theater.

A dated public corrections archive is not live yet. Response times are not guaranteed. Affiliate payout disputes are not editorial score corrections. Security vulnerabilities use /security/, not this channel.

Corrections protect readers from stale prices, misstated features, or unsupported tested claims. They also keep source registers honest across data-privacy, password-manager, and antivirus coverage.

Launch products such as Aura, NordPass, and Bitdefender stay subject to the same pricing-evidence rules. Corrections do not invent scores, testing hours, or coupons to fill gaps.

Material errors affecting scores, prices, availability, or testing status should be corrected promptly once verified. Cosmetic typos may be fixed without a public note.

We do not invent updated-daily badges. Update labels should reflect real verification work. Overall scores are not assigned until verification is complete, even when starting prices are Verified. Missing commercial terms stay verified rather than invented.

1) Intake via /contact/ with URL, quote, and source.

2) Triage for materiality and safety (security issues escalate to /security/).

3) Verify against primary sources and existing source registers.

4) Update page copy, examples, and price records as needed.

5) Adjust update labels; add a public log entry when that archive exists.

Material corrections include wrong starting prices, stale plan names, availability errors, unsupported we-tested wording, missing who-should-not-buy guidance on a commercial page, and affiliate disclosure gaps near a tracked CTA.

Non-material fixes include typos, broken internal links, formatting regressions, and clarifications that do not change a purchase decision. We still fix those promptly but may not publish a dated note.

Challenges to tool routing, free-action order, privacy statements, or results explanations are in scope when they could mislead a purchase or overstate what the tool measures.

We will not correct a tool into claiming a live scan, inventing dollar savings, or publishing a product editorial score without a signed test record.

Do not treat this process page as a live corrections archive, product ranking, or guarantee that Aura, NordPass, Bitdefender, or any other product will be rescored on demand.

Anyone mid-compromise needs vendor or institutional help. Free hygiene and /security-checkup/ remain practical next steps while the public log is not yet live.

A public corrections log may be added later under this URL or a dated archive page. It is not claimed as live today.

Editorial policy, methodology, and affiliate disclosure define what we will and will not claim while research continues.

Correction requests: /contact/ or intel@securitycheckli.st. Do not send passwords, MFA codes, or payment credentials. Security researchers: security@securitycheckli.st and /security/.

Public operator identity: SecurityChecklist; +1 888 437 8441; One World Trade Center, 285 Fulton Street, 85th Floor, Suite 8500, New York, NY 10007, United States.