6

Lots of bits and pieces of information and chaotic data spread across the web and it does cost an arm and a leg to gather them together to form something larger and consistent that would prove to be much more useful.

Is it legally viable to scrape these factual data / information from different websites, compile and re-organize them as databases / data sets that will then be licensed under a proprietary license?

Thus far after some research, I find factual data can't be copyrighted, but the particular compilation / structure of data can. Does this mean I can do whatever with the scraped factual data as long as I have my own unique data organization / compilation / structure?

For example, I want to make a business information database off hundreds of different websites and then radically re-organize / re-structure / re-index these different data sets into one database that is better than any of the sources. Can I proprietorially license this particular database I made?

I know I can never own the data as they are straight facts. Right? But can I OWN the particular data organization and legally profit from it?

We are operating in US, but the data could be from websites on other continents.

  • Comments are not for extended discussion; this conversation has been moved to chat. – Dale M Sep 30 '19 at 0:43
11
+100

From your question(s), as well as your various comments, I understand you to have two general inquiries:

1. Is there any infringement of copyright laws if you use things like the titles of books, games, apps, names, address (and any other number of things) which you will then put into datasets that will be licensed for proprietary commercial purposes?

You may freely put titles, names of people, places or things into datasets without fear that you are infringing on copyright or any other laws. That is clear.

Copyright law does not protect names, titles, short phrases or expressions. Even if a name, title, or short phrase is novel or distinctive it cannot be protected by copyright. So, there is no point in discussing the doctrine of fair use in this context, because Fair Use is a defense, or a legal safe harbor that is merely an exception to copyright infringement allowing people to use a copyrighted works under specific circumstances.

As I understand your intended endeavor, you will not be infringing on any copyrights to the extent that you are merely using factual data, like names of copyrighted things for the purpose of creating a dataset or an application to help access it. This is why I say you need not concern yourself with the test for Fair Use with regard to this issue.

The Copyright Office states clearly, despite what people may think, that there are no exclusive rights in brief combinations of words such as:

• Names of products or services • Names of businesses, organizations, or groups (including the names of performing groups) • Pseudonyms of individuals (including pen or stage names) • Titles of works • Catchwords, catchphrases, mottoes, slogans, or short advertising expressions • Listings of ingredients, as in recipes, labels, or formulas. When a recipe or formula is accompanied by an explanation or directions, the text directions may be copyrightable, but the recipe or formula itself remains uncopyrightable.

Hence, these things are not registrable under a copyright.

While something may be potentially attached to or included in copyrighted material, is not in and of itself subject to the protections of these laws. If it (whatever it is) cannot be registered for a copyright, it is not copyrightable. Because copyright registration/notices have been optional since 1989, when the U.S. attached itself to the Berne Convention, whereby copyright protection is automatic as soon as a work is “fixed in a tangible medium of expression” (written down, recorded, painted, etc.) it’s protected. No notice is required. Registration only becomes required for litigation or enforcement purposes. But this is really extraneous to your inquiry anyway, as far as it applies to the actual data. When you get into copying whole databases for your purpose, that analysis is different.

2. You want to "scrub" the internet for information that you intend to put into your proprietary datasets and use for commercial purposes, some or most of which is already in a database or some organized form, and you want to know if there is some sort of copyright or duty owned to the person who originally databased the materials?

Since ideas, procedures, principles, discoveries, and devices are all specifically excluded from copyright protection, if you want to compile this type of information from the internet for the purpose of creating datasets, or searchable databases, this is permissible.

That said, there are protections for existing databases under copyright law, provided under the concept of a "compilation copyright". A compilation copyright protects the collection and creative assembling of data or other materials. Compilation copyrights protect the collection and assembling of data or other materials, such that databases are generally protected by copyright law as compilations.

Under the Copyright Act, a compilation is defined as a "collection and assembling of preexisting materials or of data that are selected in such a way that the resulting work as a whole constitutes an original work of authorship." 17. U.S.C. § 101.

The preexisting materials or data may be protected by copyright since the selections of materials and the form they take in an existing database may be original enough to be subject to a copyright. However, the data itself is merely information and is not protectable.

The Copyright Act specifically states that the copyright in a compilation extends only to the compilation itself, and not to the underlying materials or data. 17 U.S.C. § 103(b). As a result, "compilation copyrights" can't be used to place protection upon those things that are otherwise not protectable.

In the case of Feist Publications, Inc. v. Rural Telephone Service Company, Inc., the U.S. Supreme Court ruled that a compilation work such as a database must contain a minimum level of creativity in order to be protectable under the Copyright Act. Feist makes clear that even a copyright protected database does not hold the right to prevent an individual from extracting factual data from the database (so long as you're not copying the entire database as a whole). If you take an already compiled and copyrighted dataset in its entirety, you must obtain a license for its use. However, if you are merely amassing great amounts of data to then put into your own dataset, that you are free to do.

The big issue will be (and you seem to realize this) where you will amass this data from. Some websites have specific licenses in place that say you cannot use or rework their content. However, many times these websites simply throw these license requirements out there for users to see, despite the fact that they may not be (and some would argue) are not enforceable.

The courts have heard arguments that "contracts" (the end-user licenses) that protect databases and information on websites is beyond the protection available through copyright law should be "preempted" by the Copyright Act itself.

The preemption argument goes like this: Federal law controlling something that is subject to interstate commerce or use, should be controlled by the federal laws. So,since the federal government has enacted the Copyright Act to govern any protections to any original works, states should be (arguably are) prohibited from having contradictory laws.

Because of the ability of a federal statute to preempt state law, and the fact that the Copyright Act at 17 U.S.C. § 301 sets forth specific preemptions, no state may create rights that are equivalent to any of the exclusive rights provided under the Act.

It is this concept of preemption that prevents copyright protection from varying depending upon the state where a work of authorship is created. Arguably, the same is true for the internet, and supposed contractual relationship created through licenses that dictates how non-copyrightable material may be used.

In the case of ProCD, Incorporated v. Matthew Zeidenberg and Silken Mountain Web Services, Inc. the court examined whether an end-user of a CD ROM phone database was subject to the license, when they extracted a large portion of the database and made it available over the Internet.

The database was almost the same as the type of data in the Feist case-The lower court rejected all copyright claims and found that the shrinkwrap license that controlled the end user's right to use the data was both unenforceable (as a shrink wrap license) and preempted by the Copyright Act. As a result, there was no relief available to the creator of the phone database and the end-user was free to extract the data and use it as he saw fit. However, on appeal this decision was reversed (7th circuit).

The appellate court did acknowledge that the database (on the CD) was not original enough to be protected by copyright (finding no copyright infringement by the end-user); However, they did find the end-user was breach of contract, since the shrink-wrap license prohibited the end-user's conduct.

What this tells us is that these licenses (on websites) may or may not be enforceable. While the 7th Circuit found a contract right pursuant to the license, despite the preemption argument, another appellate court that is more liberal may find otherwise. Also, this was a disk, not the internet, which is the "wild west" of information, largely unregulated and unlitigated as it pertains to the legality and enforceability of (some) regulations that do exist. License agreements for site use on the internet are everywhere. If you take a database from some site that has a license saying you cannot take their work and add to it, or whatever, and you do add it to other databases that are not licensed and then make your own dataset - chances are you are NOT going to be infringing on anyone's copyright. That said, you may be in breach of contract (the license) if they find out about it, and sue you (using it doesn't put you in breach; only getting sued and having a court determine you're in breach puts you in breach. It may be a distinction worth contemplation, but that is up to you). The safest, bet would be to get a license from them to rework the materials. If the material is generic enough, and will be changed enough, that you are creating your own new (copyrightable) work - I'm not sure how they would know you "scrubbed the data in contravention of their license agreement ( I have NO CLUE if there is coding or metadata attached to it such that it's identifiable in that way. I have not tech background and do not endorse taking what's not yours). But if they can and do know, they could cause problems for you.

Lastly, I will just say that the internet is littered with sites that claim copyrights, or impose unenforceable licenses on material that is ripe for public use. Just because it says it's theirs does not make it so. The inverse is also true. Just because a site does not claim copyright to something, does not mean it is in the public domain.

I would recommend either sticking to public domain/use sites for your scrubbing endeavors, or seeking permissions from the sites who impose licensing requirements. Short of that, I would recommend (as I already have) seeking an formal legal opinion to say that you are not imposing on anyone's copyrights (this could only be done once you showed an attorney every place you took material from, as well as what the material is), and that the licenses from sites with generalized information that may try to limit use, are unenforceable. I would do this before you invest a lot of time or money into something that is largely based on the accumulation of other peoples work product.

I wish there was an answer certain, but there just isn't without seeing everything in the end.

| improve this answer | |
  • Always worth reading a @gracey209 answer, if for nothing more than the little pearls, like: "The internet is littered with sites that claim copyrights, or impose unenforceable licenses on material that is ripe for public use. Just because it says it's theirs does not make it so." – feetwet Sep 10 '15 at 20:40
  • Thank you so much for such an in-depth answer! Seems it'll take a few days for me to digest it all. – datasn.io Sep 11 '15 at 0:52
  • @kavoir, you are most welcomed. Thanks for the bounty! Best of luck. Let me know and we can chat if you have any follow-up questions after you've considered everything. – gracey209 Sep 11 '15 at 1:04
6

It's actually impossible to answer w/out knowing where you're intending to do this. In the US, collection criteria & presentation might make it copyrightable. In some other places (e.g., the UK & Europe) databases are protected by sui generis database rights.

You'd want to track when & where you got each bit of data, and what licenses it was provided under, to reduce the chances of a protracted lawsuit. (When is important, as websites may change their license terms, so you'll want to grab a snapshot of the license terms on each day that you scraped them.)

Also note that some "facts" are written as sentences or presented as graphs – in the US, those are copyrightable, as are photographs establishing facts. Take the case of TV listings: The time a show is scheduled on a given channel on is a fact and not copyrightable in the US, but the summary of the episode is a creative work, and copyrightable. Creative filtering (selection) or presentation may be copyrightable; that issue was left open in Feist v. Rural.

| improve this answer | |
  • I was going to write almost exactly this in a comment and then ask the question be narrowed with actual facts pertaining to all these things. – gracey209 Sep 6 '15 at 14:15
1

Short Answer

You don't need to license data to your users to generate revenue if you adopt any of the following business models.

  • Software as a Service (SaaS)

  • Pay-per-use Web Application

  • Data API

Explanation

It sounds like you're describing either one of the above business models in your question. In all cases, the value of your reorganized datasets will be in the way your app or service allows the user to interact with it to do useful things. So I think you might not really want or need to license the datasets at all — just charge for the service and the use of your software, app or API.

Implementing a Data API Model

If you prefer to just focus on the data and let your users build their own apps, then building a data API might be your best option. With this product, you would allow your users send RESTful HTTP requests to your data service.

The service would respond (most likely) with a JSON-P callback to supply the data. You would need to thoroughly document all the methods available from your API along with example calls in various common languages. (Start with cURL as that is relatively universal.)

In this model, as with the others, you would issue authorization credentials to all your users (this is what they would pay for). Then with each data call, they would supply these credentials which would in turn be verified server-side before sending the response.


Disclaimer: I am not an attorney so don't follow my advice. Consult a real attorney as that is the only way to make sure you stay out of trouble.

| improve this answer | |
  • Thanks. That's more or less what I have in mind but the core value is still the data rather than the application. We will enable our clients / customers to easily build their own applications on our data but at our end, we will focus on just the data part. So what we are directly monetizing is still the data, not the application. Any further idea please? – datasn.io Sep 9 '15 at 9:26
  • @kavoir.com: I updated my response based on your feedback. You will most likely want to build a data API and license the use of that API. So make sure to read that part of my answer closely. – Alexanne Senger Sep 9 '15 at 21:25
  • Nice technical details. Thank you! You are not an attorney but certainly is a wicked (in a cool way :)) programmer. These are great advice and I will definitely follow them. However, what I'm more worried is the websites I scrape from could sue me for profiting on factual data from their website. It may seem I'm charging API requests but the core value is still the data. If I don't license the data, what should I say when a client asks me what license it is and to what extent that he can use our data? In the end, I'm selling the data, not the subscription or API requests. – datasn.io Sep 10 '15 at 4:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.