Take-Aways (AI)
  • Liechtenstein’s recom­men­da­ti­on makes a clear distinc­tion bet­ween “era­su­re” (irrever­si­ble obli­te­ra­ti­on) and “des­truc­tion” (inclu­ding des­truc­tion of the data carrier).
  • The draft of the Swiss DPA allo­ws data con­trol­lers to choo­se bet­ween era­su­re and des­truc­tion; stan­dard era­su­re orders are alre­a­dy dee­med to be erasure.

The data pro­tec­tion office of the Prin­ci­pa­li­ty of Liech­ten­stein has recent­ly laun­ched a Recom­men­da­ti­on for the des­truc­tion of per­so­nal data published. The docu­ment is available as a PDF at the fol­lo­wing link: www.llv.li/files/dss/pdf-llv-dss-empfehlung-vernichtung-von-daten.pdf. Like the draft Swiss DPA, the Recom­men­da­ti­on distin­gu­is­hes bet­ween “era­su­re” and “des­truc­tion” of data. It defi­nes the terms as follows:

At Dele­ti­on the Irre­trie­va­ble des­truc­tion or ren­de­ring unre­co­gnizable and thus under­s­tood to mean the irrever­si­ble rem­oval of per­so­nal data stored in data coll­ec­tions. This means that pre­vious­ly exi­sting per­so­nal data is no lon­ger pre­sent or unre­co­gnizable after the pro­cess of dele­ti­on – the era­su­re pro­cess – and can no lon­ger be recons­truc­ted. Any data car­ri­er can usual­ly be writ­ten to and used again after deletion.

At the Des­truc­tion the data car­ri­er its­elf is also destroyed:

In col­lo­quial lan­guage, the term des­truc­tion is used when the infor­ma­ti­on or the per­so­nal refe­rence also the data car­ri­er its­elf is destroyed.

The docu­ment leans obvious and is based on the same con­cept of dele­ti­on. This is not defi­ned in the GDPR; howe­ver, the GDPR howe­ver, also under­stands dele­ti­on as a pro­cess that exclu­des the per­cep­ti­on of the infor­ma­ti­on embo­di­ed in the date wit­hout dis­pro­por­tio­na­te effort (wher­eby it is not only a mat­ter of the pos­si­bi­li­ties of the per­son responsible).

The draft FADP does not con­tain a legal defi­ni­ti­on of des­truc­tion or dele­ti­on. Howe­ver, the mes­sa­ge comm­ents on this as follows:

The term “Destroy” is stron­ger than the term “dele­te” and implies that the data is irre­trie­v­a­b­ly destroy­ed. If the data exists on paper, this is to be burn or to shred. The des­truc­tion of elec­tro­nic data is more dif­fi­cult. If the data was trans­mit­ted by means of a CD or a USB stick, the data car­ri­er must be ren­de­red unusable and all copies must be hand­led in such a way that the data can no lon­ger be made rea­da­ble. In the case of per­so­nal data that was trans­mit­ted as an attach­ment to an e‑mail, any inter­me­dia­te sto­rage of this e‑mail must also be destroy­ed. Usu­al dele­ti­on com­mands or a mere refor­mat­ting do not repre­sent a des­truc­tion, but a dele­ti­on.

The­re are signi­fi­cant dif­fe­ren­ces to the GDPR and the recom­men­da­ti­on from Liech­ten­stein: Accor­ding to the embas­sy com­mon dele­te com­mands” are alre­a­dy suf­fi­ci­ent for a dele­ti­on. This is under­lined by the fact that “des­truc­tion” as defi­ni­ti­ve dele­ti­on refers not only to data car­ri­ers – as in the Liech­ten­stein recom­men­da­ti­on – but also to data. Con­ver­se­ly, this con­firms that “nor­mal” dele­ti­on does not con­sti­tu­te defi­ni­ti­ve dele­ti­on. This is cle­ar­ly sta­ted in the mes­sa­ge fol­lo­wing the lea­ding decis­i­on BVGE 2015/13.

Inte­re­st­ingly, the draft FADP nowhe­re expli­ci­t­ly requi­res des­truc­tion; it speaks of “des­truc­tion or dele­ti­on” in each case. Thus, in each case it should be be left to the per­son respon­si­ble, whe­ther it “dele­tes” or “destroys”, in appli­ca­ti­on of the prin­ci­ples of data secu­ri­ty and thus on the basis of a risk assessment.

For com­pa­nies in the pro­cess of imple­men­ta­ti­on, this is good news: If the GDPR stan­dard is ancho­red as a group stan­dard, which is com­mon for ope­ra­tio­nal rea­sons and legal risk con­side­ra­ti­ons, no adap­t­ati­on for the GDPR will be requi­red in the area of dele­ti­on concepts.