The Bava­ri­an Sta­te Office for Data Pro­tec­tion Super­vi­si­on (BayL­DA) has issued the Acti­vi­ty report for year 2019 published – below are refe­ren­ces to some of the points rai­sed in it (sel­ec­tion):

Com­plaints and consultations

First of all, 2019 was again a sharp increa­se in com­plaints and “con­trol requests” (reports of data pri­va­cy vio­la­ti­ons by per­sons not affec­ted by them), which are recei­ved faster than they can be processed:

In con­trast, the Con­sul­ting volu­me drop­ped shar­ply after a 2018 spike, pos­si­bly due to resour­ces available online:

What also increa­sed shar­ply were the Data pro­tec­tion brea­ches:

Staf­fing in com­pa­ri­son with the FDPIC

Per­son­nel deve­lo­p­ment at Bayl­DA is also interesting:

  • Until 31.12.2016: 16 positions
  • Until 31.12.2017: 20 positions
  • Until 31.12.2018: 24 positions
  • Until 31.12.2019: 33 posi­ti­ons

For com­pa­ri­son the Per­son­nel deve­lo­p­ment at the FDPIC accor­ding to its last acti­vi­ty report, as far as the area of DPA (excl. BGÖ) is concerned:

  • 2005: 22 digits
  • 2010: 23 digits
  • 2018: 24 digits
  • 2019: 24 digits

The FDPIC the­r­e­fo­re curr­ent­ly has around 27% fewer posts in the area of data pro­tec­tion (excl. BGÖ) than the BayL­DA. Howe­ver, Bava­ria has near­ly twice as many inha­bi­tants as Switz­er­land. At the same time, unli­ke the FDPIC, the BayL­DA deals exclu­si­ve­ly with pri­va­te data pro­tec­tion (for public bodies, ano­ther aut­ho­ri­ty is respon­si­ble, the Sta­te Com­mis­sio­ner for Data Protection).

It may be fur­ther assu­med that the acti­vi­ties of the FDPIC within data pro­tec­tion (excl. BGÖ) may result in 35% the pri­va­te sec­tor concerns.[mfn]Based on the 2019 acti­vi­ty report. In the area of con­sul­ta­ti­on, the pri­va­te sec­tor accounts for about half of the effort, but some DPA acti­vi­ty are­as con­cern only the public sec­tor, e.g., par­ti­ci­pa­ti­on in legis­la­ti­on or coope­ra­ti­on with the can­tons. Howe­ver, the acti­vi­ty report does not break down the acti­vi­ties as a who­le bet­ween the pri­va­te and public sec­tors, and some figu­res appear contradictory.[/mfn] Accor­ding to this, the FDPIC has at its dis­po­sal for the pri­va­te sec­tor has appro­xi­m­ate­ly the same staf­fing as the BayL­DA for com­pa­ra­ble are­as of respon­si­bi­li­ty, but pro­ba­b­ly with con­sider­a­b­ly fewer tasks, sin­ce the FDPIC today has no aut­ho­ri­ty to issue orders and also has few data pro­tec­tion breach noti­fi­ca­ti­ons to deal with in the pri­va­te sec­tor. Per­haps this explains why the FDPIC, despi­te the scar­ci­ty of resources[mfn]The FDPIC has been pro­mi­sed a total of ten addi­tio­nal posi­ti­ons, but the­se have not yet been approved[/mfn], takes the time to also deal with tasks in the pri­va­te sec­tor that do not actual­ly fall within his area of respon­si­bi­li­ty, but – not out of dog­ma­tic, but out of legal poli­cy con­cerns – are assi­gned to the con­su­mer pro­tec­tion clo­se to home are to be attri­bu­ted to. This inclu­des, for exam­p­le, the demand for trans­pa­ren­cy in con­stel­la­ti­ons invol­ving anony­mous data, as well as the (legal­ly unfoun­ded) con­cern that con­sent is requi­red when pro­ce­s­sing per­so­nal data requi­ring spe­cial pro­tec­tion and per­so­na­li­ty pro­files. In any case, it would also be inte­re­st­ing to publish the avera­ge tasks per employee or per posi­ti­on, as the BayL­DA does.

The FDPIC’s call for more resour­ces is nevert­hel­ess not unju­sti­fi­ed (in any case, data pro­tec­tion is hel­ped more by enfor­cing the DPA than by mere­ly tigh­tening the law), but it would meet with more under­stan­ding if the FDPIC were to place more empha­sis in its acti­vi­ties on delinea­ting its acti­vi­ties along the scope of the DPA and were to pro­ce­ed in an equal­ly risk-based man­ner, as is requi­red of data pro­ces­sors – and place less empha­sis on per­cei­ved data pro­tec­tion and con­su­mer pro­tec­tion, on the panacea of awa­re­ness-rai­sing, and on respon­ding to reports by the media and cer­tain acti­vists with poli­ti­cal con­cerns. Media covera­ge and public inte­rest are not the same thing, and the stron­ger the respon­se to media reports, the grea­ter some risk of instru­men­ta­lizati­on and thus a thre­at to independence.

Con­trols and tests

  • In this area, the BayL­DA has focu­sed on, among other things. Cyber­se­cu­ri­ty and online track­ing focu­sed becau­se the­se topics were more fre­quent­ly the sub­ject of com­plaints (i.e.: what is visi­ble to the out­side world is not sur­pri­sin­gly more likely to be the sub­ject of com­plaints). In this regard, the BayL­DA states:

    Alt­hough we only use web­sites of lar­ger com­pa­nies, some of which are listed on the stock exch­an­ge, with regard to long-estab­lished Safe­ty requi­re­ments exami­ned, we found that num­e­rous short­co­mings were in place. The secu­ri­ty mea­su­res taken often had to be clas­si­fi­ed as ina­de­qua­te. […] Also in the area Track­ing The result of our audit was deso­la­te out: None of the web­sites audi­ted met the requi­re­ment for per­mis­si­ble con­sent under the GDPR, even though the web­sites had inte­gra­ted third-par­ty track­ing tools and thus initia­ted data pro­ce­s­sing by third-par­ty services.

    Fur­ther details on the­se audit results can be found here.

  • In the area of Accoun­ta­bi­li­ty (“Accoun­ta­bi­li­ty”; Art. 5 (2) DSGVO; wit­hout coun­ter­part in the E‑DSG), the BayL­DA states:

    Despi­te this and the num­e­rous publi­ca­ti­ons by the super­vi­so­ry aut­ho­ri­ties as a who­le, many respon­si­ble par­ties were over­whel­med in terms of accoun­ta­bi­li­ty. Some com­pa­nies thought it was enough to print out the website’s pri­va­cy poli­cy to the super­vi­so­ry aut­ho­ri­ty or decla­re, “Adver­ti­sing is a legi­ti­ma­te inte­rest and
    that’s why you’­re allo­wed to do that”.

    To the neces­sa­ry evi­dence belon­ged rather:

    • Direc­to­ry of pro­ce­s­sing acti­vi­ties (Art. 30 DS-GVO),
    • Data pro­tec­tion impact assess­ment (Art. 35 GDPR),
    • appro­ved rules of con­duct (Art. 40 GDPR),
    • Cer­ti­fi­ca­ti­on (Art. 42 GDPR),
    • Data breach noti­fi­ca­ti­ons (Artic­le 33 of the GDPR) and
    • Con­tracts for com­mis­sio­ned pro­ce­s­sing (Art. 28 (3) DS-GVO)

    In addi­ti­on, accoun­ta­bi­li­ty could through other data pro­tec­tion docu­men­ta­ti­on take place, e.g. through this:

      • Con­tract Management
      • Con­cepts for ensu­ring the rights of data subjects
      • Pro­ce­s­ses of the data pro­tec­tion organization
      • Intro­duc­tion of data pro­tec­tion guidelines
      • Inter­nal or exter­nal audits
      • Employee trai­ning
      • Legal opi­ni­on
      • Cer­ti­fi­ca­ti­ons accor­ding to DIN and ISO standards
      • Other records such as reports, memos, or minutes.

    The BayL­DA test cata­log for accoun­ta­bi­li­ty and thus a good check­list for the imple­men­ta­ti­on of the GDPR can be found here: Link.

Affec­ted rights

No-Gos” in the Right to Information

With refe­rence to the right to infor­ma­ti­on, the BayL­DA first notes the fol­lo­wing “no-goes” of the respon­si­ble par­ties, but also of the applicants:

  • Respon­si­ble:
    • Igno­ring requests for infor­ma­ti­on when iden­ti­ty is in doubt;
    • Infor­ma­ti­on about exclu­si­ve­ly master data as per­so­nal data;
    • Invo­ca­ti­on of dis­pro­por­tio­na­te effort wit­hout expl­ana­ti­on of the circumstances;
  • Per­son con­cer­ned:
    • Sub­mis­si­on of the com­plaint by the data sub­ject befo­re the expiry of the pro­ce­s­sing period;
    • Dis­re­gar­ding the pur­po­se of the right to infor­ma­ti­on – here the BayL­DA expli­ci­t­ly sta­tes “The right to infor­ma­ti­on is inten­ded to Exclu­si­ve­ly data pro­tec­tion goals be pur­sued. This right shall not for the coll­ec­tion of evi­dence ser­ve for other exi­sting con­flicts.” In Switz­er­land, this point is not yet enti­re­ly clear, despi­te the CS ruling by the Fede­ral Supre­me Court. It would not be sur­pri­sing if the courts are cal­led upon to pro­vi­de fur­ther cla­ri­fi­ca­ti­on here in the future;
    • Asser­ti­on of the right to infor­ma­ti­on against the lawy­er of the other party;
    • Com­plaint wit­hout pro­ba­ti­ve evidence.

Staged infor­ma­ti­on in the case of blan­ket requests for information

With refe­rence to the duty of insu­rance com­pa­nies to pro­vi­de infor­ma­ti­on, but in sub­stance gene­ral­ly valid for con­trol­lers with exten­si­ve pro­ce­s­sing acti­vi­ties (and also cor­rect for Switz­er­land), the BayL­DA sta­tes that the duty of insu­rance com­pa­nies to pro­vi­de infor­ma­ti­on is not limi­t­ed to the policyholder’s master data, but that in the case of blan­ket requests for infor­ma­ti­on, it is per­mis­si­ble in to pro­vi­de infor­ma­ti­on only about the master data in a first step. Fur­ther infor­ma­ti­on shall only be pro­vi­ded if the request for infor­ma­ti­on is spe­ci­fi­ed accor­din­gly by the policyholder.

Data pro­tec­tion on the Internet

Face­book Fan Pages

The BayL­DA suc­cinct­ly states,

Accor­ding to the cur­rent sta­tus, ope­ra­tors of Face­book fan pages have No pos­si­bi­li­ty to ope­ra­te them in a data pro­tec­tion com­pli­ant man­ner and must the­r­e­fo­re expect to be the addres­see of orders issued by the super­vi­so­ry authorities.

Wit­hout suf­fi­ci­ent know­ledge of the pro­ce­s­sing acti­vi­ties, the ope­ra­tor of the Fan­page can­not assess whe­ther they are car­ri­ed out lawfully.
As long as Face­book does not impro­ve this situa­ti­on, it is not pos­si­ble to ope­ra­te a fan page in com­pli­ance with data pro­tec­tion laws, despi­te the “Page Con­trol­ler Adden­dums“of Face­book (the agree­ment within the mea­ning of Art. 26 of the GDPR – for fur­ther infor­ma­ti­on see. here).

Track­ing Tools

As men­tio­ned, the BayL­DA pla­ced gre­at empha­sis on the use of track­ing tools on the Inter­net during the audits. Here is the “Gui­dance from the super­vi­so­ry aut­ho­ri­ties for tele­me­dia pro­vi­ders” (as of March 2019) must be obser­ved. Regar­ding Goog­le Ana­ly­tics, the opi­ni­on of the BayL­DA is as follows:

For exam­p­le, the so-cal­led “data release” to Goog­le is acti­va­ted by default. Taking into account the “Gui­dance for Tele­me­dia Pro­vi­ders”, this means the fol­lo­wing: If the web­site ope­ra­tor grants Goog­le the opti­on to share the web­site visi­tors’ data with for own pur­po­ses to use, this requi­res a Con­sent of the user.

Adver­ti­sing and address trading

In 2019, the BayLDA’s atten­ti­on was drawn seve­ral times to banks that also pro­cess cus­to­mer data to crea­te exten­si­ve adver­ti­sing pro­files, inclu­ding on the basis of data from advi­so­ry dis­cus­sions and usa­ge data from online ban­king and ban­king apps, data from ongo­ing con­tracts and payment tran­sac­tion data. This pro­ce­s­sing was in each case based on a balan­cing of inte­rests pur­su­ant to Art. 6 (1) f DSGVO.

Howe­ver, it can­not gene­ral­ly be assu­med that the pro­mo­tio­nal inte­rests of the cre­dit insti­tu­ti­on out­weigh the legi­ti­ma­te inte­rests of the cus­to­mers in exclu­ding pro­ce­s­sing in the case of such com­pre­hen­si­ve pro­fil­ing. The­r­e­fo­re, we are of the opi­ni­on that such pro­ce­s­sing only in con­junc­tion with the con­sent of the cus­to­mer is to be imple­men­ted in a legal­ly com­pli­ant manner.

This is espe­ci­al­ly true

with regard to the eva­lua­ti­on of payment tran­sac­tion data, which is prac­ti­ced in some cases, sin­ce, for exam­p­le, the infor­ma­ti­on on the pur­po­se of use from cre­dit trans­fers and direct debits often also spe­cial cate­go­ries of per­so­nal data (e.g. when paying mem­ber­ship fees to poli­ti­cal par­ties and trade uni­ons or sett­ling medi­cal bills). In the case of this type of par­ti­cu­lar­ly pro­tec­ted data, Art. 9 DS-GVO gene­ral­ly pro­hi­bits it from being pro­ce­s­sed on the basis of a balan­cing of inte­rests within the mea­ning of Art. 6 (1) (f) DS-GVO.

Howe­ver, one could also have asked whe­ther spe­cial cate­go­ries of data are actual­ly pro­ce­s­sed if raw data are used which allow cor­re­spon­din­gly pro­tec­ted fin­dings, but if the raw data are not used with regard to this meaningful­ness (e.g. if no cus­to­mer cate­go­ry “poli­ti­cal­ly libe­ral” or “case of ill­ness” is for­med). Artic­le 9 (1) of the GDPR does not neces­s­a­ri­ly exclude this view, which is why it is reco­gnized, for exam­p­le, that employee pho­tos are not to be regard­ed as health data, even for peo­p­le who wear glas­ses, as long as they are not eva­lua­ted with regard to this characteristic.

Inter­na­tio­nal data traffic

The fol­lo­wing state­ments can be found regar­ding the Pri­va­cy Shield:

It should also be poin­ted out that the Pri­va­cy Shield, at least indi­rect­ly, also Sub­ject of a refe­rence pro­ce­du­re curr­ent­ly being heard by the Euro­pean Court of Justi­ce (“Schrems II”) [dazu here] is, in which for the a ruling can be expec­ted in the first months of 2020 is. Even if the spe­ci­fic pro­ce­e­dings do not direct­ly con­cern the vali­di­ty of the Pri­va­cy Shield decis­i­on, it can­not be ruled out that the ECJ in its judgment may also rele­vant state­ments on the Pri­va­cy Shield could meet. Even a Inva­li­da­ti­on of the Pri­va­cy Shield by the ECJ in the con­text of the upco­ming ruling can­not be com­ple­te­ly ruled out, at least accor­ding to some obser­vers. In the con­text of the afo­re­men­tio­ned pro­ce­e­dings heard by the ECJ (“Schrems II”), the ECJ is cal­led upon, based on a refer­ral from the hig­hest court in Ire­land (Irish High Court), to rule on the Vali­di­ty of the EU stan­dard data pro­tec­tion clau­ses for trans­fers to pro­ces­sors (Com­mis­si­on Decis­i­on 2010/87/EU of 15.02.2010).

Employee data protection

In the area of employee data pro­tec­tion – which is par­ti­cu­lar­ly stron­gly influen­ced by natio­nal law – the BayL­DA sta­tes the fol­lo­wing regar­ding access to e‑mails of employees who have left the company:

If, as in the spe­ci­fic case at hand, the pri­va­te use of the Inter­net and e‑mail is pro­hi­bi­ted, the per­mis­si­bi­li­ty of the employer’s access to the e‑mail box of the employee who has left the com­pa­ny is gover­ned by Sec­tion 26 (1) sen­tence 1 BDSDG. Accor­din­gly, the employer’s hand­ling of employee data for pur­po­ses of the employment rela­ti­on­ship is per­mis­si­ble if it is neces­sa­ry for the per­for­mance or ter­mi­na­ti­on of the employment rela­ti­on­ship. The employer is entit­led to the offi­ci­al e‑mails, so that he can dis­po­se of them after the employee con­cer­ned has left the com­pa­ny. In addi­ti­on, if e‑mails from the mail­box are requi­red for the fur­ther pro­ce­s­sing of busi­ness tran­sac­tions, the employer must be able to access them. Should he access an e‑mail with pri­va­te con­tent Howe­ver, he would not be allo­wed to take note of them and would eit­her have to pass them on to the employee who has left the com­pa­ny or to the employee who has left the com­pa­ny. Trans­mit or dele­te. In such a case, the con­sent of the employee who has left the com­pa­ny is not required.

Data secu­ri­ty

Data pro­tec­tion breaches

The trend that began nbach the ent­ry into force of the GDPR has con­tin­ued in 2019 – the num­ber of data breach noti­fi­ca­ti­ons con­ti­nues to rise shar­ply. The most com­mon cate­go­ries rela­te to cyber­at­tacks, encryp­ti­on Tro­jans, mal­wa­re, loss, theft, soft­ware and posting errors, and mis-dis­patches. Well over half of repor­ted data brea­ches, howe­ver, invol­ve cir­cum­stances that are
have a rather “nor­mal” risk for the affec­ted indi­vi­du­als and whe­re often no fur­ther reme­di­al action needs to be taken by BayL­DA. Howe­ver, cyber­at­tacks can pose signi­fi­cant harm to vic­tims, which is why BayL­DA has deci­ded to focus on
“Cyber­se­cu­ri­ty” to be pur­sued fur­ther and expan­ded as far as possible.

E‑mail com­mu­ni­ca­ti­on bet­ween pro­fes­sio­nal sec­re­cy hol­ders and data subjects

Lawy­ers and other pro­fes­sio­nal sec­re­cy hol­ders often com­mu­ni­ca­te with the sec­re­cy owner by e‑mail. which is also per­mis­si­ble under Art. 6(1)(f) DSGVO (legi­ti­ma­te inte­rest in effi­ci­ent pro­ce­s­sing). Howe­ver, accor­ding to Art. 32 DSGVO, pro­fes­sio­nal sec­re­cy hol­ders must

In our opi­ni­on, when sen­ding e‑mails, it is essen­ti­al to ensu­re the pre­sence of an Trans­port encryp­ti­on pay atten­ti­on. With a high risk for the rights and free­doms is addi­tio­nal­ly a Con­tent encryp­ti­on (for exam­p­le, using PGP or SMIME).

This shows, among other things, that the fact of pro­fes­sio­nal sec­re­cy pro­tec­tion alo­ne does not mean that all secrets are to be con­side­red high-risk, but that the data pro­tec­tion law cri­te­ria of risk are to be applied unch­an­ged to per­so­nal data pro­tec­ted by secrecy.

With Con­sent of the data sub­ject, con­tent encryp­ti­on can also be wai­ved for high-risk data, wher­eby the con­sent of all data sub­jects is required.

In addi­ti­on, con­tent encryp­ti­on is always requi­red when the recipient’s email pro­vi­der encrypts email con­tent. eva­lua­tes for adver­ti­sing pur­po­ses.

Fining pro­ce­du­re

In 2019, the BayL­DA has issued a Cen­tral Fines Office (ZBS) crea­ted. The two peo­p­le in the ZBS work exclu­si­ve­ly in this area.

In 2019, the BayL­DA com­ple­ted appro­xi­m­ate­ly 100 fine pro­ce­e­dings, one with a fine under the GDPR (no lon­ger becau­se old law applies to vio­la­ti­ons com­mit­ted under old law under the favora­bi­li­ty principle).