R.J. Kelly of the Wealth Legacy Group wrote a great article on the importance of a good board of directors for privately held corporations. Click here for article
Wednesday, July 27, 2011
Great Article on Importance of Boards of Directors
R.J. Kelly of the Wealth Legacy Group wrote a great article on the importance of a good board of directors for privately held corporations. Click here for article
Saturday, July 23, 2011
Indian Tribes are Immune from Lawsuits
A little known fact is that American Indian Tribes (and their economic enterprises) can't be sued. The tribes enjoy sovereign immunity from lawsuits. Federal and state courts do not have jurisdiction over them. A definitive case was the Kiowa Tribe vs. Oklahoma Manufacturing Technologies. The Kiowa Tribe defaulted on a promissory note and was sued in state court. The lower courts found the tribe was within the jurisdiction of the state court for off-reservation economic activity. The U.S. Supreme Court reversed and held that the tribe was immune from suit.
In recent years, Indian tribes and their casinos, in particular, have become major economic forces. There are several Indian casinos in and around San Diego County. Anyone contracting with them cannot enforce those contracts normally. The tribes can sue however, just like a foreign entity not subject to U.S. jurisdiction can bring suit in U.S. courts against U.S. persons.
The exceptions are very explicit contract terms that waive sovereign immunity and/or arbitration clauses. Anyone contracting with an Indian tribe or any entity owned by a tribe must use particular care in forming the contract with that tribe.
In recent years, Indian tribes and their casinos, in particular, have become major economic forces. There are several Indian casinos in and around San Diego County. Anyone contracting with them cannot enforce those contracts normally. The tribes can sue however, just like a foreign entity not subject to U.S. jurisdiction can bring suit in U.S. courts against U.S. persons.
The exceptions are very explicit contract terms that waive sovereign immunity and/or arbitration clauses. Anyone contracting with an Indian tribe or any entity owned by a tribe must use particular care in forming the contract with that tribe.
Tuesday, June 14, 2011
Social Media Is Advertising
Advertising laws are now being applied to social media. Any business with a Facebook account or is on Twitter must understand that those means of communication are legally considered advertising.
I attended a great telephone seminar today that was sponsored by the Intellectual Property Section of the California State Bar regarding advertising law. Among the many topics covered was social media as used by businesses.
The Federal Trade Commission and the courts have held that advertising and unfair competition laws apply to the use of social media by businesses. Furthermore, CAN-SPAM, the Federal anti-spam email law also applies.
Facebook has sued several business entities that spammed Facebook users. The courts held that Facebook had standing to use as an ISP under CAN-SPAM and that CAN-SPAM applied to communications on Facebook.
The FTC recently sued a plastic surgery clinic in Florida for unfair competition. The clinic used various types of social media, including blogs, to create an Internet buzz. Employees provided comments on Facebook and fake customers reviews, among other things.
The FTC sued on the basis that such practices were deceptive advertising. If an employee "Likes" his/her employer's Facebook page and provides favorable comments, and does not reveal that the he/she is an employee, then that is the same as writing a false customer testimonial. The business is liable under false advertising and unfair competition laws.
Any business that might get into any form of social media must have a social media policy that takes these legal issues into account.
Wednesday, June 1, 2011
Stolen notebooks = $23 million judgment
An employee quit his job and took a couple of binders of documents with him to his new job at a competing company. This is a very common scenario; employees taking information or unique content with them when they leave a job. They think that no one will know or care.
However, the outcome proved disastrous for the employee and his new employer. More than 10 years later, the employee and his new employer were hit with a judgment of more than $23 million dollars for copyright infringement.
I tell my clients that copyright law is very strong and can provide powerful remedies for the owners of copyrights. A recently published Federal case illustrates the strength of the U.S. Copyright Act and why one shouldn't steal documents or use misappropriated documents from another company.
In William A. Graham Co. v. Haughy, a Federal appellate court upheld an award of damages of more than $19 million and more than $4.6 million in pre-judgment interest for copyright infringement. The infringement in this case was for the theft and use of two binders of documents that had been prepared by the plaintiff in the case - an insurance brokerage. The binders were used by the plaintiff's agents to sell insurance products.
An employee left the plaintiff's employment and took with him copies of the documents in the binders. He gave the documents to his new employer, a competing insurance brokerage. The new employer gave copies of the documents to its agents and used them for more than a decade before the plaintiff discovered the theft and use.
The plaintiff sued the competing company and its former employer. Although there is a statute of limitations for copyright infringement, it does start to run until the copyright owner discovers, or should have discovered, the infringement. The plaintiff sought profits earned by the defendants that were attributable to the use of the documents in selling insurance products. This is a form of infringement called indirect infringement. The plaintiff wasn't seeking damages for the value of the documents themselves but the profits that were attributable to their use.
A jury found that the documents helped the defendants to attain tens of millions of dollars in profits in selling insurance. The jury found that the portion of those profits attributable to the use of the documents was more than $19 million and added pre-judgment interest of $4.6 million.
The lessons: register your copyrights for all the documents, art and content that you create, and don't steal or use stolen property!
Wednesday, May 18, 2011
ISPs must respond to warrants to identify subscribers
A California court ruled recently that an ISP must respond to warrants demanding the identification of its subscribers.
In criminal hacking case, the court held that the police could force an ISP (in that case, Time Warner) to give the identity and address of a Time Warner subscriber based on a IP (Internet Protocol) address.
The police subsequently searched the defendant's home and found evidence of the defendant hacking into a public school's computer network. The defendant claimed that he had a privacy expectation for his information with Time Warner.
"A subscriber has no expectation of privacy in the subscriber information he supplies to his Internet provider. Therefore, his challenge to a warrant requiring his Internet provider to identify him through his Internet Protocol (IP) number has no merit." wrote the court in People vs. Stipo. The appellate court found no expectation of privacy in the defendant's subscriber information.
This case has some interesting implications, not only for criminal cases, but civil cases as well since a civil subpoena could also be used to find out identifying information as well.
In criminal hacking case, the court held that the police could force an ISP (in that case, Time Warner) to give the identity and address of a Time Warner subscriber based on a IP (Internet Protocol) address.
The police subsequently searched the defendant's home and found evidence of the defendant hacking into a public school's computer network. The defendant claimed that he had a privacy expectation for his information with Time Warner.
"A subscriber has no expectation of privacy in the subscriber information he supplies to his Internet provider. Therefore, his challenge to a warrant requiring his Internet provider to identify him through his Internet Protocol (IP) number has no merit." wrote the court in People vs. Stipo. The appellate court found no expectation of privacy in the defendant's subscriber information.
This case has some interesting implications, not only for criminal cases, but civil cases as well since a civil subpoena could also be used to find out identifying information as well.
Wednesday, May 11, 2011
Employees can be criminally prosecuted for misuse of computers
Employees can be criminally prosecuted for unauthorized and illegal use of computers and computer networks, but only if the employer has a strong and clear computer use policy. A Federal court recently held that an employee can be criminally prosecuted if the employee accessed the employer’s computer system in order to defraud the employer.
In U.S. v. Nosal, No. 10--10038 (9th Cir, April 28, 2011), the 9th Circuit Court of Appeals held that employees could be prosecuted under the Federal Computer Fraud and Abuse Act (the “CFAA”).
CFAA is a statute that was originally intended to allow for the criminal prosecution of hackers. In the Nosal case, three employees used their employer's computer and obtain trade secrets from the employer. The employees then quit and started their own business using the employer's information.
The employees were prosecuted under CFAA by the U.S. Government. Their defense was that CFAA was intended to prosecute hackers who did not have authorization to enter a computer or a computer network. They argued that they should not be criminally prosecuted because they had access to the system. (Of course, the employer could have sued but that is less serious than a criminal prosecution).
However, the government successfully argued when the employees used their user names and passwords to access the employer's trade secrets, they exceeded their authorization and broke the law.
The key to the case: The employer had strong computer use and confidentiality policies. All employees were required to sign agreements that explained what was the employer's confidential information, its sensitive nature, and clearly stated that such information was only to be used for the employer's purpose. All of the employer's computers were restricted access and protected by passwords and user names. So, despite their status as employees with access to the employer's computer system, the court determined that the employees were, legally, no better than hackers.
I have had several instances of business owners who have been ripped off by employees stealing confidential information. They now have a big stick to fight back with.
Businesses should develop clear computer use policies that forbid the use of their computers for anything other than company business, protect their computers with user names and passwords, and have their employees sign well written confidentiality agreements. The threat of criminal prosecution is much more weighty than the threat of a lawsuit and will go farther to keep this type of theft in check.
In U.S. v. Nosal, No. 10--10038 (9th Cir, April 28, 2011), the 9th Circuit Court of Appeals held that employees could be prosecuted under the Federal Computer Fraud and Abuse Act (the “CFAA”).
CFAA is a statute that was originally intended to allow for the criminal prosecution of hackers. In the Nosal case, three employees used their employer's computer and obtain trade secrets from the employer. The employees then quit and started their own business using the employer's information.
The employees were prosecuted under CFAA by the U.S. Government. Their defense was that CFAA was intended to prosecute hackers who did not have authorization to enter a computer or a computer network. They argued that they should not be criminally prosecuted because they had access to the system. (Of course, the employer could have sued but that is less serious than a criminal prosecution).
However, the government successfully argued when the employees used their user names and passwords to access the employer's trade secrets, they exceeded their authorization and broke the law.
The key to the case: The employer had strong computer use and confidentiality policies. All employees were required to sign agreements that explained what was the employer's confidential information, its sensitive nature, and clearly stated that such information was only to be used for the employer's purpose. All of the employer's computers were restricted access and protected by passwords and user names. So, despite their status as employees with access to the employer's computer system, the court determined that the employees were, legally, no better than hackers.
I have had several instances of business owners who have been ripped off by employees stealing confidential information. They now have a big stick to fight back with.
Businesses should develop clear computer use policies that forbid the use of their computers for anything other than company business, protect their computers with user names and passwords, and have their employees sign well written confidentiality agreements. The threat of criminal prosecution is much more weighty than the threat of a lawsuit and will go farther to keep this type of theft in check.
Saturday, May 7, 2011
Copyright Trolls - Don't use stock pictures without a license
Intellectual property has become a hardball arena in recent years. Small businesses steal trademarks and trade secrets from each other. Patent trolls file serial lawsuits extorting money from busineses. Now we have copyright trolls.
A client was recently threatened with legal action by a stock photo company. This stock photo company sells photographs on-line for use in websites. Typically, a website owner or developer can download and use a photo for a royalty of $5.00 to $10.00.
My client had a stock photo on his website. He received a demand letter from a stock photo company that had the rights to sell licenses to use this photo. My client's website developer had downloaded this photo from somewhere (the developer was a little vague).
The stock photo company initially demanded $1,500.00 and threatened to take legal action if not paid. My client discussed the matter with the stock photo company which progressively lowered its demand to around $900.00.
The threat of legal action was serious. If you use a computer to download copyright protected art from a website and use it on your website, you can be liable for up to $150,000 in statutory damages, plus statutory attorneys fees, per download. So, the potential exposure was huge, even for a lousy stock photo.
The stock photo company had an entire division devoted to collecting large fees from companies that had used the stock photo company's photos without authorization. They searched the Internet with special software that looked for their photos and then checked to see if the use of the photos was authorized. If not, then they would aggressively demand outrageous fees and threaten legal action. Furthermore, the photos on the company's website were easily downloaded without payment of a royalty and watermarks were easy to crop out. The company essentially had a copyright troll division searching out the unwary using their cheap photos.
In my client's case, the photo on his website was not registered with the U.S. Copyright Office. Since it was not registered, the stock photo company could not collect the huge statutory damages but only actual damages, in this case about $5.00. My client removed the photo from his website and the stock photo company left him alone when we asked for registration information.
Lessons:
1. Do not use someone else's photos, pictures, videos, etc. on your website.
2. If you are a web developer, pay all royalties necessary for every bit of art on a website.
3. Ask you website developer for proof of a license for all stock photos or other art on a website. You will have to pay the price if the developer stole them.
Labels:
copyright trolls,
copyrights,
stock photographs
Subscribe to:
Comments (Atom)
