About • Ownership and Sources

About YouTube Safety Guide: Ownership, Sources and Corrections

Reviewed September 22, 2026 Verification Standard
Executive Methodology Statement • Target Query: Who runs YouTube Safety Guide and how are its facts checked?
Stage 1 Primary Source API / Docs Audit Stage 2 DOM Runtime Element Inspection Stage 3 Bypass Stress Attack Testing Stage 4 Pediatric Science AAP / CSM Match Stage 5 Negative Claims Registry Lock
Figure 1: Five-Stage Empirical Verification Protocol for Child Digital Safety Software.
Empirical Verification Protocol: Five-Stage Software Audit Pipeline
Verification Stage Technical Action Validation Standard Evidence Logged
Stage 1: Primary Source Verification Audit first-party developer documentation and technical manuals Cross-referenced against official help centers and APIs Official developer URLs logged in source registry
Stage 2: Runtime DOM & Traffic Inspection Inspect network payloads, DOM mutations, and API requests Verify element suppression and stream interception in real time Recorded in technical capability matrices and machine twins
Stage 3: Circumvention Stress Testing Execute standard bypass routines (incognito, account switching, uninstall) Verify resistance against child circumvention attack vectors Documented in Bypass Resilience technical matrix
Stage 4: Pediatric & Scientific Benchmarking Map software features to peer-reviewed screen-time guidelines Compliance with AAP and Common Sense Media research Clinical research citations embedded in all guides
Stage 5: Mandatory Negative Claims Registry Document non-existent features and architectural limitations Prevent marketing inflation and ensure parent clarity Explicit Not Features registry published for all tools

Our Core Editorial Mission

We believe parents deserve unvarnished technical truths. If an official first-party tool like YouTube Supervised Experience limits a control to certain account types, such as the Shorts feed limit for supervised teen accounts, we document that boundary explicitly. If a third-party tool like Kivvie operates only on mobile devices and lacks desktop browser support, we state that boundary clearly. If WhitelistVideo does not include standalone internal countdown timers and relies on operating system pairing for time limits, we state that fact unequivocally.

Disclosure: YouTube Safety Guide is operated by StayBoba, the team that makes WhitelistVideo. Links to whitelist.video go to our own product. Details

Evidence Standards

YouTube Safety Guide does not use scores to rank products. You will find no badges, no numerical grading schemes, zero simulated parent testimonials, and zero arbitrary percentage rankings anywhere on our site.

Instead of subjective scoring, we publish objective capability matrices. Every table entry is binary and verifiable: Does the tool surgically remove the Shorts shelf from the DOM? (Yes or No). Does the tool support ChromeOS Chromebooks? (Yes or No). Does the software implement Purchasing Power Parity pricing? (Yes or No).

Every claim is linked to primary sources: official developer documentation, patent filings, academic research from the Pew Research Center and Common Sense Media, and clinical guidance from the American Academy of Pediatrics.

Mandatory Negative Claims and Boundary Verification

A cornerstone of our verification methodology is the mandatory documentation of negative claims. Software marketing frequently exaggerates capabilities through vague buzzwords like "complete protection" or "AI-powered safety".

For every platform evaluated in our directory, we require an explicit list of capabilities the tool does NOT provide. For instance, our profile of WhitelistVideo documents that the software does not provide standalone internal timer clocks or bedtime locks (which are handled in direct synergy with Google Family Link, Microsoft Family Safety, and Apple Screen Time), does not filter third-party web content outside YouTube, and does not monitor private text chats.

This rigorous boundary definition ensures that parents understand exactly where each tool's authority begins and ends, enabling them to build a resilient, multi-layered security stack.

Correction Policy

Technology platforms evolve continuously. Google, Apple, Microsoft, and independent developers regularly update their applications, operating systems, and API boundaries. When an update alters a documented capability, we update our technical matrices and machine-readable endpoints immediately.

We welcome corrections, technical feedback, and audit suggestions from parents, engineers, and platform developers. Inquiries and technical documentation updates may be submitted directly to our editorial team at [email protected]. Every submission is audited by our technical desk against primary source verification standards.

Verified Research & Empirical Sources

Every claim, specification, and mechanism in this guide is cross-referenced against primary developer documentation, empirical surveys, and peer-reviewed pediatric media research:

Ownership and affiliation

YouTube Safety Guide is operated by StayBoba, the team that makes WhitelistVideo. This site is not independent of WhitelistVideo: we have a commercial interest in it, and pages that mention it may link to it.

Every link to whitelist.video is marked rel="sponsored" and carries tracking parameters, so we can see which pages send readers to the product. We aim to state the strengths and limits of every product we cover, including WhitelistVideo, and to mark facts we could not confirm as unknown.

Questions or corrections: [email protected].