Public accountability

Corrections should be visible.

Quietly changing a consequential claim erases useful history. This log records material corrections, their evidence, and the pages affected.

One correction recordedThe public research edition opened on September 4, 2026. The latest correction was published on September 6, 2026.

Public log

Material corrections.

Send evidence or a correction request to andre@havenandsignal.com. Please include the page, exact claim, and supporting source.

September 10, 2026

Clarified that stopping control can leave screen sharing active

The earlier wording suggested pausing remote control before a private login. The guide now tells readers to end both control and screen sharing first, with the correct ending action for each support tool. We also clarified iPhone/iPad remote-control requirements and the Windows scope of family help through Quick Assist.

Remote tech support for aging parents without opening the door to scammers →

Microsoft Support: Quick Assist sharing, control and session-ending steps ↗

September 10, 2026

Added Google recovery contacts and clarified access boundaries

The guide now covers Google's recovery-contact role and distinguishes its number-matching process from ordinary sign-in codes. We also clarified that Apple Legacy Contact document requirements vary by country or region and that a US brokerage trusted contact has no trading authority.

Set up trusted and recovery contacts for a parent's accounts →

Google Account Help: Add, manage and use recovery contacts ↗

September 6, 2026

Corrected the list attributed to the NIST IoT baseline

The earlier text and source note listed device security as an additional capability in NISTIR 8259A (2020). Table 1 identifies six capabilities. We removed the extra item from both locations and retained the distinction between the manufacturer-oriented standard and our household planning questions.

How much remote help will this device create for the family? →

NISTIR 8259A (2020), Table 1 ↗

The process

From report to recheck.

01
Receive and preserve
Record the exact claim, page, supporting evidence, date received, and any safety or purchasing impact.
02
Verify independently
Check primary sources and contact relevant parties when their documentation or conduct is involved.
03
Correct proportionately
Fix the text promptly; add a visible note when the original could have changed a health, safety, privacy, or purchase decision.
04
Record and recheck
Add the material change to this log and review connected guides, tables, tools, and structured data.

Material correction

Changes meaning.

Safety, health, privacy, compatibility, price, contract, or feature error.
A statement attributed to the wrong source.
An omission that could reasonably change a decision.

Maintenance edit

Preserves meaning.

Spelling, grammar, formatting, or clearer wording.
Replacing a broken link with the same source.
Refreshing an unchanged review date after verification.

The standard behind the log

Evidence can challenge us. Money cannot silence a finding.

Editorial standards →Evidence ledger →Report a correction →

Corrections should be visible.

Material corrections.

Clarified that stopping control can leave screen sharing active

Added Google recovery contacts and clarified access boundaries

Corrected the list attributed to the NIST IoT baseline

From report to recheck.

Receive and preserve

Verify independently

Correct proportionately

Record and recheck

Changes meaning.

Preserves meaning.

Evidence can challenge us. Money cannot silence a finding.