Corrections

How to report an error on cyberpresso.com, what happens next, and what we have fixed · Last updated November 9, 2026

If something on cyberpresso.com is wrong, a price, a plan name, a claim about a product or a missing source, tell us and we will check it against the primary source and fix the page.

How to report an error

Email louis@dupple.com with:

the URL of the page;
what the page says and what it should say;
where the right figure is published, ideally the vendor's own pricing page, documentation, filing or advisory.

We usually reply within two business days. Vendors are welcome to report errors about their own products; a request without a source, or one that asks us to remove a criticism rather than correct a fact, will not change the page.

What happens next

We re-read the primary source ourselves. A report is a lead, not a source.
If the page is wrong, we fix every place on it that repeats the error (summary, table, cards, FAQ and structured data) and the other pages on the site that make the same claim.
The page's "Updated" date moves to the day of the fix. Its original publication date does not change.
Substantive corrections are listed below, with the date and what changed. Typos and wording changes that do not change a fact are not listed.

Corrections log

Substantive corrections on cyberpresso.com, newest first
Date	Page	Type	What changed
October 14, 2026	/corrections	Correction	This log said that the page header "now names any paid placement" and that a guide's header carries a vendor's paid-placement disclosure. That was true on 25 September and stopped being true on 8 October, when the wording changed (next entry), but the log kept describing the old state. The entries now say what the pages show today: a header line that product links may be affiliate links, linked to how we rate, and one generic closing line. No page names a paying vendor.
October 8, 2026	/how-we-rate	Correction	Disclosure wording changed. Review pages no longer name a paying vendor in the header, and no page says whether it carries a paid placement. The header says that product links may be affiliate links and links to how we rate; every review and blog page ends with one generic line: Some offers on this page may be paid placements or contain affiliate links. A paid placement can set a vendor's position in a guide, and the vendor may write or approve the text of its own entry.
September 25, 2026	/how-we-rate	Correction	Review pages carried an "Editorially reviewed" badge and the line "No pay-for-placement", and the reviews hub said rankings were never influenced by payment. Some guides on our sites include a vendor that paid to be listed, so the badge and line were removed. For the first days the page header named the paying vendor; that was replaced on 8 October 2026 by the generic wording described in the entry of that date.
September 25, 2026	/reviews/best-ai-for-penetration-testing	Correction	Escape paid to be listed in this guide, and the page did not say so. On 25 September the disclosure was added to the page header. Since 8 October 2026 it reads differently: the header says that product links may be affiliate links and links to how we rate, the page ends with the line that offers on it may be paid placements or contain affiliate links, and neither names the vendor.
September 25, 2026	/blog/packagist-ios-spyware-themes	Sources added	Links added to the primary sources the story rests on: Socket Threat Research's August 31 report, Socket's earlier March note, and the US Treasury (OFAC) press release on the FUNNULL sanctions.
September 23, 2026	/reviews/bitwarden-review	Correction	Bitwarden's prices appeared in euros without saying so. Bitwarden publishes no US-dollar list price for these plans, so the review now labels them as the EU list (Premium from €1.23 a month, business plans from €1.79) instead of converting them to dollars.
August 19, 2026	/blog/generative-ai-in-cybersecurity	Correction	The guide opened on an invented analyst scenario and quoted an unsourced "95 percent" accuracy figure. Both were removed, and "hands-on" wording was dropped: we compare vendor documentation, changelogs and public user reports, and we do not run a test lab.

Entries dated before September 25, 2026 were compiled from our publishing history and are not an exhaustive list for that period; from that date every substantive correction is added here. Read the editorial policy for how pages are checked before they are published.