Is TextRecruit Extension safe on LinkedIn?
TextRecruit Extension is on LinkedIn's active extension-detection (AED) list. Risk rating: MEDIUM.
Runs locally — session stays in your browser · on LinkedIn's detection list.
Does LinkedIn detect TextRecruit Extension? What we found in its code
Session handling: NO SESSION ACCESS → app.textrecruit.com (candidate phone/name/URL only; not LinkedIn session).
Medium
TextRecruit Extension — FAQ
Is TextRecruit Extension safe to use on LinkedIn?
Our static code audit rates TextRecruit Extension MEDIUM risk. It works through your own logged-in browser session — your cookie stays on your machine and only scraped results are uploaded — which is safer than cloud tools that take your session. It is still a Chrome extension LinkedIn can detect, and its ID is on LinkedIn's detection list.
Does LinkedIn detect TextRecruit Extension?
Yes. TextRecruit Extension's extension ID is on LinkedIn's active extension-detection (AED) list, so LinkedIn's page code probes for it on every visit (it requests the file disabled.html) — LinkedIn knows the extension is installed before you do anything.
Can TextRecruit Extension get my LinkedIn account banned or restricted?
Detection isn't an instant ban — LinkedIn scores accounts on many cumulative signals. But TextRecruit Extension stacks a known extension ID on LinkedIn's list, and independent reviews report restrictions and permanent bans for Chrome-extension automators. Safe daily limits reduce the behavioral risk but can't offset a detectable architecture.
Does TextRecruit Extension have access to my LinkedIn account?
It reads LinkedIn data through your own browser session (the Voyager API) and uploads only the results — your session token itself stays on your machine.
How does TextRecruit Extension work — is it a Chrome extension or a cloud tool?
TextRecruit Extension is a extension (DOM-scrape, no session access) that runs inside your own Chrome browser.
What is a safer alternative to TextRecruit Extension?
A standalone desktop app such as Linked Helper removes the two extension-specific detection surfaces: there is no Chrome-Store ID for LinkedIn's AED scanner to probe and nothing injected into the page for its DOM scan, and your session never leaves your machine. No tool is unbannable, but the surface it exposes is far smaller.