Amazon Says No To Blippy

Michael Arrington

J. Michael Arrington (born March 13, 1970 in Huntington Beach, California) is a serial entrepreneur and the founder of TechCrunch, a blog covering startups and technology news. Arrington attended Claremont McKenna College (BA Economics, 1992) and Stanford Law School (JD, 1995) and practiced as a corporate and securities lawyer at two law firms: O’Melveny & Myers and Wilson Sonsini Goodrich... → Learn More

Saturday, February 6th, 2010

Screen shot 2009-12-11 at 11.55.23 AMBlippy, the Twitter-like service that lets users publish the details of all their purchases, is just a couple of months old. But it already got Stephen Colbert’s attention (thumbs up). And now it has Amazon’s too (thumbs down).

Cofounder Philip Kaplan first mentioned that Amazon had turned off Blippy’s access to the service on an episode of TWiST with Jason Calacanis. I spoke to Kaplan tonight about Amazon’s reaction to Blippy.

He says they didn’t block Blippy, but simply insisted that the service stop pulling user purchase data, and erase all historical data they had already collected. They were also summoned to Seattle to speak with a “high ranking executive” of the company. Blippy complied (with both the summons and the demand to stop accessing user data).

Kaplan is soft stepping around the Amazon issue, and is hoping to come to some agreement with the company to allow them to access data in the future. He says “We believe our users feel strongly, as we do, that it is their right to access and use their data however they want. We’re optimistic that Amazon will come to the same conclusion.”

None of the other thirteen companies Blippy takes data from have complained, Kaplan says. And he notes that users must actually request data to be collected before Blippy begins to do that.

There is certainly an issue with how Blippy collects data – by storing user credentials on their own servers. But Blippy says they use APIs to log users in when available. And that may be the issue Amazon has with Blippy.

But it doesn’t explain why they’re insisting Blippy delete historical data that’s already been collected. The users have given their permission, and in fact have indicated that they want this data to be moved to Blippy. And it is the users’ data, after all. Amazon would be smart to remember that.

Perhaps, and I’m speculating here, there’s a reason Amazon doesn’t want all this data published. They’ve engaged in variable pricing in the past to test the demand curve, for example. They certainly may be using it again.

Company: Blippy
Website: blippy.com
Launch Date: December 11, 2009
Funding: $12.9M

Blippy is a service that allows users to automatically share their credit card transactions as they make them. This includes the place the purchase was made, the amount, and in some cases, the item. This is all placed in a social stream where other Blippy users can comment on and “like” the various items. In May 2011, Blippy shut down its service.

→ Learn more

Philip Kaplan (@pud) is a programmer and entrepreneur in San Francisco, CA. He is the founder of Fandalism (social network for musicians), TinyLetter (email service provider, acquired by MailChimp), Blippy (venture-backed social commerce company), and AdBrite (a large Internet ad network). He also developed several iPhone apps, including the best selling “Punch Your Friends.” In 2010, Philip was entrepreneur-in-residence at Charles River Ventures. Philip founded and sold several other businesses including F-ckedcompany.com and PK Interactive,...

→ Learn more

“Jason McCabe Calacanis was CEO and co-founder of Weblogs, Inc., a network of widely read blogs including Engadget – ranked # 1 by Technorati, Joystiq, Autoblog, and Blogging Baby. Founded in January 2004, Weblogs, Inc. became a wholly owned subsidiary of AOL in November of 2005. Calacanis maintained editorial supervision over Weblogs, Inc. as a senior vice president of AOL. In June 2006, Calacanis relaunched Netscape, the iconic browser owned by AOL and was named its general manager....

→ Learn more

Tags: ,
blog comments powered by Disqus