Privacy Policy
Last updated: October 14, 2026
Our Core Privacy Commitment
- •No Account Needed: InspectFrame requires no sign-up, login, email address, or profile to verify video claims.
- •Zero Watch History Tracking: We never log, store, or profile your personal YouTube watch history, search queries, or browsing behavior.
- •Minimal Processing: Only public spoken caption transcripts of the video currently playing are analyzed to match factual claims against primary records.
- •No Data Selling: We never sell, rent, monetize, or transmit your data to advertisers or third-party data brokers.
1. Single-Purpose Operation
InspectFrame ("we", "our", or "the extension") is built with a single, clear objective: to provide real-time, second-level factual verification and primary source citations for spoken assertions in public YouTube videos.
The extension activates strictly when you navigate to a YouTube video page (https://www.youtube.com/watch*). Outside of the active YouTube video player interface, InspectFrame is completely inert and does not execute code or monitor any browser activity.
2. Information We Never Collect
We believe privacy is an architectural principle, not an afterthought. InspectFrame is specifically designed not to collect:
- Personal Identity: Your name, email, Google account credentials, or profile information.
- Browsing Activity: The URLs, tabs, or domains you visit outside YouTube.
- Personal Watch History: A record of which videos you watch, how long you watch, or your personal playlists.
- Search & Interaction Data: Search bar queries, comments posted, likes, or user interactions on YouTube.
- Keystrokes & Form Inputs: We never intercept user inputs, keystrokes, passwords, or personal communications.
3. Information We Process & How It Is Handled
To provide verified citations and factual determinations, the extension processes:
- Public Video ID: The YouTube video identifier (e.g.
XHvWDkko23U) is used to check whether certified claim verifications have already been computed for that public clip. - Spoken Caption Transcripts: Audio-derived transcript segments are evaluated through our verification model against public government records, certified election tallies, scientific archives, and authoritative reference sources.
- Feedback Telemetry: If you explicitly click the anonymous "Helpful" or "Dispute" button in the drawer, an anonymous rating is logged against that specific claim ID to trigger secondary review. No user identifier is attached.
4. Browser Permissions Explained
When installing InspectFrame from the Chrome Web Store, the extension requests the minimum permissions required for operation:
Allows the extension to inject the verification button, floating verdict drawer, and timeline scrub bar ticks into the native YouTube video player interface.
Used to inject and manage the fact-checking timeline overlay and verdict drawer when you actively navigate to a YouTube video.
Used to detect URL changes and navigation events within YouTube's single-page app so verification markers update dynamically when switching videos.
Used exclusively to recognize your authentication session from inspectframe.com to synchronize your plan tier and verification quota without requiring a separate in-extension login. We never read cookies from YouTube or any third-party domain.
Used to save your client preferences locally (such as toggle states, audio cues, and cached claim determinations) using chrome.storage.local. This data never leaves your device.
5. External Primary Source Links
Every determination in InspectFrame includes direct citation links to primary sources (e.g. Wikipedia, peer-reviewed journals, certified election archives, and institutional publications).
When you click an external receipt link, you are directed to that third-party publisher’s website, which operates under its own independent privacy policy. InspectFrame does not track your activity on external sites.
6. Data Security & Storage
All communications between the InspectFrame client extension and our verification backend are encrypted using Transport Layer Security (TLS 1.3). Claim verification determinations are cached anonymously against public video hashes on secure infrastructure.
7. Changes to This Policy
We may periodically update this Privacy Policy to reflect technical improvements or regulatory compliance updates. If material changes are made, we will update the "Last updated" timestamp at the top of this document.
8. Contact Us Regarding Privacy
If you have questions, feedback, or concerns regarding our privacy architecture or data practices, please reach out through our Contact Form or email us directly at: