Yes, it is. Contrary to popular belief, there’s nothing shady or illicit about web scraping itself. That does not mean that any kind of web scraping is legal. Like all human activity, it needs to remain within certain boundaries. In web scraping, the most important boundaries are personal data and intellectual property regulations, but other factors, such as the website’s terms of service can play a role as well. If you want to learn more about the legality of web scraping, read on. We will cover the most important areas of confusion one by one and give you some useful tips to keep your scrapers compliant and ethical. *We are lawyers, but we are not your lawyers. Even though we want to help as much as we can, we do not know the details of your project. For professional legal advice, please talk to a certified lawyer in your country.* *This article was written in August 2021 and updated in April 2022 to [reflect the latest developments](#updatelatest-news-in-2022) in the area.* **What you’ll learn:** - [Common misconceptions around web scraping.](#common-misconceptions) - [The most important things to keep your scrapers ethical.](#how-to-make-ethical-scrapers) - [What’s personal data and how to identify it.](#think-twice-before-scraping-personal-data) - [How copyright influences scraping.](#scraping-copyrighted-content) - [How websites prevent scraping with their Terms of Use.](#terms-of-use-and-scraping) - [What is the CFAA and how it relates to web scraping.](#cfaa-and-criminal-liability-in-the-us)

Web scraping is legal if you scrape data publicly available on the internet. But some kinds of data are protected by international regulations, so be careful scraping personal data, intellectual property, or confidential data. Respect your target websites and use empathy to create ethical scrapers. If you would like to discuss your web scraping project with our team, you can contact us via this form. ## Common misconceptions Before we start, let’s clear up a few fallacies. We sometimes hear that “web scrapers operate in a grey area of law”. Or that “web scraping is illegal, but nobody enforces the illegality, because it’s difficult”. Sometimes even that “web scraping is hacking” or “web scrapers are stealing our data”. We've heard this from clients, friends, interviewees, and other companies. The thing is, none of that is true. ### Myth 1: Web scraping is illegal It’s all a matter of what you scrape and how you scrape it. It’s quite similar to taking pictures with your phone. In most cases, it is perfectly legal, but taking pictures of an army base or confidential documents might get you in trouble. Web scraping is the same. There is no law or rule banning web scraping. But that does not mean you can scrape everything. ### Myth 2: Web scrapers operate in a grey area of law Not at all. Legitimate web scraping companies are regular businesses and follow the same set of rules and regulations everyone else needs to follow to do their respective business. Web scraping is not heavily regulated, that’s true. But that does not imply anything illicit. Quite the contrary. ### Myth 3: Web scraping is hacking Even though the word hacking has many interpretations, it’s mostly used to describe access to a computer system through non-standard means, exploiting the system. Web scrapers access websites exactly the same as a legitimate human user would. They do not exploit vulnerabilities and they access only data that’s publicly available. ### Myth 4: Web scrapers are stealing data Web scrapers only collect data that’s publicly available on the internet. Can public data be stolen? Imagine you see a nice shirt in a store, so you pull out your phone and take a note of the brand and price. Would you think you stole the information? No, you wouldn’t. Yes, some kinds of data are protected by various regulations and we’ll cover that later, but other than that, there’s nothing to worry about when collecting facts like prices, locations, or review stars.

![Webscraping_legal](https://blog.apify.com/content/images/2021/09/Webscraping_legal.jpg) ## How to make ethical scrapers Even though most of the bad things you read about scraping are not true, you still need to be careful about it. Frankly, you should be careful when doing business of any kind. And web scraping is no exception. There are certain kinds of data you should not scrape before talking to your lawyer and the most important kind is personal data, with intellectual property in close second. It does not mean that web scraping is dangerous. There are rules, yes, but you can use empathy to tell whether your scraping will be ethical and lawful or not. [Amber Zamora](#further-reading) proposes a list of features that an ethical scraper should have: - The data scraper acts as a good citizen of the web, and does not seek to overburden the targeted website; - The information copied was publicly available and not behind a password authentication barrier; - The information copied was primarily factual in nature, and the taking did not infringe on the rights — including copyrights — of another; and - The information was used to create a transformative product and was not used to steal market share from the target website by luring away users or creating a substantially similar product. If you follow these guidelines, you can be confident that your scrapers will be ethical. > This article provides guidelines for scraping ethically as a business. If you're scraping for your personal project or for academic research, it will be a bit easier for you, but we will not cover those exceptions here. ## Think twice before scraping personal data Not too long ago, few people worried about personal data. There were no specific regulations and everyone’s names, birthdays, and shopping preferences were free to use. This is no longer the case in the European Union (EU), California and other jurisdictions. If you scrape personal data, you should definitely learn about the [General Data Protection Regulation](https://ec.europa.eu/info/law/law-topic/data-protection/data-protection-eu_en) (**GDPR**) and [California Consumer Privacy Act](https://oag.ca.gov/privacy/ccpa) (**CCPA**) and your local regulations. Since the regulations are different around the world, you need to think carefully about where from and whose data you scrape. In some countries, it might be completely fine, while in other places you should avoid personal data completely. If you want to learn more, [here's a great comparison](https://fpf.org/wp-content/uploads/2018/11/GDPR_CCPA_Comparison-Guide.pdf) of the GDPR and CCPA. How do you know whether to apply GDPR, CCPA, or some other regulation? This is a simplification, but if you're from the EU, you do business in the EU, or the people whose data you want are in the EU, GDPR will apply. It is a far-reaching regulation. On the other hand, CCPA applies only to California businesses and residents in California. We use it for comparison and because it's pioneering legislation in the United States. Wherever you are, you should always check your own country's privacy laws. ### What is personal data (information) anyway? **GDPR** defines **personal data** as follows: “Personal data means **any information** relating to an identified or identifiable natural person” That’s a bit hard to read, but gives us an idea of just how broad the definition is. Almost anything can be personal data if it relates to a specific human being. The **CCPA** definition is fairly similar, but it calls it **personal information**. For simplicity, we will use only the term personal data. To illustrate the broadness of the definition, let’s look at some **examples** of personal data: * Official data about a person * name, surname * date of birth * address * social security number, passport number, national ID number * employment information * Contact details * phone number * email address * IP address * Facebook, Twitter, and other network handles * Data often collected by applications * location either by address or GPS * shopping preferences * behavioral data * Video + audio recordings of people and biometric data * Special categories of personal data * sex, gender, and sexual orientation * racial or ethnic origin * religious beliefs * political opinions * medical records As you can see, pretty much any information about a human being constitutes personal data. Don't forget that this is not an exhaustive list. When in doubt, read the definition again and try to decide whether your piece of information fits it or not. ### Publicly available personal data A large part of the web scraping community lives under the wrong impression that only private personal data is protected, whatever that means, and that scraping personal data from publicly available sources - websites - is totally fine. Well, it depends. Under GDPR, all personal data is protected and it does not matter at all where the data comes from. A company in the EU [was fined a pretty large sum](https://iapp.org/news/a/polish-court-overturns-dpas-first-gdpr-fine/) for scraping public data from the Polish business register. A court later overturned the fine, but explicitly upheld the ban on scraping publicly available data. Under CCPA, information made available by the government, such as business register data, is considered "publicly available" and therefore not protected. In the US, there's an important case dealing with the scraping of publicly available data from social networks: [HiQ vs. LinkedIn](https://en.wikipedia.org/wiki/HiQ_Labs_v._LinkedIn). We're still waiting for the final decision, but the preliminary outcomes support the idea of scraping personal information that was made public by the person. In 2023, the [California Privacy Rights Act](https://en.wikipedia.org/wiki/2020_California_Proposition_24) (**CPRA**) will come into effect and it will broaden the CCPA definition of publicly available information. Data that was previously made public by the subject will no longer be protected. This may effectively allow the scraping of personal data from websites where people make their personal data freely available, like **LinkedIn** or **Facebook**, but only in California. We expect other US states might take inspiration from the CCPA and CPRA in their own privacy legislation. ### How to scrape personal data ethically Before you start with the legal analysis, use empathy. Do you think the person whose data you're scraping would be happy about it? Does it benefit a greater good? When scraping ethically, we're not only considering what's legal, but also what's right. Apify has a beautiful use case with [Thorn](https://www.thorn.org/spotlight/) where we [find lost children](https://apify.com/success-stories/fighting-child-traffickers-with-technology) by scraping personal data. We're really proud of it and we firmly believe it passes the [legitimate interest](https://www.itgovernance.eu/blog/en/the-gdpr-legitimate-interest-what-is-it-and-when-does-it-apply) test and the [vital interest and public interest](https://www.itgovernance.co.uk/blog/gdpr-lawful-bases-for-processing-with-examples) tests of GDPR. Once you're certain that you're not hurting anyone with your scraping, you should analyze which regulations apply to you. If you're a company in the EU, GDPR applies to you even if you want to scrape personal data of people somewhere else in the world. As an EU business, you must do your research. Sometimes it will be okay to move forward because of legitimate interest, but more often than not you will have to pass that personal data scraping project to your non-EU partners or competitors. On the other hand, if you're not an EU company, you don't do business in the EU, and you don't target people who are in the EU, you could be good to go. Also make sure to check your local regulations, like the CCPA. Finally, you should program your scrapers to collect as little personal data as possible and keep that data only temporarily. Making a database of people and their information (e.g. for lead generation) is a very difficult case in protected jurisdictions, whereas scraping people from Google Maps reviews to automatically identify fake reviews and then discarding the personal data could easily pass the legitimate interest test.

Meta v Social Data Trading Ltd.

Meta Platforms, Inc. v. Social Data Trading Ltd.

In late December 2021, Meta Platforms, Inc., sued Hong Kong-based Social Data Trading Ltd. for scraping Instagram and Facebook profile data. Meta's case is built on the allegation that Social Data Trading Ltd. circumvented Meta's blocking measures and thereby engaged in illegal hacking under Section 502 of California's Penal Code. Meta had blocked Social Data Trading accounts, but alleges that the defendant used "thousands of automated Instagram accounts to improperly collect and aggregate data". The case is interesting because it will determine whether the use of fake accounts to bypass limited access to data is illegal.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gvxvw9eriu2yjpy4pkhr.jpg) ## Scraping copyrighted content Pretty much everything on the internet is protected by some kind of copyright. Some things more obviously than others. Music, movies, photographs? Sure, protected. News articles, blog posts, social media posts, research papers? Also protected. Websites' HTML, databases' structure and content, images, logos, and digital graphics? All those things are protected by copyright. The one thing not protected by copyright are plain facts. But what does that mean for web scraping? If a piece of content is copyrighted, it means, among other things, that you cannot make copies of it without the author's consent (license) or a legal permission. Since the very definition of scraping is copying of content, and you almost never have the author's explicit consent, the legal permissions are your best bet. As always, the laws around the world vary. We will only discuss EU and US regulations. ### Data mining in the European Union In the EU, the scraping of copyrighted content is permitted by Article 3 and 4 of the [Directive 2019/790 on copyright and related rights in the Digital Single Market](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32019L0790&from=EN) (**DSM Directive**). The DSM Directive permits **text and data mining**, which means: > any automated analytical technique aimed at analysing text and data in digital form in order to generate information which includes, but is not limited to, patterns, trends and correlations; This is very important, because it means that **scraping** of copyrighted content **is only permitted for the purposes of generating information**. For example, you can scrape a webpage to extract prices from it, or books for natural language analysis, but you **cannot** scrape news articles and then republish them on your own website. There are more conditions that you need to meet before your scraping is permitted: - Scrape only what you have **lawful access** to - publicly available data. - For **scientific research**, you can freely scrape almost anything. - For **business**, the content owner can **opt out** of scraping by **expressly** reserving that right **in a machine-readable format**. #### Application of `robots.txt` The DSM Directive does not go into detail on how the express reservation in a machine-readable format should look like, but the general assumption is that the website owner can use the `Disallow` command of the [`robots.txt`](https://developers.google.com/search/docs/advanced/robots/intro) standard or other similar means to express that reservation. If the URLs you want to scrape are disallowed, you should not scrape them. Otherwise you risk infringing the owners' copyright. ### Fair use in the United States In the US, the scraping of copyrighted content is permitted by the [fair use doctrine](https://www.copyright.gov/fair-use/more-info.html). The rules are somehow similar to the European ones, but they do not make a sharp distinction between scientific research and for-profit scraping. The fundamental case law for application of fair use to scraping is the [Authors Guild v. Google](https://en.wikipedia.org/wiki/Authors_Guild,_Inc._v._Google,_Inc.) (**Google Books case**). In the Google Books case, the court found that making virtual copies of copyrighted content - whole books - was permitted under fair use. In applying the fair use doctrine to your scraping, we recommend first checking if you meet those conditions: - The original content is **transformed** in a meaningful way. For example, a webpage's HTML is transformed into a list of product names and prices. Do not republish original content. - Do **not create a competing product**. Scraping real estate offers for quantitative analysis is most likely ok. Scraping the same to publish them on your own website is most definitely not. - If you can, **do not copy a substantial portion** of the original work. If you don't need certain data, don't scrape it. ### Facts are not copyrightable, but watch out for database protection It stems from the definition of copyright that facts cannot be protected because they are not an original work of an author but merely observations of reality. This was confirmed in [C.B.C. Distribution and Marketing, Inc. v. Major League Baseball Advanced Media, L.P.](https://www.lexisnexis.com/community/casebrief/p/casebrief-c-b-c-distribution-mktg-v-major-league-baseball-advanced-l-p) What this means for scraping is that you mostly don't have to worry about copyright when you're scraping facts like stock prices or weather data in the US. In the EU, things get a little more complicated. Under Directive 96/9/EC on the legal protection of databases (**Database Directive**) even facts can be protected, if their collection, verification or presentation required substantial investment. It means that if someone put a lot of effort into creating a collection of data, you can't just copy it and do whatever you want with it. Luckily, this limitation is overridden by the DSM Directive. So if you're scraping facts in the EU, make sure you meet the conditions [listed above](#data-mining-in-the-european-union). ### Ethical scrapers do not publish original works Even though there are multiple ways to permissible scraping in the EU or the US, we would like to stress that the **most important** factor of all is to **respect the original author's work and their business model**. If you do that, there will hardly be any complaint from them. An ethical scraper does not re-publish or sell original works for its own profit. That's piracy, not scraping. ## Terms of Use and scraping Can websites contractually limit scraping in their terms of use? Yes, they can. This may change in the future, but nothing currently prevents the website owner from adding provisions that ban scraping or automated access. But the real question is: Are those provisions enforceable? The legal theory behind contract enforceability is rather complex, but when talking about web scraping, the number one thing to check is the way how the contract was created. ### Browsewrap agreements Browsewrap agreement is a term used to describe contracts that were concluded simply by visiting a website. The worst kinds of terms and conditions may be hidden in a footer or buried deep in dropdown menus. Luckily, legal theory generally does not accept agreements of this type as valid, because it's unlikely that the user even read the agreement and therefore could not agree with its terms. The key component is the presentation of the agreement to the user. If the website uses a pop-up window to show the agreement, or positions the link to the agreement in prominent places, even a browsewrap agreement could be enforceable. The related case law is nicely [summarized on Wikipedia](https://en.wikipedia.org/wiki/Browse_wrap). ![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/nnk32wbmwiutb8cq7hdw.png) _Apify's terms of use are browsewrap for visitors because they're in our footer_ ### Clickwrap agreements Clickwrap agreements, on the other hand, require an action by the user. Those terms will not be concluded simply by browsing a website, but by clicking a button or ticking a checkbox. This type of agreement is extremely common in online stores and in sign-up forms where the user needs to tick a checkbox before proceeding, or where the "Next" button has a note that says "By continuing you agree to our Terms and Conditions". Clickwrap agreements are perfectly fine and fair contracts and the courts will readily enforce them. As evidenced in the [Ryanair v PR Aviation](https://curia.europa.eu/juris/document/document.jsf?text=&docid=161388&pageIndex=0&doclang=EN&mode=req&dir=&occ=first&part=1&cid=340454) case.text=&docid=161388&pageIndex=0&doclang=EN&mode=req&dir=&occ=first&part=1&cid=340454) case. ![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/eznb1d2ud71dd7byoy83.png) _ Apify's terms of use change to clickwrap as soon as a visitor decides to sign up_ ### DSM Directive and Terms of Use Scrapers in the EU will have a slightly easier time now thanks to the DSM Directive. [As we mentioned above](#data-mining-in-the-european-union), data mining is allowed under certain conditions and if the website owner wants to opt-out of scraping, they need to do that in a machine-readable format. This brings added security to web scrapers, because they don't need their legal department to find and review complex terms and conditions of the website. Their scrapers will do that automatically. ### Simple framework to evaluate Terms of Use when scraping Even though the theory and case law might seem complex, in reality, it's quite easy to determine whether a website can successfully prevent scraping by its Terms of Use. When creating the scraper for a given website, pay special attention to the steps the robot takes through the website. Does it at any point need to click a button that refers to the website's terms? Or does it need to close a modal with the terms to keep going? Is it performing a sign-up to some service? If the robot needs to perform a step that would bind a human to the website's terms, then it's very likely the terms were accepted lawfully and were binding. On the other hand, if throughout the whole scraping flow you have not seen a single mention of the terms and conditions anywhere, they are probably buried somewhere deep and it's probably not your job to go looking for them. If the website owners want the terms to be binding, they should display them prominently. It's only fair. Still, you should let your lawyers decide if you have any doubts. This is a quote from the [earlier mentioned](#publicly-available-personal-data) HiQ v LinkedIn preliminary injunction ruling. We feel it is a great guideline on how unilateral bans on scraping by the website owners should be approached: > [...] on balance, the public interest favors hiQ’s position. We agree with the district court that giving companies like LinkedIn free rein to decide, on any basis, who can collect and use data — data that the companies do not own, that they otherwise make publicly available to viewers, and that the companies themselves collect and use — risks the possible creation of information monopolies that would disserve the public interest. ## CFAA and criminal liability in the US The final issue web scrapers face only in the US. It is the extremely common claim that web scraping violates the Computer Fraud and Abuse Act - a [controversial](https://www.cnet.com/news/from-wargames-to-aaron-swartz-how-u-s-anti-hacking-law-went-astray/) anti-hacking law enacted in 1986 (yes, that's before the modern Internet even existed). Under CFAA, accessing a computer system without authorization is a criminal offense. And courts have been arguing what "without authorization" means ever since. The US Supreme Court has upheld a narrow interpretation of the law. In [Van Buren v United States](https://www.natlawreview.com/article/supreme-court-ends-long-running-circuit-split-over-cfaa-exceeds-authorized-access) the Supreme Court held that *"the CFAA’s “exceeds authorized access” provision covers those who obtain information from computer networks or databases to which their computer access does not extend and does not cover those who, like Van Buren, have improper motives for obtaining information that is otherwise available to them."* If we try to extrapolate this ruling to web scraping, we might want to say that "scraping publicly available data is okay". The reality is that the Supreme Court did not explicitly say so and left it to the Ninth Circuit's judges to update their HiQ v LinkedIn ruling in light of the Van Buren case. ## Update - latest news in 2022 On April 18, 2022, the Ninth Circuit yet again confirmed that scraping publicly available data is not capable of violating the CFAA. The Ninth Circuit built upon the case of Van Buren, where the US Supreme Court used the “gates-up-or-down inquiry” (i.e. if authorization is required and has been given, the gates are up; if authorization is required and has not been given, the gates are down) for access to a protected computer. In the newest HiQ v LinkedIn judgment the Ninth Circuit pointed out that a defining feature of public websites is their lack of limitations on access; therefore using the gate analogy - there were no gates to lift or lower in the first place. In other words, where there is no authorization required in the first place, there is nothing to withdraw from later. The CFAA concept of “without authorization” simply does not apply to public websites. ## Conclusion So, is web scraping legal or not? It's a complex problem, but we firmly believe that it is and we hope this short and daringly simplified legal analysis convinced you as well. We also believe that web scraping has a great future ahead. We can see a slow but steady paradigm shift in the acceptance of scraping as a useful and ethical tool for gathering information and even creating new information on the internet. In the end, it's nothing more than [automation of work](https://www.eff.org/deeplinks/2018/04/scraping-just-automated-access-and-everyone-does-it) normally done by humans. Web scraping just makes the process faster and more reliable. Best of all, it allows people to focus on more important matters. Apify helps [rescue trafficked children](https://apify.com/success-stories/fighting-child-traffickers-with-technology), find [lost dogs](https://apify.com/success-stories/the-lost-dog-app) and even [restore forests](https://apify.com/success-stories/helping-the-planet-with-data) with web scraping so it can't be all bad, can it? 🙂 ## Further reading If you still haven't had enough, here's a list of a few forward-looking texts that explain the topics we discussed in far more detail than we ever could in this article. - [Making Room For Big Data: Web Scraping and an Affirmative Right to Access Publicly Available Information Online by **Amber Zamora**](https://digitalcommons.pepperdine.edu/cgi/viewcontent.cgi?article=1194&context=jbel) - [GitHub Copilot is not infringing your copyright by **Julia Reda**](https://juliareda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/) - [HiQ v LinkedIn disctrict court judgement](https://ia600100.us.archive.org/29/items/gov.uscourts.cand.312704/gov.uscourts.cand.312704.63.0.pdf) - [HiQ v LinkedIn appellate court judgement](https://cases.justia.com/federal/appellate-courts/ca9/17-16783/17-16783-2019-09-09.pdf?ts=1568048483) - [HiQ v LinkedIn United States Court of Appeals for the Ninth Circuit affirmation of district court judgement](https://cdn.ca9.uscourts.gov/datastore/opinions/2022/04/18/17-16783.pdf)

ariansohrabi

Is web scraping legal?

Join Our Newsletter. No Spam, Only the good stuff.