← Blog

Sales emails

Is web scraping legal for B2B lead generation? (2026)

2026-11-16 · updated 2026-11-16 · 16 min read · Adam Axelsson, founder of Revexa

Partly. In the US, scraping public web pages is usually not a federal computer crime, but it can still breach the site's terms. In the EU, GDPR applies to every person whose data you scrape, public or not, and regulators say lawful scraping is hard. The Supreme Court's Van Buren ruling (2021) and the Ninth Circuit's hiQ v. LinkedIn ruling (2022) narrowed the Computer Fraud and Abuse Act: a public website "has erected no gates to lift or lower in the first place". Contract claims still work: hiQ agreed to a $500,000 judgment and a ban on scraping LinkedIn in December 2022. In Europe, the Dutch regulator says you need a legal basis even for information that is "voor iedereen openbaar toegankelijk" (publicly accessible to everyone), and the fines we found for scraping run from €240,000 (Kaspr, 2024) to €30.5 million (Clearview AI, 2024). Company-level data, official business registers and licensed APIs carry the least risk.

Checked on 17 November 2026 against the law texts on govinfo.gov and EUR-Lex, the court records, and the Dutch AP's and the CNIL's own guidance and decisions. This is not legal advice.

Scraping decides how you get the data. Whether you may then email or message those people is a separate question with its own rules per country: see cold email laws by country, the US, the Netherlands and France.

Web scraping for lead generation at a glance

QuestionShort answerSource
US: is scraping a public page a federal crime?Usually not: the Ninth Circuit held that "without authorization" does not apply to public websitesCFAA, 18 U.S.C. 1030; Van Buren (2021); hiQ v. LinkedIn (9th Cir., 18 April 2022)
US: scraping behind a login or with fake accountsHigh risk: hiQ stipulated to CFAA liability based on its data collection and on password-protected pages reached with fake accountshiQ stipulation filed 6 December 2022; consent judgment entered 8 December 2022
US: do the site's terms of service bind you?Yes for logged-in users: hiQ was found in breach of LinkedIn's User Agreement; terms did not reach Bright Data's logged-off scrapinghiQ order (filed 4 November 2022); Meta v. Bright Data (23 January 2024)
EU: does GDPR apply to public data?Yes, to any information about an identifiable person, wherever you found itGDPR art. 4(1), 6, 14; Dutch AP guidance
EU: legal basis for B2B lead listsIn practice only legitimate interest, which needs a balancing test; a commercial interest can qualifyGDPR art. 6(1)(f); CJEU C-621/22 (4 October 2024)
EU: must you tell people?Yes, including the source, within one month and at the latest at your first messageGDPR art. 14(2)(f) and 14(3)(a) and (b)
EU: copying a whole directoryMay infringe the database right even if each entry is publicDirective 96/9/EC art. 7; CJEU C-762/19
Lowest riskCompany-level data, official registers released for re-use, licensed APIsGDPR recital 14; Regulation (EU) 2023/138
Maximum fine (EU)EUR 20 million or 4% of worldwide turnover, whichever is higherGDPR art. 83(5)

The US: the CFAA after Van Buren and hiQ

The federal anti-hacking law, the Computer Fraud and Abuse Act, makes it an offence when someone "intentionally accesses a computer without authorization or exceeds authorized access, and thereby obtains" ... "information from any protected computer" (18 U.S.C. 1030(a)(2)(C)). It also gives a civil claim: "Any person who suffers damage or loss by reason of a violation of this section may maintain a civil action against the violator to obtain compensatory damages and injunctive relief or other equitable relief" (section 1030(g)). For years, platforms used it against scrapers.

Van Buren v. United States (3 June 2021). The Supreme Court held that a person "exceeds authorized access" when they obtain information from areas of a computer "that are off limits to him", not when they misuse data they were allowed to see. It called this a "gates-up-or-down inquiry", and it warned that the government's broader reading "would attach criminal penalties to a breathtaking amount of commonplace computer activity". In footnote 8 the Court left open whether the gates are only technical or also include "limits contained in contracts or policies" (opinion).

hiQ Labs v. LinkedIn (Ninth Circuit, 18 April 2022). hiQ scraped public LinkedIn profiles to sell analytics to employers. On remand after Van Buren, the court wrote that "a defining feature of public websites is that their publicly available sections lack limitations on access; instead, those sections are open to anyone with a web browser", so such a computer "has erected no gates to lift or lower in the first place". Its conclusion: the concept of "without authorization" "does not apply to public websites". It added a warning for scrapers: "Entities that view themselves as victims of data scraping are not without resort, even if the CFAA does not apply", naming trespass to chattels, breach of contract and other claims (opinion). The ruling was on a preliminary injunction, not a final judgment.

How hiQ ended. Back in the district court, Judge Chen found that hiQ "breached LinkedIn’s User Agreement both through its own scraping of LinkedIn’s site and using scraped data, and through turkers’ creation of false identities on LinkedIn’s platform". He granted LinkedIn summary judgment on the fake accounts and left the scraping claim open only because hiQ had raised waiver and estoppel defenses (order dated 27 October 2022, filed publicly on 4 November 2022, Docket 404). On 6 December 2022 the parties filed a stipulated consent judgment, and the judge entered it on 8 December 2022 (Docket 406): "Judgment in the amount of $500,000 USD is hereby entered against hiQ and in favor of LinkedIn", plus a permanent ban on "using automated means to access and/or copy data from the LinkedIn platform, whether logged in to a LinkedIn account or not, without express written permission of LinkedIn" and an order to destroy the scraped data and code. hiQ also stipulated that LinkedIn could establish CFAA liability "based on hiQ’s data collection practices and based on hiQ’s direct access to password-protected pages on LinkedIn’s platforms using fake accounts" (Docket 405). A stipulation is a settlement, not a court finding.

Meta v. Bright Data (23 January 2024). Meta sued Bright Data, which sells data scraped from Facebook and Instagram, for breach of contract. The same judge held that "the Terms do not apply to Bright Data’s logged-off scraping of publicly viewable data", because Meta's terms govern users while they use their accounts (order). Meta dropped its remaining claim and waived its right to appeal on 23 February 2024 (stipulation). The order did not decide anything about scraping while logged in.

Scraped email addresses. US email law adds one rule of its own: knowingly sending an email that already breaks CAN-SPAM to an address "obtained using an automated means from an Internet website" whose operator promised not to share addresses is an aggravated violation (15 U.S.C. 7704(b)(1)). More in is cold email legal in the US.

Our reading for US lead generation: logged-off collection of truly public business pages is the lowest-risk form of scraping. Logging in, using fake or rented accounts, rotating proxies to get around blocks, or ignoring a cease-and-desist letter moves you towards the facts that cost hiQ the case. We did not cover state privacy laws here.

Terms of service and contract claims

For B2B lead generation, the site people most often ask about is LinkedIn. Its User Agreement, in force since 3 November 2025, says in section 8.2 that members will not "Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services". It also bans using "bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages".

The two US cases point in the same direction. A logged-in user has accepted the terms, and hiQ was found in breach. A logged-off visitor who never accepted them was outside Meta's terms. Scraping LinkedIn from your own account, through an extension or a tool that uses your session, is therefore the clearest contract breach, and LinkedIn can also restrict your account. The full LinkedIn case history, including the 2025 and 2026 lawsuits, is in is LinkedIn scraping legal; automating your own account is covered in is LinkedIn automation legal. More in LinkedIn outreach without restrictions and LinkedIn automation tools compared.

In the EU, terms can matter even more. In Ryanair v. PR Aviation (C-30/14, 15 January 2015), the EU Court of Justice held that the database directive does not apply to a database protected neither by copyright nor by the database right, so the directive does not prevent its maker "from laying down contractual limitations on its use by third parties, without prejudice to the applicable national law" (judgment). The CNIL says the same in privacy terms (see below).

The EU: GDPR applies to scraped personal data

GDPR protects "any information relating to an identified or identifiable natural person" (article 4(1)). A name, a job title and a work email are personal data, and collecting, storing and using them is processing. Nothing in the regulation exempts information because it is public. Three articles do most of the work for a scraped lead list (GDPR):

  • Article 6, a legal basis. For a company building prospect lists, that is in practice legitimate interest (article 6(1)(f)): processing "necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject".
  • Article 14, telling people. Where data "have not been obtained from the data subject", you must tell them who you are, why you process the data, your legitimate interest and "from which source the personal data originate, and if applicable, whether it came from publicly accessible sources". If you use the data to contact the person, you must do this "at the latest at the time of the first communication to that data subject" (article 14(3)(b)).
  • Article 21, objection. People can object to direct marketing at any time, and then you must stop. More in GDPR and B2B email under legitimate interest.

Can a commercial interest be legitimate? Yes, said the EU Court of Justice on 4 October 2024 in KNLTB (C-621/22), a case brought against the Dutch AP. A commercial interest "could constitute a legitimate interest ... provided that it is not contrary to the law", but the processing must be "strictly necessary" and the person's interests must not override it, where "the reasonable expectations of the data subject" weigh heavily (judgment).

Does GDPR reach a US scraper? It applies outside the EU when a company offers goods or services to people in the EU or monitors their behaviour there, as the Dutch AP's guidance explains (GDPR article 3(2)). Clearview AI, a US company, was fined by both the Dutch and the French regulators (see below).

What the Dutch AP says

The Autoriteit Persoonsgegevens published its guidance on scraping by private organisations on 1 May 2024. Its summary at the time: "Scraping door private partijen en particulieren is vrijwel nooit toegestaan" (our translation: scraping by private parties and individuals is almost never allowed) (AP, archived 20 May 2024). That version also said a purely commercial interest could never be a legitimate interest: "Heeft u bij de verwerking van persoonsgegevens alleen een zuiver commercieel belang? Dan kunt u volgens het standpunt van de AP geen geslaagd beroep doen op de grondslag gerechtvaardigd belang" (our translation: if your only interest is purely commercial, in the AP's view you cannot rely on legitimate interest) (PDF, May 2024, archived).

After the KNLTB judgment, the AP published a new version on 2 April 2025, and the line about purely commercial interests is gone (AP guidance page, PDF, April 2025). The rest stays strict. On public data:

"Deze grondslag heeft u óók nodig als u alleen informatie verzamelt die al op internet staat en die voor iedereen openbaar toegankelijk is."

Our translation: you also need this legal basis if you only collect information that is already on the internet and publicly accessible to everyone. The AP adds that "zullen vooral gerichte vormen van scraping door private organisaties rechtmatig kunnen zijn" (our translation: it is mainly targeted forms of scraping by private organisations that can be lawful). Among the uses that can "waarschijnlijk nooit AVG-proof" be set up (our translation: probably never be made GDPR-compliant), it lists scraping the "internet om profielen van betrokkenen te maken en die vervolgens door te verkopen" (our translation: the internet to build profiles of people and then sell them on).

We found no AP text on scraping for B2B lead generation as such. Our reading: a broad scrape of people's profiles to build a prospect database sits close to the AP's example of uses that can probably never comply, while collecting a few named decision-makers at companies you have already chosen, for a stated purpose, is the targeted kind it describes as possibly lawful.

What the CNIL says

France's regulator inspected companies that harvest contact details for sales prospecting in 2019 and published its conclusions on 30 April 2020. Its core point:

"Ces données, bien que publiquement accessibles, sont des données personnelles. Dès lors, elles ne sont pas librement réutilisables par tout responsable de traitement et ne peuvent être réexploitées à l’insu de la personne concernée."

Our translation: these data, although publicly accessible, are personal data. They are therefore not freely reusable by any controller and cannot be reused without the person's knowledge. The CNIL also ties privacy to contract: some tools extract data "à partir de sites web dont les conditions générales d’utilisation (CGU) interdisent l’aspiration et la réutilisation des données à des fins commerciales. Dans cette hypothèse, cette pratique n’est donc pas autorisée" (our translation: from websites whose terms of use forbid harvesting and reusing the data for commercial purposes; in that case the practice is not allowed). It asks users of scraping tools to give the article 14 information, including the source, at the latest at the first contact (CNIL).

The cases in that article concern mostly consumers (classified ads and online directories). For B2B email, the CNIL accepts legitimate interest when the message relates to the person's job; see is cold email legal in France.

The EU database right

The EU also protects the investment behind a database. Article 7 of the database directive gives a maker who made "a substantial investment in either the obtaining, verification or presentation of the contents" the right "to prevent extraction and/or re-utilization of the whole or of a substantial part, evaluated qualitatively and/or quantitatively, of the contents of that database". Repeated and systematic extraction of "insubstantial parts" is also banned where it conflicts with normal exploitation of the database (article 7(5)). The right expires fifteen years from 1 January of the year after the database was completed, and a substantial new investment gives the database its own new term (article 10) (Directive 96/9/EC).

In CV-Online Latvia v. Melons (C-762/19, 3 June 2021), the Court held that a search engine that copies and indexes a database "freely accessible on the Internet" is extracting and re-utilising its content, which the maker may prohibit where it harms the maker's investment (judgment). Our reading: copying most of a business directory or a job board into your own lead database is a database-right risk on top of GDPR, even when every single entry is public.

Fines and real cases

DateCaseOutcomeSource
17 October 2022CNIL v. Clearview AI: photos scraped from public pages, viewable "without logging in to an account"Fine of €20 million and an order to stop collecting data on people in France without a legal basisCNIL press release, 20 October 2022 (archived), Légifrance SAN-2022-019
8 December 2022hiQ v. LinkedIn, consent judgment (stipulation filed 6 December)$500,000 judgment against hiQ, permanent ban on scraping LinkedIn, data and code destroyedDocket 406
23 January 2024Meta v. Bright DataBright Data won: Meta's terms did not cover logged-off scraping of public dataOrder
16 May 2024 (announced 3 September 2024)Dutch AP v. Clearview AIFine of €30.5 million plus orders under penalty of up to more than €5 million; using Clearview is also prohibitedDutch AP
5 December 2024CNIL v. Kaspr, a LinkedIn contact-data extension with about 160 million contactsFine of €240,000, in particular for collecting contact details users had restricted to their 1st and 2nd-degree connections, retaining data too long and informing people late and only in EnglishCNIL
4 March 2026CNIL closes the Kaspr orderKaspr "chose to delete its database and cease all data collection on LinkedIn"CNIL

Two details matter for sales teams. In Kaspr, answering people that their data came "from publicly accessible sources" was not enough; the CNIL wanted "all available information as to the source". And the Dutch AP warned Clearview's customers directly: "Clearview breaks the law, and this makes using the services of Clearview illegal." Our reading: buying a scraped list does not move the GDPR duties to the seller. You become a controller of that data when you use it.

What is lower risk

Company-level data. GDPR "does not cover the processing of personal data which concerns legal persons and in particular undertakings established as legal persons, including the name and the form of the legal person and the contact details of the legal person" (recital 14). Company name, industry, size, technology, funding, hiring and other signals about a company are therefore outside GDPR when they are about a legal person. Sole traders and named employees are natural persons, so their data is covered (our reading of recital 14 and article 4(1)). More on company signals in buying signals in B2B.

Official registers released for re-use. Under Regulation (EU) 2023/138, public bodies must publish basic company information from business registers "in machine-readable formats via APIs", for re-use under CC0, CC BY 4.0 "or any equivalent or less restrictive open licence". The regulation applies "from 16 months after entry into force", which by our count is 9 June 2024. It also says that where the data includes personal data, GDPR still applies (recital 8) (Regulation 2023/138). Our reading: a register API gives you a clear licence and no terms-of-service fight, but a director's or sole trader's name in it is still personal data.

Licensed APIs and data vendors. Access under a contract removes the CFAA and terms-of-service questions. It does not remove GDPR. Ask the vendor where each contact came from, because you must be able to name the source to the person (article 14(2)(f)), and Kaspr shows that "publicly accessible sources" is not an answer. Vendors compared in best B2B data providers 2026.

Targeted, minimal collection. Pick the company first from company-level signals, then find one relevant person for that account, collect only what you need, tell them where you got their details within one month and at the latest in your first message, and stop at the first objection. That follows the targeted model the AP describes (our reading).

Checklist for scraping and B2B lead generation

  1. Prefer company-level data and official register APIs over scraping people.
  2. Never scrape behind a login, with fake or rented accounts, or after a cease-and-desist letter.
  3. Read the site's terms before you collect; in France, the CNIL says collection is not allowed when the terms ban it.
  4. Write a legitimate interests assessment before you collect personal data in the EU, and keep it.
  5. Collect only the fields you need for a defined purpose, and set a retention period that does not renew itself.
  6. Tell each person the source of their data within one month and at the latest in your first message, in a language they understand.
  7. Stop at the first objection, in every channel, and keep a suppression list.
  8. Check the sending rules for each recipient's country before you email or message: cold email laws by country.

Where Leo fits

Leo, the buying-signal agent Revexa builds, watches company-level signals such as hiring, funding and new executives, and drafts messages for LinkedIn and email. In review mode, the default, you read and approve every draft before it goes out; you can switch on autonomous mode per channel. You are the sender, so whether a message to a given person is lawful where they live is yours to check. Leo is the wrong tool if you want a scraper that exports profiles in bulk.

Common questions

Is web scraping legal in the US?

Scraping public pages is usually not a federal crime: after Van Buren (2021), the Ninth Circuit held in hiQ v. LinkedIn (2022) that "without authorization" "does not apply to public websites". Contract, trespass and copyright claims remain, and hiQ ended with a $500,000 stipulated judgment in December 2022.

Is it legal to scrape LinkedIn for leads?

It breaches LinkedIn's User Agreement, whose section 8.2 bans software "to scrape or copy the Services, including profiles". In the EU, GDPR also applies: the CNIL fined Kaspr €240,000 in December 2024 for, among other things, collecting LinkedIn contact details users had restricted. Details in is LinkedIn scraping legal.

Does GDPR apply to publicly available data?

Yes. The Dutch AP says you need a legal basis even for information that is publicly accessible to everyone, and the CNIL says public data "ne sont pas librement réutilisables" (are not freely reusable). You must also tell people where you got their data.

Is it legal to buy a scraped lead list in the EU?

Buying does not remove the seller's problems. You become a controller of the data you use, so you need your own legal basis, must name the source to each person and must honour objections (our reading of GDPR articles 6, 14 and 21).

What is the safest data source for B2B lead generation?

Company-level data, which GDPR does not cover when it concerns legal persons (recital 14), and official business registers published for re-use through APIs under Regulation (EU) 2023/138. Named people in those sources are still personal data.