What about if a company use the information that you shared during interview I am a software engineer in Germany, I had an issue and i don't know how to react: Several weeks ago i had a job interview with a recently founded startup; I met with a co-founder of startup and we had an interview more than an hour long. The first of the things he talked about was that they had just founded the company and needed someone who would commit to the company as a technical leader. The company is going to have a mobile app aimed at a specific sector; but the guy didn't know anything about software world. I explained my experiences and I told how should they behave, which kind of technology they should use, what is the profitable approach to develop this application. The guy really liked what I said and offered me a job. We had a deal but without any contract; because he offered me a salary that did not make sense for me. After i denied this salary he said the salary is negotiable, he can rise my salary and share a part of revenue with me; but he also asked about time to clarify this topics. We had two more time meetings and several phone calls and a lot of mails and text during this time. I shared with him some more information about technical issues. I did some research and I shared the results with him. Everything was ok and I was waiting for the contract, but yesterday I asked about the salary that he is going to pay and some more topics about work via a message and today he just call me back and said he can not work with me without giving any more details. Now I want to ask, is this legal? Can he use information that I shared with him like profitable technology choices? I don't know someone else who has had similar experiences; but it really bothers me and I just want to hear some expert's ideas.
Unless you were operating under a non-disclosure agreement he (and you) can use any information that he learned unless it violates IP law. It sound like what you told him is generic (if expert) views on high-level approaches to software design. That is, you didn't give him slabs of code that you own the copyright for or disclose trade secrets that you own. That sort of advice is freely usable by him. There is a reason that consultants in every field don't give away their advice before signing the contract. Now you know what it is.
You have several issues. Breach of Contract When you sign up with each of those services you are entering a legally binding contract and must comply with the terms of that contract. For example, this is taken from Facebook's terms: Here are some commitments you make to us relating to registering and maintaining the security of your account: You will not provide any false personal information on Facebook, or create an account for anyone other than yourself without permission. You will not create more than one personal account. I haven't checked but its a fair bet that the other services have similar terms. Unless you have permission, what you are doing breaches these terms of service. If what you do causes damage to Facebook et al then they can sue you and your employer for damages. Even if it doesn't they can probably bar you from having an account for as long as they like. Improper use of images This is jurisdictional but it is generally required to have the permission of the subject of a photograph where that photograph is used for commercial gain. There are exceptions where the person is not the primary subject (e.g. crowd shots, or images primarily of something else where the person happens to be in the shot) but the type of photos you would use for these services are not going to be exempt. The sanctions for breaching this will be dependent on jurisdiction. Breach of Copyright Somebody owns the copyright in those photographs. If you do not have a licence to use them in the way you propose then you are breaching their copyright. The copyright holder can sue for damages (if any) and any profits you make. Vicarious Liability An employer is strictly liable for the actions of their employees, jointly and severally with the employee. That means a plaintiff can go after either the employer, the employee or both. An employee may have some statutory or contractual indemnity but this is by no means common.
There is no fixed definition in the law of &quot;outside activities&quot; that is applied generally. This will depend entirely on how the employment agreement defines it, and/or how the management of your company defines it. There may be a useful definition in the agreement, ideally there will be. In the far too common case that the agreement leaves this key term undefined, you will have to ask them how they define it. While it is true legally that when they draft the contract and it is ambiguous, you may adopt any reasonable definition, as a practical matter, if you do not disclose something and they consider it an &quot;outside activity&quot; They may claim this is grounds for discharge. If the employment contract requires you to disclose outside activities, you must disclose them or be in breach of that contract, which is surely grounds for discharge, and possibly grounds for a breach of contract suit. Even if it is not part of the contract, saying that you have no such activities when you in fact do is arguably fraud. Saying that you decline to inform management of your outside activities is probably legal, but might well cause them to cancel the offer of employment. If you do inform management, and the activities are approved, there would be no automatic transfer of any existing IP rights. No transfer could occur without an agreement saying so. Some companies, in their employment agreements (or other related agreements) demand that an employee transfer the IP of any project created or worked on using company resources (such as a company computer or network). Some demand a transfer for any project worked on during the employee's working hours. Some demand a transfer for any project done during the period of employment, but they must clearly specify this for it to be effective. That last is unusual, because many employees dislike it enough to go elsewhere as soon as they can, which tends to be bad for the employer. But in no case can a transfer of IP for a project unrelated to the employer's business, not using company equipment or resources, and not done during work hours, be effective without a specific agreement to this effect.
It depends to a large degree on local employment laws. Depending on how the counteroffer was worded, it might have constituted anything from a binding legal contract for employment for some reasonable minimum term, or a totally non-binding suggestion that was worth less than the air breathed while pronouncing it. Some things to consider would include: What are local employment laws like? Do they require that termination be for cause? If so, what are causes for termination? Does termination require any kind of remediation beforehand? Note that in an at-will, right-to-work state in the US, odds are that the employee can be fired for any time and for any reason, supposing the employer hasn't accidentally entered into a contract by extending the counteroffer. What did the counteroffer say? Did it stipulate that the offer was not for a definite term and that the company reserved the right to terminate the employee for any reason, or no reason at all? Odds are any sufficiently serious business in an at- will, right-to-work state would use standard legal language in any offer or counteroffer to ensure that they are on the right side of this, so odds are the counteroffer was accepted with no obligations at all on the company. Does the termination affect eligibility for unemployment benefits? I would say most likely not, as the termination would probably be recorded as being for no reason legally speaking (if they admitted to terminating the employee for seeking other employment, interested government officials could take a dim view of the company's actions). You'd probably have at least some unemployment compensation coming your way. Some professional - not legal - advice. Never accept a counteroffer. Only get another offer in the first place if you are committed to leaving your current employer no matter what. If your company really insists, you should insist on a minimum definite term of employment written into a legal contract which is signed by an executive and notarized. No company will agree to this (unless the term is shorter than you'd want as a full-time W-2 anyway) but if they do, hey, you have some security (if the company agrees to this, have your own lawyer - whom you pay with your own money - review the document). Even then, I would be very, very careful about staying at a company after getting a counteroffer. Don't do it. Ever. Never accept a counteroffer. One comment asks why I recommend never accepting a counteroffer. There are at least two reasons: The reason you are looking for a new job should be that there is something about your current job that isn't completely satisfactory and that you haven't been able to fix. Either you have grown out of the position, don't like the work, feel you're underpaid, don't get along with somebody, etc. If you were unable or unwilling to fix any of these issues without having another job on the table, having another job on the table shouldn't be what makes you willing and able to fix them. Why work somewhere that you'd constantly need to go job hunting to address workplace issues? Unless the company makes firm agreements about how long they're going to keep you around, you have no guarantee that they'll keep you. Presumably, you didn't have one before, and you don't have one at the new job, but the fact that you are currently employed might support the assumption that your employment would be continued at your current employer and the offer might support the assumption the new employer plans to employ you indefinitely. When you put in your notice, it makes the company more aware of the fact that you could leave at any time; while a perfectly rational actor would realize that this doesn't change the situation at all, companies are run by people and people often act irrationally. Perhaps your manager is vindictive, perhaps your manager is scared that you will still leave after accepting the counteroffer. Maybe your manager knows there are layoffs coming but needs you for the busy season. Hiring replacements can be time-consuming and expensive - and employees who are getting offers of employment elsewhere and putting in notice might be seen as risks. I'm not saying that accepting a counteroffer has always turned out badly. Falling coconuts kill 150 people every year. Still, I am not going to add a coconut rider to my insurance policy and I am not going to accept a counteroffer.
If you have an agreement with a company that specifies &quot;you agree to give me something of value, in case I give you something of value&quot;, you have a contract. In order for there to be a contract, there has to be actual acceptance of the offer. You can put out on a web page some contract stating those terms, and if you get positive acceptance of the contract (hence the standard click-through technology), then as long as you have done the thing promised, you can bill them for doing the thing promised. It's not clear what thing of value you are offering on the web page, since it's not &quot;doing actual work&quot;. Them sending you an email isn't you doing something. One thing you could do is block all incoming emails, and for money you agree to unblock emails from registered subscribers. Just announcing that you will bill anyone for emailing you does not create a contract, because the emailer need not have even seen your announcement. This is why e-contracts need a click-through button. It's legal to request money, but there is no legal obligation for them to comply. That will be $10, please.
NDA provisions in general are rather similar. In particular the ones covering the exceptions to the confidentiality obligations required to the receiving party. Such provisions normally have the following wording (more or less): Information shall not be treated as Confidential if: - at the time of disclosure is already in the public domain or becomes available to the public w/o breach by receiving party; - the receiving party receives it from a third party free to lawfully disclose such information; - was in the prior lawfull possession of the receiving party; - was independently developed by the receiving party; - is approved to be released by the disclosing party; or - the receiving party is required by law to disclose in response to a valid order of a court or by a government agency. Your particular case might not necessarily fall under any of this exceptions (i do not know the exact wording of the NDA you're referring to) but in any case, please note that simply telling a third party that you are discussing the development of "an app similar to x but with a better UX and simpler design", might already be considered as a breach of confidentiality. Surely the NDA is identified as being Confidential itself and it probably also contains a section saying something like: "This Agreement and its contents shall be treated as Confidential Information".
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.
(IANAL, of course) My employer tells me that EVERY professional activity belongs to the company and for EVERY activity I mentioned before I need to get written permission, That's true for software (and inventions) that may be relevant for them, but not for other professional activities. which could be withdrawn at any moment. No, not in that very general sense. they can give the permission to publish possibly relevant pieces of code on SX, and they can withdraw that permission for the future. But they cannot take it back for the past. Once they tell you they don't want your invention, there's no way back from that decision (and there are legal deadlines for claiming relevance). Even if they require written permission for you to take a side job, they must give it unless they can show a valid reason against you taking the side job in question. And that would be a per-side-job decision. And it doesn't matter if I do it on my free time on my computer at home or not. That is indeed the case for copyright of software and for inventions. clause is to protect your employer from you helping anyone who is their competitor/you being their competitor while the employment lasts. This is pretty standard and, I believe, not only legal but would be the case also if they had not spelled out this to you. The lines between what is and what is not competition are sometimes a bit complicated* So, if your employer specializes in subway station surveillance systems and you work on face recognition and then help out your local pigeon breeder's association by implementing automatic door opening by camera + automated face recognition of the [unwinged] members that's close enough to touching the interests of your employer that I'd consider it off-limits unless you had talked to your employer and they are happy with this project (after all, they could be preparing similar products unknown to you). OTOH, overhauling the crappy Excel macros for the regional annual breeder's competition would be fine. And in general, the lower your position there and the further from the actual focus of the company, the more normal it is to have another job (think janitors, canteen staff of a software company as opposed to a janitor in a hire-a-janitor-service company) The general duty not be in competition with your employer also in general prevents you from being involved in a competitor business to the extent that you have noticable influence over that competitor. So the second part of clause 1 shouldn't be too surprising, neither. (update) OTOH, what may make this particular clause invalid is the requirement also for publicly traded shares that they cannot come with voting rights. I somehow suspect that thus prohibiting you from "normal person small scale ownership" of publicly traded stocks (not all of them even have non-voting shares) is undue and invalid (too broad a restriction). However, if that clause is invalid the legal default of "no competition to employer" still applies. Here's a (German language) web site of a lawyer that discusses these questions See also here https://www.hensche.de/Rechtsanwalt_Arbeitsrecht_Handbuch_Wettbewerbsverbot.html Unlike the 1st clause, this is AFAIK not a spelled out default of German employment law, but it may be a spelled out version of a Tarifvertrag (unionized group contract). In any case it is probably legal to have this clause in the contract. The point is that the employer can only forbid the side job if it is against their reasonable interests, a general "no side jobs whatsoever" would be invalid. Side note: they may even be of the opinion that employment law forces them to have some such clause: the employer has a legal responsibility to ensure that you are not working more than the number of hours allowed by law. I've had such a permission that stated the constraint that the permission is valid only as long as I ensure that I stay within those legal limits and my working ability for employer is not compromised. https://www.hensche.de/Rechtsanwalt_Arbeitsrecht_Handbuch_Nebentaetigkeit.html https://www.fachanwalt.de/ratgeber/nebentaetigkeit-als-arbeitnehmer-anmelden-zustimmung-und-muster-antrag https://www.haufe.de/personal/arbeitsrecht/top-thema-nebenbeschaeftigung/nebentaetigkeit-und-arbeitsrecht-was-erlaubt-ist_76_418602.html Copyright law for employees in Germany is somewhat difficult. the one exception is copyright of software where §69b UrhG transfers the transferrable rights automatically to the employer. Whether the software is written out of office and outside working hours is irrelevant, as long as it is done in "fulfillment of the employee's role or the employer's orders" (famous court case) so again, if at work you code facial recognition systems and in the evening the pigeon breeders accounting system, the latter is not related to your work. Your open source game is also OK unless you are employed as game developer. Also that not all code is subject to copyright. An obvious explanation on SX explaining a typical pattern would not be a creative work (though the full answer may very well be) in the first place. But for creative works other than software such as plans how to implement features, technical drawings, etc. working hours or not seems to be more important for assigning the rights and the rules seem to be more similar to employee invention law ArbnErfG): if it is outside working hours and possibly relevant for the employer, the employee has to offer it to the employer before trying to sell to someone else. The clause that employer must give permission to publication of content that is possibly relevant for them seems to me to be in line with these general rules. https://www.zeit.de/karriere/beruf/2011-06/arbeitsrecht-urheberrecht https://eventfaq.de/25510-urheberrechte-im-arbeitsverhaeltnis/ http://www.urheberrecht-leipzig.de/urheberrecht-nutzungsrechte-des-arbeitgebers-an-kreativen-leistungen-der-mitarbeiter.html * I've been advised in a situation where I still believe I was not competing, and even had a written permission, that this is the stuff that makes lawyers rich, and both employee and employer poor.... Take home message: even if you believe to legally have the right to publish on SX/contribute to an open source project, think again whether you'd want this to be the source of a conflict with your employer - or whether there isn't a win-win possibility that makes everyone happy instead. What is the most legal way to participate in public activities in such situation? I'd advise to be open about what public activities you'd like follow. Whatever the contract says, your employer can always give your more permissions. In the past, I've found the majority of employers being happy to see me contributing (some had similar clauses to yours and just wanted to know, some was happy about an open source project I brought, some like to be able to say where their employees volounteer, etc.). Although there was one who wasn't (and that did contribute to my decision to leave there). From that experience, I'd personally discuss this early on now: in case the employer turns out to be too intrusive (speak to Betriebsrat or lawyer or your union if you have one to make sure they really overstep their rights) for my liking, for me that would be a reason to cancel the contract which is easier &amp; faster during probation period.