if a non profit uses the .com domain or a for profit uses the .org domain , would that be false advertising and suable? Do organizations have to use domains according to their financial status and would they be liable for civil or criminal liability if they didn't use domains appropriate to their status (non profit/.org or for profit/.com). Also would using a website that has ad revenue or cookies on it automatically make one a customer or trader legally (the item traded being personal data)?
There is no law pertaining to top level domains, defining &quot;appropriateness&quot;. Instead, some organization is an administrator, and there is an understanding as to what the purpose of the domain is, but this is not legally enforceable. The TLDs com, org, net are open to anyone, whereas edu is limited in the US to accredited post-secondary institutions, however some non-educational commercial enterprises were grandfathered in. Insofar as registering a com-domain website does not entail &quot;an intent to make profit&quot; and registering an org-domain website does not entail &quot;an intent to not make a profit&quot;, there is no deception w.r.t. internet users. One would of course have to be truthful in registering the domain. Public Interest Registry, the administrator for org, does not even purport that businesses registered under org should be &quot;nonprofit&quot;.
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.
The Quora statement that the word &quot;facebook&quot; cannot be used in a domain name without permission is incorrect, or at least too broad. If a site or app is intended to work with Facebook, it may say so. However it may not use the word &quot;Facebook&quot; whch is trademark, in such a way as to suggest that it is an official Facebook product, or that it is endorsed, authorized, or sponsored by the makers of Facebook, or to cause confusion with the original Facebook. Whether a domain name containing &quot;facebook&quot; does that depends on the details. There are multiple precedents for criticism sites. A domain such as &quot;facebooksucks.com&quot; would not be trademark infringement, and there is caselaw to support this. But that is not what might be wanted here. Perhaps &quot;unofficialfacebookhelper.com&quot; would suffice. But to return to the question asked, use of a word in the hypertext metadata in the &quot;Head&quot; element is a reasonable way of indicating that the site is to be used in connection with Facebook, but there would need to be some additional notice or disclaimer making it very clear to any user that the site is in no way affiliated, endorsed, authorized, or sponsored by the makers of Facebook. The use of a trademark to identify another product with which a given product works is known as nominative use. The law specifically allows it, providing it is not done in such a way as to cause confusion, or to falsely suggest sponsorship, approval, or some relationship that does not exist. However, large corporate trademark owners are known to claim more rights than the law allows them. Such owners may try to suppress nominative use that they hae not approved, although they could not win a trademark lawsuit over such use. US Law 15 U.S. Code § 1125 (c)(3) provides the relevant part: The following shall not be actionable as dilution by blurring or dilution by tarnishment under this subsection: (A) Any fair use, including a nominative or descriptive fair use, or facilitation of such fair use, of a famous mark by another person other than as a designation of source for the person’s own goods or services
Can you unambiguously, legally, and conclusively determine what is and is not a "porn site"? I'm sure many are easy... but what about that "Swimsuit modeling" site, or the "Artistic Nudes" site featuring classic French Renaissance paintings? There will always be a grey area. What makes a "site" in a legal sense? Consider all the blog sites filled with user generated content: If just a few pages out of tens-of-thousands are hardcore, indisputable porn, would you require the entire domain to be classified XXX, even if 99% of its content is completely innocent? Who would enforce this? Are you proposing an "Internet Police" force to review all new domain names and their content before they get approved? That is called "Prior Restraint on Free Speech", and is established law. Suppose a site does get approved, then immediately changes the content of their pages from Cooking Recipes to hard-core porn. Who is going to review and approve every update to every website, when sites are updated constantly?! Maybe you're proposing that any individual who finds porn on a .ORG site has the right to sue for damages? This would likely clog the courts with endless vigilante lawsuits about what content belongs on which domain. This is a flat out horrible, poorly thought out idea.
It's possible that CAD has a separate licence from the authors of ABC that allows them to produce a closed source copy. If not, they have no right to distribute CAD. However two wrongs don't make a right, and so you don't get to violate the copyright of CAD.* Unfortunately, unless you are one of the authors of ABC, you have no standing to sue the authors of CAD. You can only notify the authors of ABC and hope they do. If the authors of ABC don't have the resources to pursue the matter, you may be out of luck. That's one of the reasons the FSF gets copyright assignments for their projects. * It turns out that this is a much more debateable issue than I first thought. Some courts have held that an unauthorized derivative work is not copyrightable.
This is relatively uncharted legal territory, so until multiple cases establish some sort of precedent, we can only guess. I know of no legal requirement that a Browser or User has to submit cookies or referrer data or other meta-information accurately. In that regard, a user is unlikely to be prosecuted just for submitting HTTP headers. It is likely closely related to Free Speech issues. The DMCA spells out that it is illegal to circumvent copyright protection measures. While this law is typically used to make it illegal to copy DVDs, video-games or streaming movies, it is possible that the "3-free articles" policy could be interpreted as a copyright protection mechanism, and defeating it by changing HTTP headers is a circumvention. A good summary is here. A specific site's TOS (Terms of Service) probably contains language that spells out it is a violation to use the site in a manner other than as it is intended. This is a typical anti-hacking, anti-screen-scraping provision. Altering a browser session to circumvent their services is probably a violation of the license to access the site, and may open a user to a civil lawsuit for damages or even criminal hacking charges (the details of which are different state-to-state)
Short preface: You might want to consult with a lawyer if what that website does really constitutes trademark infringement. But the question did not ask for that. It asked what to do if you want to send a C&amp;D to a website without contact information. That's the question I will answer here. Whether or not the C&amp;D letter itself has merit in this particular situation is another question, and probably one which would violate our &quot;specific legal advise&quot; rule. You can use a whois-database to find the public information on who operates a domain. Doing so for the domain in question yields that the contact information of the actual domain owner was &quot;Withheld for Privacy Purposes&quot;. That means the domain was registered through a domain-by-proxy service. The postal address in Iceland you see in the record is the address of that service, not of the domain owner. But you can see the registrar which hosts the domain: &quot;Name Cheap Inc.&quot;. So that's somewhere you can address complaints to. If you cause them enough problems, then you might be able to get them to take the website down. Those discount webhosters don't make nearly enough money per customer to fight their legal battles for them. Just reading a C&amp;D letter already costs them more than hosting a website for a year. So they might just fire the customer to avoid the trouble of dealing with you. But then the website might just reappear hosted by some other company a day later and you are back at square one. The registrar should also be able to tell you the real identity of the person who operates the website. However, they will likely not tell you without putting up a fight, as revealing private information without being legally obligated to might make them liable for violating a bunch of privacy laws. Ask your lawyer if there is any hope to get a subpoena forcing them to give you the identity.
For land ownership records and other similar scenarios such as business directors, the requirement for these to be public will be in legislation rather than a contract - this provides the legal basis, see GDPR Article 6(1c). Additionally when government departments are doing it they also have 6(1e) as lawful basis: "1. Processing shall be lawful only if and to the extent that at least one of the following applies: ... (c) processing is necessary for compliance with a legal obligation to which the controller is subject; ... (e) processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller;" -- GDPR, Article 6(1c,e). I'm not familiar enough with the specific legislation that will apply here but pretty sure this will be the case, and having said this you may well find public registries also become less public going forward. The reason ICANN has come under fire, is partly because under GDPR privacy is a protected fundamental right and therefore to comply personal data should be kept private by default and privacy never something you would be required to pay extra for. Any contract ICANN have in place with their registrars will not override legislation, it is in fact the other way around. "2. The controller shall implement appropriate technical and organisational measures for ensuring that, by default, only personal data which are necessary for each specific purpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage and their accessibility. In particular, such measures shall ensure that by default personal data are not made accessible without the individual's intervention to an indefinite number of natural persons." -- GDPR, Article 25(2). This doesn't stop ICANN from maintaining a register of domain name owners (registrants), but it does mean they can't just publish all records upon request to anyone anymore - whether people will be granted access to personal data will now depend on if they have a lawful basis for this, and in these cases their processing of the personal data will be limited to those purposes. Being nosey doesn't count! "When assessing whether consent is freely given, utmost account shall be taken of whether, inter alia, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of the contract." -- GDPR, Article 7 (4) - Conditions for consent. What this means essentially, is that if the consent is conditional for the contract it will not be treated as freely given, and therefore not valid - it will no longer be acceptable to contractually bind the provision of a product or service with consent to publish personal data or any other form of processing such as marketing mailing lists. Looking now at the specific points you have raised: "GDPR article 6 allows for processing of personal data on a contractual basis (section 1b)" Whilst this is true, this is only part of it - it doesn't allow for unlimited processing for any purpose and sharing it with any people, if you look at Article 5(b) it states that the information is collected for specific explicit legitimate purposes. Each purpose requires its own legal basis and needs to be compatible with the principles of GDPR. Without consent, ICANN currently does not have a legal basis to make the WHOIS records public for EU citizens and should have adopted some technical controls to require them to opt-in if they wish to be included in the public register. They're coming under fire for non-compliance having been given 2 years to prepare and change their systems/processes. "processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract;" Again whilst this is true, not all processing is necessary for the performance of a contract. In the same way people must give consent to receive marketing communications, they must freely give consent for their information to be shared/published (separate to the contract for provision of service) in the absence of other lawful basis for this processing. "Also section 1c, processing is necessary for compliance with a legal obligation to which the controller is subject;" There is no legislation which requires them to publish the personal data of domain name registrants. In this paragraph 'legal obligations' refers to those required by legislation (i.e. statutory obligations), not contracts (or non-statutory obligations) which are covered under Article 6(1b). "And finally section 1e, processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller;" ICANN has no official government-assigned authority, and publishing the personal data globally is not in the interests of the data subject's or others' welfare or well-being - this is what is meant by 'public interest'. As far as I can see what ICANN are actually doing to comply seems to be accepted by the European Data Protection Board, they are only 'under fire' as you say because they are late in doing so. The deadline was 25th May 2018 and they had 2 years to prepare like all other organisations.