What enforcement has looked like
Shield is the instructive case. It was the most conservative product in the category and it still lost, because the extension itself was the exposure. The risk attaches to the mechanism, not to the intent.
What triggers a restriction
| Mechanism | What LinkedIn sees | Policed |
|---|---|---|
| Volume actions | Bulk connection requests, bulk messaging, auto endorsing, auto commenting | Hardest |
| Scraping | Profile or company data pulled at a rate or scale no person could, across people you have no relationship with | Hard |
| Extension signatures | Page interactions that do not look like a mouse, detectable regardless of what the extension does | Hard |
| Unofficial publishing | A post submitted by replaying LinkedIn's internal requests instead of going through the interface or the documented API | Hard |
| Session and IP mismatch | Sign ins from a vendor's servers, on an address and device that are not yours. The same shape as a compromised account | Hard |
| Reading a page you opened | One person, one session, one browser, at human speed | Not a trigger |
Safe, and not safe
Looks like a person using LinkedIn
Gets accounts limited
Worth being precise aboutLinkedIn publishes no tier list of penalties, so any escalation ladder is inference from what members report. Consistently described: a block on specific features lasting hours, a lock lasting days that needs identity verification, and permanent removal, where appeals rarely succeed. Plan for the middle one.
Four questions to ask before installing anything
| Ask | The answer you want | The answer that should stop you |
|---|---|---|
| Does it need a browser extension? | No | Yes. You inherit both LinkedIn's view of extensions and the Chrome Web Store's |
| Does it want your LinkedIn password? | No, you sign in yourself in a real browser | Yes, so it can sign in from its own infrastructure |
| What performs the publish? | LinkedIn's composer, or its documented API on an app you registered | Their servers, through an undocumented route, while your machine is off |
| Does it read only what you opened? | Yes, one page at a time | It collects in the background across profiles you never visited |
Where Everpost sits
The honest caveatEverpost does include automated connection requests and messaging. They sit behind an explicit unlock that says there is no compliant path for them. The caps above still apply and the kill switch still stops them. Unlock those and you take the ordinary risk of LinkedIn automation. No architecture protects you from it.
If you are already restricted
No vendor can promise how LinkedIn will behave, this one included. What a vendor can do is describe its mechanism precisely enough that you can judge it yourself, which is what this page has tried to do.
The version where you press post
No extension, no stored credentials, no server. Free tier, no card.
Request early access See pricing