Take-Aways (AI)
  • The Art. 29 Group sets out gui­ding prin­ci­ples on trans­pa­ren­cy, which give tho­se respon­si­ble a high degree of dis­creti­on in prac­ti­cal implementation.
  • The recom­men­ded “laye­red” approach applies to con­tent and time pro­vi­si­on; com­ple­te expl­ana­ti­ons must also be available as a document.
  • Acti­ve noti­fi­ca­ti­on of the data sub­jects is requi­red for com­pre­hen­si­ve adjust­ments to data pro­tec­tion decla­ra­ti­ons, other­wi­se publi­ca­ti­on is sufficient.
  • For excep­ti­ons pur­su­ant to Art. 14 para. 5 lit. b (dis­pro­por­tio­na­te effort), pro­tec­ti­ve mea­su­res are man­da­to­ry; publi­ca­ti­on on the Inter­net can be such a measure.

The Artic­le 29 Working Par­ty published the final ver­si­on of Working Paper 260 on trans­pa­ren­cy on April 13, 2018 (WP260 rev.01). A com­pa­ri­son of this ver­si­on with the hea­ring ver­si­on published in Janu­ary 2018 The fol­lo­wing is a sum­ma­ry of the situa­ti­on – which is, of cour­se, not exhaus­ti­ve. – A Com­pa­ri­son docu­ment (red­li­ne) is available here: PDF.

    • The Art. 29 Group empha­si­zes that not all nuan­ces can be map­ped and that the goal is for respon­si­ble par­ties to under­stand “at a high level” what the Group means by trans­pa­ren­cy – unders­coring that the prin­ci­ples are gui­ding, but that the­re is dis­creti­on in imple­men­ting transparency;
    • In gene­ral, howe­ver, the approach of the Art. 29 Group has not beco­me more prag­ma­tic. Some refe­ren­ces – most­ly in nuan­ces – even repre­sent tightenings;
    • when Data pro­tec­tion decla­ra­ti­ons to be adapt­ed due to the GDPR, this should be actively com­mu­ni­ca­ted to the affec­ted per­sons if the chan­ges are com­pre­hen­si­ve. Other­wi­se, publi­ca­ti­on is sufficient;
    • spe­cial con­side­ra­ti­on must be given to child­ren in the wor­ding and design of data pro­tec­tion decla­ra­ti­ons if the decla­ra­ti­on con­cerns a pro­ce­s­sing ope­ra­ti­on which is aimed at child­ren or which is likely to affect child­ren of lite­ra­te age to a par­ti­cu­lar extent;
    • the “laye­red” approachThe group recom­mends that the laye­red approach be applied not only to elec­tro­nic decla­ra­ti­ons, but also to the timing of the pro­cess: If just-in-time noti­ces are pro­vi­ded (e.g., as mou­se-over text in an online form), the enti­re state­ment must also be available as a docu­ment; this, too, repres­ents a laye­red approach in the group’s view. The­re are addi­tio­nal comm­ents on the “laye­red” approach;
    • inde­ter­mi­na­te for­mu­la­ti­ons (“may”, “might”, “some”, “pos­si­ble” etc.) should be avo­ided. If they are used nevert­hel­ess, the per­son respon­si­ble should be able to explain why such terms are neces­sa­ry and that they do not vio­la­te the prin­ci­ple of fair­ness – after all;
    • at Editing chan­ges a new noti­fi­ca­ti­on should be made accor­ding to the opi­ni­on alre­a­dy expres­sed so far – the Working Par­ty pro­po­ses new cri­te­ria to be taken into account in this context;
    • the pri­va­cy group gives a new exam­p­le of the Excep­ti­on in Art. 14 (5) lit. b DSGVO (“dis­pro­por­tio­na­te effort”):

      A lar­ge metro­po­li­tan hos­pi­tal requi­res all pati­ents for day pro­ce­du­res, lon­ger-term admis­si­ons and appoint­ments to fill in a Pati­ent Infor­ma­ti­on Form which seeks the details of two next-of-kin (data sub­jects). Given the very lar­ge volu­me of pati­ents pas­sing through the hos­pi­tal on a dai­ly basis, it would invol­ve dis­pro­por­tio­na­te effort on the part of the hos­pi­tal to pro­vi­de all per­sons who have been listed as next-of-kin on forms fil­led in by pati­ents each day with the infor­ma­ti­on requi­red under Artic­le 14

    • If a data con­trol­ler invo­kes this excep­ti­on, it is obli­ged to take pro­tec­ti­ve mea­su­res pur­su­ant to Artic­le 14 (5) (b) GDPR. The Working Par­ty now con­firms that such a pro­tec­ti­ve mea­su­re can con­sist of, for exam­p­le, posting a data pro­tec­tion state­ment on the Inter­net that crea­tes the cor­re­spon­ding transparency.