What kind of ownership do I have over articles I wrote? So, a few months ago I was working for a big blog and then I resigned because I didn't want to write any more articles for them. Some of the articles were original and a few were translations by me from other articles. Do I have any claim to ownership if the articles? I had no contract with them governing what I can do with the material I wrote, so would it be possible for me to ask the owner of the blog to take them down? Is there any law on this issue? In case you need to know I live in Greece, and the blog is based in Greece.
There are three questions relevant to this issue: Who owned the copyright in the first place? Was the copyright transferred? If not, was a license given to the site to use the content? In general, under most countries' laws, the person who creates an original work owns the copyright. The person with the copyright has the right to copy and distribute the work, and the right to prevent others from doing so. In some cases, such as where a work is created as a "work for hire" by certain employees under certain circumstances, the initial copyright is held by a third party. You will need a lawyer familiar with your jurisdiction and your circumstances to determine if this is the case. Finally, even if you own the copyright, you can license others to use your content. This may be in an express written document, or it may be an implied license--implied, for instance, by the act of posting it on their blog. The existence and scope of such a license is, again, something that will have to be determined based on your country's specific laws and your specific situation. The bottom line is: if you submitted articles to that blog, you can't complain that they posted them. Depending on the license in effect, you might be able to get them taken down, or you might not. You need a lawyer, not the internet, to tell you what your rights are in this very specific case.
Can a city request deletion of all personal data that uses a certain domain for logins? Well, they can, but they have no legal backing to make it happen. Their chances of succeeding are about as good as me requesting a Ferrari, a Yacht and a Mansion. I can make that request. People will laugh. I will not get it. I'm a little worried that I shouldn't allow certain domains to be used as logins in the first place, especially ones that might be school related You have no way to know who owns what email address. And it's none of your business. Your only interest should be in whether the address is owned by the person that is creating the account. You probably already do that by sending a confirmation link to the email address when people sign up. I'd like to have some idea for future reference if there's any case where the GDPR would require me to comply with such a request The only way you have to comply with such a request is if the owner can prove their identity. As far as I understood, the &quot;Finnish city&quot; was three degrees away from that. They could not provide any proof they are who they said they are, they could not provide a finite list of accounts they claimed to own and they could not even provide proof they own those accounts. They literally just wrote an email with zero legal meaning. I want to figure out the right way to reply to emails like this one The correct way to handle this is have a feature on your website where the account owner can delete their own account. GDPR compliant. Then you make a text template explaining how to use that feature and reply with that template to every request, no matter how stupid (like this case) they are. If they cannot identify themselves to you by proving they have access to their &quot;own&quot; email, they have no business wasting your time. Legally, they could provide you with a different method of identification. In case of a Finnish school, that would probably need to be power of attorney from all children's legal guardians and a specific way to identify the accounts that is consistent with the data given (for example if they entered their full name and address on your website). You would probably in your rights to demand a certified translation if it's all in Finnish. Apart from the fact that you as a private US citizen have no real means to check the validity of all that paperwork, personally, if I saw hundreds of pages of certified translated paperwork, I would probably just comply. Not sure it it were actually enough, but it certainly gets an A+ for effort to delete data from a private website. But a real lawyer might give better advice with a real case on their hands. Is deleting the data actually more of a legal liability than not deleting it in some cases? (People shouldn't be able to delete other people's accounts.) Indeed. You should not delete people's data because a random punk on the internet sent you an email. You need to identify who the request is from and if they are allowed to make such a request. Whether you have a legal duty to actually keep data, is up to you or your lawyer to find out. It depends on your data and laws. It is perfectly legal to make a website with a textfield that deletes any data you enter after a second. Destruction of data you own is only a problem if you break other laws with it. For example the IRS might not be amused if you destroyed invoices and other proof of taxable income. &quot;Some dude claimed I must in an email&quot; is not going to fly with them. That said, again, please, identify who you deal with, find out if their claim is valid. Don't do stuff because random internet punks write you an email. Because the next mail you get, will be from a Nigerian Prince. Please wisen up before opening that one. People on the internet, through stupidity or malice, might not have your best interests at heart. Don't believe random emails.
I would imagine they are yours and were always yours. You bought them. You intended to either give them to the company as a gift, sell them to the company or sign them over to the company as part of your initial capital contribution. Without a company none of those can happen.
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.)
You can do whatever you like with posts made after you change the rules - you have to leave the previous stuff alone. The contributors' have accepted the terms of the licence: They own the copyright or have permission from the copyright holder to post it (the promise) They agree that it can be edited altered or removed CC-BY-SA allows people to copy the stuff off the website and republish it - this is way outside what the contributors agreed to. These people have given permission for their work to be altered but not copied.
There is no IP in ideas Any code would by subject to copyright (who owns that copyright is itself a convoluted and separate question), however, if the 4 of you abandoned any existing code, notes and images and start over you would have no legal impediment.
You should probably get a lawyer, but my reading is this: The company whose SDK you use owns their SDK, owns their code, and is free to take any of your ideas how to improve their code without paying you. But they say that ideas are ten a penny, so this is mostly there to prevent pointless lawsuits. On the other hand, it says that everything you do with your product is yours. I might be completely wrong, that's why you should get a lawyer.
This basically is about the legal responsibility a web-site owner has for user-created content that violate copyright or other laws (such as libel laws). In the USA, this situation is covered by the DMCA. In the EU, this situation is covered by the e-commerce directive. In other jurisdictions, other regulation may apply. The DMCA (USA) is the simplest of those regulations. It stipulates a protocol of Notice and takedown. A web-site owner that complies with this protocol is given Save Harbour. This means that a compliant web-site owner cannot be sued. This goes both for a web-site that is a registered business, and a site run by an individual. The owner of the IP may, however, take the individual who stole and published copyright protected work to court, and will do probably do so if the financial loss was substantial (e.g. a major motion picture was leaked before hitting the cinemas). In the EU, the law is much less explicit than in the USA. Basically, the Notice and takedown protocol works like in the USA, but since it is not part of the law, it is less formal. In the USA, you can safely not act on any complaint that does not strictly follow the protocol (you just have to give feedback so they can fix it). Not so in the EU. And as follows from Delfi AS vs. Estonia, you can be sued even if you take down stuff. In particular if you create an environment for anonymous postings that encourage transgressions and have no means of moderation in place. So if the web-site is located in the EU, the website owner need to exercise more caution when he lets friends publish content, than when a website owner in the USA.