Guide
Outbound without LinkedIn automation: what the User Agreement actually says.
A founder deciding how to do outbound hears "everyone automates LinkedIn" and "LinkedIn bans automation" in the same week. Both are true. This page sets out what the contract says, what enforcement has looked like since 2022, and what a single person sending from their own account may still do. General information, not legal advice; the law of your market and of the recipient's applies. Written 2026-11-13.
1. The contract you accepted
LinkedIn's User Agreement is a contract between LinkedIn and each member. Section 8 ("Dos and Don'ts") lists what a member promises not to do, and the promises that matter for outbound are in section 8.2. Paraphrased, a member agrees not to:
- develop, support or use software, scripts, robots, crawlers, browser plug-ins or add-ons, or any other means, to scrape the service or copy profiles and other data from it;
- use bots or other unauthorised automated methods to access the service, add or download contacts, or send or redirect messages;
- override security features or bypass access controls and use limits, such as search result caps or the limit on profile views;
- use, disclose or distribute data obtained in breach of the agreement, or sell, rent or otherwise monetise the service or data obtained from it;
- create a false identity or misrepresent who you are.
The Professional Community Policies, which the agreement incorporates, repeat the point for everyday conduct: be who you say you are, do not spam, do not use tools that automate activity. LinkedIn's help centre adds a page on prohibited software and extensions: third-party tools that scrape the site, automate actions or change how its pages look (the overlay extensions that draw their own panels on top of a profile) are not permitted, and a member whose account is found using one may be restricted or closed.
Two things follow. First, the rule is not about volume. One automated message is a breach; a thousand hand-written ones are not. Second, the agreement binds the member. A vendor's tool running on your session, with your cookie or your password, is your breach, and the account at risk is yours.
2. What enforcement looked like, 2022 to 2026
hiQ Labs v. LinkedIn (2017 to 2022). hiQ scraped public profiles to sell workforce analytics. The case is remembered for the Ninth Circuit's view that scraping pages anyone can see is unlikely to be unauthorised access under the US Computer Fraud and Abuse Act. It ended differently: in November 2022 the district court held that hiQ had breached the User Agreement, both by scraping and by hiring workers to run fake profiles, and in December 2022 the parties agreed a judgment in which hiQ paid US$500,000 and accepted a permanent injunction against scraping LinkedIn and an order to destroy the data and the code built from it. The lesson for a founder is that the contract claim, not the hacking statute, is the one that bit.
Proxycurl (2025). In January 2025 LinkedIn sued the operator of Proxycurl, a profile-data API sold to sales and recruiting tools, in federal court in California (case no. 3:25-cv-00828), alleging the creation of hundreds of thousands of fake accounts to scrape member profiles. Proxycurl announced its shutdown within the year. Any product built on that API lost its data source with it.
Artisan (December 2025 to January 2026). Artisan sells an autonomous "AI BDR" that writes and sends on its customers' behalf. LinkedIn banned the company in late December 2025 and reinstated it in January 2026. By the company's own account, LinkedIn objected to the use of its name on Artisan's site and to data Artisan had bought from brokers who had scraped LinkedIn; Artisan removed every mention of LinkedIn from its site to be reinstated.
The pattern is consistent: the targets are vendors that scrape at scale, run fake accounts or drive members' sessions. Members who use such a tool are reached by account restriction, which arrives without a court case and without notice. For a solo founder whose network is the business, that is the risk that matters.
3. What stays allowed
Nothing in the agreement stops a person from using LinkedIn as a person. Paraphrased from the same texts, you may:
- search, open and read public profiles and company pages yourself, within the limits LinkedIn applies to your account;
- write your own notes about what you read, in your own files, and keep your own list of whom you intend to contact;
- send connection requests and messages yourself, from your own account, as yourself, one at a time, with text you wrote or approved;
- use the features LinkedIn sells for the purpose (Sales Navigator, InMail) in the way their own terms describe.
The line runs between a human acting through LinkedIn's own interface and software acting on the human's behalf. Reading by hand is allowed; a crawler is not. Sending one message you approved is allowed; a queue that sends while you sleep is not. An extension that shows you your own notes beside a profile is in a grey area the help page resolves against you if it also pulls data from the page.
4. How GenTool fits
GenTool was built on the other side of that line, and the security page and privacy notice describe the same facts in the same words:
- Research comes from company pages, not LinkedIn. GenTool opens the public pages of the companies you name or that it suggests (team, about, careers, changelog, press) and records each claim with its URL, a verbatim excerpt and a timestamp. It stores a personal LinkedIn profile URL only when the company's own site or Hunter's record showed it, and never opens LinkedIn.
- No LinkedIn connection. GenTool never operates a LinkedIn or e-mail account and never holds those credentials. There is no extension, no session cookie, no stored password.
- No automation. There is no sending code path to switch on. A row you approve gives you the connection note and the message as text; you open LinkedIn yourself, decide, paste, send, and record the receipt in GenTool. Marking a row sent records your receipt and nothing else.
- You send from your own account. Our terms ask you to send from your own identified account, as yourself, and to comply with LinkedIn's User Agreement and your mailbox provider's terms. GenTool gives you the research and the QA; the account, the message and the decision stay yours.
That is why GenTool has no LinkedIn-ban story to tell and never will: the product does not touch the service the agreement protects. If you send into Germany, read the companion guide on section 7 UWG before the first e-mail.
Sources
- LinkedIn User Agreement, section 8 ("Dos and Don'ts"), in the version in force on the date above: linkedin.com/legal/user-agreement
- LinkedIn Professional Community Policies: linkedin.com/legal/professional-community-policies
- LinkedIn Help, "Prohibited software and extensions": linkedin.com/help/linkedin/answer/a1341387
- hiQ Labs, Inc. v. LinkedIn Corp., No. 3:17-cv-03301 (N.D. Cal.): order on summary judgment of 4 November 2022; stipulation and consent judgment entered December 2022 (US$500,000, permanent injunction): the stipulated judgment (PDF)
- LinkedIn Corp. v. Nubela Pte. Ltd. (Proxycurl) et al., No. 3:25-cv-00828 (N.D. Cal., filed 24 January 2025); LinkedIn's statement: news.linkedin.com, "LinkedIn takes legal action to defend member privacy"
- Artisan's ban and reinstatement: TechCrunch, 7 January 2026, "Yes, LinkedIn banned AI agent startup Artisan, but now it's back"
Written 2026-11-13; general information, not legal advice. LinkedIn changes its texts; the links above go to the current versions, and the paraphrases here were checked against the versions in force on that date. Nothing on this page was retrieved from LinkedIn by GenTool's software.