5 client-side LinkedIn tools — all opt-in, all local to your browser.
These tools are off by default. Enable the ones you want in the extension's Options page under LinkedIn Features. Everything runs in your browser — Video Controls Plus never automates LinkedIn actions or sends your data anywhere.
The Profile Visitor Anonymizer is a client-side privacy tool that removes known tracking scripts and 1x1 tracking pixels from LinkedIn pages as they load, intercepts in-page requests whose URL matches activity/profile-view tracking patterns, and hides online-presence indicators with CSS. It works entirely from heuristic domain and pattern lists baked into the extension, runs only on the LinkedIn tab you have open, and stores its counters locally in your browser. It does not block traffic at the network level, does not make you invisible to LinkedIn's servers, and does not change any of your LinkedIn privacy account settings.
Example: Before quietly checking a recruiter's profile, you enable the anonymizer so LinkedIn's in-page activity and presence beacons matching its tracking patterns are stripped from that tab while you read.
Does this make me completely invisible on LinkedIn? No. It only removes scripts and pixels that match its built-in tracking lists on the page you have open and hides presence indicators with CSS. It cannot stop LinkedIn's servers from logging requests you make, and it is not a guaranteed anonymous-browsing mode.
Is any of my browsing sent anywhere? No. All blocking happens in your browser and the counters (trackers blocked, sessions protected) are stored only in your local extension storage. Nothing is uploaded to a server or to us.
Will it change my LinkedIn privacy settings? No. It never touches your account settings. To truly hide profile views you still set 'Private mode' in LinkedIn's own settings; this tool only strips matching in-page trackers.
Why does it sometimes block nothing? It only removes elements whose URLs match its known tracking domains and patterns. If LinkedIn changes its markup or loads trackers a different way, the heuristics may not match and the count stays at zero.
This is a heuristic, in-page tool: it only removes scripts/pixels matching its built-in domain and pattern lists on the page you are viewing, runs only after the page loads in your browser, and does not guarantee LinkedIn's own 'who viewed your profile' feature won't still register a view. Counters stay in your browser and LinkedIn may change its markup at any time.
The Feed Noise Reducer is a client-side feed filter that scans the LinkedIn posts visible on your current page and hides, blurs, or collapses ones that match your rules. It uses simple keyword and pattern checks (sponsored flags, promotional phrases, job/event language, hashtag counts, engagement thresholds, reposts) plus your own keyword, author, and company blocklists. All rules and the filter log are stored locally in your browser; it only reads posts already rendered on the page you are scrolling and never automates likes, comments, or any LinkedIn action.
Example: Tired of webinar invites and 'limited time offer' posts, you enable hashtag-spam and event-promo filtering in collapse mode, so those posts shrink to a thin labeled strip you can expand only if you want to.
Does it use AI to decide what's noise? No. It matches posts against fixed keyword lists, hashtag counts, sponsored flags, and your own blocklists. It is rule-based, so it is predictable but can miss cleverly worded promos.
Do my blocklists and keyword filters leave my browser? No. Your blocked authors, blocked companies, keyword filters, and the filter statistics are saved only in your local browser storage. Nothing is sent to a server.
Does blocking an author affect them on LinkedIn? No. Blocking is purely local visual filtering in your feed. The author is never notified, unfollowed, or affected on LinkedIn; only your view changes.
What if it hides a post I wanted to see? Use blur or collapse mode instead of hide, and click the 'Show' button on the post's filter indicator to restore it. You can also remove the matching keyword or author from your lists.
Filtering is heuristic phrase/pattern matching, not AI, so it can miss disguised promos or occasionally hide a normal post that happens to use those words; restore any post with the 'Show' button. It only acts on posts present on your current feed page, and LinkedIn layout changes can affect which posts it recognizes.
The Connection Request Spam Filter scans the pending invitations shown on your LinkedIn My Network / invitations page and scores each one for spam using regex pattern groups (sales, recruiter, MLM, crypto), suspicious title keywords, emoji/short-message checks, and a mutual-connection minimum, plus your own whitelist and blacklist. Detected spam invitations get a visible 'Spam %' badge and are dimmed. It is heuristic and rule-based, not AI; all settings and the declined-request log stay in your browser, and it only ever reads invitations already on the current page.
Example: Your invitations fill up with 'I can help you 10x your revenue, book a call' messages from no-mutual-connection accounts; the filter scores them high, badges them 'Spam 85%', and (if you opted in) ignores only the highest-confidence ones for you.
Will it decline real people by mistake? It can, because scoring is rule-based. That is why auto-decline only fires on high-confidence matches and is OFF by default. With auto-decline off, it only badges requests so you make the final call.
Does it send messages or accept connections automatically? No. The only action it can take is clicking LinkedIn's own Ignore button on high-confidence spam when you opt in. It never accepts invitations, sends messages, or automates outreach.
Where are my whitelist, blacklist, and declined log stored? All of them live only in your local browser storage. The declined-request history is capped at the last 100 entries and nothing is uploaded anywhere.
Why are some invitations not scored? It only analyzes invitation cards present on your current invitations page and skips ones it has already processed. If LinkedIn changes its markup, some cards may not be recognized.
Scoring is heuristic pattern-matching, so it can mislabel a genuine request or miss a polished spammer — always review before relying on auto-decline. Auto-decline only triggers on high-confidence matches and simply clicks LinkedIn's existing Ignore button; it never sends messages or accepts anyone. It only sees invitations rendered on the current page, and the log of declined requests stays local (capped to the last 100).
The Email Privacy Protector is a client-side tool that hides or blurs mailto/email links on LinkedIn profile pages with CSS, can show an alternative contact link or message option instead, and watches for signs of automated scraping (browser automation flags like navigator.webdriver, known scraper user-agent patterns, and unusually rapid fetch activity) on the page you are viewing. Detection is heuristic and runs only in your current tab; it shows a local on-page warning banner and keeps a local privacy score and detection log. It cannot change your LinkedIn email-visibility settings and cannot stop scraping that happens on someone else's machine.
Example: On your own profile you enable email hiding plus a 'Contact Form' alternative, so casual visitors see a tidy contact button instead of a raw mailto link, and you get an on-page alert if the tab shows automation/scraper signals.
Does this actually stop people from scraping my email? Not on their end. It hides/blurs email links in your own browser view and warns you when the current tab shows automation signals, but it cannot control what scrapers do on their own machines or against LinkedIn's servers.
Does it change my real LinkedIn email visibility? No. It applies a CSS overlay to hide or blur the email on the page you are viewing. To control who can actually see your email, change the visibility setting inside LinkedIn itself.
Is the privacy score an official LinkedIn rating? No. It is a local heuristic checklist computed by the extension (for example, deducting points if your email is broadly visible or protection is off). It is guidance, not an audited security report.
Where do detections and stats go? They are saved only in your local browser storage (detection history is capped at the last 100 entries). Nothing about your email or browsing is sent to any server.
Scraper detection is heuristic and local: it checks the current page for automation flags, user-agent patterns, and rapid request bursts, so it can produce false alerts and cannot detect server-side scraping or scraping on other devices. Hiding the email is a CSS overlay on the page you view, not a change to LinkedIn's actual email-visibility setting. The privacy score is a built-in checklist heuristic, not a verified audit, and all data stays in your browser.
The Session Activity Monitor is a client-side tool that records each LinkedIn session it sees in this browser, building a local device fingerprint (hashed from user-agent, language, screen size, and timezone offset) and an approximate location guessed from your browser's timezone. It raises local on-page alerts for a new device, a new location, too many concurrent sessions, or logins during unusual hours, based on the history stored only in this browser. It cannot see your real LinkedIn account sessions on other devices, does not use GPS or IP geolocation, and the 'Force Logout' action simply navigates the current tab to LinkedIn's logout page.
Example: You open LinkedIn from a coworking laptop with a different timezone; the monitor sees an unfamiliar device fingerprint and new timezone-based location and pops a local 'New Location' alert so you can acknowledge it or log that tab out.
Can it see if someone logged into my LinkedIn from another country? No. It only knows about sessions seen in this browser. For real account-wide session and device info, use LinkedIn's own 'Where you're signed in' security settings. This tool is a local, browser-scoped monitor.
How does it know my location? It guesses a country/region from your browser's timezone using a small built-in mapping. It does not use GPS, IP geolocation, or any external service, so the location is approximate and stays in your browser.
What does 'Force Logout' actually do? It navigates the current tab to LinkedIn's logout URL, signing this browser out. It cannot remotely end a session on a different device, because it has no access to those sessions.
Is my session history uploaded anywhere? No. Sessions, alerts, and activity logs are stored only in your local browser storage (with recent-entry caps) and are never sent to a server or to us.
This monitors only sessions observed within this browser/profile — it cannot read or end your actual LinkedIn sessions on other phones or computers. Location is inferred from the browser timezone (a rough mapping for a handful of zones), not GPS or IP, so it is approximate. The session and alert history is stored locally (capped to recent entries) and 'Force Logout' just navigates this tab to LinkedIn's /logout page.
All features
Last updated 2026-11-10 by the Video Controls Plus team.