Take-Aways (AI)
  • DPAs should strict­ly fol­low the wor­ding of Art. 28 GDPR to avo­id unin­ten­ded devia­ti­ons and inter­pre­ta­ti­on risks.
  • DPAs must defi­ne pro­ce­s­sing, dura­ti­on and secu­ri­ty mea­su­res in con­cre­te and ongo­ing detail, inclu­ding mini­mum requi­re­ments and tech­no­lo­gi­cal progress.
  • Regu­la­ti­ons on sub­con­trac­tors must ensu­re trans­pa­ren­cy, a genui­ne right of veto, direct claims and audit rights for the controller.

Accor­ding to the GDPR, data con­trol­lers and data pro­ces­sors must con­clude an agree­ment within the mea­ning of Art. 28 (3) of the GDPR (data pro­ce­s­sing agree­ment, ADV). Art. 28 (6) DSGVO pro­vi­des that ADV may, whe­re appli­ca­ble, be based on Stan­dard Con­trac­tu­al Clau­ses (Stan­dard Con­trac­tu­al Clau­ses, SSC) can be based.

On this basis, the Danish Data Pro­tec­tion Aut­ho­ri­ty has sub­mit­ted a draft of such SSCs to the Euro­pean Data Pro­tec­tion Board (EDSA). This is likely to be the model docu­ment available on the authority’s web­site available sam­ple docu­ment act.

Of par­ti­cu­lar inte­rest are the fol­lo­wing comm­ents from EDSA, which, while also rela­ted to pro­po­sed SCCs, are also rele­vant to ADV in indi­vi­du­al cases and could be used by ADV in con­tract nego­tia­ti­ons for argu­ment pur­po­ses. Such nego­tia­ti­ons are incre­a­sing­ly fre­quent and deman­ding in practice.

  • In gene­ral, it makes sen­se to base the wor­ding of the ADV on the wor­ding of Art. 28 GDPR in order to avo­id the impres­si­on that devia­ti­ons are intended.
  • Dura­ti­onADV should not be ter­minable sepa­ra­te­ly from the under­ly­ing ser­vice agree­ment as long as data pro­ce­s­sing con­ti­nues. In prac­ti­ce, ADV start at the latest with the first data pro­ce­s­sing and end at the ear­liest with its end.
  • Data secu­ri­ty mea­su­res:
    • The data secu­ri­ty mea­su­res to be taken by the pro­ces­sor must take account of tech­ni­cal pro­gress in each case – i.e. throug­hout the dura­ti­on of the com­mis­sio­ned processing.
    • The ADV should spe­ci­fy the mini­mum mea­su­res in an annex. In prac­ti­ce, this is often still the case in accordance with an ear­lier regu­la­ti­on of the Ger­man BDSG; howe­ver, the GDPR does not make this mandatory.
  • Sub­con­trac­tor:
    • ADV should list all pre-appro­ved sub­con­trac­tors in an annex so that the con­trol­ler remains spe­ci­fi­cal­ly infor­med of any chan­ges. In prac­ti­ce, this is often not done, at least not when all group com­pa­nies of the pro­ces­sor are appro­ved as subcontractors.
    • In the case of new sub­con­trac­tors, the respon­si­ble per­son must have a genui­ne choice, which requi­res, among other things, a rea­sonable peri­od of time for his or her right of veto.
    • The EDSA express­ly wel­co­mes the obli­ga­ti­on of the pro­ces­sor to pro­vi­de in sub­con­tracts for direct claims of the con­trol­ler against the sub­con­trac­tor, which can take effect, for exam­p­le, in the event of insol­ven­cy of the processor.
    • The respon­si­ble par­ty must have an audit right direct­ly with the subcontractor.
  • Sup­portThe ADV should spe­ci­fi­cal­ly regu­la­te the processor’s sup­port obli­ga­ti­ons. For exam­p­le, they should spe­ci­fy whe­ther the pro­ces­sor only for­wards data sub­ject requests (and if so, with what dead­line) or pro­ce­s­ses them accor­ding to the controller’s ins­truc­tions, and whe­ther or not it may inter­act direct­ly with data sub­jects, etc.
  • Con­cre­tizati­on of pro­ce­s­singAs is well known, the ADV must spe­ci­fy the pro­ce­s­sing by indi­ca­ting the sub­ject and dura­ti­on and the natu­re and pur­po­se of the pro­ce­s­sing, the type of per­so­nal data con­cer­ned and the cate­go­ries of data sub­jects. Accor­ding to the EDSA, this infor­ma­ti­on must be pro­vi­ded “in the most detail­ed man­ner pos­si­ble”, for each indi­vi­du­al pro­ce­s­sing cover­ed by the ADV.