Does a 16yo without a work permit have rights to the code he was paid to develop? I am sixteen, and I have a summer job for a software company. In my state (Maine), a work permit from school is required for someone of my age to have a job but it was never filled out. I assume someone forgot. I am also aware that minors can void contracts. However, I am unsure whether or not that extends to employment contracts. I, along with one other employee, am currently putting work towards a ~$100,000 contract, and am being paid the same as I would be had I worked at the local McDonalds. During the course of the job, I wrote software on computers provided by the company. Can I void the contract, and claim the work I did as my intellectual property? Am I even technically employed given I never submitted a work permit?
No As a 16 year old you do not need a Child Work Permit - these are required for "[a] minor under 16 years of age". Notwithstanding, minor's contracts can be classified as valid, voidable or void. There are two types of valid contracts: Contracts for "necessaries", and Employment, apprenticeship and training contracts. Your employment contract is binding and any IP you produced in the course of it belongs to your employer.
Your boss is totally wrong. Legally, there is no such thing as a "probation period" in the UK. You have the right to your holiday payment, according to the days that you worked. What can happen: The legal minimum is I think 28 days per year including bank holidays, but most companies give 23 or 24 days PLUS eight days bank holiday. Your contract may say that the first three months are called probation period, and during that time you only get the legal minimum, and after that the much more common higher amount. That would be legal. But even so, you would be entitled to seven days, minus any bank holidays where you didn't work.
No. You cannot be held liable for violating the EULA if you have never used the software and are only reporting what people who did use it told you. Of course, people bring groundless lawsuits all the time and you might have to defend such a lawsuit if you are sued. In some places you could be subpoenaed to disclose your sources, and in others, a reporter's privilege would allow you to quash such a subpoena.
If it's patented then it doesn't matter that you independently came up with it. Most software is not patented, though. Most developers do not even think about patents when writing code. In theory you could spend your time keeping up to date on software patents so that you avoid infringing. But this probably only makes sense for specialists who would want to read the latest patents in their field anyway. All software is protected by literary copyright, though. In this case they will try to prove that you did not independently created it, and did copy it. Whelan v. Jaslow in 1986 ruled that structure, sequence and organization of a computer program were protected by copyright. So you could be liable even if you did not just copy and paste sections of code. But even if you're worried the court would get things wrong and think you copied a program when you never even saw it in the first place, there is really nothing you can do about it.
Ideas aren't property Your employer does not own your ideas. However, neither do you. Ideas are not something that is protected by intellectual property law. To be IP, you need more than an idea. What is IP? The most common types are: Patents - protect inventions and new processes Trade marks - protect logos, words and other branding Copyright - protects art, writing, music, film, and computer programs Registered designs - protects the visual design of a product Circuit layout rights - protect layout designs or plans of integrated circuits used in computer-generated designs Plant breeders rights - protect the commercial rights of new plant varieties. The normal operation of IP law is that if a person is engaged under a contract of service (e.g. an employment contract) then their employer owns all the IP they make which includes progress towards something that might be IP (e.g. all the work that leads up to a patentable invention). However, if they are engaged under a contract for service (e.g. an independent contractor), then the worker owns the IP. The work the employer owns is generally limited to work in the course of the employment. So if you are a software developer they will generally own all code you write that is useful for their business but won't own the romantic novel you write in your spare time. In either case, the specific contract can override the default assumption. What can you do? You can certainly use the idea for the app but you can't use anything that is subject to your employer's IP. That means you can't use any code or copy the user interface - it all has to be redeveloped from scratch. You also can’t develop something that would be of use to their business while you are still an employee.
The real question isn't whether there is a law, but whether you want to keep your job. If you want to do something that you believe will affect your company negatively, and you ask whether it's legal or not, the question alone should show you it's a bad idea. And another question is whether you can be sued, and what it will cost you even if you can win a case, and the answers to that are "yes" and "a lot".
There have been cases in the UK where paying someone's legal bills was interpreted as joining their case. So when A with no money libels someone, and B with deep pockets pays A's lawyer, then B risks being held liable for damages if A gets convicted. So B should be very careful. Just giving you money is probably the safest. But attorney-client privilege is between attorney and client. I have been laid off twice with my company asking me to take an employment lawyer and paying for it. (Interestingly each time the bill was exactly the maximum amount the company was willing to pay :-) It would have been absurd if my company could demand information that is under attorney-client privilege just because they paid the bill. Why did two companies pay the lawyers bill? Because that way they ensure that the separation is without problems. The lawyer explained the settlement contract and what it meant exactly. They also checked that the contract didn’t contain anything unacceptable which the company would have fixed. So if I had tried to sue them later I would have no chance to win (but there was no reason to sue). Another reason not to sue was that the company offered I settlement that was very significantly more than was legally required, but if you sued them you would only get what you got in court - most likely less than you would get without suing. So basically they paid to make sure I would have no reason to sue them later.
For cases where this occurred within the United States, with works created on or after January 1, 1978: (the OP has since clarified that their scenario occurred elsewhere) By default, the author (the actual creator) of a work is the owner of the copyright. However, this is not the case if the work is a &quot;work made for hire&quot; for an employer. In that case, the company is considered the author of the work, and owns the copyright. From US Copyright Office Circular 09: If a work is made for hire, an employer is considered the author even if an employee actually created the work. The employer can be a firm, an organization, or an individual. Works are considered to be made for hire in two situations, as described by that circular (emphasis added): a) a work prepared by an employee within the scope of his or her employment or b) a work specially ordered or commissioned...if the parties expressly agree in a written instrument signed by them that the work shall be considered a work made for hire. If no written agreement was signed and no employment relationship existed, then ownership of the copyright to the software would go to the person who wrote it, and they would be able to do anything that a copyright holder could do with a work, including using it however they want or selling it. Do note that this would only apply to software or changes made by the person in this situation. They could not, for example, sell or distribute any other piece of the software written by other people without the copyright holder's permission, even if these pieces are necessary to use the software that this person created.