Do you work with start-up companies and need a basic understanding of the various intellectual property issues that can arise?
I will be co-presenting in this online seminar that will help you:
- understand the trademark and copyright problems your client may encounter with branding;
- learn how to protect your client’s branding once established;
- familiarize your practice with patents, including what they protect, timing, and strategies to prevent inadvertent loss of patent rights before filing the application;
- understand trade secrets and the importance of non-disclosure and confidentiality agreements;
- recognize intellectual property issues relating to technology, including open source code and the cloud;
- establish a proactive approach toward intellectual property ownership between cofounders, employees, and vendors; understand business names, domain names, promotional issues, and website content concerns.
The program qualifies for 1.5 hours MCLE credit.
I would like to personally invite you to attend the upcoming Law Ed program titled, “Identifying Intellectual Property Issues in Start-Ups,” which I will be co-presenting via live webcast on Tuesday, May 27th.
Presented by the ISBA Business Advice and Financial Planning Section
Co-Sponsored by the ISBA Intellectual Property Section
July 19, 2013
Fifield v. Premier Dealer Services, Inc.
The plaintiff in this declaratory judgment action had been employed by a subsidiary of an insurance company that marketed finance and insurance products to the automotive industry. After a sale of that business, plaintiff’s employment was terminated, but he was offered employment conditioned upon his acceptance of an “Employee Confidentiality and Inventions Agreement” (the agreement) which included non-solicitation and non-compete provisions. The agreement states in pertinent part:
“Employee agrees that for a period of two (2) years from the date Employee’s employment terminates for any reason, Employee will not, directly or indirectly, within any of the 50 states of the United States, for the purposes of providing products or services in competition with the Company (i) solicit any customers, dealers, agents, reinsurers, PARCs, and/or producers to cease their relationship with the Company *** or (ii) interfere with or damage any relationship between the Company and customers, dealers, agents, reinsurers , PARCs, and/or producers *** or (iii) *** accept business of any former customers, dealers, agents, reinsurers, PARCs, and/or producers with whom the Company had a business relationship within the previous twelve (12) months prior to Employee’s termination.”
Plaintiff successfully negotiated with Premier a provision that the restrictive covenants would NOT apply if he was terminated without cause during the first year of his employment (the first-year provision). Three months later, plaintiff resigned, began working for a competitor and sued to have the restrictive covenants held unenforceable stating that plaintiff had no access to confidential and proprietary information. The trial court held that the restrictive Covenants were unenforceable for lack of “consideration” – a legal term of art that generally means a bargained-for exchange of value. The appeals court affirmed.
Defendant argued that the non-solicitation and non-compete provisions were enforceable because the offer of employment was adequate consideration, there was a mutual exchange of promises (employment in exchange for restrictions), and the covenants were pre-employment, not post- employment. Defendant further argued that “the purpose of Illinois law regarding restrictive covenants is to protect against the illusory benefit of at-will employment” which was “nullified by the inclusion of the first-year [non-enforcement] provision in the agreement.”
Plaintiff countered with the argument that the provisions in the agreement are unenforceable because Illinois law requires employment to continue for a substantial period of time and that “Illinois courts have repeatedly held that two years of continued employment is adequate consideration to support a restrictive covenant…regardless of whether an employee is terminated or decides to resign on his own.”
The appellate court agreed with plaintiff citing Brown & Brown, Inc. v. Mudron, 379 Ill. App. 3d 724, 728 (2008) which held that the promise of continued employment in the context of post-employment restrictive covenants may be an illusory benefit where the employment is at-will. “Illinois courts have held that continued employment for two years or more constitutes adequate consideration. Id. at 728-29.”
The Fifield decisions has already generated a great deal of discussion from corporate board rooms to legal blogs. Unfortunately for businesses and their lawyers, the case leaves many unanswered questions.
For example, the court does not discuss whether the outcome would have been different if the employee were a high-level executive with immediate access to a wide range of highly sensitive confidential and proprietary information. At best,mother court simply mentions the plaintiff’s allegations that he had no access to such information.
Another area of uncertainty impacts start-up and early stage businesses. Very young businesses are often highly dynamic and early employees have access to a broad swath of the company’s Intangible assets such as business and revenue models, marketing plans, computer software and hardware and prospective customers, regardless of whether they serve a customer service function or “C-suite” executive function. The requirement that an employee have two years continued employment before a restrictive covenant becomes enforceable ignores the very real dynamic of start-up companies.
Lastly, an important question that went unanswered is whether the employer can offer some other “consideration” besides two years continued employment. For example, is there a pure monetary consideration that would support enforcement of the covenant? What if the covenant only lasted as long as the period of the departing employee’s employment?
If you have restrictive covenants in your agreements with employees, it is strongly recommended that you meet with your lawyer to discuss the impact of this case on these agreements and your business. At the very least, you should carefully review your non-compete and non-solicitation agreements to see if they are supported by adequate consideration. If you have questions or concerns, or just don’t know how to begin, feel free to contact the lawyers at Leavens, Strand, Glover & Adler for a free, in-person or over-the-phone consultation. You can also email the author here: email@example.com.
July 1, 2013
Enacted by Congress in 1986, the Computer Fraud and Abuse Act (CFAA) builds upon existing computer fraud law (18 U.S.C. § 1030). Initially, the CFAA was intended to limit federal jurisdiction to cases “with a compelling federal interest-i.e., where computers of the federal government or certain financial institutions are involved or where the crime itself is interstate in nature.” Notably, the CFAA criminalized certain computer-related acts such as distribution of malicious software code, propagating denial of service attacks as well as trafficking in passwords and similar items. Recently, the CFAA has gained prominence as a bludgeon used to prosecute a wide-range of activities, some broadly labelled “hacking” and other stretching the boundaries of “unauthorized” computer access.
Two recently introduced bills, one by Representative Zoe Lofgren (D-CA) in the House and one by Senator Ron Wyden (D-OR) in the Senate aim to amend the CFAA in hopes of ameliorating application of the CFAA to claims of breach of terms of service, employment agreements. Additionally, with the nickname “Aaron’s Law,” they also seek to limit what some see as the CFAA’s tendency to allow for overzealous prosecution that they claim characterized Aaron Swartz’s case.
In short the bills would amend the meaning of “exceeds authorized access,” changing it to “access without authorization,” which is defined to mean:
“to obtain information on a protected computer”;
“that the accesser lacks authorization to obtain”; and
“by knowingly circumventing one or more technological or physical measures that are designed to exclude or prevent unauthorized individuals from obtaining that information.”
For a well-documented discussion of the application and boundaries of the CFAA, check out the Electronic Frontier Foundations Legal Treatise on civil and criminal cases involving the Computer Fraud and Abuse Act here.
As businesses become ever more dependent on digital assets and systems, a working knowledge of the legal and regulatory framework that defines and protects those assets is paramount.
If you or your executive teams has questions about securing and protecting digital assets, please feel free to contact David M. Adler for a free consultation. LSGA advises a wide range of businesses on creating, protecting and leveraging digital assets as well as computer, data and information security and privacy.
Please tweet, comment on, and forward is article!
David M. Adler | Leavens, Strand, Glover & Adler, LLC
203 North LaSalle Street, Suite 2550
Chicago, Illinois 60601
Direct: (866) 734-2568
Direct Fax: (312) 275-7534
*2012 Illinois Super Lawyer http://bit.ly/gFfpAt
The rapid growth and expansion in the mobile market presents a number of privacy and security issues for mobile software and hardware developers, platform operators, advertisers and marketers who collect, store, use and share consumer information. As awareness of privacy risks grow among consumers, legislators and regulators are increasing scrutiny of mobile privacy and privacy policies in mobile apps.
Businesses operating in the mobile industry are facing a widening array of Regulatory compliance issues. Staying abreast of legal risks and issues can be daunting. How can mobile operators and application developers spot trends and adjust strategies to start competitive? First, keep an eye on FTC activity. Second, monitor new bills coming up in Congress. Third, follow this blog, adlerlaw.wordpress.com.
FTC Privacy Enforcement Actions
Earlier this year, the FTC expanded mobile privacy obligations beyond software to include hardware makers when it announced a settlement with HTC America over charges that HTC failed to use adequate “security by design” in millions of consumer mobile devices. As a result, the company is required to patch vulnerabilities on the devices which include #Smartphones and #Tablets. The settlement, the first action involving a mobile device manufacturer and the new “Privacy By Design” guidelines, sheds some light on the legal risks for mobile device manufacturers and, to some extent, mobile application developers.
Congressional Privacy Laws, Bills & Initiatives
Not surprisingly, federal legislators are taking up the mantle of Consumer Privacy in the area of Mobile Applications. In January 2013, U.S. Rep. Hank Johnson, introduced his mobile privacy bill, The Application Privacy, Protection and Security Act of 2013, or the “APPS Act,”. The bill focuses on transparency, user control and security, mandating that an application 1) provide the user with notice of the terms and conditions governing the collection, use, storage, and sharing of the personal data, and 2) obtain the consent of the user to the terms and conditions. Significantly, the privacy notice is required to include a description of the categories of personal data that
will be collected, the categories of purposes for which the personal data will be used, and the categories of third parties with which the personal data will be shared.
The Bill also requires that application developers have a data retention policy that governs the length for which the personal data will be stored and the terms and conditions applicable to storage, including a description of the rights of the user and the process by which the user may exercise such rights in addition to data security and access procedures and safeguards.
App developers unaware of the data protection requirements may face significant risks and potential harm to their reputation among users of smart devices. If you have concerns about what key data protection and privacy legal requirements apply to mobile applications and the types of processing an app may undertake contact us for a mobile app legal audit. Vague or incomplete descriptions of the ways which a mobile app handles data or a lack of meaningful consent from end users before that processing takes place can lead to significant legal risk. Poor security measures, an apparent trend towards data maximisation and the elasticity of purposes for which personal data are being collected further contribute to the data protection risks found within the current app environment.
Learn more David M. Adler here.