Is Findy: Email Search and Outreach by Reply safe?
Findy reads your LinkedIn session cookies and auth headers and sends them to Reply.io to operate LinkedIn on your behalf.
The background worker captures your LinkedIn cookies (li_at, li_a, JSESSIONID, csrf-token, bcookie, liap) and Voyager API request headers, bundles them as linkedInAccountV2Credentials, and forwards them to the Reply.io web app so its servers can drive LinkedIn for outreach. It also intercepts your authenticated Google Contacts hovercard request on contacts.google.com (the 'at' token and f.req payload) and stores it to replay the Contacts API server-side for contact enrichment. These data flows are part of the product's sales-outreach function; a Reply.CE OAuth client_secret is also hardcoded in the shipped bundle.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itreply.io - 1 other listing from the same operator, none carrying a finding
reply.io - 1 other listing from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
1 other listing published from this account, 80k+ users between them, none of them carrying a finding.
Shared hosts - 7 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed Findy: Email Search and Outreach by Reply 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.
- api.reply.io
Findy: Email Search and Outreach by Reply sends data to api.reply.io. One other extension we have analyzed sends data here.
- oauth.reply.io
Findy: Email Search and Outreach by Reply sends data to oauth.reply.io. No other extension we have analyzed sends data here.
- run.reply.io
Findy: Email Search and Outreach by Reply sends data to run.reply.io. No other extension we have analyzed sends data here.