Am I legally responsible for being a developer of a code, if my customer uses it illegally? I am from an Europe country, I work online and get orders on freelancer websites. Few months ago, I had a customer hiring me to do some Bitcoin-related coding, I'm one of their developers for 6-7 months now. I have already created 2 of their main projects (they have like 7-8). The code I wrote had nothing illegal in itself as far as I understand (basically I wrote a system in which users sign up for my customer's services, and get notifications, deposit addresses etc, and I delivered the source) Today, I saw some very bad claims about them online, which I'm not sure if true or fake. But I'm still really worried... I have only received money for my programming, even lower than usual fee (because I needed the money). My question is, am I responsible for what they do with my code? I don't know anymore if their business is legit, should I stop working for them immediately? or I can continue if I'm not sure? Am I already in trouble? P.S. I have generalized anxiety issue, and this constant stress doesn't let me sleep, so any help is really appreciated.
As a baseline, you may assume that your code will be used legally. It sounds like this still applies in your case: there is an entirely reasonable and legal use for login code, so you had no reason to assume that there might be a problem. This puts you legally in the clear. To be liable, you'd need to know or at least reasonably suspect that your code would be used to violate the law.
You can't, in general, know whether a distributor of a work has permission to distribute, or is a pirate site. I verified that they have posted an illegal copy of a work that I created, and I know that I did not grant permission to them (or anyone) to infringe my copyright. Both hosting and downloading works without permission is a violation of copyright law, so both parties are liable. Downloaders may erroneously rely on the "I didn't know!" defense, which in the US carries no legal weight. Even so, if you download my book, it will probably cost me vastly more to sue you for infringement than the damages that I might be awarded over your infringement. Usually, copyright holders go after the pirate sites, and only rarely go after particularly egregious serial downloaders.
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.)
If I understand your question correctly, you have some clients who have paid you for services that you have not yet provided and, indeed, they have not yet requested. Is this correct? The accounting term for this is a "prepayment". The correct accounting treatment is to increase an asset account (your bank account) and create a liability account (Prepayments or something similar). You need to talk to your accountant about how to treat these for consumption and income taxes. Legally, these people are now creditors of your business - just like all of your suppliers and employees. There is no legal requirement to escrow or otherwise treat this as trust money. Basically, if your business goes bust they will lose their money. This is something that you should have dealt with in your contract with your customers - if you are running an online business then you should get a lawyer to revise your terms of service to cover things like how they can ask for a refund (and how long you have to get it to them) and how long (or if) they forfeit the funds. As it stands the money effectively becomes yours after whatever time under a statute of limitation applies to transactions of this type and size (under whatever law applies to the contract) since after that time they cannot sue to get it back.
the first two highlighted parts seem to contradict each other. No, in this case they do not. The first highlighted portion refers to works or items produced "for or under the direction of the Company", whereas the second highlight refers to your creations that satisfy conditions (a) and (b). Where contradictions actually exist, the doctrine of contra proferentem entitles you (the non-draftsman of the contract) to adopt the portion or reasonable interpretation that favors your legal position. Also wondering how valid those statements actually are They are valid and become enforceable as soon as you sign the contract or your subsequent conduct reflects your acceptance thereof. it's a matter of privacy. So the question is what I can do or what the reality is of the situation The reality is that you are asked to sign a contract that is abusive and ridiculous. One vulnerability from describing your inventions (presumably in Appendix A) is that the employer gets "irrevocable, worldwide, etc" rights on them as soon as you "use or disclose any [items listed in Appendix A] when acting within the scope of [your] employment". This means that if instead of reinventing the wheel you share or apply any portion of your prior creations so as to enhance your productivity, you knowingly and irreversibly grant to the employer perpetual rights to those items. Legal disputes regarding APIs can become extremely intricate. And, since judges usually have no decent background on IT, even those few judges with integrity are unlikely to grasp the key subtleties that would lead to a correct ruling. "not useful with or related to any Company Interest" is very vague. The company could be interested in literally anything these days. Clauses which are too vague or excessively wide-encompassing are supposedly stricken as unconscionable, unenforceable, etc. However, I personally would foreclose upfront the risk of judicial hassle and decline the abusive contract. Legal issues aside, keep in mind that you are offering your expertise (in terms of supply &amp; demand, you are on the supply side). This fact has a less derogatory connotation than "asking for a job". Accordingly, the relation between the parties should be more leveled.
The DMCA prohibits circumvention of technological measures that effectively control access to a copyrighted work. So you can't legally "crack" the software, period -- even if you own a disc containing the software and have a valid license to use it, a license to use the work is not authorization to circumvent access controls. So if the disc is copy-protected, by my understanding of the DMCA, you're kinda screwed. (The company might be willing to provide you a replacement copy, even if only to maintain the illusion that the software is "licensed, not sold". But you can't make one yourself.) Likewise, if you have a copy of the disc but have lost the license key, you're screwed. Even if you could prove beyond any doubt that you are the licensee, there's not any law i'm aware of that would compel the copyright owner to provide you another license key. And courts have held that distribution of license keys without authorization is a violation of the DMCA. So whoever might provide you another key, if they're not the copyright holder, has broken the law. If you managed to copy the disc from a friend (without circumventing any kind of copy protection), and had your own license key, you might be in a better position. Many EULAs allow you to make a backup copy. Even if they didn't, copyright law does, so there's a possible case for fair use.
The general rule is that the author of the software owns the copyright, so that would be the student. This is regardless of whether the student writes the code for fun, or for a thesis. If a student is hired to write that code, then it kind of depends on the university rules, and who hires the student. In the case of a "work for hire", the employer owns the copyright. However, it is non-trivial to determine whether that principle is applicable in the case of a student hired by the university. In part, it depends on which country this is in because work for hire laws are not exactly the same everywhere, and in part it depends on the details of the employment my a university. In a typical US institution RA appointment, it would come down to university policy – some universities declare that copyright in all student-written software is retained by the student. You would need to look for something resembling an "IP Policy" – here is a sample, note that such policies are subject to revision.
Makerbot's explanation of the Terms is accurate This is comparable with most other services that host and display User-created content - even with SaaS providers, as per Interpretation of content ownership/usage in service provider agreement. They are correct that they are asking for the lots of broad rights, but it's all qualified with (my emphasis): 3.2 License. You hereby grant, and you represent and warrant that you have the right to grant, to the Company and its affiliates and partners, an irrevocable, nonexclusive, royalty-free and fully paid, worldwide license to reproduce, distribute, publicly display and perform, prepare derivative works of, incorporate into other works, and otherwise use your User Content, and to grant sublicenses of the foregoing, solely for the purposes of including your User Content in the Site and Services. That is, if they use your User Content for a purpose other than including it in the Site and Services (and you have not agreed to this use), you may be entitled to relief in the form of an injunction or damages.