Is it legal in the US to update my website copyright automatically? If I release my website in Dec 2015, the copyright date should definitely say "© 2015". Once Jan 1st comes around, if I automatically (with Javascript or some server side code) change it to "© 2016" is that legal? No code has changed, so there is nothing that is really copyright 2016. I tried searching for an answer, but everything I found was about how to change automatically, not if it was OK to do so.
Yes. It is legal to update the copyright automatically. It is also legal to put the wrong year, whether it is 100 years ago, or 100 years in the future. (See 17 USC 406, which explains that an error in the date is only relevant for works published prior to March 1, 1989.) Today, you can put whatever you'd like there, as the copyright notice on a website has very little legal meaning. There are 2 main reasons for this: All content is automatically copyright protected whether you specify the copyright or not. (United States Copyright Office: Copyright Notices: "U.S. law no longer requires the use of a copyright notice") It's common knowledge that it is extremely easy to update a website and its content, so if you ever get into a legal battle where you need to prove which party created something first, the copyright date written on a website will not be considered valid evidence. Other mechanisms will need to be used, such as registered copyright or perhaps even code vaults with a trusted 3rd party. However, by displaying a proper copyright notice, "the court will not give any weight to a defendant’s use of an innocent infringement defense". (Copyright notices) That being said, what should you do? The most popular options are: Don't display a copyright notice at all. Display copyright without a year. Display the current year. Display a range from the first publish year to the current year. Display the year of last content publish. Note that the last option (display the year of the last content publish) is what some copyright experts still recommend today. But IMHO that is an outdated practice and is pointless. If your site has 1000 webpages on it, and you add one more page this year and update the site-wide copyright year along with it, that obviously does not reset the true copyright year of the other 1000 pages. Also, some people believe that a website with a copyright year older than the current year makes the site appear stale, which may hurt the site's reputation. If you feel that your website could fall into that category, then an auto-update or no year at all is probably the best way to go.
It doesn't make a difference if the product is free or commercial use, if it's initiated by a company or an individual. What you are considering would be a &quot;derivative work&quot; and without explicit permission from the copyright holder, it is considered a violation.
Provided you are in one of the 170+ countries signatory to the Berne Convention (the current 10 non-signatories are, exhaustively: Eritrea, Marshall Islands, Nauru, Palau, San Marino, Iran, Iraq, Ethiopia, Somalia, and South Sudan), then copyright comes into existence at the moment a work is fixed in a tangible medium, not when it is published. The initial copyright owner is the author of the work. In cases of employment, the "author" might be the natural person who authored the work, or the corporate person who employed the natural author. To clarify your thinking about registration: copyright registration is a public record of authorship (or copyright ownership). Registration does not create a copyright, but is merely a recording of the copyright that was automatically created at the moment of original authorship. Depending on circumstances and jurisdiction, Alan might have a legitimate claim to copyright on his own work. However, he will be quite hard-pressed to find a convincing theory of law that allows him to publish the unpublished copyrighted work of other people without their permission. This leaves him either to admit defeat -- he cannot possibly own the copyright of his coworkers' code, so he cannot have legally reproduced it -- or else make the baldfaced lie that the code has no other authors other than Alan himself. For your company to disprove such a claim, you may employ sworn testimony of your coworkers, you may employ code analysis to show differing coding styles (suggestive of multiple authors), or you may show code backups or version control history showing the progressive authorship of the work over time by many people. (Sure, a Git history is possible to fake, but a realistic history with feature branches, "whoops, undid the typo in the last commit" messages, etc. would lend significant weight to your company being the original authors.)
It depends on what information you are sharing, how you got it, and what rights the business asserts over the information. For example, if it is content created by the business and they claim copyright protection you can only use it without their permission in accordance with Fair use exceptions. If you obtain the information through some limited/conditional access agreement you would be subject to the terms of that agreement. As always: If you want a legal opinion specific to your use case you need to consult a lawyer in your jurisdiction.
"Public domain" refers to things in principle copyrightable but where protection has lapsed, been repudiated, or is a statutory exception (such as government works). A website is not "in the public domain". The idea that a website is "public property" is (*cough*) mistaken. There are basically two ways in which a web interaction could be illegal. The first regards whether accessing another person's computer is illegally accessing a computer, which is a crime. Authorization essentially comes down to "permission": if the owner permits me to access the computer, I am authorized. Putting stuff out there on a web server is an open-ended grant of permission to look at a web page. That simply means that if I create a web page (with a bunch of links or not), I am granting you permission to interact with my computer to that extent. It does not create permission to hack into a password-protected subdirectory. An ordinary web crawler automates what a clicking human does. Copyright law is also relevant, in that the stuff I put on my webpage is not to be copied without permission. Any webpage access necessarily involves automatic copying from machine to machine: in putting stuff out there for the world to see, I am saying that the world can do that level of automatic copying that arises from normal html-and-click interactions. It does not mean that you can download and do stuff with my copyrighted content (i.e., it is not an abandonment of copyright: I did not put that stuff in the public domain). Putting a web page out there in an unrestricted fashion means that you've given a certain level of permission to "copy" (at least in the automatic server-to-browser viewing sense). I may want to impose conditions on peoples' access to my stuff, so I can impose terms on such material. For instance, I may require users to agree to certain conditions before accessing the CoolStuff subdirectory. Users then have to jump through a minor hoop and agree to those terms. In that case, my permission is conditional, and if you violate the terms of that agreement, I may be able to sue you for copyright infringement. It could then be a violation of my terms of service (TOS) if I say "you may not crawl my website" (in less vague language). A TOS gets its legal power from copyright law, because every webpage interaction involves copying (I assume that technical point is obvious), and copying can only be done with permission. You may technologically overcome my weak click-through technology so that the bot just says "sure whatever" and proceeds to illegally use my web page: I can sue you now for copyright infringement. The robot-specific methods of meta-tags and robots.txt have no legal force. Although there is a way to say "no you may not," which is tailored to automated access, the meaning and enforcement of these devices has not yet reached the law. If my page uses NOFOLLOW and your program doesn't know or care, you (your program) do not (yet) have a duty to understand, detect and respect that tag. Prior registration is also not a legal requirement, and very many pages that are on the master crawl list get there from being linked to by someone else's web page. Again, there is at present no legal requirement of pre-registration (and there is no effective mechanism for verifying that the site owner has registered the site). Archiving and especially re-displaying someone's content is, on the other hand, not legal. It would be plainly copyright infringement if you were to scoop up someone else's webpage and host it. You can analyze their material and somehow associate it with some search terms, and display a link to that page, but you cannot copy and republish their material. You can put very short snippets out there taken from a web page, under the "fair use" doctrine, but you can't wholesale republish a webpage. (It should be noted that the archive.org is an internationally recognized library, and libraries have extra statutory powers to archive).
You can put anything you like in a ToS document, but not everything you might put there will be enforceable. By posting something on the web, you are inviting anyone to read it. In some jurisdictions that may include the right to make and store a personal copy, although not multiple copies or a copy for commercial use. You can taker technical measures to prevent automated access and automated downloads (scraping). There was a case (hiQ Labs, Inc. v. LinkedIn Corp, 938 F.3d 985 (9th Cir. 2019)) in which access restrictions were held binding in a US court, but in that case the site owner had notified the would-be reuser (a competitor) directly. The laws on this sort of thing may differ from country to country, and are not as well-settled as older parts of the law tend to be. The question asks: can I list in my terms of service that all users acknowledge I own their posts ... The only way in which the host could &quot;own&quot; the posts would be if the users transferred copyright to the host, or granted the host an exclusive license. Under US law this would take a written and signed document. Clicking an &quot;I agree&quot; box or button might constitute a valid signature. A statement that &quot;by using this site you agree ...&quot; would pretty clearly not. You might prohibit bots copying from your site and posting duplicates, but to prohibit users re-posting their own messages elsewhere is harder, legally, and leas reasonable in my view. Under US law you could not actually file suit for copyright infringement until you had registered the copyright, but that is not true in many other countries.
In Germany, there is no concept that corresponds directly to public domain. You automatically hold the Urheberrecht (~ copyright) for all creative works that you make, and it can't be given up or transferred (§29 UrhG). The work only enters the Gemeinfreiheit (~public domain) 70 years after your death. You can however license Verwertungsrechte (economic usage rights). When you make creative works in the course of employment (see §43 UrhG), your employer automatically gets the Verwertungsrechte necessary in the context for the work, which is typically an exclusive right (no one else, not even you, can use the work). Your are not in an employment relationship with your school, so it has no rights to your works and cannot prevent you from publishing them on copyright grounds. When you see advice on the internet to check with your school first, that is U.S.-specific advice. Since you're still a minor (7–17), you only have limited capacity to enter contracts or legal transactions (bedingte Geschäftsfähigkeit). While you are able to make transactions involving your own means (e.g. buying something with your pocket money) or make transactions that are only to your benefit (such as accepting a gift), other transactions are schwebend unwirksam (~ pending ratification), until your parents agree. The relevant law is in §107 and §108 BGB. This is a problem with open source licenses. If you publish software under a license, this license is schwebend unwirksam. Someone might start using the software under the license. But then if your parents refuse ratification, the license would be invalid, and everyone would have to stop using your software and destroy any derivative works they made. This is a bit of a problem, especially since open source licenses are otherwise assumed to be irrevocable. So if you want to offer a license (including open source licenses), please give legal certainty to the recipients of the license and ask your parents for their consent first, possibly even in writing. Per §107 BGB, the license you offer with their consent will be valid.
According to CENDI, yes the US government is able to claim copyright on works internationally. The law in question which makes US government works public domain in the US (17 U.S. Code § 105) only does so within the confines of US copyright. Since copyright protection is on a per-country basis, there's no reason that the US government couldn't assert IP rights under foreign copyright law (though I didn't go looking for an example). While the Berne Convention generally requires countries to provide foreign works the same protection as domestic works, I can think of two general reasons why US government works wouldn't fall under copyright protection in some countries: The country simply doesn't apply copyright protection to any government works (don't know how common this is). The country applies the rule of the shorter term. If they do, they aren't required to provide a longer term of protection than the country of origin does (which is nil in this case).