TOTAL: {[ getCartTotalCost() | currencyFilter ]} Update cart for total shopping_basket Checkout

Canada Dashboard Digest | Notes from the IAPP Canada Managing Director, January 5, 2018 Related reading: Countries collaborate to combat rapid use of spyware 

rss_feed

""

Happy New Year!

I hope you had a nice little holiday, enjoyed some good times with friends and family, and maybe ate a little too much. Heck, that’s why gym memberships always thrive at this time of year, right?

I’m still in holiday mode, having taken the time yesterday to play hooky and watch the latest Star Wars movie. I really don’t understand why some people didn't like it. I think it’s great, except for maybe that part where he’s milking the alien and drinking the fluid that squirts out! That scene I could have done without. That’s all I’m going to say, because my kids warned me not to write any spoilers into the Digest. And, admittedly, there's no connection to privacy. Although I stand to be corrected if anyone can make a link.

One thing I did do work-wise this week was catch up on some privacy news. You should take the same opportunity now by reading the blurbs we have gathered for you below. 

The one news story that caught my attention was the class action settlement of 17.5 million dollars. It still needs court approval, but the fact that both sides agree to this amount is quite remarkable. The case is about the lost hard drive that contained the personal information of over half a million students who had student loans registered with the federal government. Each affected individual is entitled to an automatic $60. Meanwhile, add it all up and the plaintiff-side lawyers who took on the risk are going to get paid nicely. Personally, I think it’s telling that we’re starting to see real consequences for doing privacy badly. I'm just irked that this time around it was the federal government and, as such, I have to foot the bill as a taxpayer.

Enjoy this and other privacy news stories, and have a great weekend. 

Comments

If you want to comment on this post, you need to login.