Is it legal (in USA) to charge for scraped (public) datasets? I recently came across ScrapeHero which publicly sells scraped datasets of various kinds. Store locations, product lists etc. Example: IKEA USA locations. Is it fully OK in USA to simply state that The data on this data store is gathered from one or more public sources.We do not claim ownership or copyrights for the data, we only charge for the effort required to gather, clean and structure the data&quot;. I don't doubt that the information is public, but still it's money being made on other people's information. And nowhere is the source listed. As per example of IKEA, the store locations are available in exactly same format by a simple URL. Note: I am not from USA (so do not have knowledge in details of the legality of this) - and I have no affiliation to said online store. Just wondering.
united-states Facts are not copyrightable. Assuming Scrapehero collected these facts in a legal manner and assuming the source of these facts does not contain copyrighted (protected) material, then selling such a collection may be legal. Of particular relevance is Feist Publications, Inc., v. Rural Telephone Service Co.. Here, Feist Publications copied Rural's phone directory into Feist's own phone directory. The supreme court found that Rural's phone directory was not copyrightable and thus not protected. Of course, this cuts both ways. Assuming Scrapehero did not inject creativity into the data, nothing stops a recipient of such data from distributing it themselves. In practice, this probably isn't a concern for Scrapehero. This answer is US-specific. Some countries recognize Database Rights, which may prevent such activity.
As written, your question seems to ask for legal advice in a specific case. That would be off-topic. If you are asking strictly as a hypothetical: In germany, there is supposed to be the Bestellerprinzip for services of a real state agent (whoever retains the agent pays the fees). This was clarified in the Gesetz zur Regelung der Wohnungsvermittlung as changed in 2015. Landlords and real estate agents are frequently trying to get around it, but getting the legal construction of the contracts wrong would mean a substantial fine.
You would first have to find out if publishing a book was &quot;for commercial purposes&quot;. I can write a book and publish it as a hobby. Next you check if there is any copyright infringement. It doesn't sound like there is. Using your website as a tool to create these diagrams doesn't give you copyright unless the result contains your own copyrighted work. So at best there is a violation of your terms and conditions for your website. You can sue about that, but might have to specify damages. If you allow commercial use say for a fee of $1,000, that would give you grounds to claim damages. Or if someone used your website so excessively that it costs you money, that would be damages.
Probably not. There are potential problems on the levels of copyright, data protection, and the Youtube terms of service. You should assume that comments are typically covered by copyright. You do not have a license to these comments, only YouTube does. Therefore, YouTube can show the comments but you can't copy them – just like YouTube can stream your videos but others can't download them and host them on their own websites. To cover the copyright angle, you'd either need to obtain a license from the commenters, or get a sub-license from YouTube, or identify a suitable copyright exception. The comments are personal data within the meaning of the GDPR, so that your processing of these comments (including mere storage) would be subject to GDPR as well. You need a legal basis for processing personal data. Which legal basis is suitable would depend on the purpose of processing, and on your relationship with the commenters. Potentially applicable legal bases in this context: you have a contract with the commenters that requires you to show the comments on your website. For example, I could see such a contract if there were a “featured comment” perk for a Patreon subscription. But this is not going to fly with random commenters. you have a legitimate interest (LI) that allows the processing. A LI requires that you conduct a balancing test where you weigh this interest against the commenter's rights. This is very specific to the purposes for which you want to show the comments. However, a LI will generally only apply if you have an existing relationship with the commenters, making it possible for them to expect that this processing will occur – unlikely if you'll be scraping comments from YouTube. you have obtained consent from the data subject. Consent must be specific, informed, freely given, and unambiguous – you can't obtain consent by writing “by commenting under this video you consent to XXX” in the video description. Regardless of legal basis, you would have to inform the commenters under Art 14 GDPR when you scrape their comments from the platform. Finally, consider the platform terms of service. I have not read the YouTube ToS recently, so I don't know what their specific conditions are. But in general, such ToS will not allow you to scrape content from their platform in order to host it somewhere else. The ToS might allow certain actions like embedding a link/iframe to such videos on other sites, without allowing other actions such as copying other user's content to your site.
I spent a few years working in and around the Energy industry - including a stint working at a supplier, I'm no longer there so unfortunately I no longer have access to the email chains I had discussing this with legal. The consensus at the time was that a "traditional" i.e. non-half-hourly (NHH), non-smart meter reading itself was not considered personal data - they are conceptually tied to a metering point (which may or may not be a physical meter), not to an individual and don't represent an individual's energy consumption (the granularity of the reading is insufficient to tell anything about the usage profile) But this information, while all around the implementation of GDPR it was a couple of years back and to be honest it was bugging me that I might be out-of-date on the current practices so I reached out to a former colleague who was the Data Protection Officer at the supplier I worked at to try and get a more up-to-date take. He's since moved on but was there until recently so has more experience with the topic since GDPR actually went into effect. I asked him whether a) estimated opening reads were considered "personal data" and b) what would happen with a request to change one under article 16 and he had this to say, I've translated industry-speak in square brackets: a) for NHH ["Non Half Hourly" - meters that are read ad-hoc, essentially all non-smart domestic meters will be this] an estimated reading wasn't personal data automatically until the billing flag was set in CRM and those would be the only ones we'd include on an SAR [Subject Access Request], any others are internal data not personal. HH ["Half Hourly" - meters for higher consumption users, typically larger business premises are billed on increments for each half hour so have readings for each] and remote [smart meter] readings are always personal for domestic and microb [micro-businesses are a certain class of non-domestic energy customer see condition 7A] b) erm no! we'd only change it if the value in CRM didn't match the value in the D10 [industry Data Flow used to transmit meter reads] for some reason. if they match it's an accurate representation of what we estimate the reading to be so it's just a vanilla billing dispute not a data protection issue so i'd have punted it to [name of person who was head of metering] From that it would sound as though the estimated read would count as personal data - so long as it's being used for billing purposes, but that doesn't mean they have to accept your read in it's stead. It all comes down to accuracy - GDPR requires that personal data be "accurate" but provides no definition as to what "accurate" means (which makes sense since you can't give a one-size-fits-all answer that isn't an encyclopedia) and while The Electricity Directive 2019 confirms the need for accuracy in billing again it doesn't tell us what that means. The implementation is left to member state regulators. In the UK this is OFGEM and all opening meter readings are validated through third parties (so you don't end up with the foxes guarding the hen house!) and are calculated using the following formula: Last validated reading for the meter point &lt;= supplied reading &lt;= (expected daily usage x number of days since last validated reading x 2.5) where "expected daily usage" is obtained from a database maintained by the regulator - it's calculated off meter type, property type, property use, previous validated reads etc. So if the customer provides a reading that falls outside the above the supplier can (and in practice invariably will) reject it as being inaccurate. Now this is why the when a meter reading is provided matters - reads you provide are always assumed to be the read on the day you give them. With opening reads there's some leeway, I can't remember the official rule on how much but usually they give you up to the next estimated read is generated but more on that later. Now if the reading you're trying to submit is a "now" reading and it's failed the validation criteria and you aren't happy with the rejection you can force the issue by demanding the supplier come read the meter. You don't say how long has passed since the opening read - more than the week from what you've said so presumably at least a month (guessing you've had at least your first bill). Now if they are saying the opening read was X (based on the estimated usage) and you're it should have been X + Y and the current reading is X + Y + Z you want to pay your actual usage Z not Y + Z. What you need to do is dispute the opening read, which you're entitled to do, arguably GDPR of Article 16 gives you this right, but on it's own it's a weak argument. There's established means by which an estimated read's "accuracy" is determined and assuming they followed that they're going to just tell you that as far as they are concerned it is accurate. Any challenge to that accuracy is going to have to be done within the legal/regulatory frameworks for assessing accuracy, that's what they're there for, if they won't accept your reading escalate that to the regulator - and as soon as you can. OFGEM for example allow disputing of opening reads for 12 months - it doesn't have to be resolved within that 12 months it just has to be lodged with them within that time. If you try and use the GDPR angle to pursue this IMHO it's going to muddy the waters and not help you get what you need - pursue this on billing accuracy.
Is that extortion? false advertising? or in any way illegal? Not at all. The owner of the site is simply exercising his right as outlined in the terms and conditions from when the user signed up. And giving users an option for continued use of the site (that is, for him not to exercise a right of which they were always aware) does not constitute extortion.
If it was illegal to make the entire copy, it is illegal to copy half the file. See also, e.g., Basic Books v. Kinko's Graphics Corp., 758 F. Supp. 1522 (S.D.N.Y. 1991) In response to the question of whether moving it to someone else's servers makes a difference: it is the act of copying, not the possession of the copy, that is the violation of copyright law. As for the copy a service assists someone to make, contributory liability would be the issue. You don't need to be the person making the copies to be contributing to the infringement--material contribution to the copying process and knowledge of infringement run a serious risk of creating contributory liability. If seriously considering such a service as a business model someone would need to consult a copyright expert with technical knowledge or pay counsel with technical knowledge for a good bit of time to do some research. There are major civil and criminal consequences if the industry or the government decides to go after a service doing this, so legal expenses would be a significant and important cost of doing business that would significantly increase barriers to entry. In addition, the service would likely be in violation of its agreement with storage vendors, who would want to minimize their legal exposure and might well discontinue the service when they learned what it was doing.
a few quick notes that come to mind. As the commenters point out: DSGVO is indeed the German equivalent name to the GDPR (English term) "Imprint" isn't a privacy related topic that much, as such it's not really changed by the upcoming GDPR The GDPR changes many things, but the requirement for up front information isn't one of them - so it would've already been a rule to follow Sometimes the question who is responsible for privacy information might not be that easy to decide when you're on platforms. I take this situation as being pretty clear though. You are basically given a blank slate, you can do with that page whatever you want, and the visitor has no clue whatsoever that it might be hosted by Github. In addition to this, Github would be classified as a data processor (providing the tool) and you as the data controller who is in charge of practically everything except for the provision of the page. I hope this helps. Btw. it's not that hard anymore to write a privacy policy these days.