Is requesting a customer database for testing purposes legal? We're a company working in building industry and have a program, develeoped together with our software vendor, to create quotes and configurate products. The program uses a MS SQL database. It stores mainly following data (customer created): quotes, created material, prices (extra charge), users with names, company phone numbers, emails, etc., customers (customers of our customer), text modules (cover notes, terms, etc.). When we release a new version (update) sometimes issues occur which happen only at our customers because they've a different database structure for example or different data. Therefore my question: is it legal to ask a customer if we can use their database for testing purpose or is it not?
It's not illegal to ask. Whether they can give it to you, and under what circumstances, is another, much more complicated matter. For instance, if the database contains health information covered by HIPAA in the United States, or personal information covered by laws like GDPR or CCPA, the customer's ability to share the database may be restricted, either requiring additional confidentiality obligations/use restrictions, or preventing sharing entirely.
Awareness of consequences If you knew (or had reasons to suspect) that the server end implemented something like (whether intentionally, or by way of a bug/omission): if variableThing == **MyValue** { causeALotOfTrouble() } — then yes, you pretty much can be held accountable. Otherwise highly unlikely. By default, it is reasonable to expect that servers handle/filter/sanitise user input properly no matter where the request comes from, so modifying a URL is merely seeking certain data from the server — which it is free to supply or deny. For example, if MyValue is an SQL injection attempt, then yes. If it is trying to filter out the results by a certain criteria, then no.
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.
Are all interview questions that don't apply to essential functions illegal? No. Not all such questions are illegal, but see one exception from California legislation as pointed out by @GeorgeWhite and others in section 432.7 of the state Labor Code. Other jurisdictions very likely have equivalent prohibitions, but questions like the one you envisioned ("What music do you like") would not infringe statutory provisions. Generally speaking, it is lawful for an employer to assess candidates' personality &amp; non-essential skills under casual and not-so-casual scenarios through the use of questions with no relevance to the job at issue. Only in very specific circumstances certain pattern(s) of questions may lead to a finding of harassment or discrimination. Questions related to categories which the Civil Rights Act protects are risky because a rejected candidate would have at least some grounds for a claim of discrimination. Those categories are [candidate's] race, color, religion, sex, and national origin. Questions on those protected categories are not illegal, but the employer will have the burden of proving that its challenged practice (i.e., making seemingly discriminatory questions) "is job related for the position in question and consistent with business necessity" (see 42 USC § 2000e-2(k)(1)(A)(ii)) rather than for purposes of unlawful discrimination.
No. That clause does not give other users a licence to reproduce the work (other than what is necessary to access or use it) or create derivative works. The copyright owner has the exclusive right to do those things. (See 17 USC 106.) The clause you quote only indicates that other users can "access" (download for viewing) your "information" and use it, too. It doesn't give away any of your exclusive copyright in the work. You do grant Facebook a licence to do certain things with your work in section 2.1 of the Terms of Service, though.
You Own The Code To answer your question on whether or not it is copyright infringement: Yes, you do own the rights to the written code but posting it on Github gives Github the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it. To simply put it, no matter what license you use, you give GitHub the right to host your code and to use your code to improve their products and features. This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive your Content. So with respect to code that’s already on GitHub, I think the answer to the question of copyright infringement is fairly straightforward. Things aren’t quite as clear-cut in a scenario where Copilot is trained on code that is hosted outside of GitHub. In that situation, the copyright infringement question would hinge largely on the concept of fair use. If Copilot is being trained on code outside of GitHub, we accept that at least some of what they’re looking at is copyrightable work. So, the question then becomes if it’s fair use. Now, you ultimately can’t conclude definitively that something is fair use until you go to court and a judge agrees with your assessment. But I think there’s a strong case to be made that Copilot’s use of code is very transformative, a point which would favor the fair use argument. There is precedent for this sort of situation. Take the case of Google Books, for example. Google scanned millions of books, provided people who were doing research with the ability to search the book, and provided the user a small snippet of the text that the user was searching for in the book itself. The court did in fact find that was fair use. The use was very transformative. It allowed people to search millions of books. It didn’t substitute for the book itself. It didn’t really take away anything from the copyright holders; in fact, it made it easier for readers to access the work and actually opened a broader market for book authors. And, it was a huge value add on top of the copyrighted corpus. In the latter scenario, a lot depends on the thoroughness and the length of Copilot’s suggestions. The more complex and lengthy the suggestion, the more likely it has some sort of copyrightable expression. If a suggestion is short enough, the fact that it repeats something in someone else’s code may not make it copyrightable expression. There’s also the question of whether what’s being produced is actually a copy of what’s in the corpus. That’s a little unclear right now. GitHub reports that Copilot is mostly producing brand-new material, only regurgitating copies of learned code 0.1% of the time. But, we have seen certain examples online of the suggestions and those suggestions include fairly large amounts of code and code that clearly is being copied because it even includes comments from the original source code.
Legal unless you violate copyright. Screenshots will probably be fair use. The manuals/how-tos need to be your originals, not copies from anywhere.
Yes, it is legal to do that More exactly, it is not copyright infringement. Reverse engineering has been found to be a fair use under US copyright law in: Sega Enterprises v. Accolade 977 F.2d 1510 (9th Cir. 1992); Sony Computer Entertainment v. Connectix 203 F.3d 596 (9th Cir. 2000).; and Atari Games Corp. v. Nintendo of America, Inc. 975 F.2d 832 (Fed. Cir. 1992). In general pure reverse engineering is fair use when the reuser has not agreed to a contract limiting reverse engineering and has not obtained a copy through deception. But a file format is considered to be an idea or a method of operation, and so is not protected by copyright at all, and nothing that is done with it could ever be copyright infringement. See https://social.msdn.microsoft.com/Forums/windows/en-US/3269d4f3-8b39-4a2c-8205-1a55e0c6774d/are-file-types-copyrighted?forum=Vsexpressvcs and &quot;Does copyright protect data file formats?&quot; from Lexology, the latter citing EU law and the case of SAS Institute Inc. v World Programming Ltd in the Court of Justice of the European Union (CJEU). Thus there is no copyright infringement in reverse engineering a file format, or in then writing and distributing code to read, write, or, modify files in such a format. If a valid patent applies, that may prevent creating or using such software without a license from the patent holder. But my understanding is that in most cases a file format will not be subject to a patent.