How can a company buy an internet domain? How can a just formed legal entity (a company XYZ) buy an internet domain (e.g. www.xyz.com)? It has to be a human doing that. When I have checked the forms to fill in, they always ask for first name and last name of the owner of the internet domain. Is the solution that a human buys it on themselves, sells it to the company and the XYZ company announces the change to the internet domain provider? Thank you.
ICANN (the authority that regulates domain name registration) maintains the WHOIS standard, and all domain registrars (where you buy a domain) have to follow it. The WHOIS Standard has for a field for both Name and Organization : Registrant Name: EXAMPLE REGISTRANT Registrant Organization: EXAMPLE ORGANIZATION Foot-note n°4 has this to say about those fields. For the Registrant, Admin and Tech contact fields requiring a &quot;Name&quot; or &quot;Organization&quot;, the output must include either the name or organization (or both, if available). For registration purposes (this is different from the commercial purposes where the answer from Trish would apply) they can do both (using an agent name) or either
First of all, this assumes that the debt consolidation firm would be willing to buy, and the CC company willing to sell. With a trial already scheduled, this might well not be the case. Secondly, when (if) the debt consolidation firm buys the debt, they buy the rights of the seller. In many states the trial could go forward, with the debt consolidation firm substituted as plaintiff. It is not automatic that a sale of the debt would postpone the legal case. Certainly if this happened once, it seems very unlikely that a second debt consolidation firm would buy the debt from the first. And as the comments by Moo and ohwilleke suggest, such a scheme would be fraudulent and criminal, if discovered. It might also constitute contempt of court for intentionally abusing the process of the court. Not a good or safe idea.
IANAL, and as @GeorgeBailey suggests, you should ask one. That said, some aspects of your question are directly addressable with what we know. Does US law states anything about this? Yes. Federally this falls under the Wiretap Act, 18 U.S.C. §2511. Workplace monitoring generally falls under either the "System Administrator Exception" or under Consent. In general, continuing past a banner constitutes consent. Does company policy enforcement with such a warning over ride the right to not be subject to surveillance? In general, yes. You don't need to use the companies network if you don't want to consent - and they don't need to hire you if you don't want to use their network. But it's their network, and their rules apply. There are some nuances, and courts have found that the wording of the notice has made a difference in some cases, but overall, if the systems are properly posted with banners, then the employer may capture communications. See the "Bannering and Consent" section of this article from cybertelecom.org, e.g.: Even if no clicking is required, a user who sees the banner before logging on to the network has received notice of the monitoring. By using the network in light of the notice, the user impliedly consents to monitoring pursuant to 18 U.S.C. § 2511(2)(c)-(d). Note that stored data is covered by different laws than communications. It's a nuance. Is it ethical to sniff all the data without giving any other warning than the logon banner? "Ethical" is a very different question than "Legal", and largely more subjective. Most employers require signed consent for monitoring as a condition of employment, and use banners thereafter. That is ethical by my definition, in that it meets or exceeds the requirements of the law, and does not mislead or use subterfuge. The tone of your question suggests you find it distasteful, and therefore probably it violates your personal code of ethics.
You've really got two questions here: 1) "Is it an invasion of privacy to know that I'm using an ad blocker?", and 2) "Is it discrimination to refuse service based on what software I'm running?". Taking them in order: Because of how HTTP/HTML works, there are essentially two ways for a server operator to know what software you are running. Your browser announces that it's running something. This usually takes the form of a modified User-Agent header. I'm not aware of any privacy laws that consider "Person A told me something" to be an invasion of Person A's privacy. They guess it based on the actions your browser takes. For example, if the website gets a request for a page, and the site's ad network does not get a matching request for an ad, the server deduces that the user is running an ad blocker. Since this is based on things that the server operator could reasonably be expected to be informed of, it isn't an invasion of privacy under any law I'm aware of. Is it discrimination? Yes. But not all discrimination is illegal. In general, only discrimination based on protected categories (race, sex, etc.) is prohibited, and I can't imagine a jurisdiction making "choice of browser add-ons" to be one of those categories, not least because it's something the person being discriminated against can easily change.
The CEO wants to "fool" users You are essentially admitting that the company you are working for is about to deceit its customers and asking whether that is legal. The relevant set of laws is rather sparse and does not give direct answers in regards to oAuth tokens or other details of that level (which is probably making your CEO think he can "handle" the arising questions). Probably the most relevant bit of legislation that applies here is The Federal Trade Commission Act (15 U.S.C. §§41-58) which prohibits unfair or deceptive practices and has been applied to online privacy and data security policies. I am pretty sure that, in practice, if the users take your company to court, it will be held liable because: users are allowing us to read their CRM data and once we get the data, the data become ours, and we can do whatever we want with it. Is this true? While the users are still allowing you to read their data it is completely up to the Terms/EULA what you can do with it. However, once you have made the users think that they have withdrawn your access (e.g. they "deleted" oAuth tokens), you are no longer authorized to read the current data (although the Terms may still allow you to use the old data you obtained when you had access). Silently continuing to access their data without their knowledge/approval is definitely a deceit. The CEO wants us to download all of their emails and store them in our database There would be nothing wrong with that if it was in the Terms. But if it is not, that would be a blatant (and easily punishable) breach of privacy. Note that you may also be held personally liable for this wrongdoing (if/when proved so). "Just doing your job" claim will not work.
Other Entities means Legal Person The reason for the term &quot;legal person&quot; is that some legal persons are not people: companies and corporations are &quot;persons&quot; legally speaking (they can legally do most of the things an ordinary person can do), but they are not people in a literal sense (human beings) This is very similar to Corporate Personhood. Among the recognized items for legal personhood are usually groups of people, such as a corporation, states or countries, but also churches and temples. In rare cases, Temple buildings and at least two rivers are legal persons. All non-natural legal persons have in common, that they are represented by natural persons - aka humans. A computer program is not represented by a natural person. A natural person (possibly representing a legal person) can use a program to agree to a contract, but a program agreeing on its own is not following the basic principle of a contract, which requires a meeting of the minds on the offer. The computer program becomes the tool that facilitates the contract, for example by offering a prewritten contract to people that want to use the service. Since the contract is usually offered by the service providers as is with no renegotiation allowed, those contracts can only be accepted or not - their side of the bargain is offered and then facilitated by the computer of the service provider - we have an invitation to treat. If a natural or legal person is able to agree (through its representative), the contract becomes binding. If you are not a legal person - so neither a human nor one of the recognized categories - you can not agree to the TOS, the contract is void.
As was mentioned in a comment, in the United States, businesses are generally registered at the state level. The information collected, and the extent to which or manner in which the public has access to it, varies from state to state. There may still be states where that's a paper-only process, but I'd guess in most of them it's accessible online, at least for basic information. For example, in Michigan the Department of Licensing and Regulatory Affairs has a Business Entity Search tool. If a business deals directly with consumers, it may be a member of the Better Business Bureau. Even if it isn't, but consumers have complained about it, the BBB will make public the information it has about the purported business. If a company is publicly traded (that is, it's corporation that issues stock, and the stock is traded on a stock exchange), it is required by law to be registered with the Securities and Exchange Commission. The SEC's EDGAR tool will display the company's filings, which should include annual and quarterly reports. If the company is or wants to be a government contractor, it generally needs to register with the General Services Administration, and certain information about successfully registered entities is publicly viewable in that system. (Conversely, the same system also lists "Excluded Parties" who are prohibited or partially restricted from doing business with the government.) Depending on what the business does, it may also be subject to registration with and regulation by additional state or federal agencies. For a full picture, however, unless you're dealing with the obvious agent of a Fortune 500 company, you'll probably want to get information from a private credit-check service as well; for example, as also mentioned in a comment, Dun &amp; Bradstreet for the business itself, or for a really small business a personal credit report on each of the owners and officers.
No, you're not required to sign any contracts. But since you're offering a service, you do have to manage some compliance tasks. You are a data controller under the UK GDPR, regardless of whether you have a company. This brings with it various compliance requirements. For example, you MUST post a privacy notice in accordance with Art 13 GDPR that explains how you process user's information. You must sign data processing agreements with your data processors, such as your server providers. And you should reconsider transfers of data to the US, since such transfers are illegal or at least quite questionable in the wake of the 2020 Schrems II ruling. You now have prospective users that are asking you for an Art 28 data processing agreement (DPA). These are likely other organizations that are data controllers of their own. For them to use your browser extension, they either need to find a legal basis that allows them to share their user's/employee's data with you (controller to controller transfer), or they need you to act as their data processor (controller to processor transfer). The third alternative is not to use your plugin at all. Of these, a C2P arrangement is most convenient for these other orgs, but involves a bit of paperwork to set up first. If you want to act as their processor, this doesn't mean you'd have to create a company (though a corporation might be very desirable as a liability shield). Being a processor means that you're contractually bound to only use the personal data as instructed by the controller, and not for your own purposes. This restricts what you can do, and has some special compliance requirements. For example, you cannot engage new subprocessors without your controller's approval. However, processor status can also be convenient for you because you're not responsible for interacting with the controller's data subjects, e.g. you're not responsible for handling their data subject access requests. Note that it's possible to simultaneously be a controller for some users, and a processor for others. E.g. Google Docs is offered directly to users as a B2C product so that Google is a controller, but also as a B2B product as Google Workspace, where Google acts as a data processor. Personally, I'd rather not sign any contracts unless I'm doing it as a business, and adequately compensated for providing this service. GDPR is only one compliance aspect out of many, making it unwise to offer a SaaS product as a hobby. For example, copying other people's web content has copyright implications… A potential alternative for some of the organizations asking you might be to make it possible for them to self-host your backend, so that they are not required to rely on you as a data processor. If you have no plans to commercialize your software, making it Open Source could be a solution. But you're in no way required to do that if you don't want to.