Is CaptainFact safe?

Clean risk

CaptainFact sends matching YouTube video URLs to graphql.captainfact.io to load fact-checking statements.

CaptainFact runs on YouTube pages and checks whether the current video appears in its cached CaptainFact video list. When there is a match, it sends the YouTube URL to graphql.captainfact.io in a GraphQL request so it can display fact-checking statements in the page overlay.

CaptainFactv2.0.0Chrome Web Store
0Risk
Who publishes it

CaptainFact - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
CaptainFact
Registered address
Les Halles Civiques, 27 Rue Piat, Paris 75020, France
Registered contact
Benjamin Piouffle

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 2.0.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on m.youtube.com

    *://m.youtube.com/*

  • Read and change your data on www.youtube.com

    *://www.youtube.com/*

  • Read and change your data on captainfact.io

    *://*.captainfact.io/*/*

  • Store data in your browser

    storage

Where it sends data

Destinations our analysis observed CaptainFact contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • graphql.captainfact.io

    CaptainFact sends data to graphql.captainfact.io. No other extension we have analysed sends data here.

Updated 30 September 2026fnnhlmbnlbgomamcolcpgncflofhjckm