Techdirt. Stories filed under "contacts"

Can A Company Keep An Employee's LinkedIn Account After They're No Longer Employed?

Mike Masnick — Fri, 30 Dec 2011 04:50:01 PST

Venkat Balasubramani has the story of a bizarre fight between a company, Sawabeh Information Services, and the founders of Edcomm, a company that Sawabeh bought in 2010. A few months later, the founders of Edcomm were fired, and the lawsuits commenced. There are a variety of issues here, and Venkat's post goes through most of them in detail, but I wanted to focus on just one: the fight over who gets to control Dr. Linda Eagle's LinkedIn account. Eagle was one of the founders of Edcomm and the key figure in this fight. Sawabeh claims that Eagle "misappropriated" her own LinkedIn account and the contacts associated with it, by continuing to use it after being fired.

While I can kind of understand some of the legal fights over who gets to control Twitter accounts, the entire point of a LinkedIn account is to represent an individual and their job history. How would it possibly make sense for a company to control an ex-employee's LinkedIn account?

The company seems to think that the LinkedIn account was more like a rolodex. Because (for reasons that are beyond me), Eagle had let others in the company access and manage her account, as soon as she was fired, people at the company accessed her account and then changed her "name" and profile picture to someone else at the company. That would be pretty shocking for her connections, who might not know who the guy was at all. They also tried to do this with the account of one of the other fired founders, but they didn't have his password. Apparently the company asked LinkedIn to hand over the password, and LinkedIn, properly, told the company to get lost.

Either way, the court digs into the "misappropriation" question with the LinkedIn account and refuses to dismiss it out of hand (at this stage of the case), which seems too bad. However, there's an unclear issue of who "developed" the contacts in the account:

The Counterclaim Complaint expressly alleges that, with respect to the LinkedIn account connections and content, "Edcomm personnel, not Dr. Eagle, developed and maintained all connections and much of the content on the LinkedIn Account, actions that were taken solely at Edcomm’s expense and exclusively for its own benefit." ... While Plaintiff argues that Edcomm fails to allege facts that would show that it made a substantial investment of time, effort, and money into creating the cell phone number or LinkedIn account, Edcomm counters that its employees developed the accounts and maintained the connections, which are the route through which Edcomm contacts instructors and specific personnel within its clients. As these conflicting allegations create an issue of fact requiring further discovery, the Court must deny the Motion for Judgment on the Pleadings as to the misappropriation counterclaim.

Of course, I wonder if they're arguing about the wrong thing here. If the company developed the contacts, perhaps it has a right to ask for a copy of the contacts, but the account itself seems like it should belong to Eagle. Part of the problem here is the idea that contacts are some scarce resource. Both parties can have them, and the simplest thing would be, if there is a legitimate claim that the company developed those relationships, to require that their contact info be provided to the company -- but leave the account in the hands of Eagle.

Either way, the case should be a warning for any company that wants to control the LinkedIn accounts of its employees.

Permalink | Comments | Email This Story

Hot News Doctrine Already Being Stretched; Company Says Its Contact Database Is Hot News

Mike Masnick — Thu, 13 May 2010 12:01:23 PDT

In the last year, there's been a sudden resurgence in interest in the concept of "hot news," a doctrine that most people thought was dead and buried, which allowed a judicially-created form of intellectual property on factual information that was deemed to be "hot news." There's no statute that covers this. Just a court decision. And that was a century or so ago. But... the concept started showing back up in court recently, and in March a ruling came down, blocking a website from reporting on news for two hours, using this doctrine. With that on the books, other "hot news" lawsuits were quickly filed.

However, one such recent lawsuit seems to stretch the concept of hot news so far that you can only sit back and admire the audacity of including it in the lawsuit, while fearing the results should a court actually buy it. Thomas O'Toole has the details of what is likely to be a very interesting lawsuit on a few different factors, beyond just the hot news claim (but we'll get to those other issues, so read on...).

The case apparently involves an employee at Goldman Sachs (or potentially multiple employees) who got the username and password of another account holder on a database put together by a company called Ipreo Networks, called "Bigdough." Bigdough is apparently a database of contact info on 80,000 financial industry people. The Goldman Sachs employee(s) logged in with someone else's username/password and downloaded a bunch of information.

This sort of thing happens all of the time. People share logins all of the time. Violating it is basically a terms of service violation, but here the company has broken out the big guns. Yes, it's claiming that the contact info in its database represents "hot news," and Goldman accessing it is a violation of the "hot news" doctrine. Think about that for a second. Contact information. "Hot news?" And, of course, the whole purpose of the "hot news" doctrine is about another publisher republishing the information -- something that Goldman Sachs didn't do here at all. The whole "hot news" claim here seems to stretch the (already questionable) concept way past the breaking point. Hopefully that part gets tossed quickly. Otherwise, imagine what else will suddenly be called "hot news."

But that's not all that's interesting in this case. As O'Toole notes in his report, there are two other interesting legal questions, having to do with the use of someone else's login. First, there's the question of whether or not Goldman Sachs is liable here, even if the actions are just that of a rogue employee (or group of employees). O'Toole points out that the legal standard to get GS on the hook here is pretty damn high. The second question, of course, is whether or not just using a login that someone shared with you is a violation of the Computer Fraud and Abuse Act (CFAA). We recently discussed how there are also a growing series of cases trying to stretch the CFAA to make all sorts of activities classified as "unauthorized access." CFAA was really designed as an anti-hacking law -- which was about people really breaking in to a computer system. If someone simply shares their login credentials with you, does that really count as criminal hacking? If that's the case, an awful lot of people may be guilty of doing so.

So, this should be a fun one to follow. Three separate interesting legal questions, and in all three cases, Ipreo appears to be trying to stretch the law beyond its intentions, so hopefully the court recognizes this. If you want to see the full filing, it's below:

Permalink | Comments | Email This Story

Do You Own Your Social Networking Friends? Or Does Your Employer?

Mike Masnick — Tue, 12 Aug 2008 11:15:00 PDT

In the sales world, you're often judged on the size and quality of your "rolodex" of contacts. No one expects a salesperson jumping from one job to another to somehow "forget" everyone they know -- or to cough up their entire list of contacts to the previous company. Yet that seems to be what happened in the UK. Slashdot points us to the news of a court ruling where a guy was forced to give up his LinkedIn contact list to his former employer after he left the company to start his own business. In this case, the original company had actively encouraged its employees to make use of LinkedIn, even though it was under the individual's control, rather than the employer's.

Expect to see plenty more lawsuits like this going forward. For many users of social networks from LinkedIn to MySpace to Facebook, the connections you make blur the lines between professional and personal -- and the questions of who actually "owns" those contacts will become a legal issue that the courts will decide over and over again. Of course, the truth is that this is a silly debate. No one "owns" a contact in the first place. If the company has a rule requiring employees to hand over contacts to the company, then it should employ a CRM system which the company controls. Otherwise, reaching into a personal social networking account seems to go beyond what's reasonable.

Permalink | Comments | Email This Story