CASL enforcement

As most people know, the Canadian Anti-Spam Law (CASL) went into effect July 1 of this year. This month, the CRTC concluded its first investigation.

A computer reseller based in Saskatchewan was placed under investigation by the CRTC after large numbers of complaints were made through the Spam Reporting Centre. The CRTC revealed that a server owned by the computer reseller sent millions of e-mail spam messages through Saskatchewan-based internet service provider, Access Communications. […] Exercising its discretion, the CRTC chose not to fine the business. CRCT Concludes First Enforcement

One of the biggest complaints about CASL was that innocent senders who just happened to inadvertently violate CASL would be hit with business ending fines. But the agencies tasked with enforcement have discretion. There are no minimum fines that they have to impose, they have discretion. Their first enforcement action demonstrates this. It would be easy for the CRTC to impose business ending fines on their initial case, as a warning to other senders. They didn’t do that.
CRTC has demonstrated they’re willing to work with businesses that violate CASL. That gives all senders a little bit of breathing room for the next 2.5 years. Come July 1, 2017, individual users can exercise their private rights of action against senders. The PRoA is really an unknown variable. How many Canadians are annoyed enough by unsolicited emails that they’re willing to take senders to court? I don’t really know.

Related Posts

Happy Canada Day, CASL now in effect

It’s Canada Day, and this year it has special connotations for email senders who are in Canada or sending to Canadian residents.
CASL is now in effect. For in depth guidance, go visit Matt Vernhout’s excellent series on CASL.  But for those of you who just want the Cliff notes here’s the high points
If you are in Canada or you are sending to residents in Canada:

Read More

Have fun storming the CASL!

I’ve given Humble Bundle my (tagged) email address a bunch of times – as part of purchases, as my username on their website, to download games and books I’ve bought.
And, naturally, they’ve sent me newsletters announcing when they have new sales. Did I check a checkbox or uncheck a checkbox? I don’t remember, and don’t really care. It’s a company I have a real relationship with and have purchased from, they’re sending content I want to see, and I trust them not to misuse my address and to honour an unsubscription request.
So … probably opt-in, and I’m fairly sure they’ve confirmed that it’s my email address. But did they explicitly tell me they’d use my email address for a newsletter? I and my email archive don’t remember that far back, and it’s quite possible that Humble Bundle’s current staff and records don’t either.
In todays newsletter, right above their talking about their summer sales, they had this:
 
All_Mailboxes__Found_118_matches_for_search_
 
They’re confirming that I want to keep getting newsletters, and stressing why I want to keep getting them. Their database probably dates back to the iron age, or at least 2010, and my clicking on the big, friendly green button both lets them know that I’m an engaged subscriber and lets them record in their database that “Yes! This subscriber has explicitly said they want our newsletters!”.
Gradually adding that information to their subscriber database will let them better make decisions in the future about what content to send, how often, whether to try and reengage with a subset of their subscribers.
Oh, and there’s CASL, of course.
If you or your recipients have a Canadian presence you have a little less than eighteen months to make sure you have documented, explicit consent from any recipients for whom you only have implicit (e.g. business relationship) consent or for whom you’ve lost the original records.

Read More

CASL is more privacy law than anti-spam law

Michael Geist, a law professor in Canada, writes about the new CASL law, why it’s necessary and why it’s more about privacy and consumer protection than just about spam.

Read More