GDPR may require changes to Canadian data contracts
2019-03-06
Canadian businesses may need to account for the European Union’s wide-reaching General Data Protection Regulation (GDPR) in their processing contracts, Toronto business lawyer Peter Murphy tells AdvocateDaily.com.
The GDPR came into effect in May last year, replacing the looser Data Privacy Directive (DPD) which had governed the handling of personal data within the EU for more than two decades.
Murphy, partner with Shibley Righton LLP, says Canadians may wonder why they must comply with a regulation from a foreign jurisdiction, but he explains that GDPR’s reach is extensive.
"The GDPR applies to any business that engages in data processing related to goods and services offered to EU residents, regardless of where their business is located," he says.
“It also applies to businesses that monitor the behaviour of individuals where the behaviour takes place in the EU,” Murphy adds. “Where the GDPR applies, Canadians may be surprised by some of the resulting requirements.”
Whatever difficulties that compliance with the new regulation imposes on data processing businesses in this country, Murphy says they can’t afford to ignore the GDPR, thanks to the eye-watering nature of its potential penalties. Under the GDPR, fines for non-compliance may be imposed in amounts up to the larger of four per cent of an organization’s global turnover, or 20 million euros — about $30 million Canadian.
“That’s way beyond any fines that may be awarded under Canadian privacy laws,” Murphy says.
Although companies that are currently in compliance with Canada’s federal Personal Information Protection and Electronic Documents Act (PIPEDA) face a smaller jump than their counterparts south of the border, Murphy says there is still a significant gap they will need to bridge to achieve GDPR compliance.
“Canadian privacy laws are more onerous than the American ones, but they still tend to be principle-based and open to interpretation, whereas the GDPR is more prescriptive and specific in terms of the obligations it imposes,” he says.
For example, Murphy says the GDPR divides its data processing requirements into two categories: those for “data controllers” who determine the purpose and means of processing certain personal data, and a separate set for “data processors,” who process data on behalf of controllers.
“It’s important to understand the distinction,” says Murphy, adding that the GDPR lays out specific requirements for inclusion in contracts concerning the processing of personal data. These requirements include the following:
Murphy says that covering the GDPR properly in data processing contracts is more than just an exercise in legal compliance.
"Complying with these requirements may impose unanticipated costs on one or more parties to these agreements,” Murphy says. “Taking the GDPR's requirements into account is of great importance now that the GDPR is in force, not only to avoid fines but also to properly allocate obligations arising from compliance and related costs among the parties to data processing contracts.”