<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
<title>Techdirt. Stories about &quot;icbc&quot;</title>
<description>Easily digestible tech news...</description>
<link>http://www.techdirt.com/</link>
<language>en-us</language>
<image><title>Techdirt. Stories about &quot;icbc&quot;</title><url>http://www.techdirt.com/images/td-88x31.gif</url><link>http://www.techdirt.com/</link></image>
<item>
<pubDate>Thu, 13 Aug 2009 17:45:00 PDT</pubDate>
<title>Insurance Company Sues Website Offering Claim Advice... Saying It's Infringing</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20090811/0255025840.shtml</link>
<guid>http://www.techdirt.com/articles/20090811/0255025840.shtml</guid>
<description><![CDATA[ Yet another example of "entitlement culture," as companies misuse intellectual property law to try to prop up questionable business models, comes in this latest story, sent in by Jesse.  An insurance company in British Columbia, Canada, called ICBC, is <a href="http://www.theprovince.com/news/ICBC sues claim advice website/1867453/story.html" target="_new">suing a website that offers advice on how not to get your insurance claim denied</a>.  Obviously, for policy holders, this is useful information.  But, to ICBC, it's copyright infringement.  Well, at least that's what the article linked above says.  I have a hard time seeing how there's a copyright claim here -- especially since the ICBC spokesperson states that they don't have a problem with the content, and that they just have to protect their trademark.  So... let's give ICBC the benefit of the doubt and assume the newspaper reporter screwed up, and this is actually a trademark claim rather than a copyright claim (professional reporters for the win, again!).  Even so, this would seem like a typical "gripes site" type discussion where, as long as it's clear that the site in question is not run by the company, there shouldn't be any problem.  In fact, given that the site provides useful information for ICBC customers, it's difficult to see what the problem is, other than that the insurance company doesn't like its policy holders to learn how to stand up for their rights.<br /><br /><a href="http://www.techdirt.com/articles/20090811/0255025840.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20090811/0255025840.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20090811/0255025840.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>entitlement-culture</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20090811/0255025840</wfw:commentRss>
</item>
<item>
<pubDate>Mon, 18 May 2009 04:51:43 PDT</pubDate>
<title>Canadian Insurance Company Snooped On Jurors Insurance Claims During Trial</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20090515/0233034895.shtml</link>
<guid>http://www.techdirt.com/articles/20090515/0233034895.shtml</guid>
<description><![CDATA[ We've seen it over and over again -- when people have access to large databases of information, it's almost impossible for them to resist the temptation to abuse the info.  The latest example comes via <a href="http://twitter.com/PrivacyLaw/statuses/1799990298" target="_new">Michael Scott</a>, who points us to the news that the Insurance Corporation of B.C. (ICBC) was caught <a href="http://www.vancouversun.com/news/ICBC admits snooping into jurors private files/1593554/story.html" target="_new">checking its own database to examine the claim histories of potential jurors</a> in a trial in which the company was involved.  Not surprisingly, this is a massive breach of Canadian privacy laws and also raises questions about the jury itself.  The judge in the case is now trying to find out if ICBC has done this in other cases as well.  ICBC seems to be bending over backwards to say this won't happen again and that it's put in place safeguards, but it's not clear why it happened in the first place.<br /><br /><a href="http://www.techdirt.com/articles/20090515/0233034895.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20090515/0233034895.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20090515/0233034895.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>that-seems-bad</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20090515/0233034895</wfw:commentRss>
</item>
</channel>
</rss>