Social media as evidence in an employment lawsuit is an area of the law that is, to put it mildly, unsettled.  A recent decision by a Pennsylvania state court weighs in on the side of parties seeking to discover information contained on social-media sites of other parties. In the case of Zimmerman v. Weis Markets, Inc., No. CV-09-1535 (Pa. CP May 19, 2011), the court held that a person who voluntarily posts photos or information to a social-networking profile has no reasonable expectation of privacy in those posts that would prevent their discovery.

The plaintiff-employee, Zimmerman, sued his employer after he was injured on the job by a fork lift. Zimmerman sought lost wages, as well as compensation for pain and suffering as a result of the “permanent diminution in [his] ability to enjoy life and life’s pleasures.” In support of his damages claim, Zimmerman alleged during a deposition that he could no longer wear shorts because he was so embarrassed by scarring on his leg.

Subsequently, counsel for Weis Markets did what all employment attorneys should do—they checked Facebook. On public portions of Zimmerman’s Facebook and MySpace pages, he had posted pictures of himself wearing shorts with his scars clearly visible. Based on the public information available, Weis Markets sought access to the private portions of Zimmerman’s profiles. In his effort to protect this information, Zimmerman claimed that his privacy interest outweighed the need to obtain relevant information in discovery.

So far in this series, we’ve seen how an employee’s LinkedIn profile can (at least arguably) constitute evidence of the following:

In this post, we’ll look at the potential implications of a former employee’s inaccurate LinkedIn profile.

linkedin logo by webtreats

In Asanov v. Legeido, a former employee posted, inaccurately, on his LinkedIn profile that he was the owner of the company by which he was previously employed.  The company alleged that the employee posted the inaccurate information in his profile to help his job search.  The company filed suit against the former employee alleging trademark infringement and intentional interference with its prospective business relations.

Medical-marijuana laws have been blazing a trail across the U.S. since California’s passage of Proposition 215 in 1996.  This year, the Delaware General Assembly began experimenting with marijuana legislation.  With the passage of Senate Bill 17 (“S.B. 17”), on May 11, 2011, which was signed by Governor Markell immediately, Delaware joined the 15 other states and the District of Columbia that have bills legalizing marijuana for medicinal purposes. medical marijuana

S.B. 17 shares many common elements with medicinal marijuana legislation across the country.  But there are some key differences that could have a major impact on Delaware employers.  Essentially, S.B. 17 decriminalizes marijuana under state law in certain limited circumstances. Delawareans with certain specific debilitating medical conditions and who have received certification of a physician, must apply for a state-issued medical marijuana card.  Cardholders are permitted to possess no more than 6 ounces of marijuana and are not permitted to grow their own.

Cardholders will be able to legally purchase marijuana at state-licensed non-profit dispensaries known as “compassion centers.”  There will be only one state licensed dispensary in each county.  The Delaware Department of Health and Social Services, which will administer the registrations for patients, caregivers, and compassion centers, has until July 1, 2012, to develop the regulations needed to implement the new law.

Unlike many other states’ medicinal-marijuana laws, S.B. 17 contains provisions that apply directly to employers. Specifically, although the bill prohibits cardholders from using medicinal marijuana at work, it also bars discrimination against them in hiring, termination, or other terms and conditions of employment. The new law also makes it clear that positive drug tests can’t serve as a basis for discipline of a cardholder unless the person “used, possessed, or was impaired by marijuana” at work during normal working hours.

This point is further clarified by a subsequent provision in the law, which states that cardholders “shall not be considered to be under the influence of marijuana solely because of the presence of metabolites or components of marijuana that appear in insufficient concentration to cause impairment” in a drug test.  Regardless of the the passage of S.B. 17, it is important to note that marijuana use remains illegal under the federal Controlled Substances Act.

Continue reading . . .

Continue reading

Stories of employees who get fired for exercising poor judgment in their use of social media constantly make the news.  There are too many to report, really.  But some can serve as valuable lessons, thereby warranting a bit of special attention.  Here’s one such story, reported by My Fox Philly.comtwitter icon rounded square

Vanessa Williams was a social-media specialist with an economic development agency in Bethlehem, Pa.  That was, at least, until Friday, when she posted the following on the company’s official Twitter account:

We start summer hours today. That means most of the staff leave at noon, many to hit the links. Do you observe summer hours?  What do you do?

In this post, I continue my review of employment-law cases in which LinkedIn played a substantive role.  In the first post in the series, I discussed a case in which an employee’s LinkedIn profile was argued to constitute evidence of a single, integrated enterprise.  In the second post, I discussed a case in which LinkedIn profiles were used to establish successor liability.  In the third post, I discussed the use of a LinkedIn profile to establish an employer’s liability for the acts of its agent.  In this post, I discuss cases in which LinkedIn evidence was argued to constitute evidence in support of a claim for misappropriation of trade secrets. linkedin logo by webtreats

In Sasqua Group, Inc. v. Courtney, an employer sought an injunction against its former employee, who had left to open a competing business.  The employer alleged that its client database constituted a protectable trade secret.  But the court disagreed, giving credit to the testimony of the former employee that she could easily replicate the information contained on the database through Internet searches of LinkedIn, Facebook, and Bloomberg.

This case raises interesting questions about what steps employers should be taking to protect their client contact information from becoming publicly available and, more specifically, whether employers should consider a policy that addresses whether  an employee may or may not upload his work-related contacts to his LinkedIn profile. 

The Third Circuit gave employers new reasons to worry about misclassifying their employees in its decision in Figueroa v. Precision Surgical, Inc., (PDF), C.A. No. 10-4449.  A former employee brought suit seeking to invalidate the non-competition provision in his independent-contractor agreement (“ICA”).  The plaintiff alleged that his former employer had materially breached the contract and, therefore, could not enforce it against him. approved-stamp

During the course of his 6-years with the organization, the plaintiff’s relationship became more like that of an independent contractor.  For example, the company required that the plaintiff: (1) devote 100% of his energy to selling the company’s products; (2) report to his supervisors daily and attend monthly meetings; (3) abide by a dress code; and (4) obtain permission from before giving quotes to certain prospective customers.

As the supervision and reporting requirements became more onerous, the plaintiff objected and, eventually, requested a new contract that clarified his status as an independent contractor.  The company refused and stated that it intended to convert all sales positions to employees, eliminating all independent contractor positions.  When he refused to make the conversion to employee status, his contract was terminated. 

In this post, I continue my review of employment-law cases in which LinkedIn played a substantive role in the outcome of the parties’ dispute. linkedin logo by webtreats

In the first post in this series, I discussed Freire v. Keystone Title Settlement Services, in which the LinkedIn profile of the plaintiff’s manager was argued to constitute evidence that two entities should be considered a single, integrated enterprise. In the second post, I discussed Steinberg v. Young, in which the court found that the LinkedIn profiles of 5 employees constituted evidence that the defendant was the successor entity of the company that previously had employed the plaintiff.

In this post, I discuss a case involving the LinkedIn profile as the basis for holding an employer liable for online comments of another party.

Law360 reports (subscription required), that the Chicago Regional Office of National Labor Relations Board (NLRB) issued a complaint last week against Karl Knauz Motors, Inc., alleging that it violated the National Labor Relations Act NLRB white (NLRA), when it fired an employee for comments he posted on his Facebook page.  The allegations in the complaint are minimal at best.  In sum, it claims that:

On or about June 14, 2010, Charging Party Becker posted on his Facebook page employees’ concerted protest and concerns about Respondent’s handling of a sales event which could impact their earnings.

It then states that Becker was terminated a week later and claims that the termination was intended to discourage employees from engaging in concerted activities. 

Probably not successfully.  But that didn’t stop one employer from trying. In Lee v. PMSI, Inc., the plaintiff sued her former employer for pregnancy discrimination. The employer filed a counterclaim under the Computer Fraud and Abuse Act (CFAA).  The basis for the claim was that Lee engaged in “excessive internet usage” and “visit[ed] personal websites such as Facebook and monitor[ed] and [sent] personal email through her Verizon web mail account.”  That’s right–the employer sued its former employee on the basis that the employee’s on-duty Facebook use constituted a violation of the CFAA. FB Logo

As you may imagine, the federal district court did not find merit in this claim.  U.S. District Judge Steven D. Merryday, of the Middle District of Florida, Tampa Division, granted the employee’s motion to dismiss, finding that the employer had failed to allege either of the two bases for a CFAA violation–that the employee caused damages to the computer system or that the employee obtained information to which she was not entitled.

Additionally, the employer failed to allege that the employee “exceeded authorized access.”  This prong has been the sticking point for those courts that are split as to whether the CFAA–a statute intended for use in the prosecution of computer hackers–should be applied in the employment context.  Although there is a split of authority on when it is that a disloyal employee loses her authorization to access the employer’s computer network, these facts seem to go beyond any reasonable interpretation of the statute. 

In this post, I continue my review of employment-law cases in which LinkedIn played a substantive role in determining the case’s outcome. In the first post in this series, I discussed Freire v. Keystone Title Settlement Services, in which the LinkedIn profile of the plaintiff’s manager was argued to constitute evidence that two entities should be considered a single, integrated enterprise. In this post, I look at a similar case involving successor liability. linkedin logo by webtreats

2. Successor Liability

In Steinberg v. Young, the plaintiff had alleged breach of his employment contract. The claim went to arbitration and the plaintiff won. When he tried to collect on the judgment, though, he claimed that the defendant—the owner or majority shareholder of several corporate entities, including the one that had lost in arbitration—had been fraudulently transferring assets out of the various entities to defeat the plaintiff’s collection efforts.

Contact Information