Can job interview questions be confidential? Some time ago I had a technical job interview with Google. The invitation email had a line our interview questions are confidential, so please keep things under wraps Is this legally enforceable? I doubt that, as I did not sign any contract with Google. And this condition looks like "upon reading this you agree to following".
Can job interview questions be confidential? Is this legally enforceable? It is lawful, unless the nature of questions is outlawed or hinting at illegal activity. For practical purposes, though, confidentiality would be hard to enforce because Google cannot realistically prevent you from disclosing those questions. Whether or not Google can remedy any breach of that clause, that is a separate and uncertain aspect. Google's clause is binding only if you consent to it. Signing an NDA is not the only way to render confidentiality binding. Consent can be evidenced by anything that reflects your agreement to abide by that condition. It could be an email reply, or by subsequent conduct such as attending the interview with knowledge that constraint and without objecting to it. The fact that you attended the interview after reading that email makes their clause binding unless you objected and they nonetheless conducted the interview.
It is legal for a company to ask for any information they want as a condition of doing business with you, so long as their request isn't proscribed by law. I don't know of any jurisdiction where a request for banking or credit information is illegal. (In this case, however, it does seem like you are being phished. You could report the matter to your country's consumer protection agency.)
Well, as always, the answer is &quot;it depends&quot;. It isn't illegal per se. If both parties agree, it's good business. You get paid for the work of compiling the report. For example, let's say you leave and are no longer working for them, and they call you and say &quot;hey, you know those security vulnerabilities you were talking about last year? Yeah, the boss finally decided to give it priority, but it seems we kept no notes in that meeting. Could you compile a report for us? I know you no longer work here, but we would pay you a little more than the normal contractor rate if you are interested&quot;. That's perfectly fine. Now, not disclosing them when you found them could be seen as a breach of contract, which implicitely includes the duty of loyalty. Keeping it a secret to cash in on later is certainly sleazy. The compiled report might, depending on state laws, your specific contract, and who can pay the better lawyer, end up as their's. You can only compile that report because you worked there and you got knowledge of those vulnerabilites only as a part of your job. And finally, even if you did compile a report and it is waterproof and it is yours exclusively, it very much depends on the &quot;else&quot;. What if they just say &quot;no thanks&quot;? Selling that report to someone else is illegal. So you have exactly one legal buyer and that buyer knows it. Does not sound like a great bargaining position. If you approach them, it takes a lot of skill and maybe a bit of legal training to make sure it does come across as an offer of &quot;good business&quot;. I think it would be easy to be misinterpreted as either blackmail or selling them knowledge they legally probably already own. So unless you are certain you can fit into that &quot;good business&quot; model of selling your work compiling a report, instead of selling the knowledge of their secrets, it might be safer to not do that. If they approach you, it should not be a problem, but if you approach them, it will be a mess, no matter how well you mean it.
This would not be terribly unusual and would probably be enforceable. An NDA's restrictions would almost always survive the term of the agreement and keeping what you promised not to disclose secret forever would be a pretty common default. If you inherit nuclear missile designs in an old trunk from your grandfather from when he worked for a defense contractor, you can't give them to a terrorist group either. There is not "standard" NDA, but there are provisions which are more common to include in some form and those that are less common. If it was breached, there would be a statute of limitations running from the discovery of the breach to file suit, however. Also, damages would be minimal if the confidential information became outdated, for example, because the business in question ceased to exist a couple of decades ago, and no one would spend the money to enforce it.
Contacting a business email about a business matter is usually fine, but in this case we have an unsolicited marketing communication (spam), not really a business matter. The client's jurisdiction likely has more specific rules about spam. Also, it is unusual (read: presumably illegitimate) to contact individual employees rather than the company's official address with the offering. From the GDPR perspective, every processing of personal data (such as email addresses that might identify natural persons) needs a legal basis (Art 6). Let's go through them: consent? No. necessary for performance of a contract involving the data subject? No. legal obligation? No. vital interests? No. public interest? No. legitimate interest? Perhaps. The client has a legitimate interest to conduct their business. However, this legitimate interest must not be overridden by the data subject's interests, rights, and freedoms. Such as the interest in not being disturbed by spam mails. It is the Data Controller's (your client's) responsibility to balance the legitimate interest themselves to determine whether they have a legal basis, but I really don't think that they do. In conclusion, your client's idea is a bad idea: They likely do not have a legal basis for this under the GDPR. They are likely violating more specific anti-spam laws in their jurisdiction. They are working hard to get their domain put on spam filter lists. Note that already the step of collecting employee email addresses is personal data processing and needs a legal basis. Of course, the GDPR does not apply when the client is not established in the EU and only processes the addresses of persons that are not in the EU.
are employers legally allowed to punish (e.g. fire, reprimand, etc.) an employee who shares wage/salary information with their colleagues? No. Section 8 of the BC Labour Relations Code preserves for the employee &quot;the freedom to communicate to an employee a statement of fact [...] with respect to the employer's business&quot;. More conclusively, section 64 entitles a person to disclose --except for purposes of picketing-- &quot;information [...] relating to terms or conditions of employment or work done or to be done by that person&quot;. Wage/salary information clearly is a condition of employment. the only answer to that question relies on a law from a different province (Ontario) and so is not relevant in BC. That answer is relevant to Canada (also the question was about Canada). That answer cites a statute from Ontario because that is the jurisdiction that the asker specified. It would be tiresome as well as futile to provide the statutory equivalent of every province on a matter that the provinces are very unlikely to legislate materially differently.
You don't say what jurisdiction's patent laws you're interested in, and priority dates can differ in different schemes. I'm answering as to U.S. law only. In the United States, under the current hybrid "first-inventor-to-file" system, the priority date--the date that determines who "wins" if there are multiple claims to a specific invention--is, with some exceptions that I won't go into, the date of your first application. In other words, the date that the PTO got it in the mail. Once your application is submitted, it is--again, with some limitations I won't get into--prior art for the purposes of any later-submitted application. They can't get another application later, grant it first, and then deny your application based on the later-submitted application. Your application date would still win out. Could someone in the USPTO slip your application out of the stack, fudge the dates, and convince some other company to submit a similar application to get priority over you? Not as a practical matter, no. The USPTO isn't one guy in a room; it's a large organization, and the person who opens the mail, types in your application details, and sends you a receipt, isn't the same guy who knows whether your invention is any good or not. And, frankly, very few patentable inventions are going to be worth someone risking their job and/or jail time over--especially when there would be significant evidence of the misconduct--for example, your patent agent's files. So what are the chances that the examiner on your patent: 1) Is a nefarious character who has lived a life of public service long enough and wants to go rogue; 2) Has a friend in the mailroom who is also an expert in the field of your invention; and 3) Has a conduct in industry who is willing to break the law for the rights to your invention? Slim to none. And if you have an invention that is really so revolutionary that it's going to be worth so many people risking so much to steal it, odds are there will be other evidence that you were the inventor.
The essential parts of a trade secret are that (a) it is something that you keep secret, and (b) something that gives you an advantage in trade because you know it and others don't. A trade secret remains a trade secret if you give it to someone else under a non-disclosure agreement. If it is available where anyone can download it, either intentionally or by carelessness, then it isn't a trade secret anymore (as soon as it actually gets downloaded). If it gets made public through some illegal activity, well, that's too complicated for me. Anyway, YOU don't have to pretend anything. A claim that something is a trade secret doesn't make it one. And if something is a trade secret, no claim about it is necessary. If you download the software without doing anything illegal then it isn't a trade secret. To reply to the comment: If the sequence of events is this: I download the source code. I read the license. The license says "by using the software ..." then clearly I have the source code before using the software. At that point the trade secret status is lost. We don't need to discuss whether the license would have been enforcible, because the software is already downloaded before the license starts applying. I can tell anyone in the world about it. (I can't give the software to anyone, because that is copyright infringement, a totally different matter).