Can you provide free technical services to Iranians from America? Is it legal to provide free technical services to Iranians, or to grant them access to services such as websites and social media? Is it the duty of American Companies to actively prevent access from Iranian IPs and Users? To what extent can use be permitted? The question is about the exchange of information/services that would otherwise be freely offered to Americans under the scope of legal subject matter. I'm only concerned about the ramifications from the side of a corporation or person residing and operating in the USA.
It really depends on what "services" you are providing, but generally speaking you would be in violation of the Department of Treasury, Office of Foreign Assets Control (OFAC). These regulations are spelled out in 31 CFR §560.205 and 560.420 and apply to US citizens and residents wherever located. Specifically, the action that is prohibited is the "exportation, reexportation, sale or supply of goods, technology, or services to Iran. Here "Services" is broadly construed to mean anything of value even if no money is exchanged, including providing technical assistance to an Iranian national or Iranian institution. See See § 560.204; §560.410. The civil penalty for violation of these sanctions would be $250,000 or an amount "equal to twice the amount that is the basis of the violation". Criminal penalties may include fines up to $1 million and 20 years in prison. Now there are some exempt transactions outlined by § 560.210 (c) which may be applicable here, however it would be up to you to prove that these are "information or informational materials" as defined by § 560.315. For more information, 31 CFR Part 560, Subpart B refers to the prohibited transactions with Iran. Since you are not specifically spelling out what services you intend to provide, it is difficult to say for sure you would be in violation of them. It should be noted though that the US Government uses publicly funded money to run a proxy server through which Iranians can access otherwise blocked websites such as social media in Iran.
It is certainly possible to transfer a copyright or other IP without an explicit charge, indeed it can be a pure gift, and normally would be when it is left by will, as is common enough. From a paid consultant it might be clearer to include a statement that the transfer is part of the consulting assignment, rather than putting a price of zero in a blank. But one could instead convey a permanent non-exclusive license, granting permission to use or modify the work in any way desired, ans saying that this is provided as part of the consulting process. Then there would be no question of what rights the consultant retained, or that the same or a very similar solution could be provided to different clients. Indeed such a license would not be so very different from a CC-BY license, or any of several open source licenses, although I would not use one of those by name. But the legal effect would be much the same, and the wording could be similar. Otherwise there could be a later claim that the right transferred precluded the consultant from using the same solution for other clients. Even if such a claim was not legally sound, and was not upheld, it could be a distraction and costly of time and energy at least.
Such use might well be illegal, and subject the user to tort liability, or possibly even criminal liability. Parties For this discussion let us call the person or company that developed and wants to protect the information D, the person or company that downloaded and wants to use the information U, and the person who placed the information on the server P. Trade Secret One possible source of liability is if D considers the information to be a trade-secret. The law on trade secrets varies to some extent in different countries, although there is a general similarity. Since no jurisdiction is specified in the question, I am going to look at the united-states law. Definition The LII page on &quot;Trade Secrets defines a trade secret under the US Uniform Trade Secrets Act (&quot;UTSA&quot;) as: &quot;information, including a formula, pattern, compilation, program, device, method, technique, or process that: Derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use; and Is the subject of efforts that are reasonable under the circumstances to maintain its secrecy. A similar definition is given by the USPTO page on &quot;trade secret policy&quot;. Prior to the USTA, and still in those US states that have not adopted the USTA, trade secrets were/are protected under the common law. The LII page lists the common law factors, as given by the Restatement of Torts (1939) § 757, comment b: The extent to which the information is known outside the claimant's business The extent to which it is known by employees and others involved in the business The extent of measures taken by the claimant to guard the secrecy of the information The value of the information to the business and its competitors The amount of effort or money expended by the business in developing the information The ease or difficulty with which the information could be properly acquired or duplicated by others These factors may apply in other common-law countries. In either case, one must consider how the would-be user came to acquire the information, and thus how it came to be on the server from which it was downloaded. One must also consider whether it was the subject of &quot;reasonable efforts&quot; to protect its secrecy, under the circumstances. Circumstances If P was violating an obligation of confidentiality, such as an NDA or a duty as part of an employment relationship, then the placement of the info on the server was improper. In such a case its acquisition by another, such as U might constitute misappropriation. The same would be true if a person under an obligation of confidentiality arranged for the server to be indexed by a search engine, when it should not have been. The case for misappropriation would be stronger if U knew that the information was considered confidential by D, and also if P had informed U about where to find the info, or what search terms would uncover it. If P was acting with the permission of D, and P or someone else at D simply failed to realize that the server was, or might become, indexed, then the question is whether the steps taken by D to keep the info secret were reasonable. If this a case of &quot;inadvertent disclosure resulting from the trade secret holder's failure to take reasonable protective measures&quot; then there is no misappropriation, and the actions of U are lawful. That will depend of a judgement of whether D's actions were reasonable in light of the value of the info and the overall circumstances. If the placement of the info on the server is considered to constitute &quot;general publication&quot; of the info, so that it is no longer secret in any meaningful sense, then D may have a claim against P, but not against U unless U acted in collaboration with P. Copyright Law The documents downloaded from the4 server are almost surely protected by copyright. Directly incorporating them into an open source project without permission from the copyright holder would be copyright infringement, and would subject U to a suit for infringement. However, copyright does not protect ideas, methods, or facts. If U learns a method or idea from the document, and uses that knowledge without directly copying or closely paraphrasing the document, there is no copyright infringement and no claim under copyright law. Patent Law The question does not mention any patents. It is possible that D has patented the method describe in the downloaded documents. If so, and if the patent is valid, any use by U would be patent infringement, and the question of how U learned the info becomes irrelevant. However, most software developments such as data structures are not patented, so this is a somewhat unlikely, albeit possible, case. Notre that if the information is covered by a patent is is by definition not secret, as all patents must be openly disclosed. But they may not be widely publicized, and if U does not make a patent search, U may not realize that the document includes patented technology. This possibility is largely incompatible with the trade secret possibility, althogh it is possible to use trade secrets in connection with patented tech. Conclusion In short whether U may lawfully use then info, or is subject to a tort claim by D, or even criminal action, depend on the details of the overall facts. U would do well to take legal advice on the matter before proceeding to use the info.
Yes, barring any statutory prohibitions against such a rule. I would be very surprised if any existed. They don't exist in any jurisdiction I'm familiar with. Look up the local by-laws to be sure.
To use an API over a network connection (as opposed to, e.g., the Windows API), a user communicates a request to the API host, or server, and awaits a response. The host of the remote API can refuse to serve requests from users for probably any reason. Such services often require users to accept a license as a condition of using the service, and they may charge a fee as a condition of the license. A license to use a service is obviously not necessarily bound to a license for the use of its source code, just as the ability to reach the service is not dependent on the ability to see (let alone use) the code in any format, whether it be the source code or some compiled form of the code. In essence, source licenses and service licenses have different primary goals, at least inasmuch as the source license seeks to restrict someone who has actual physical access to compiled code, and possibly source code. Service licenses do not have that concern, though I have seen service licenses that also prohibit decompiling. This is probably the result of a CYA attitude among lawyers: the language is already in the standard software license text, and it doesn't hurt anything to leave it in, and it could help if a service user somehow managed to download the program code.
Makerbot's explanation of the Terms is accurate This is comparable with most other services that host and display User-created content - even with SaaS providers, as per Interpretation of content ownership/usage in service provider agreement. They are correct that they are asking for the lots of broad rights, but it's all qualified with (my emphasis): 3.2 License. You hereby grant, and you represent and warrant that you have the right to grant, to the Company and its affiliates and partners, an irrevocable, nonexclusive, royalty-free and fully paid, worldwide license to reproduce, distribute, publicly display and perform, prepare derivative works of, incorporate into other works, and otherwise use your User Content, and to grant sublicenses of the foregoing, solely for the purposes of including your User Content in the Site and Services. That is, if they use your User Content for a purpose other than including it in the Site and Services (and you have not agreed to this use), you may be entitled to relief in the form of an injunction or damages.
I’m guessing you have seen a sign in a business that read - “Management reserves the right to refuse service to anyone”. At least in the US, they do not need a reason as long as the reason isn’t unlawful discrimination. They can decide not to serve you.
My remarks pertain only to US Law. Laws vary in other countries. Subject matter eligible for copyright protection in the US must be expressive and creative. To the extent data are merely measurements of observable fact in the world, they are not copyrightable. It may be that the presentation or interpretation of data is eligible for copyright protection (for example, artwork used in charts, graphs, graphics, etc., that is expressive and creative), subject to various equitable use provisions (in particular Fair Use, which is still a legal grey area). The methods by which data are gathered can be considered IP, but is the domain of patents. Methods are not copyrightable (17 USC 102(b)).