Navigation or feature update
A setting name, path, default, availability rule, or interface has materially changed.
Change log · corrections · version notes
Settings change. The update trail should be visible.
This page records substantive changes to public guidance and paid guides. Dates are updated only when the underlying content has been reviewed or corrected.
Recommendation changed
New evidence or repeated parent experience changes what KidPhoneSetup recommends.
A factual error was fixed
The original statement, correction, affected pages, and date should be stated plainly.
Current public record
Recent substantive updates
This log begins with the redesigned website foundation. Individual guide entries will be added after each guide completes its current-version audit.
Site reliability and trust
Clearer product evidence and failure-safe checkout
Published the flagship guide’s existing 16-page scope and September 22 source-review date without claiming a new live-device test. Added real sample pages, named founder and support contact, privacy and contact pages, correct guide-finder routing, resilient Payhip states, accessibility labels, and product-card measurement.
Site foundation
New decision-led website and P0 content
Added Start Here routing, a printable pre-handoff checklist, guide comparison, methodology, about, FAQ, 30-day review, richer purchase paths, and this update record. Replaced generic “five guides” messaging with the actual eleven-guide catalogue.
Scheduled
Product-by-product verification
Each guide will receive its own dated entry after account flows, terminology, version scope, limitations, and screenshots have been checked against current official documentation.
Why the log is short
A long update log would be easy to fabricate. KidPhoneSetup records only real, substantive work. The absence of a guide-specific entry means the current-version audit has not yet been documented here.
Find a problem?
Corrections are part of maintenance—not an embarrassment.
Email Kevin McFaul at kidphonesetup@gmail.com. Include the guide name, page number, device, operating-system version, and what appeared on screen.
Never work around a broken step by guessing.
Pause, verify against current official documentation, and use the correction path so the guide and public content can be checked together.