Is Facebook Comments Exporter safe?
Facebook Comments Exporter removes Content-Security-Policy headers on Facebook pages before injecting its scripts.
On Facebook and web.facebook.com pages, the extension uses declarativeNetRequest to remove Content-Security-Policy and Content-Security-Policy-Report-Only headers for page and XHR responses, then registers scripts in the page context. If GraphQL loading errors occur, its injected script sends an error report that includes the current Facebook page URL to esuit-dev-sentry.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
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 1.0.1. 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 www.facebook.com
https://www.facebook.com/*
Read and change your data on web.facebook.com
https://web.facebook.com/*
Run its own code inside the pages you visit
scripting
Store data in your browser
storage
Block and redirect the requests your browser makes
declarativeNetRequest
Where it sends data
Destinations our analysis observed Facebook Comments Exporter 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.
- esuit-dev-sentry-6b0d6.web.app
Facebook Comments Exporter sends data to esuit-dev-sentry-6b0d6.web.app. No other extension we have analysed sends data here.