How much of a codebase can be considered intellectual property? If you write some code, generally you or your employer 'own' that code (I won't go into who 'owns' open source code because it's not what I'm talking about). It's yours/theirs to do with what you please. But at what point can you reasonably say "this code is mine"? It seems reasonable to say a 100,000+ LOC codebase written by in-house developers belongs to the company they work for. You could stretch further and say "this function is mine". It might be a very specialised function using an algorithm you created to perform some task, so really yes, that is yours because no one else created it, you did. But what about boilerplate code and small snippets? What about "Hello World"? Millions of programmers have written a Hello World since the early 70's, but you couldn't say because you wrote one that you 'own' Hello World in your chosen language. What factors distinguish code classed as something that can be owned from code "anyone could have written"? There's only a certain number of reasonable ways of achieving some programming task, and you surely can't claim ownership of any code that does the same thing just because you wrote one first (or can you?). For example... A friend of mine got a job for a trendy new startup (the kind where beanbags and having a wacky office environment took precedent over actually doing anything) that swiftly sank beneath the waves. He was given a project that could have been handled by one programmer and got through what he estimates as 10-15% of the actual programming before being let go. He also did all of the design phase and supposedly has documentation to prove it. I want (with him) to use what he already wrote to finish the project and launch it as our own, but he's worried his former employer may come after him and accuse him of stealing the company's (which is now defunct) property. Ideally I'm looking for legal precedent if anyone knows of any, but I think it might be hard to come by if any exists at all.
Yes and no. [note, the following is all written about US law. In other jurisdictions laws are, of course, different (though usually not drastically so.)] In the US there are (at least) three different bodies of law that might apply to code: copyright, patents, trade secrets. Copyright covers original expression. Anything you write is automatically, immediately protected under copyright. The copyright applies to the code itself, and anything "derived" from that code. It's up to the courts to decide exactly what "derived" means. One case that's long been viewed as a landmark in this area is Gates Rubber v. Bando Chemicals. The Court of Appeals for the tenth Circuit decision includes a section titled: "The Test for Determining Whether the Copyright of a Computer Program Has Been Infringed." Note that you can register a copyright, and that can be worthwhile, such as helping recover some damages you can't otherwise. Patents are quite different from copyrights. Where a copyright covers expression of an idea, a patent covers a specific invention. Rather than being awarded automatically, a patent has to be applied for, and awarded only after the patent office has determined that there's no relevant prior art to prevent it from being awarded. A patent, however, covers things like somebody else independently discovering/inventing what's covered by the patent. A trade secret could (at least theoretically) apply to some process or procedure embodied in the code. A trade secret mostly applies to a situation where (for example) you're trying to form an alliance with some other company, and in the process tell them things you don't tell the general public. If you've identified the fact that what you're telling them is a trade secret, and they then tell a competitor (or the general public, etc.) or more generally use that information in any way other than the originally intended purpose, it could constitute a trade secret violation. As a side-note: patents and copyright fall under federal law, so they're basically uniform nation-wide. Trade secrets mostly fall under state law, so the exact details vary by state. Absent a reason to believe otherwise, I'd guess your interest here is primarily in copyright infringement. The key here would be showing that one piece of code was derived from the other. That is, it specifically would not apply in a case where there were only a limited number of ways of doing something, so anybody who wanted to do that had to use one of those ways. Since this would not indicate actual derivation, it would not indicate copyright violation.
Sure, you can. But if you, from the US, contract with and pay someone outside the US and then use the results of that effort - the reverse-engineered code, either directly in violation of copyright or to find workarounds - within the US, you may not be culpable in a criminal sense (depending on different jurisdictions and trade/IP agreements), but you certainly would be liable in a civil sense. If the US based software developer (I assume a US-based software company, as you said "outside the US") tracks you down, they can open a civil action against you for any damages they want to claim, including theft of IP, loss of profits, EULA violations, and on and on, because you posses and are using reverse engineered code. How much money do you have to lose?
It's not clear exactly what you're asking, when you say "the company I work for" – i.e. are you asking "can they fire me?" (almost certainly they can, even if their TOS thinking is legally misguided – unless in your country there are laws that prevent firing employees). To be certain, you need to hire an attorney who is sufficiently savvy about web page technology that they can accurately judge what you are doing, and whether you can fruitfully resist their demands. You seem to be skeptical of their position because you are "not affecting their servers in any way". The TOS is not about affecting their servers, it is about affecting their intellectual property. It appears that your code does a number of the prohibited actions such as and perhaps most importantly "modify". If you have distributed a program that allows users to modify company content on their own computers, then the user might be in violation of the TOS, but not you (since you're not running a server that redistributes). However, I am betting that in order to create and test the program you had to violate the TOS. Additionally, you could be vicariously liable for the infringements of others, especially if this program can only be used to infringe on copyright, and you know this fact. That is pretty much the end of the legal part. As for how you should respond, your attorney, and not Law SE, deals in recommendations.
In Google LLC v. Oracle America, Inc., 593 U.S. ___ (2021), the US Supreme Court addressed the reproduction of a subset of the Java API. The majority assumed for the sake of argument that the Java API was protected by copyright, but went on to hold that the reproduction was a fair use. We shall assume, but purely for argument’s sake, that the entire Sun Java API falls within the definition of that which can be copyrighted. We shall ask instead whether Google’s use of part of that API was a “fair use.” Unlike the Federal Circuit, we conclude that it was. So, it is an open question whether an API is protected by copyright, but the precedent from the Federal Circuit will be persuasive authority. The Federal Circuit held that the API is protected by copyright and the Supreme Court did not upset that conclusion. Second, the factors that led the court to conclude the reproduction of part of the Java API was fair use could turn out another way in another fact scenario. Some of the reasoning seems to generalize, but some seems specific to the Java development ecosystem. Briefly, the court recognized: API authorship is a creative process, but is &quot;functional in nature&quot; The reproduction was intended to assist interoperability; it was commercial; there was no evidence of bad faith The amount of code taken was a small amount of the entire Java work, an amount consistent with its goals The market harms to Oracle were dubious My prediction is that there will continue to be significant case-by-case uncertainty as to the applicability of the fair-use defence in this context.
Is it ok to copy the game concept and even with mostly similar content like "fighting", "building houses" etc ? Yes, but ... I should also mention that pretty much my whole User Interface is based on the User Interface from "Parallel Kingdoms" Is copyright violation. Ideas are not protected by IP law. The tangible representation of those ideas (art, words, layout, format etc.) is protected.
What happened is that you created a legal mess. You are obviously on the hook for copyright infringement. The maintainers of the project will scramble to replace your code with newly written code. They will likely ask your company which code they are complaining about - that puts your company into the problematic situation that they shouldn't identify code that isn't theirs, that it will be hard to sue for infringing code when they didn't give the project maintainers a chance to fix it, and that everything they identify will be replaced. Since it is your actions that caused the trouble, anyone suffering damages from your actions can sue you.
The Organization Does Not Own the Copyright As you were clearly not an employee of the organization, and did not have a specific contract with them, this was not a &quot;work-made-for-hire&quot; (WFH). Therefore, the copyright initially belonged to the author, in this case the programmer, that is you. That being so, it would require a written document to transfer the copyright to another during your lifetime. In future there should be a written agreement in such a case, spelling out just what rights are to be retained by whom. It can save lots of trouble. The organization would have an implied license to use the software. The terms of this would be defined by the conduct of the parties, and might be a matter of dispute. Probably there would be a non-exclusive license without any fee or ending date. Probably there would be no license to distribute to others unless you explicitly grant one. Specific US Laws 17 USC 101 defines a WFH: A “work made for hire” is— (1) a work prepared by an employee within the scope of his or her employment; or (2) a work specially ordered or commissioned for use as a contribution to a collective work, as a part of a motion picture or other audiovisual work, as a translation, as a supplementary work, as a compilation, as an instructional text, as a test, as answer material for a test, or as an atlas, if the parties expressly agree in a written instrument signed by them that the work shall be considered a work made for hire. For the purpose of the foregoing sentence, a “supplementary work” is a work prepared for publication as a secondary adjunct to a work by another author for the purpose of introducing, concluding, illustrating, explaining, revising, commenting upon, or assisting in the use of the other work, such as forewords, afterwords, pictorial illustrations, maps, charts, tables, editorial notes, musical arrangements, answer material for tests, bibliographies, appendixes, and indexes, and an “instructional text” is a literary, pictorial, or graphic work prepared for publication and with the purpose of use in systematic instructional activities. (emphasis added) 17 USC 201 provides that: (a) Initial Ownership. — Copyright in a work protected under this title vests initially in the author or authors of the work. The authors of a joint work are coowners of copyright in the work. (b) Works Made for Hire. — In the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author for purposes of this title, and, unless the parties have expressly agreed otherwise in a written instrument signed by them, owns all of the rights comprised in the copyright. ... (d) Transfer of Ownership.— (d) (1) The ownership of a copyright may be transferred in whole or in part by any means of conveyance or by operation of law, and may be bequeathed by will or pass as personal property by the applicable laws of intestate succession. (d) (2) Any of the exclusive rights comprised in a copyright, including any subdivision of any of the rights specified by section 106, may be transferred as provided by clause (1) and owned separately. The owner of any particular exclusive right is entitled, to the extent of that right, to all of the protection and remedies accorded to the copyright owner by this title. 17 USC 204 provides that: (a) A transfer of copyright ownership, other than by operation of law, is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed or such owner’s duly authorized agent.
Unless the game is out of copyright, e.g. chess, snakes and ladders, Go, or checkers, your software would probably be considered a derivative work of the copyrighted game and an actionable infringement. The fact that you do not monetize it is not a defense. You would need written permission in the form of a license agreement from the copyright owner to do this legally. The penalties for violating copyright laws in this way could be punishingly serious.