Public Record

Corrections

When we publish a factual error and fix it, we record what was wrong, what’s right now, and why, in plain language. The list is reverse-chronological so the most recent change is at the top.

Log

Public corrections log for Silent Security.net
Date Page What changed Why
2026-09-27 Best two-way radios guide The Motorola T800 was described as “The most feature-rich consumer GMRS radio available, with Bluetooth connectivity, GPS location sharing” and labeled “Bluetooth GPS 35-mile GMRS.” The T800 is now correctly described as a license-free FRS radio that shares location and sends texts off-grid through the Motorola Talkabout app, labeled “Bluetooth texting 35-mile FRS.” The T800 uses FRS, which needs no license. GMRS requires an FCC license, so the old label could mislead readers about licensing. Location comes from the paired phone through the app, not a GPS in the radio.
2026-09-24 1Password review The review used stale exact prices and broad superiority claims without claim-linked current sources. Exact prices were removed, claims were bounded, current first-party sources were linked, and the unpublished hands-on status was disclosed. Changing prices and comparative claims require current evidence and precise disclosure.
2026-09-24 Bitdefender review The review included stale exact prices and unsupported system-impact and competitor comparisons. Exact prices and unsupported comparisons were removed. Current lab-result context is now linked directly to AV-TEST. Performance comparisons need current independent evidence and clear limits.
2026-09-24 SimpliSafe review The review listed stale equipment and monitoring prices and described outage, network-backup, integration, and moving behavior too broadly. Prices were removed and the affected statements now identify plan, hardware, location, and current-instruction dependencies. Plan-dependent features should not be presented as universal product behavior.
2026-09-24 Ring Alarm review The review used stale prices, unsupported installation and competitor claims, and privacy wording without a visible claim-linked source. The review now uses current-plan checks, bounded comparisons, an unpublished hands-on disclosure, and first-party plus FTC source links. Price, performance, comparison, and privacy claims require traceable evidence.
2026-09-24 Aura review The review used stale plan prices and unsupported alert-speed, category-leadership, competitor, and insurance-coverage statements. Prices and unsupported comparisons were removed. Insurance language now defers to policy terms, and current Aura plan, family, and insurance sources are linked. Monitoring and insurance benefits must be bounded by current plan and policy documents.

How Corrections Work

Our publishing process when we get something wrong

  1. You report it. Use the contact form, the “Spotted an error?” link on any review, or email us. The most useful reports include the page URL and the specific wording that’s off.
  2. We verify. The editorial team checks the claim against primary sources. If the fact is wrong, we move to step 3. If it’s our wording that’s ambiguous, we move to step 3 anyway because clarity is part of accuracy.
  3. We update the page. The corrected wording goes live, with the page’s dateModified bumped.
  4. We log it here. Original wording, corrected wording, and the reason in plain language. The log entry is permanent.
  5. We notify the reporter when we have an email address to reach.

We do not silently rewrite history. If a published claim was wrong, the wrongness is part of the record. That is the point of a public log. The only edits we make without a log entry are formatting, typos that don’t change meaning, and updates to live data (pricing, availability) that the page already presents as time-sensitive.

Related