Skip to main content

GDPR - You can't amend the model clauses?

"You can't amend the model clauses!"

I always hear this people saying that  you cannot amend the model clauses, even the lawyer make such statement when I approached them for consultation during singing model contractual clauses. 


We absolutely can amend the model clauses, provided your terms are purely commercial in nature and do not impact the protection of the data, nor the rights of data subjects or supervisory authorities.

Clause 10 of the 2010 Controller-to-Processor Model Clauses:

"The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause." (emphasis added).

In fact, as if to emphasize the point, the 2010 Model Clause even include an "illustrative" and "optional" indemnification clause.

Similar language exists in the 2004 Controller-to-Controller Model Clauses too at Clause VII:

"The parties may not modify these clauses except to update any information in Annex B, in which case they will inform the authority where required. This does not preclude the parties from adding additional commercial clauses where required." (emphasis added).

(In the interests of completeness, the original 2001 Controller-To-Controller Model Clauses do not expressly permit the addition of commercial clauses, which is as good a reason as any to avoid using them.)

And, if that weren't enough, even the Article 29 Working Party has weighed in on this issue with its FAQs on the 2010 Model Clauses: "7)

Is it possible to add commercial clauses to the Model Clauses?

As clearly stated in clause 10, parties must not vary or modify the Model Clauses, but this shall not prevent the parties from adding clauses on business-related issues where required, as long as they do not contradict the Model Clauses."

Any amendments you make should be purely commercial in nature, or intended to explain how some of the model clause rights should work in practice.


For example,

You might choose to limit the liability between the two parties to the model clauses (but not the data subjects!) by reference to liability caps agreed within a master services agreement between the parties.

Alternatively, you might seek a general, upfront consent from the EU data exporter to the data importer's appointment of sub processors, provided the appointed sub processors fulfill the requirements of the model clauses.

Or you might seek to explain how the EU data exporter can exercise its model clause audit rights against the data importer in practice - for example, through reliance on the data importer's independent third party audit certifications or written responses to audit questionnaires etc.

Comments

Popular posts from this blog

MTBF MTTR MTTD

Juniper SRX : Proxy ARP on Juniper SRX

Proxy ARP ( Address Resolution Protocol ) is a technique by which a intermediate network device like router replies to ARP request for a given IP address that is not part of local network.  The router acts as a proxy for the destination device to which the host wants to communicate and provides its own MAC address as the reply. Note: Proxy ARP can help devices on a network reach remote subnets without the need to configure routing or a default gateway. Disadvantages of Proxy ARP Proxy ARP can lead to security and performance issues on the network.  It poses a security risk by making the network vulnerable to ARP spoofinf attack. In attacks, malicious devices can impersonate proxies. Intercept or modify traffic between devices. It may introduce inconsistency into the network’s topology. Addressing scheme by concealing device locations and identities. Let see when and how proxy ARP is configured in Juniper by answering below questions which often comes to our mind ...