Is Engage AI safe?
Engage AI exposes a Facebook-session bridge to any page loaded from http://localhost:9000 with no additional token check.
Engage AI's background service worker listens for messages from external pages via chrome.runtime.onMessageExternal, restricted only to the plaintext origin http://localhost:9000. A page served from that origin can request the user's Facebook access token, friend list, incoming/outgoing friend requests, and activity/message metadata, or issue an arbitrary-URL GET request that runs with the extension's own cookie-backed session and returns the raw response. Commented-out alternate URLs in the extension's config suggest this was left over from local development rather than pointed at the production web app.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itQwertyFace Media, LLC - 3 other listings from the same operator, 2 of them carrying a finding
QwertyFace Media, LLC - 3 other listings from the same operator, 2 of them carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
3 other listings published from this account, 5k+ users between them. 2 of them carry a finding.
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.2. 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 googleapis.com
https://*.googleapis.com/*
Read and change your data on cloudki.io
https://cloudki.io/*
Read and change your data on app.cloudki.io
https://app.cloudki.io/*
Read and change your data on facebook.com
https://*.facebook.com/*
Read and change your data on www.facebook.com
https://www.facebook.com/messages/t/*
Read and change your data on www.messenger.com
https://www.messenger.com/*
Read and change your data on m.facebook.com
https://m.facebook.com/*
Read and change your data on res.cloudinary.com
https://res.cloudinary.com/* and 1 more
Read and change your data on elmessenger.cloudki.io
https://elmessenger.cloudki.io/*
Read and change your data on mbasic.facebook.com
https://mbasic.facebook.com/*
Read and change your data on localhost:5000
http://localhost:5000/*
Read and change your data on next2.cloudki.io
https://next2.cloudki.io/*
Read and change your data on elm-glitch.glitch.me
https://elm-glitch.glitch.me/*
Read and change your data on elm-prod.herokuapp.com
https://elm-prod.herokuapp.com/*
Read and change your data on elmessengertest.herokuapp.com
https://elmessengertest.herokuapp.com/*
Store data in your browser
storage
Read whatever you have copied to your clipboard
clipboardRead
Store an unlimited amount of data in your browser
unlimitedStorage
Block and redirect the requests your browser makes
declarativeNetRequest
Read and change cookies, including the ones that keep you signed in
cookies
See the address and title of every tab you have open
tabs
Where it sends data
Destinations our analysis observed Engage AI 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.
- www.facebook.comwidely used
Engage AI sends data to www.facebook.com. A widely used service: 30 other extensions we have analyzed send data here.
- localhost:9000 (local page, if reachable)
Engage AI sends data to localhost:9000 (local page, if reachable). Named as a recipient in this extension's own analysis.