How to act in name of company rather than natural person by e-mail etc? It makes a difference for tax and liability reasons if an action is done by a natural person vs a legal entity. How to make sure that actions are ascribed to the legal entity rather than one's natural person? What are the requirements by law and best practices? For e-mail, I guess a e-mail domain name with the name of the company would be advisable? Or an e-mail signature that is attached to every e-mail?
The question of whether a person was acting on their own behalf or that of a company would generally be a question of fact, so if such a case came to court it would be for both sides to present evidence and argue for their interpretation of it. In most cases the context makes it clear. You mention having a company email domain and associated email signature; that is certainly good practice and would go a long way towards creating a presumption that you were acting for a company. Also signing yourself with your job title or role (e.g. "Joe Bloggs, Chief Bottlewasher") makes it clear that you are speaking in your role as an employee. The content of the communication also matters; if you use your company email address to order goods from a supplier that the company has used before then the recipient can reasonably assume that you are ordering on behalf of the company and a court is likely to agree. OTOH if you use the company address to send libellous emails then the recipient would have a much higher bar to claim that this was the company view rather than a personal one.
That GDPR Disclaimer is no protection in some jurisdictions: the applicable laws to that situation in germany for example don't care about the GDPR: Cold calling, mailing, or e-mailing private people to advertise services all is handled by the same law: Without the consent it is expressly illegal under §7 of the law against unfair competition (Gesetz gegen unlauteren Wettbewerb UWG) and such cases are rather Slam-Dunk if the origin can be made out. The punishment can be a 300.000 € fine. The fact that to email someone you need their e-mail address and that e-mail addresses and private addresses are by default considered personally identifiable information is making it worse for the advertizer: Without either an exception (there is none available to cold-emailing) or special allowance of the person the data belongs to, you violate §4 of the federal data protection law (Bundesdatenschutzgesetzes BDSG) just by handling their e-mail address. That's a separate crime from the UWG one, adding up to another 300.000 € fine under §43 BDSG - or even up to 2 years in prison under §44 BDSG! Oh, and if the email does not contain a proper sender's address, that's another chance for a huge fine under the UWG... So, GDPR is your least trouble, if you violate the marketing laws of a country, or their own data privacy laws. A disclaimer means nothing as the act of sending the mail, even to an unintended addressee, is what is illegal and the law as written does not give a damn about 'I didn't want to advertise to that person' when in fact you sent them unwanted advertisements. Oh, and the very repository you suggest? It would violate the very same §4 BDSG and be illegal for processing private data if it was not actively asked to do that by the end user. As a result, that database is useless: It does kick back all people not in its database. Its database is incomplete because only few people give their address to that database as people not aware of the database never add their data on their own. So it regularly violates §4 BDSG with every German citizen's e-mail address it gets and kicks back, and claiming those addresses would be OK, it throws the company trying to check the database under the bus because they rely on data that is impossible to be reliable. tl;dr Don't do cold-(e)-mail marketing. You throw yourself into boiling oil with a lit torch in hand. further reading Other laws banning such behavior I had listed here, and I quote myself: The US has the CAN-SPAM-Act, which illegalizes sending unsocialised advertisements. You may NOT send a mail if any of the following is true: it has no opt-out the email was gained by 'harvesting' contains a header not matching the text contains less than one sentence the adressee does not have any relation to you In fact, you are liable for a 5-digit fine per infringing e-mail in the US. The FTC itself suggests to never buy e-mail lists - as E-mail harvesting or generating any possible e-mail adress itself is illegal.
Submit emails in their totality Your testimonial affidavit can quote or cite them as applicable. There is no protection of anyone’s privacy in court. By the way, the email where admissions were made is probably inadmissible if it was sent were in the course of bona fide negotiation to resolve the dispute. If the other party objects they will be thrown out - I wouldn’t hang my case on them.
This notice has no legal power what so ever. This has been, and is being, used as a legal backup and a scare tactic. For the most part, if someone gets some sort of "sensitive" information in an email, and it was not intended for them - this notice will serve as a scare tactic to make people get rid of it because of the legal sound of the disclaimer. Also, the senders are preparing themselves for a legal battle by having the notice in email’s body. In case that the sender sent some “sensitive” data to the wrong recipient, they can be potentially held liable for privacy breach of information similar stuff. So, when they show up in court they can potentially use the argument that they did everything within their power to protect the information by adding the disclaimer and the fact that the privacy breach happened is due to a natural human error. Basically, there is no disclaimer that can protect against actual libelous or defamatory content. The most a disclaimer can accomplish in this respect is to reduce the responsibility of the company, since it can prove that the company has acted responsibly and done everything in its power to stop employees from committing these offenses. [1] If you as an employee of a company shared sensitive information or personal information by mistake, you, and the company are still liable for your own action. It can be argued in court that the recipient’s email was not verified, that a human error is not an excuse because the information could have been encrypted with a password, the information could have been transmitted via a phone call or in person, and a bunch of other excuses that will hold the company liable for damages. There is no legal doctrine or theory under which an email confidentiality disclaimer is enforceable in a circumstance like this. There is virtually no scholarly analysis of the impact of email disclaimers and very little analysis by non-scholars. One of the few authors who have commented on the subject suggests that the misconception that email disclaimers have validity may arise from the mistaken belief that the Electronic Communications Privacy Act (ECPA) somehow applies. Michael Santarcangelo, “Do Email Disclaimers Matter?,” Sec. Catalyst (Oct. 17, 2007). But, as this author points out, the ECPA prohibits only “intercepting” emails. Emails that arrive at their destination—even if the sender did not intend that destination—are not emails that have been intercepted in transit, and the ECPA is therefore inapplicable. In short, the ECPA is focused on the criminal intent of the interceptor, not the ability of the sender to execute his or her own intentions. With regard to communications with lawyers, the rules are a little different. Model Rule of Professional Conduct 4.4(b) states, “A lawyer who receives a document relating to the representation of the lawyer’s client and knows or reasonably should know that the document was inadvertently sent shall promptly notify the sender.” It is noteworthy that the rule requires only notice and doesn’t require refraining from reading the document or prohibit other use of the document. And a number of states haven’t even adopted Rule 4.4(b), so there may not be a requirement even to notify the sender in certain states. Nonetheless, if a court is examining “fairness” in connection with waiver of privilege, a disclaimer on an email sent to a lawyer might help. [4]
I was told that when you sign something in the UK, then it is your signature, no matter what name you are using. So if you sign a contract with my name, then it's your signature and you are bound by the contract. Things might be invalid because you signed and not me. For example, if you sign a contract selling my car in my name, then that contract is not valid. If some document needs signatures of two witnesses, and you sign with your name, then with my name, then there are no two signatures. As far as I know, signing under a false name is not in itself criminal, but might very well be supporting fraud, for example, and might therefore be illegal. The contract for the sale of my car, signed by you using my name, would very likely be part of fraud and therefore criminal.
Owing to the First Amendment, in the United States your recourse would be limited to civil action based on violations of terms of service (meaning that "the authorities" are not going to knock on their doors to tell them to behave). This is not "spam" (which could be regulated) as the term is generally understood. It is annoying, but probably does not constitute threatening or child porn. It might involve violation of an anti-impersonation law such as this one from Texas, if the offender uses the persona of a real person as opposed to a fictitious person). That law, moreover, does not criminalize simple annoying. Prosecution may be possible in the UK.
No more than using your own phone, eyeglasses or underwear while working for the LLC. These are all tools of trade than one wold expect employees of the LLC to bring to their job (especially underwear). There is potentially a problem if assets of the LLC are alienated for personal use rather than the other way around. However, that would be subject to a reasonableness test - using your work computer to book a personal holiday is eminently reasonable. Where there is a real liability issue is if the use of that personal asset caused damage to third parties e.g. if the personal computer was hacked and damage resulted. This would allow a potential plaintiff to bypass the LLC and sue the owner directly (or, more likely, as well).
The common law is permissive That is to say that, in a common law jurisdiction, the law is about what you must not do rather than about what you must do. Now, particular statutes may be phrased as requiring certain actions but, if you read them the “common law way” to coin a phrase, they are really imposing sanctions for doing the prohibited thing that falls outside those parameters. Since there is no legal prohibition on using multiple names (simultaneously or sequentially) you are free to do so. Now, there are common law prohibitions of, for example, fraud or tax evasion. So, if you use different names for the purpose of doing those prohibited things, then that is illegal but it is the specific criminality that is sanctioned, not the use of the alias in perpetrating it. The UK has a law that makes it a crime to not register the birth of a child. It also imposes some (and by most country’s standards, very few) restrictions on the name a child can be registered under. But there is no legal obligation on the child or their parents to use the registered name in any particular circumstances. There may be difficulties (amounting to impossibility in some cases) in obtaining a passport, opening a bank account, or claiming social security under a non-registered name but that is due to the necessity to identify the individual for which the name serves as a proxy. However, outside the requirements of specific statutes or administrative procedures, the common law position is that your name is what people call you and you identify as your name. The second part is important - I have been called dickhead on many occasions but I do not consider it to be my name. The UK has a patronymic tradition for surnames so, usually, on marriage, the female adopts the surname of the male and that, through the marriage certificate, becomes her registered name. However, it is extremely common for women to continue to use their original (and now not registered) name in their professional life and her new name in her private life. This can be problematic. My wife, has on server all occasions been refused permission to board a plane because the ticket (booked by others) was in her maiden name - a name for which she has no official identification. However, that’s a procedural problem - she didn’t do anything illegal.