What exactly does &quot;Copyright &#169; [year] [company]&quot; on a website entail? Almost every website has some variation of "Copyright © [year] [company]" at the bottom. Sometimes they also add "All rights reserved". What exactly do those terms entail? My biggest concern is this: by writing that, is the company claiming to own everything on the website, even potentially copyrighted user-submitted material?
The notice has a lot to do with legacy requirements in the United States to claim the copyright to a work. Up until 1989, the copyright notice was required. Today, the statements are mainly maintained to protect against "innocent infringement" which might reduce what a content owner can get in court. What exactly do those terms entail? That the owner stated owns all rights and you may do nothing with the content. My biggest concern is this: by writing that, is the company claiming to own everything on the website, even potentially copyrighted user-submitted material? That's exactly what they are doing. Depending on the terms of the specific site, content contributors generally either assign copyright to the site owner or license the content in a way that allows the site owner to do exactly what they want with it. Site creators with the smarts or money to do it right/get someone to do it right usually state something like: Copyright [Site Owner] and contributors. Other sites (like this one) state specifically what they hold the copyright to: site design / logo © 2015 Stack Exchange Inc THIS IS NOT LEGAL ADVICE. CONSULT AN ATTORNEY REGARDING YOUR SPECIFIC SITUATION.
Think of a website that has gives no option for the users to delete what they have posted -but still the users can delete their account completely. That's easy - this is exactly how all StackExchange sites (including this one) work :-). See for example: How does deleting work? on meta.SE. Is it against the right to erasure mentioned here as a part of GDPR? No, it is not (otherwise StackExchange would be in rather big trouble). The "right to be forgotten" is subject to limitations. Most importantly, it only applies to personal data. Personal data is defined as (GDPR, art.4): any information relating to an identified or identifiable natural person (‘data subject’) If what you posted contains no personal information about you, it is not "relating to" you. The details are complicated (as usual, see e.g. The GDPR: What exactly is personal data?), but "personal data" is things about you (your name, your address, your sexual history, maybe even your IP address). On the other hand, if someone asks how to solve a programming problem, and you write an answer explaining what API to call, that answer is not personal data. In addition to that, even personal data may be retained if the data controller has a need to retain that information. This is also covered in article 4. For example, the controller may retain information "for the establishment, exercise or defence of legal claims" - otherwise you could buy something online without paying, and then ask the seller to forget about your purchases so they cannot collect the outstanding payment. So, in summary: A website will need to allow users to delete or hide personal data that they posted - such as their user profile information, or personal information in their posts. That does not mean they are allowed to delete entire posts - it is enough if personal information is redacted or anonymized. The website may be allowed to retain that information (hidden) if they can show legitimate interest - for example billing information, or posts that are the subject of a lawsuit. The StackExchange network, for example, covers this by allowing users to: disassociate posts from their account delete their account entirely (thus effectively disassociating all posts from personal information) asking a moderator for redaction of personal data
You probably own the copyright, since this wasn't an explicit part of your job. However, there may be other legal reasons which preclude you from using them anyway; copyright isn't all there is. Since you are in the middle of an active dispute, you should consult an actual lawyer (which I am certainly not) for legal advice.
I'm not a lawyer, but under the law as it's written, I see two problems: 17 USC 121 allows "authorized entities" to make and publish accessible copies of works. An "authorized entity" is defined as a nonprofit organization or a governmental agency that has a primary mission to provide specialized services relating to training, education, or adaptive reading or information access needs of blind or other persons with disabilities. So if you, as a private citizen, decide to do this, it could conceivably be copyright infringement. You might have to set up some kind of non-profit organization to make it legal. It's also OK (I think) if you make such copies for your own personal use, so long as you don't redistribute them. So far as I can tell, nothing under 17 USC 121 requires the original publisher to provide an "authorized entity" with a copy in any particular format (PDF, paper, or otherwise) for making accessible copies. Basically, the law seems to have envisioned organizations of sighted people purchasing paper copies, transcribing them, and republishing them; not blind individuals doing electronic transcription for themselves. It might still be worth contacting Hal Leonard and asking what they can do for you, but unfortunately it doesn't look like the law requires them to do anything for you. As Nij points out in the comments, this really seems to be a question about the company's policy, rather than the law.
The reason is 17 USC 106: the owner of copyright under this title has the exclusive rights to do and to authorize any of the following... (2) to prepare derivative works based upon the copyrighted work The original picture is the underlying protected work. The ASCII reproduction is a derivative work. If you get permission to make the derivative work, it is okay. Otherwise, it is copyright infringement. There is an escape clause, "fair use", which amounts to taking a chance that you won't be sued and then arguing that you didn't do them any prohibited harm. If you make any money off of the game, you have a major strike against you. I suggest reading the fair use FAQ; basically, it is really hard to know how a fair use defense will fare, but based on prior cases, I'd say it's infringement, not fair use.
All computer programs are not just copyrightable, they are protected by copyright as soon as they are put into fixed form (for example, as soon as I type it on my computer which will save it as a file on a disk). The copyright owner doesn't have to take any actions whatsoever to have a computer program protected by copyright. It’s not just computer programs, even many fonts are copyrighted because they are essentially computer programs. BTW. What I just wrote is also protected by copyright. There are some licenses involved that I agreed to when I submitted it to this website, and which allow the website to publish and you to read this text, but I'm the copyright holder. PS. There is a comment saying “computer programs are not literary works and therefore not copyrightable”. That may have been true or arguable in the 1980’s. It’s not true now. PS. No, stack exchange doesn’t own the copyright to my post, I do. Unless I was an employee of the company and posted on their behalf. Stack exchange needs and has a license to publish this post.
You are clearly seeking legal advice. Answers on this site come from anonymous people on the internet and are not legal advice. You should not act based on information from this site. I am unaware of any lawsuit where one would be sued for merely storing and reading HTML for personal use. Downloading a webpage is probably not a copyright violation. Most things you create, including HTML source code, are protected by copyright and copyright includes the exclusive right to choose who can read what you created. I couldn't find any actual reference to this but I would hazard a guess that displaying an HTML webpage online is implicitly allowing others to read that code. I believe this guess is correct because all modern web browsers have the capability to view source that nobody considers illegal and browsers also include the capability to save webpages to disk. These browsers are made by companies with large legal departments, I doubt Internet Explorer would include this function if using it was a copyright violation. Here begins speculation: However, your expanded question says that not only you wish to read the HTML code but you also wish to process it, extract information from it and use what you learn this way. This could, I think, be prevented by the copyright holder. Still, what you are describing is commonly done in the world. Services such as Google, Bing or the Wayback Machine go far beyond what you are doing. In theory, I can see this as being a copyright violation but again, the fact that these big companies - without any kind of contract with the website owners - keep doing it is big evidence in favor of legality of storing webpages. You should be careful about how you use the stored data, though. For example, computer programs often have a stipulation in EULA that prevents you from reverse engineering the code. I could see that the use of some websites could be protected in such manner. Further (not authoritative) internet pages on this topic: https://stackoverflow.com/q/22819287/1580088 https://answers.yahoo.com/question/index?qid=20120621055815AAvJPvN
I'm curious to know, because Google allowed their ownership of the domain to expire, why do they still have the rights to it even when it was bought by another individual. You're making an incorrect assumption here. The domain was never allowed to expire. An error in Google's domain registration interface allowed him to make an order for the domain. The domain was never actually purchased, but the act of ordering the domain gave Mr. Ved access to the domain in Google's Webmaster Tools. As the domain was never actually available for purchase, Mr. Ved had no rights to it. (The domain is not even registered through Google's domain registration interface; it's under a completely separate company, MarkMonitor, that specializes in high-value domains.)