We are very pleased about your inter­est in our com­pa­ny. Data pro­tec­tion is of a par­tic­u­lar­ly high pri­or­i­ty for the man­age­ment of BS Legal Recht­san­wälte. The use of the Inter­net pages of the BS Legal Recht­san­wälte is pos­si­ble with­out any indi­ca­tion of per­son­al data. How­ev­er, if a data sub­ject wants to use spe­cial ser­vices of our enter­prise via our web­site, pro­cess­ing of per­son­al data could become nec­es­sary. If pro­cess­ing of per­son­al data is nec­es­sary and if there is no legal basis for such pro­cess­ing, we will gen­er­al­ly obtain the con­sent of the data sub­ject. The pro­cess­ing of per­son­al data, such as the name, address, e‑mail address, or tele­phone num­ber of a data sub­ject shall always be in line with the Gen­er­al Data Pro­tec­tion Reg­u­la­tion, and in accor­dance with the coun­try-spe­cif­ic data pro­tec­tion reg­u­la­tions applic­a­ble to the BS Legal Recht­san­wälte. By means of this data pro­tec­tion dec­la­ra­tion, our enter­prise would like to inform the pub­lic about the type, scope and pur­pose of the per­son­al data we col­lect, use and process. Fur­ther­more, data sub­jects are informed of their rights by means of this data pro­tec­tion dec­la­ra­tion. As the con­troller, the BS Legal Recht­san­wälte has imple­ment­ed numer­ous tech­ni­cal and organ­i­sa­tion­al mea­sures to ensure the most com­plete pro­tec­tion of per­son­al data processed through this web­site. Nev­er­the­less, Inter­net-based data trans­mis­sions can always be sub­ject to secu­ri­ty vul­ner­a­bil­i­ties, so that absolute pro­tec­tion can­not be guar­an­teed. For this rea­son, every data sub­ject is free to trans­mit per­son­al data to us by alter­na­tive means, for exam­ple by telephone.

1. definitions

The data pro­tec­tion dec­la­ra­tion of BS Legal Recht­san­wälte is based on the terms used by the Euro­pean Direc­tive and Ordi­nance Mak­er when adopt­ing the Data Pro­tec­tion Reg­u­la­tion (DS-GVO). Our data pro­tec­tion dec­la­ra­tion should be easy to read and under­stand for the pub­lic as well as for our clients and busi­ness part­ners. To ensure this, we would like to explain the terms used in advance. We use the fol­low­ing terms, among oth­ers, in this data pro­tec­tion declaration:

(a) personal data

Per­son­al data is any infor­ma­tion relat­ing to an iden­ti­fied or iden­ti­fi­able nat­ur­al per­son (here­inafter “data sub­ject”). An iden­ti­fi­able nat­ur­al per­son is one who can be iden­ti­fied, direct­ly or indi­rect­ly, in par­tic­u­lar by ref­er­ence to an iden­ti­fi­er such as a name, an iden­ti­fi­ca­tion num­ber, loca­tion data, an online iden­ti­fi­er or to one or more fac­tors spe­cif­ic to the phys­i­cal, phys­i­o­log­i­cal, genet­ic, men­tal, eco­nom­ic, cul­tur­al or social iden­ti­ty of that nat­ur­al person.

(b) Data subject

Data sub­ject means any iden­ti­fied or iden­ti­fi­able nat­ur­al per­son whose per­son­al data are processed by the controller.

© processing

Pro­cess­ing means any oper­a­tion or set of oper­a­tions which is per­formed upon per­son­al data, whether or not by auto­mat­ic means, such as col­lec­tion, record­ing, organ­i­sa­tion, fil­ing, stor­age, adap­ta­tion or alter­ation, retrieval, con­sul­ta­tion, use, dis­clo­sure by trans­mis­sion, dis­sem­i­na­tion or oth­er­wise mak­ing avail­able, align­ment or com­bi­na­tion, restric­tion, era­sure or destruction.

(d) Restriction of processing

Restric­tion of pro­cess­ing is the mark­ing of stored per­son­al data with the aim of lim­it­ing their future processing.

(e) Profiling

Pro­fil­ing shall mean any auto­mat­ed pro­cess­ing of per­son­al data which con­sists in using such per­son­al data to eval­u­ate cer­tain per­son­al aspects relat­ing to a nat­ur­al per­son, in par­tic­u­lar to analyse or pre­dict aspects relat­ing to that nat­ur­al per­son­’s per­for­mance at work, eco­nom­ic sit­u­a­tion, health, per­son­al pref­er­ences, inter­ests, reli­a­bil­i­ty, behav­iour, loca­tion or change of location.

(f) Pseudonymisation

Pseu­do­nymi­sa­tion is the pro­cess­ing of per­son­al data in such a way that the per­son­al data can no longer be attrib­uted to a spe­cif­ic data sub­ject with­out the use of addi­tion­al infor­ma­tion, pro­vid­ed that such addi­tion­al infor­ma­tion is kept sep­a­rate­ly and is sub­ject to tech­ni­cal and organ­i­sa­tion­al mea­sures which ensure that the per­son­al data are not attrib­uted to an iden­ti­fied or iden­ti­fi­able nat­ur­al person.

(g) Controller or data controller

The con­troller or per­son respon­si­ble for pro­cess­ing is the nat­ur­al or legal per­son, pub­lic author­i­ty, agency or oth­er body which alone or joint­ly with oth­ers deter­mines the pur­pos­es and means of the pro­cess­ing of per­son­al data. Where the pur­pos­es and means of such pro­cess­ing are deter­mined by Union or Mem­ber State law, the con­troller or the spe­cif­ic cri­te­ria for its des­ig­na­tion may be pro­vid­ed for under Union or Mem­ber State law.

(h) Processor

Proces­sor means a nat­ur­al or legal per­son, pub­lic author­i­ty, agency or oth­er body which process­es per­son­al data on behalf of the controller.

(i) Recipient

A recip­i­ent is a nat­ur­al or legal per­son, pub­lic author­i­ty, agency or oth­er body to whom per­son­al data are dis­closed, whether or not a third par­ty. How­ev­er, pub­lic author­i­ties that may receive per­son­al data in the con­text of a spe­cif­ic inves­tiga­tive task under Union or Mem­ber State law shall not be con­sid­ered as recipients.

(j)      Third party

Third par­ty means any nat­ur­al or legal per­son, pub­lic author­i­ty, agency or oth­er body oth­er than the data sub­ject, the con­troller, the proces­sor and the per­sons autho­rised to process the per­son­al data under the direct respon­si­bil­i­ty of the con­troller or the processor.

(k) Consent

Con­sent is any freely giv­en spe­cif­ic and informed indi­ca­tion of his or her wish­es, in the form of a state­ment or oth­er unam­bigu­ous affir­ma­tive act, by which the data sub­ject sig­ni­fies his or her agree­ment to the pro­cess­ing of per­son­al data relat­ing to him or her.

2. the name and address of the controller

Ver­ant­wortlich­er im Sinne der Daten­schutz-Grund­verord­nung, son­stiger in den Mit­glied­staat­en der Europäis­chen Union gel­tenden Daten­schutzge­set­ze und ander­er Bes­tim­mungen mit daten­schutzrechtlichem Charak­ter ist: BS LEGAL Recht­san­wälte, Recht­san­walt Veit Strittmat­ter, Düren­er Str. 270 50935 Köln Deutsch­land Tel.: 022194336530 E‑Mail: info@bs-legal.de Web­site: www.bs-legal.de

3. Cookies

The inter­net pages of BS Legal Recht­san­wälte use cook­ies. Cook­ies are text files that are placed and stored on a com­put­er sys­tem via an inter­net brows­er. Numer­ous web­sites and servers use cook­ies. Many cook­ies con­tain a so-called cook­ie ID. A cook­ie ID is a unique iden­ti­fi­er of the cook­ie. It con­sists of a string of char­ac­ters by which Inter­net pages and servers can be assigned to the spe­cif­ic Inter­net brows­er in which the cook­ie was stored. This enables the vis­it­ed Inter­net pages and servers to dis­tin­guish the indi­vid­ual brows­er of the data sub­ject from oth­er Inter­net browsers that con­tain oth­er cook­ies. A spe­cif­ic inter­net brows­er can be recog­nised and iden­ti­fied via the unique cook­ie ID. Through the use of cook­ies, the BS Legal Recht­san­wälte can pro­vide the users of this web­site with more user-friend­ly ser­vices that would not be pos­si­ble with­out the cook­ie set­ting. By means of a cook­ie, the infor­ma­tion and offers on our web­site can be opti­mised for the ben­e­fit of the user. As already men­tioned, cook­ies enable us to recog­nise the users of our web­site. The pur­pose of this recog­ni­tion is to make it eas­i­er for users to use our web­site. For exam­ple, the user of a web­site that uses cook­ies does not have to re-enter his or her access data each time he or she vis­its the web­site, because this is done by the web­site and the cook­ie stored on the user’s com­put­er sys­tem. Anoth­er exam­ple is the cook­ie of a shop­ping bas­ket in an online shop. The online shop remem­bers the items that a cus­tomer has placed in the vir­tu­al shop­ping bas­ket via a cook­ie. The data sub­ject can pre­vent the set­ting of cook­ies by our web­site at any time by means of an appro­pri­ate set­ting of the Inter­net brows­er used and thus per­ma­nent­ly object to the set­ting of cook­ies. Fur­ther­more, cook­ies that have already been set can be delet­ed at any time via an inter­net brows­er or oth­er soft­ware pro­grammes. This is pos­si­ble in all com­mon inter­net browsers. If the data sub­ject deac­ti­vates the set­ting of cook­ies in the Inter­net brows­er used, not all func­tions of our web­site may be ful­ly usable.

4. collection of general data and information

The web­site of BS Legal Recht­san­wälte col­lects a series of gen­er­al data and infor­ma­tion every time a data sub­ject or auto­mat­ed sys­tem calls up the web­site. This gen­er­al data and infor­ma­tion is stored in the log files of the serv­er. The fol­low­ing data may be record­ed: (1) the brows­er types and ver­sions used, (2) the oper­at­ing sys­tem used by the access­ing sys­tem, (3) the web­site from which an access­ing sys­tem access­es our web­site (so-called refer­rer), (4) the sub-web­sites which are accessed via an access­ing sys­tem on our web­site, (5) the date and time of an access to the web­site, (6) an Inter­net pro­to­col address (IP address), (7) the Inter­net ser­vice provider of the access­ing sys­tem and (8) oth­er sim­i­lar data and infor­ma­tion that serve to avert dan­ger in the event of attacks on our infor­ma­tion tech­nol­o­gy sys­tems. When using these gen­er­al data and infor­ma­tion, the BS Legal Recht­san­wälte does not draw any con­clu­sions about the data sub­ject. This infor­ma­tion is rather required in order to (1) cor­rect­ly deliv­er the con­tents of our web­site, (2) opti­mise the con­tents of our web­site as well as the adver­tis­ing for the same, (3) ensure the per­ma­nent oper­abil­i­ty of our infor­ma­tion tech­nol­o­gy sys­tems and the tech­nol­o­gy of our web­site as well as (4) to pro­vide law enforce­ment author­i­ties with the infor­ma­tion nec­es­sary for pros­e­cu­tion in the event of a cyber attack. There­fore, the BS Legal Recht­san­wälte ana­lyzes anony­mous­ly col­lect­ed data and infor­ma­tion on one hand for sta­tis­ti­cal pur­pos­es and on the oth­er hand for the pur­pose of increas­ing the data pro­tec­tion and data secu­ri­ty of our enter­prise, and ulti­mate­ly ensur­ing an opti­mal lev­el of pro­tec­tion for the per­son­al data we process. The anony­mous data of the serv­er log files are stored sep­a­rate­ly from any per­son­al data pro­vid­ed by a data subject.

5. how to contact us via the website

The web­site of the BS Legal Recht­san­wälte con­tains legal require­ments which enable a quick elec­tron­ic con­tact to our enter­prise, as well as direct com­mu­ni­ca­tion with us, which also includes a gen­er­al address of the so-called elec­tron­ic mail (e‑mail address). If a data sub­ject con­tacts the con­troller by e‑mail or by using a con­tact form, the per­son­al data trans­mit­ted by the data sub­ject will be stored auto­mat­i­cal­ly. Such per­son­al data trans­mit­ted on a vol­un­tary basis by a data sub­ject to the con­troller will be stored for the pur­pos­es of pro­cess­ing or con­tact­ing the data sub­ject. This per­son­al data will not be dis­closed to third parties.

6. comment function in the blog on the website

The BS Legal Recht­san­wälte offers users the pos­si­bil­i­ty to leave indi­vid­ual com­ments on indi­vid­ual blog con­tri­bu­tions on a blog, which is on the web­site of the con­troller. A blog is a por­tal main­tained on a web­site, usu­al­ly pub­licly view­able, in which one or more per­sons, called blog­gers or web blog­gers, can post arti­cles or write down thoughts in so-called blog­posts. The blog­posts can usu­al­ly be com­ment­ed on by third par­ties. If a data sub­ject leaves a com­ment on the blog pub­lished on this web­site, in addi­tion to the com­ments left by the data sub­ject, details of the time the com­ment was entered and the user name (pseu­do­nym) cho­sen by the data sub­ject will be stored and pub­lished. Fur­ther­more, the IP address assigned by the Inter­net ser­vice provider (ISP) of the per­son con­cerned is also logged. This stor­age of the IP address takes place for secu­ri­ty rea­sons and in the event that the per­son con­cerned vio­lates the rights of third par­ties by post­ing a com­ment or posts ille­gal con­tent. The stor­age of this per­son­al data is there­fore in the con­troller’s own inter­est, so that the con­troller could excul­pate itself if nec­es­sary in the event of an infringe­ment. The per­son­al data col­lect­ed will not be dis­closed to third par­ties, unless such dis­clo­sure is required by law or serves the legal defence of the controller.

7. subscription to comments on the blog on the website

The com­ments made in the blog of BS Legal Recht­san­wälte can gen­er­al­ly be sub­scribed to by third par­ties. In par­tic­u­lar, it is pos­si­ble for a com­men­ta­tor to sub­scribe to the com­ments fol­low­ing his or her com­ment on a spe­cif­ic blog post. If a data sub­ject opts for the option to sub­scribe to com­ments, the con­troller sends an auto­mat­ic con­fir­ma­tion e‑mail in order to ver­i­fy in the dou­ble opt-in pro­ce­dure whether the own­er of the spec­i­fied e‑mail address has indeed opt­ed for this option. The option to sub­scribe to com­ments can be ter­mi­nat­ed at any time.

8. routine deletion and blocking of personal data

The con­troller shall process and store per­son­al data of the data sub­ject only for the peri­od nec­es­sary to achieve the pur­pose of stor­age or where pro­vid­ed for by the Euro­pean Direc­tive and Reg­u­la­tion or oth­er leg­is­la­tor in laws or reg­u­la­tions to which the con­troller is sub­ject. If the stor­age pur­pose ceas­es to apply or if a stor­age peri­od pre­scribed by the Euro­pean Direc­tive and Reg­u­la­tion Mak­er or anoth­er com­pe­tent leg­is­la­tor expires, the per­son­al data will be rou­tine­ly blocked or delet­ed in accor­dance with the statu­to­ry provisions.

9. rights of the data subject

• (a) Right to confirmation

  Every data sub­ject has the right, grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion, to obtain con­fir­ma­tion from the con­troller as to whether per­son­al data con­cern­ing him or her are being processed. If a data sub­ject wish­es to exer­cise this right of con­fir­ma­tion, he or she may, at any time, con­tact any employ­ee of the controller.

• b) Right of access

  Any per­son con­cerned by the pro­cess­ing of per­son­al data has the right grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion to obtain at any time from the con­troller, free of charge, infor­ma­tion about the per­son­al data stored about him or her and a copy of that infor­ma­tion. In addi­tion, the Euro­pean Direc­tive and Reg­u­la­tion Body has grant­ed the data sub­ject access to the fol­low­ing information:

  • the pur­pos­es of the processing
  • the cat­e­gories of per­son­al data processed
  • the recip­i­ents or cat­e­gories of recip­i­ents to whom the per­son­al data have been or will be dis­closed, in par­tic­u­lar in the case of recip­i­ents in third coun­tries or inter­na­tion­al organisations
  • if pos­si­ble, the planned dura­tion for which the per­son­al data will be stored or, if this is not pos­si­ble, the cri­te­ria for deter­min­ing this duration
  • the exis­tence of the right to obtain the rec­ti­fi­ca­tion or era­sure of per­son­al data con­cern­ing him or her, or the restric­tion of pro­cess­ing by the con­troller, or the right to object to such processing
  • the exis­tence of a right of appeal to a super­vi­so­ry authority
  • if the per­son­al data are not col­lect­ed from the data sub­ject: Any avail­able infor­ma­tion on the ori­gin of the data
  • the exis­tence of auto­mat­ed deci­sion-mak­ing, includ­ing pro­fil­ing, pur­suant to Arti­cle 22(1) and (4) of the GDPR and, at least in these cas­es, mean­ing­ful infor­ma­tion about the log­ic involved and the scope and intend­ed effects of such pro­cess­ing for the data subject.

  the exis­tence of auto­mat­ed deci­sion-mak­ing, includ­ing pro­fil­ing, pur­suant to Arti­cle 22(1) and (4) of the GDPR and, at least in these cas­es, mean­ing­ful infor­ma­tion about the log­ic involved and the scope and intend­ed effects of such pro­cess­ing for the data subject.

• c) Right of rectification

  Any per­son con­cerned by the pro­cess­ing of per­son­al data has the right, grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion, to obtain the rec­ti­fi­ca­tion with­out delay of inac­cu­rate per­son­al data con­cern­ing him or her. Fur­ther­more, the data sub­ject has the right to request the com­ple­tion of incom­plete per­son­al data, includ­ing by means of a sup­ple­men­tary dec­la­ra­tion, tak­ing into account the pur­pos­es of the pro­cess­ing. If a data sub­ject wish­es to exer­cise this right of rec­ti­fi­ca­tion, he or she may, at any time, con­tact any employ­ee of the controller.

• d) Right to erasure (right to be forgotten)

  Any per­son con­cerned by the pro­cess­ing of per­son­al data has the right, grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion, to obtain from the con­troller the era­sure with­out delay of per­son­al data con­cern­ing him or her, where one of the fol­low­ing grounds applies and inso­far as the pro­cess­ing is not necessary:

  • The per­son­al data were col­lect­ed or oth­er­wise processed for such pur­pos­es for which they are no longer necessary.
  • The data sub­ject revokes the con­sent on which the pro­cess­ing was based pur­suant to Art. 6(1)(a) DS-GVO or Art. 9(2)(a) DS-GVO and there is no oth­er legal basis for the processing.
  • The data sub­ject objects to the pro­cess­ing pur­suant to Arti­cle 21(1) DS-GVO and there are no over­rid­ing legit­i­mate grounds for the pro­cess­ing, or the data sub­ject objects to the pro­cess­ing pur­suant to Arti­cle 21(2) DS-GVO.
  • The per­son­al data have been processed unlawfully.
  • The era­sure of the per­son­al data is nec­es­sary for com­pli­ance with a legal oblig­a­tion under Union or Mem­ber State law to which the con­troller is subject.
  • The per­son­al data have been col­lect­ed in rela­tion to infor­ma­tion soci­ety ser­vices offered pur­suant to Arti­cle 8(1) DS-GVO.

  If one of the afore­men­tioned rea­sons applies, and a data sub­ject wish­es to arrange for the era­sure of per­son­al data stored by the BS Legal Recht­san­wälte, he or she may, at any time, con­tact any employ­ee of the con­troller. The employ­ee of BS Legal Recht­san­wälte will arrange for the era­sure request to be com­plied with imme­di­ate­ly. If the per­son­al data has been made pub­lic by BS Legal Recht­san­wälte and our com­pa­ny is respon­si­ble pur­suant to Art. 17 Para. 1 DS-GVO to erase the per­son­al data, BS Legal Recht­san­wälte shall imple­ment rea­son­able mea­sures, includ­ing tech­ni­cal mea­sures, tak­ing into account the avail­able tech­nol­o­gy and the cost of imple­men­ta­tion, in order to inform oth­er data con­trollers which process the pub­lished per­son­al data that the data sub­ject has request­ed from those oth­er data con­trollers to erase all links to or copies or repli­ca­tions of the per­son­al data, unless the pro­cess­ing is nec­es­sary. The employ­ee of BS Legal Recht­san­wälte will arrange the nec­es­sary in indi­vid­ual cases.

• (e) Right to restriction of processing

  Any per­son con­cerned by the pro­cess­ing of per­son­al data has the right, grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion, to obtain from the con­troller the restric­tion of pro­cess­ing where one of the fol­low­ing con­di­tions is met:

  • The accu­ra­cy of the per­son­al data is con­test­ed by the data sub­ject for a peri­od enabling the con­troller to ver­i­fy the accu­ra­cy of the per­son­al data.
  • The pro­cess­ing is unlaw­ful, the data sub­ject objects to the era­sure of the per­son­al data and requests instead the restric­tion of the use of the per­son­al data.
  • The con­troller no longer needs the per­son­al data for the pur­pos­es of the pro­cess­ing, but the data sub­ject needs it for the asser­tion, exer­cise or defence of legal claims.
  • The data sub­ject has object­ed to the pro­cess­ing pur­suant to Arti­cle 21(1) of the GDPR and it is not yet clear whether the legit­i­mate grounds of the con­troller over­ride those of the data subject.

  If one of the afore­men­tioned con­di­tions is met, and a data sub­ject wish­es to request the restric­tion of per­son­al data stored by the BS Legal Recht­san­wälte, he or she may, at any time, con­tact any employ­ee of the con­troller. The employ­ee of BS Legal Recht­san­wälte will arrange the restric­tion of the processing.

• f) Right to data portability

  Every per­son affect­ed by the pro­cess­ing of per­son­al data has the right grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion to receive the per­son­al data con­cern­ing him or her, which have been pro­vid­ed by the data sub­ject to a con­troller, in a struc­tured, com­mon­ly used and machine-read­able for­mat. The data sub­ject shall also have the right to trans­mit such data to anoth­er con­troller with­out hin­drance from the con­troller to whom the per­son­al data have been pro­vid­ed, pro­vid­ed that the pro­cess­ing is based on con­sent pur­suant to Arti­cle 6(1)(a) of the GDPR or Arti­cle 9(2)(a) of the GDPR or on a con­tract pur­suant to Arti­cle 6(1)(b) of the GDPR and the pro­cess­ing is car­ried out by auto­mat­ed means, unless the pro­cess­ing is nec­es­sary for the per­for­mance of a task car­ried out in the pub­lic inter­est or in the exer­cise of offi­cial author­i­ty vest­ed in the con­troller. Fur­ther­more, when exer­cis­ing the right to data porta­bil­i­ty pur­suant to Arti­cle 20(1) of the GDPR, the data sub­ject shall have the right to obtain the direct trans­fer of per­son­al data from one con­troller to anoth­er con­troller where tech­ni­cal­ly fea­si­ble and pro­vid­ed that this does not adverse­ly affect the rights and free­doms of oth­er per­sons. In order to assert the right to data porta­bil­i­ty, the data sub­ject may at any time con­tact any employ­ee of BS Legal Rechtsanwälte.

• (g) Right to object

  Any per­son affect­ed by the pro­cess­ing of per­son­al data shall have the right grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion to object at any time, on grounds relat­ing to his or her par­tic­u­lar sit­u­a­tion, to the pro­cess­ing of per­son­al data con­cern­ing him or her which is car­ried out on the basis of Arti­cle 6(1)(e) or (f) of the DS-GVO. This also applies to pro­fil­ing based on these pro­vi­sions. The BS Legal Recht­san­wälte shall no longer process the per­son­al data in the event of the objec­tion, unless we can demon­strate com­pelling legit­i­mate grounds for the pro­cess­ing which over­ride the inter­ests, rights and free­doms of the data sub­ject, or for the asser­tion, exer­cise or defence of legal claims. If the BS Legal Recht­san­wälte process­es per­son­al data for the pur­pose of direct mar­ket­ing, the data sub­ject shall have the right to object at any time to pro­cess­ing of per­son­al data processed for such mar­ket­ing. This also applies to pro­fil­ing inso­far as it is relat­ed to such direct mar­ket­ing. If the data sub­ject objects to BS Legal Recht­san­wälte to the pro­cess­ing for direct mar­ket­ing pur­pos­es, BS Legal Recht­san­wälte will no longer process the per­son­al data for these pur­pos­es. In addi­tion, the data sub­ject has the right, on grounds relat­ing to his or her par­tic­u­lar sit­u­a­tion, to object to pro­cess­ing of per­son­al data con­cern­ing him or her which is car­ried out by BS Legal Recht­san­wälte for sci­en­tif­ic or his­tor­i­cal research pur­pos­es, or for sta­tis­ti­cal pur­pos­es pur­suant to Arti­cle 89(1) of the Data Pro­tec­tion Reg­u­la­tion, unless such pro­cess­ing is nec­es­sary for the per­for­mance of a task car­ried out for rea­sons of pub­lic inter­est. In order to exer­cise the right to object, the data sub­ject may direct­ly con­tact any employ­ee of BS Legal Recht­san­wälte or anoth­er employ­ee. The data sub­ject is also free to exer­cise his/her right to object by means of auto­mat­ed pro­ce­dures using tech­ni­cal spec­i­fi­ca­tions in con­nec­tion with the use of infor­ma­tion soci­ety ser­vices, notwith­stand­ing Direc­tive 2002/58/EC.

• h) Automated decisions in individual cases, including profiling

  Any per­son con­cerned by the pro­cess­ing of per­son­al data shall have the right, grant­ed by the Euro­pean Direc­tive and the Reg­u­la­tion, not to be sub­ject to a deci­sion based sole­ly on auto­mat­ed pro­cess­ing, includ­ing pro­fil­ing, which pro­duces legal effects con­cern­ing him or her or sim­i­lar­ly sig­nif­i­cant­ly affects him or her, pro­vid­ed that the deci­sion (1) is not nec­es­sary for enter­ing into, or the per­for­mance of, a con­tract between the data sub­ject and the con­troller, or (2) is autho­rised by Union or Mem­ber State law to which the con­troller is sub­ject and that such law lays down appro­pri­ate mea­sures to safe­guard the data sub­jec­t’s rights and free­doms and legit­i­mate inter­ests, or (3) is made with the data sub­jec­t’s explic­it con­sent. If the deci­sion (1) is nec­es­sary for enter­ing into, or the per­for­mance of, a con­tract between the data sub­ject and the data con­troller, or (2) it is made with the data sub­jec­t’s explic­it con­sent, BS Legal Recht­san­wälte shall imple­ment suit­able mea­sures to safe­guard the data sub­jec­t’s rights and free­doms and legit­i­mate inter­ests, which include at least the right to obtain the data sub­jec­t’s involve­ment on the part of the con­troller, to express his or her point of view and con­test the deci­sion. If the data sub­ject wish­es to exer­cise the rights con­cern­ing auto­mat­ed deci­sions, he or she may, at any time, con­tact any employ­ee of the controller.

• i) Right to withdraw consent under data protection law

  Any per­son affect­ed by the pro­cess­ing of per­son­al data has the right grant­ed by the Euro­pean Direc­tive and Reg­u­la­tion to with­draw con­sent to the pro­cess­ing of per­son­al data at any time. If the data sub­ject wish­es to exer­cise the right to with­draw con­sent, he or she may, at any time, con­tact any employ­ee of the controller.

10. data protection during applications and the application procedure

The con­troller col­lects and process­es the per­son­al data of appli­cants for the pur­pose of han­dling the appli­ca­tion pro­ce­dure. The pro­cess­ing may also take place elec­tron­i­cal­ly. This is in par­tic­u­lar the case when an appli­cant sub­mits rel­e­vant appli­ca­tion doc­u­ments to the con­troller by elec­tron­ic means, for exam­ple by e‑mail or via a web form locat­ed on the web­site. If the con­troller con­cludes an employ­ment con­tract with an appli­cant, the trans­mit­ted data will be stored for the pur­pose of pro­cess­ing the employ­ment rela­tion­ship in com­pli­ance with the statu­to­ry pro­vi­sions. If the con­troller does not con­clude an employ­ment con­tract with the appli­cant, the appli­ca­tion doc­u­ments are auto­mat­i­cal­ly delet­ed two months after the noti­fi­ca­tion of the rejec­tion deci­sion, pro­vid­ed that no oth­er legit­i­mate inter­ests of the con­troller con­flict with such dele­tion. Oth­er legit­i­mate inter­est in this sense is, for exam­ple, a duty to pro­vide evi­dence in pro­ceed­ings under the Gen­er­al Equal Treat­ment Act (AGG).

11. data protection provisions on the use and application of Facebook

The con­troller has inte­grat­ed com­po­nents of the com­pa­ny Face­book on this web­site. Face­book is a social net­work. A social net­work is a social meet­ing place oper­at­ed on the Inter­net, an online com­mu­ni­ty that gen­er­al­ly enables users to com­mu­ni­cate and inter­act with each oth­er in vir­tu­al space. A social net­work can serve as a plat­form for exchang­ing opin­ions and expe­ri­ences or enables the inter­net com­mu­ni­ty to pro­vide per­son­al or com­pa­ny-relat­ed infor­ma­tion. Face­book allows users of the social net­work, among oth­er things, to cre­ate pri­vate pro­files, upload pho­tos and net­work via friend requests. Face­book’s oper­at­ing com­pa­ny is Face­book, Inc, 1 Hack­er Way, Men­lo Park, CA 94025, USA. If a data sub­ject lives out­side the USA or Cana­da, the con­troller of per­son­al data is Face­book Ire­land Ltd, 4 Grand Canal Square, Grand Canal Har­bour, Dublin 2, Ire­land. By each call of one of the indi­vid­ual pages of this web­site, which is oper­at­ed by the data con­troller and on which a Face­book com­po­nent (Face­book plug-in) has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly caused by the respec­tive Face­book com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing Face­book com­po­nent from Face­book. A com­plete overview of all Face­book plug-ins can be found at https://developers.facebook.com/docs/plugins/?locale=de_DE. With­in the scope of this tech­ni­cal pro­ce­dure, Face­book receives infor­ma­tion about which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged in to Face­book at the same time, Face­book recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Face­book com­po­nent and assigned by Face­book to the respec­tive Face­book account of the data sub­ject. If the data sub­ject acti­vates one of the Face­book but­tons inte­grat­ed on our web­site, for exam­ple the “Like” but­ton, or if the data sub­ject posts a com­ment, Face­book assigns this infor­ma­tion to the per­son­al Face­book user account of the data sub­ject and stores this per­son­al data. Face­book always receives infor­ma­tion via the Face­book com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is simul­ta­ne­ous­ly logged into Face­book at the time of call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Face­book com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Face­book, he or she can pre­vent the trans­mis­sion by log­ging out of his or her Face­book account before access­ing our web­site. The data pol­i­cy pub­lished by Face­book, which can be accessed at https://de-de.facebook.com/about/privacy/, pro­vides infor­ma­tion on the col­lec­tion, pro­cess­ing and use of per­son­al data by Face­book. It also explains which set­ting options Face­book offers to pro­tect the pri­va­cy of the data sub­ject. In addi­tion, var­i­ous appli­ca­tions are avail­able that make it pos­si­ble to sup­press data trans­mis­sion to Face­book. Such appli­ca­tions can be used by the data sub­ject to sup­press data trans­mis­sion to Facebook.

12. Data protection provisions on the use and application of Google AdSense

The con­troller has inte­grat­ed Google AdSense on this web­site. Google AdSense is an online ser­vice that enables the place­ment of adver­tise­ments on third-par­ty web­sites. Google AdSense is based on an algo­rithm which selects the adver­tise­ments dis­played on third-par­ty sites in accor­dance with the con­tent of the respec­tive third-par­ty site. Google AdSense allows inter­est-relat­ed tar­get­ing of the Inter­net user, which is imple­ment­ed by gen­er­at­ing indi­vid­ual user pro­files. The oper­at­ing com­pa­ny of the Google AdSense com­po­nent is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land. The pur­pose of the Google AdSense com­po­nent is to inte­grate adver­tise­ments on our web­site. Google-AdSense sets a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. What cook­ies are has already been explained above. By set­ting the cook­ie, Alpha­bet Inc. is enabled to analyse the use of our web­site. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up, on which a Google AdSense com­po­nent has been inte­grat­ed, the inter­net brows­er on the data sub­jec­t’s infor­ma­tion tech­nol­o­gy sys­tem is auto­mat­i­cal­ly caused by the respec­tive Google AdSense com­po­nent to trans­mit data to Alpha­bet Inc. for the pur­pose of online adver­tis­ing and the invoic­ing of com­mis­sions. With­in the scope of this tech­ni­cal pro­ce­dure, Alpha­bet Inc. obtains knowl­edge of per­son­al data, such as the IP address of the data sub­ject, which Alpha­bet Inc. uses, among oth­er things, to trace the ori­gin of vis­i­tors and clicks and sub­se­quent­ly to enable com­mis­sion set­tle­ments. The data sub­ject can pre­vent the set­ting of cook­ies by our web­site, as already described above, at any time by means of an appro­pri­ate set­ting of the Inter­net brows­er used and thus per­ma­nent­ly object to the set­ting of cook­ies. Such a set­ting of the Inter­net brows­er used would also pre­vent Alpha­bet Inc. from set­ting a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. In addi­tion, a cook­ie already set by Alpha­bet Inc. can be delet­ed at any time via the inter­net brows­er or oth­er soft­ware pro­grammes. Google AdSense also uses so-called track­ing pix­els. A track­ing pix­el is a minia­ture graph­ic that is embed­ded in Inter­net pages to enable log file record­ing and log file analy­sis, where­by a sta­tis­ti­cal eval­u­a­tion can be car­ried out. Based on the embed­ded track­ing pix­el, Alpha­bet Inc. may see if and when a web­site was opened by a data sub­ject, and which links were clicked by the data sub­ject. Among oth­er things, track­ing pix­els are used to eval­u­ate the flow of vis­i­tors to a web­site. Via Google AdSense, per­son­al data and infor­ma­tion, which also includes the IP address and is nec­es­sary for the col­lec­tion and billing of the adver­tise­ments dis­played, are trans­mit­ted to Alpha­bet Inc. in the Unit­ed States of Amer­i­ca. This per­son­al data is stored and processed in the Unit­ed States of Amer­i­ca. Alpha­bet Inc. may pass on this per­son­al data col­lect­ed via the tech­ni­cal process to third par­ties. Google-AdSense is explained in more detail under this link https://www.google.de/intl/de/adsense/start/.

13. Datenschutzbestimmungen zu Einsatz und Verwendung von Google Analytics (mit Anonymisierungsfunktion)

The con­troller has inte­grat­ed the Google Ana­lyt­ics com­po­nent (with anonymi­sa­tion func­tion) on this web­site. Google Ana­lyt­ics is a web analy­sis ser­vice. Web analy­sis is the col­lec­tion, com­pi­la­tion and eval­u­a­tion of data about the behav­iour of vis­i­tors to web­sites. Among oth­er things, a web analy­sis ser­vice col­lects data on the web­site from which a data sub­ject has accessed a web­site (so-called refer­rers), which sub-pages of the web­site have been accessed or how often and for how long a sub-page has been viewed. A web analy­sis is main­ly used to opti­mise a web­site and to analyse the costs and ben­e­fits of inter­net adver­tis­ing. The oper­at­ing com­pa­ny of the Google Ana­lyt­ics com­po­nent is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land. The con­troller uses the add-on “_gat._anonymizeIp” for web analy­sis via Google Ana­lyt­ics. By means of this addi­tion, the IP address of the Inter­net con­nec­tion of the data sub­ject is short­ened and anonymised by Google if access to our Inter­net pages is from a Mem­ber State of the Euro­pean Union or from anoth­er State par­ty to the Agree­ment on the Euro­pean Eco­nom­ic Area. The pur­pose of the Google Ana­lyt­ics com­po­nent is to analyse the flow of vis­i­tors to our web­site. Google uses the data and infor­ma­tion obtained, among oth­er things, to eval­u­ate the use of our web­site, to com­pile online reports for us show­ing the activ­i­ties on our web­site and to pro­vide oth­er ser­vices in con­nec­tion with the use of our web­site. Google Ana­lyt­ics sets a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. What cook­ies are has already been explained above. By set­ting the cook­ie, Google is enabled to analyse the use of our web­site. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up and on which a Google Ana­lyt­ics com­po­nent has been inte­grat­ed, the inter­net brows­er on the data sub­jec­t’s infor­ma­tion tech­nol­o­gy sys­tem is auto­mat­i­cal­ly caused by the respec­tive Google Ana­lyt­ics com­po­nent to trans­mit data to Google for the pur­pose of online analy­sis. As part of this tech­ni­cal pro­ce­dure, Google obtains knowl­edge of per­son­al data, such as the IP address of the data sub­ject, which Google uses, among oth­er things, to track the ori­gin of vis­i­tors and clicks and sub­se­quent­ly to enable com­mis­sion cal­cu­la­tions. By means of the cook­ie, per­son­al infor­ma­tion such as the time of access, the loca­tion from which access orig­i­nat­ed and the fre­quen­cy of vis­its to our web­site by the data sub­ject are stored. Each time the data sub­ject vis­its our web­site, this per­son­al data, includ­ing the IP address of the inter­net con­nec­tion used by the data sub­ject, is trans­mit­ted to Google in the Unit­ed States of Amer­i­ca. This per­son­al data is stored by Google in the Unit­ed States of Amer­i­ca. Google may pass on this per­son­al data col­lect­ed via the tech­ni­cal process to third par­ties. The data sub­ject can pre­vent the set­ting of cook­ies by our web­site, as already described above, at any time by means of an appro­pri­ate set­ting of the Inter­net brows­er used and thus per­ma­nent­ly object to the set­ting of cook­ies. Such a set­ting of the Inter­net brows­er used would also pre­vent Google from set­ting a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. In addi­tion, a cook­ie already set by Google Ana­lyt­ics can be delet­ed at any time via the inter­net brows­er or oth­er soft­ware pro­grammes. Fur­ther­more, the data sub­ject has the pos­si­bil­i­ty to object to the col­lec­tion of data gen­er­at­ed by Google Ana­lyt­ics and relat­ed to the use of this web­site as well as to the pro­cess­ing of such data by Google and to pre­vent such pro­cess­ing. For this pur­pose, the data sub­ject must down­load and install a brows­er add-on under the link https://tools.google.com/dlpage/gaoptout. This brows­er add-on informs Google Ana­lyt­ics via JavaScript that no data and infor­ma­tion on vis­its to Inter­net pages may be trans­mit­ted to Google Ana­lyt­ics. The instal­la­tion of the brows­er add-on is con­sid­ered by Google as an objec­tion. If the data sub­jec­t’s infor­ma­tion tech­nol­o­gy sys­tem is delet­ed, for­mat­ted or rein­stalled at a lat­er date, the data sub­ject must rein­stall the brows­er add-on in order to deac­ti­vate Google Ana­lyt­ics. If the brows­er add-on is unin­stalled or deac­ti­vat­ed by the data sub­ject or anoth­er per­son with­in his or her con­trol, the brows­er add-on can be rein­stalled or reac­ti­vat­ed. Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google can be found at https://www.google.de/intl/de/policies/privacy/ and at http://www.google.com/analytics/terms/de.html. Google Ana­lyt­ics is explained in more detail under this link https://www.google.com/intl/de_de/analytics/.

14. Data protection provisions on the use and application of Google Remarketing

The con­troller has inte­grat­ed Google Remar­ket­ing ser­vices on this web­site. Google Remar­ket­ing is a func­tion of Google AdWords that enables a com­pa­ny to dis­play adver­tise­ments to Inter­net users who have pre­vi­ous­ly vis­it­ed the com­pa­ny’s web­site. The inte­gra­tion of Google Remar­ket­ing thus allows a com­pa­ny to cre­ate user-relat­ed adver­tis­ing and con­se­quent­ly to dis­play inter­est-rel­e­vant adver­tise­ments to the Inter­net user. The com­pa­ny oper­at­ing the Google Remar­ket­ing ser­vices is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land. The pur­pose of Google Remar­ket­ing is the dis­play of inter­est-rel­e­vant adver­tis­ing. Google Remar­ket­ing enables us to dis­play adver­tise­ments via the Google adver­tis­ing net­work or on oth­er web­sites that are tai­lored to the indi­vid­ual needs and inter­ests of inter­net users. Google Remar­ket­ing sets a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. What cook­ies are has already been explained above. The cook­ie enables Google to recog­nise the vis­i­tor to our web­site when he or she sub­se­quent­ly vis­its web­sites that are also mem­bers of the Google adver­tis­ing net­work. Each time a web­site is accessed on which the Google Remar­ket­ing ser­vice has been inte­grat­ed, the inter­net brows­er of the per­son con­cerned auto­mat­i­cal­ly iden­ti­fies itself to Google. With­in the scope of this tech­ni­cal pro­ce­dure, Google obtains knowl­edge of per­son­al data, such as the IP address or the user’s surf­ing behav­iour, which Google uses, among oth­er things, to dis­play inter­est-rel­e­vant adver­tis­ing. By means of the cook­ie, per­son­al infor­ma­tion, such as the web­sites vis­it­ed by the per­son con­cerned, is stored. Each time the data sub­ject vis­its our web­site, per­son­al data, includ­ing the IP address of the inter­net con­nec­tion used by the data sub­ject, is trans­mit­ted to Google in the Unit­ed States of Amer­i­ca. This per­son­al data is stored by Google in the Unit­ed States of Amer­i­ca. Google may dis­close this per­son­al data col­lect­ed via the tech­ni­cal process to third par­ties. The data sub­ject can pre­vent the set­ting of cook­ies by our web­site, as already described above, at any time by means of an appro­pri­ate set­ting of the Inter­net brows­er used and thus per­ma­nent­ly object to the set­ting of cook­ies. Such a set­ting of the Inter­net brows­er used would also pre­vent Google from set­ting a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. In addi­tion, a cook­ie already set by Google Ana­lyt­ics can be delet­ed at any time via the inter­net brows­er or oth­er soft­ware pro­grammes. Fur­ther­more, the data sub­ject has the option to object to inter­est-based adver­tis­ing by Google. To do this, the data sub­ject must call up the link www.google.de/settings/ads from any of the inter­net browsers he or she uses and make the desired set­tings there. Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google can be found at https://www.google.de/intl/de/policies/privacy/.

15. Data protection provisions on the use and application of Google+.

The con­troller has inte­grat­ed the Google+ but­ton as a com­po­nent on this web­site. Google+ is a so-called social net­work. A social net­work is a social meet­ing place oper­at­ed on the Inter­net, an online com­mu­ni­ty that gen­er­al­ly enables users to com­mu­ni­cate with each oth­er and inter­act in vir­tu­al space. A social net­work can serve as a plat­form for shar­ing opin­ions and expe­ri­ences or enables the inter­net com­mu­ni­ty to pro­vide per­son­al or com­pa­ny-relat­ed infor­ma­tion. Among oth­er things, Google+ allows users of the social net­work to cre­ate pri­vate pro­files, upload pho­tos and net­work via friend requests. The oper­at­ing com­pa­ny of Google+ is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land. By each call of one of the indi­vid­ual pages of this web­site, which is oper­at­ed by the con­troller and on which a Google+ but­ton has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly caused by the respec­tive Google+ but­ton to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing Google+ but­ton from Google. With­in the scope of this tech­ni­cal pro­ce­dure, Google receives infor­ma­tion about which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. More detailed infor­ma­tion on Google+ can be found at. If the data sub­ject is logged in to Google+ at the same time, Google recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Google+ but­ton and assigned by Google to the respec­tive Google+ account of the data sub­ject. If the data sub­ject acti­vates one of the Google+ but­tons inte­grat­ed on our web­site and thus sub­mits a Google+1 rec­om­men­da­tion, Google will asso­ciate this infor­ma­tion with the data sub­jec­t’s per­son­al Google+ user account and store this per­son­al data. Google stores the Google+1 rec­om­men­da­tion of the data sub­ject and makes it pub­licly avail­able in accor­dance with the terms and con­di­tions accept­ed by the data sub­ject in this regard. A Google+1 rec­om­men­da­tion made by the data sub­ject on this web­site will sub­se­quent­ly be stored and processed togeth­er with oth­er per­son­al data, such as the name of the Google+1 account used by the data sub­ject and the pho­to stored in this account, in oth­er Google ser­vices, for exam­ple the search engine results of the Google search engine, the Google account of the data sub­ject or in oth­er places, for exam­ple on web­sites or in con­nec­tion with adver­tise­ments. Fur­ther­more, Google is able to link the vis­it to this web­site with oth­er per­son­al data stored by Google. Google also records this per­son­al infor­ma­tion for the pur­pose of improv­ing or opti­mis­ing Google’s var­i­ous ser­vices. Google always receives infor­ma­tion via the Google+ but­ton that the data sub­ject has vis­it­ed our web­site if the data sub­ject is simul­ta­ne­ous­ly logged into Google+ at the time of call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Google+ but­ton or not. If the data sub­ject does not want per­son­al data to be trans­mit­ted to Google, he or she can pre­vent such trans­mis­sion by log­ging out of his or her Google+ account before access­ing our web­site. Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google can be found at https://www.google.de/intl/de/policies/privacy/. Fur­ther infor­ma­tion from Google on the Google+1 but­ton can be found at.

16. Data protection provisions on the use and application of Google AdWords

The con­troller has inte­grat­ed Google AdWords on this web­site. Google AdWords is an inter­net adver­tis­ing ser­vice that allows adver­tis­ers to place ads in Google’s search engine results as well as in the Google adver­tis­ing net­work. Google AdWords allows an adver­tis­er to spec­i­fy cer­tain key­words in advance, by means of which an ad is dis­played in Google’s search engine results exclu­sive­ly when the user retrieves a key­word-rel­e­vant search result with the search engine. In the Google adver­tis­ing net­work, the ads are dis­trib­uted on top­ic-rel­e­vant web­sites by means of an auto­mat­ic algo­rithm and in com­pli­ance with the pre­vi­ous­ly defined key­words. The com­pa­ny oper­at­ing the Google AdWords ser­vices is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land. The pur­pose of Google AdWords is to adver­tise our web­site by dis­play­ing inter­est-rel­e­vant adver­tis­ing on the web­sites of third-par­ty com­pa­nies and in the search engine results of the Google search engine and to dis­play third-par­ty adver­tis­ing on our web­site. If a data sub­ject access­es our web­site via a Google adver­tise­ment, a so-called con­ver­sion cook­ie will be stored by Google on the data sub­jec­t’s infor­ma­tion tech­nol­o­gy sys­tem. What cook­ies are has already been explained above. A con­ver­sion cook­ie los­es its valid­i­ty after thir­ty days and does not serve to iden­ti­fy the data sub­ject. The con­ver­sion cook­ie is used to track whether cer­tain sub-pages, for exam­ple the shop­ping bas­ket of an online shop sys­tem, have been called up on our web­site, pro­vid­ed the cook­ie has not yet expired. The con­ver­sion cook­ie enables both us and Google to track whether a data sub­ject who has accessed our web­site via an AdWords ad has gen­er­at­ed a sale, i.e. has com­plet­ed or can­celled a pur­chase of goods. The data and infor­ma­tion col­lect­ed through the use of the con­ver­sion cook­ie are used by Google to com­pile vis­it sta­tis­tics for our web­site. These vis­it sta­tis­tics are in turn used by us to deter­mine the total num­ber of users who were referred to us via AdWords ads, i.e. to deter­mine the suc­cess or fail­ure of the respec­tive AdWords ad and to opti­mise our AdWords ads for the future. Nei­ther our com­pa­ny nor oth­er adver­tis­ers of Google AdWords receive infor­ma­tion from Google by means of which the data sub­ject could be iden­ti­fied. By means of the con­ver­sion cook­ie, per­son­al infor­ma­tion, such as the web­sites vis­it­ed by the data sub­ject, is stored. Each time the data sub­ject vis­its our web­site, per­son­al data, includ­ing the IP address of the inter­net con­nec­tion used by the data sub­ject, is trans­mit­ted to Google in the Unit­ed States of Amer­i­ca. This per­son­al data is stored by Google in the Unit­ed States of Amer­i­ca. Google may dis­close this per­son­al data col­lect­ed via the tech­ni­cal process to third par­ties. The data sub­ject can pre­vent the set­ting of cook­ies by our web­site at any time by means of an appro­pri­ate set­ting of the Inter­net brows­er used, as already described above, and thus per­ma­nent­ly object to the set­ting of cook­ies. Such a set­ting of the inter­net brows­er used would also pre­vent Google from set­ting a con­ver­sion cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. In addi­tion, a cook­ie already set by Google AdWords can be delet­ed at any time via the inter­net brows­er or oth­er soft­ware pro­grammes. Fur­ther­more, the data sub­ject has the option to object to inter­est-based adver­tis­ing by Google. To do this, the data sub­ject must call up the link www.google.de/settings/ads from any of the inter­net browsers he or she uses and make the desired set­tings there. Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google can be found at https://www.google.de/intl/de/policies/privacy/.

17. Data protection provisions on the use and application of Instagram

The con­troller has inte­grat­ed com­po­nents of the Insta­gram ser­vice on this web­site. Insta­gram is a ser­vice that qual­i­fies as an audio­vi­su­al plat­form and allows users to share pho­tos and videos and also to redis­trib­ute such data in oth­er social net­works. The oper­a­tor of the Insta­gram ser­vices is Face­book Ire­land Ltd, 4 Grand Canal Square, Grand Canal Har­bour, Dublin 2 Ire­land. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up and on which an Insta­gram com­po­nent (Ins­ta but­ton) has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly caused by the respec­tive Insta­gram com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing com­po­nent from Insta­gram. With­in the scope of this tech­ni­cal pro­ce­dure, Insta­gram receives infor­ma­tion about which spe­cif­ic sub­page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged into Insta­gram at the same time, Insta­gram recog­nis­es which spe­cif­ic sub-page the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Insta­gram com­po­nent and assigned by Insta­gram to the respec­tive Insta­gram account of the data sub­ject. If the data sub­ject acti­vates one of the Insta­gram but­tons inte­grat­ed on our web­site, the data and infor­ma­tion thus trans­mit­ted will be assigned to the per­son­al Insta­gram user account of the data sub­ject and stored and processed by Insta­gram. Insta­gram always receives infor­ma­tion via the Insta­gram com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is simul­ta­ne­ous­ly logged into Insta­gram at the time of call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Insta­gram com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Insta­gram, he or she can pre­vent the trans­mis­sion by log­ging out of his or her Insta­gram account before access­ing our web­site. Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Insta­gram can be found at https://help.instagram.com/155833707900388 and https://www.instagram.com/about/legal/privacy/.

18. Data protection provisions on the use and application of LinkedIn

The con­troller has inte­grat­ed com­po­nents of the LinkedIn Cor­po­ra­tion on this web­site. LinkedIn is an Inter­net-based social net­work that allows users to con­nect with exist­ing busi­ness con­tacts and to make new busi­ness con­tacts. Over 400 mil­lion reg­is­tered peo­ple use LinkedIn in more than 200 coun­tries. This makes LinkedIn cur­rent­ly the largest plat­form for busi­ness con­tacts and one of the most vis­it­ed web­sites in the world. The oper­at­ing com­pa­ny of LinkedIn is LinkedIn Cor­po­ra­tion, 2029 Stier­lin Court Moun­tain View, CA 94043, USA. For data pro­tec­tion issues out­side the USA, LinkedIn Ire­land, Pri­va­cy Pol­i­cy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ire­land, is respon­si­ble. With each indi­vid­ual call-up of our web­site that is equipped with a LinkedIn com­po­nent (LinkedIn plug-in), this com­po­nent caus­es the brows­er used by the data sub­ject to down­load a cor­re­spond­ing rep­re­sen­ta­tion of the com­po­nent from LinkedIn. Fur­ther infor­ma­tion on LinkedIn plug-ins can be found at https://developer.linkedin.com/plugins. With­in the scope of this tech­ni­cal pro­ce­dure, LinkedIn receives knowl­edge of which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged in to LinkedIn at the same time, LinkedIn recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing with each call-up of our web­site by the data sub­ject and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the LinkedIn com­po­nent and assigned by LinkedIn to the respec­tive LinkedIn account of the data sub­ject. If the data sub­ject acti­vates a LinkedIn but­ton inte­grat­ed on our web­site, LinkedIn assigns this infor­ma­tion to the per­son­al LinkedIn user account of the data sub­ject and stores this per­son­al data. LinkedIn always receives infor­ma­tion via the LinkedIn com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is simul­ta­ne­ous­ly logged into LinkedIn at the time of call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the LinkedIn com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to LinkedIn, he or she can pre­vent the trans­mis­sion by log­ging out of his or her LinkedIn account before access­ing our web­site. LinkedIn offers the pos­si­bil­i­ty to unsub­scribe from email mes­sages, SMS mes­sages and tar­get­ed ads as well as to man­age ad set­tings at https://www.linkedin.com/psettings/guest-controls. LinkedIn also uses part­ners such as Quant­cast, Google Ana­lyt­ics, BlueKai, Dou­bleClick, Nielsen, Com­score, Elo­qua and Lotame, which may set cook­ies. Such cook­ies can be reject­ed at https://www.linkedin.com/legal/cookie-policy. Linked­In’s applic­a­ble pri­va­cy pol­i­cy is avail­able at https://www.linkedin.com/legal/privacy-policy. Linked­In’s cook­ie pol­i­cy is avail­able at https://www.linkedin.com/legal/cookie-policy.

19. Data protection provisions on the use and application of Myspace

The con­troller has inte­grat­ed com­po­nents of Myspace LLC on this web­site. Myspace is a so-called social net­work. A social net­work is a social meet­ing place oper­at­ed on the Inter­net, an online com­mu­ni­ty that gen­er­al­ly enables users to com­mu­ni­cate with each oth­er and inter­act in vir­tu­al space. A social net­work can serve as a plat­form for exchang­ing opin­ions and expe­ri­ences or enables the Inter­net com­mu­ni­ty to pro­vide per­son­al or com­pa­ny-relat­ed infor­ma­tion. Myspace allows users of the social net­work, among oth­er things, to set up free user pro­files con­tain­ing pho­tos and videos, blogs or groups. The oper­at­ing com­pa­ny of Myspace is Myspace LLC, 6100 Cen­ter Dri­ve, Suite 800, 90045 Los Ange­les, USA. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up, on which a Myspace com­po­nent (Myspace plug-in) has been inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed by the respec­tive Myspace com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing Myspace com­po­nent from Myspace. More infor­ma­tion on Myspace is avail­able at https://myspace.com. With­in the scope of this tech­ni­cal pro­ce­dure, Myspace receives knowl­edge of which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged in to Myspace at the same time, Myspace recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Myspace com­po­nent and assigned by Myspace to the respec­tive Myspace account of the data sub­ject. If the data sub­ject acti­vates a Myspace but­ton inte­grat­ed on our web­site, Myspace assigns this infor­ma­tion to the per­son­al Myspace user account of the data sub­ject and stores this per­son­al data. Myspace always receives infor­ma­tion via the Myspace com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is simul­ta­ne­ous­ly logged in to Myspace at the time of call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Myspace com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Myspace, he or she can pre­vent the trans­mis­sion by log­ging out of his or her Myspace account before access­ing our web­site. The pri­va­cy pol­i­cy pub­lished by Myspace, which is avail­able at https://myspace.com/pages/privacy, pro­vides infor­ma­tion on the col­lec­tion, pro­cess­ing and use of per­son­al data by Myspace.

20. data protection provisions on the use and application of Pinterest

The con­troller has inte­grat­ed com­po­nents of Pin­ter­est Inc. on this web­site. Pin­ter­est is a so-called social net­work. A social net­work is a social meet­ing place oper­at­ed on the Inter­net, an online com­mu­ni­ty that gen­er­al­ly enables users to com­mu­ni­cate with each oth­er and inter­act in vir­tu­al space. A social net­work can serve as a plat­form for exchang­ing opin­ions and expe­ri­ences or enables the inter­net com­mu­ni­ty to pro­vide per­son­al or com­pa­ny-relat­ed infor­ma­tion. Among oth­er things, Pin­ter­est enables users of the social net­work to pub­lish image col­lec­tions and indi­vid­ual images as well as descrip­tions on vir­tu­al pin­boards (so-called pin­ning), which can then in turn be shared by oth­er users (so-called repin­ning) or com­ment­ed on. The oper­at­ing com­pa­ny of Pin­ter­est is Pin­ter­est Europe Ltd, Palmer­ston House, 2nd Floor, Fen­ian Street, Dublin 2, Ire­land. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up and on which a Pin­ter­est com­po­nent (Pin­ter­est plug-in) has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed by the respec­tive Pin­ter­est com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing Pin­ter­est com­po­nent from Pin­ter­est. More infor­ma­tion on Pin­ter­est is avail­able at https://pinterest.com/. As part of this tech­ni­cal pro­ce­dure, Pin­ter­est receives infor­ma­tion about which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged into Pin­ter­est at the same time, Pin­ter­est recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Pin­ter­est com­po­nent and assigned by Pin­ter­est to the respec­tive Pin­ter­est account of the data sub­ject. If the data sub­ject acti­vates a Pin­ter­est but­ton inte­grat­ed on our web­site, Pin­ter­est assigns this infor­ma­tion to the per­son­al Pin­ter­est user account of the data sub­ject and stores this per­son­al data. Pin­ter­est always receives infor­ma­tion via the Pin­ter­est com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is simul­ta­ne­ous­ly logged into Pin­ter­est at the time of call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Pin­ter­est com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Pin­ter­est, he or she can pre­vent the trans­mis­sion by log­ging out of his or her Pin­ter­est account before access­ing our web­site. The pri­va­cy pol­i­cy pub­lished by Pin­ter­est, which can be accessed at https://about.pinterest.com/privacy-policy, pro­vides infor­ma­tion on the col­lec­tion, pro­cess­ing and use of per­son­al data by Pinterest.

21. Data protection provisions on the use and application of SlideShare

The con­troller has inte­grat­ed SlideShare com­po­nents on this web­site. LinkedIn SlideShare is a file host­ing ser­vice that allows users to share and archive pre­sen­ta­tions and oth­er doc­u­ments such as PDF files, videos and webi­na­rs. The file host­ing ser­vice allows users to upload media con­tent in all com­mon for­mats, where­by the doc­u­ments can either be made pub­licly acces­si­ble or marked pri­vate. The oper­at­ing com­pa­ny of SlideShare is LinkedIn Ire­land Unlim­it­ed Com­pa­ny, Wilton Plaza, Wilton Place, Dublin 2, Ire­land. LinkedIn SlideShare pro­vides so-called embed codes for the media con­tent stored there (pre­sen­ta­tions, PDF files, videos, pho­tos, etc.). Embed codes are pro­gramme codes that are embed­ded in inter­net pages with the aim of dis­play­ing exter­nal con­tent on one’s own inter­net page. Embed codes make it pos­si­ble to repro­duce con­tent on one’s own web­site with­out stor­ing it on one’s own serv­er and there­by pos­si­bly vio­lat­ing the repro­duc­tion rights of the respec­tive author of the con­tent. A fur­ther advan­tage of using an embed code is that the respec­tive oper­a­tor of an Inter­net page does not use his own stor­age space and his own serv­er is there­by relieved. An embed code can be inte­grat­ed at any point on anoth­er web­site, so that exter­nal con­tent can also be insert­ed with­in one’s own text. The pur­pose of using LinkedIn SlideShare is to reduce the load on our serv­er and to avoid copy­right infringe­ments when using exter­nal con­tent at the same time. Each time our web­site is accessed, which is equipped with a SlideShare com­po­nent (embed codes), this com­po­nent caus­es the brows­er used by you to down­load cor­re­spond­ing embed­ded data from SlideShare. As part of this tech­ni­cal pro­ce­dure, LinkedIn receives infor­ma­tion about which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged into SlideShare at the same time, SlideShare recog­nis­es which spe­cif­ic sub-page the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by SlideShare and assigned by LinkedIn to the respec­tive SlideShare account of the data sub­ject. LinkedIn always receives infor­ma­tion via the SlideShare com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is logged into SlideShare at the same time as call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the embed­ded media data or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to LinkedIn, he or she can pre­vent the trans­mis­sion by log­ging out of his or her SlideShare account before access­ing our web­site. LinkedIn also uses part­ners such as Quant­cast, Google Ana­lyt­ics, BlueKai, Dou­bleClick, Nielsen, Com­score, Elo­qua and Lotame, which can set cook­ies. Such cook­ies can be reject­ed at https://www.linkedin.com/legal/cookie-policy. Linked­In’s applic­a­ble pri­va­cy pol­i­cy can be found at https://www.linkedin.com/legal/privacy-policy.

22. Data protection provisions on the use and application of Tumblr

The con­troller has inte­grat­ed Tum­blr com­po­nents on this web­site. Tum­blr is a plat­form that allows users to cre­ate and oper­ate a blog. A blog is a por­tal main­tained on a web­site, usu­al­ly pub­licly view­able, in which one or more per­sons, called blog­gers or weblog­gers, can post arti­cles or write down thoughts in so-called blog­posts. In a blog on Tum­blr, the user can, for exam­ple, pub­lish texts, images, links and videos and dis­trib­ute them in the dig­i­tal space. Tum­blr users can also trans­fer con­tent from oth­er web­sites to their own blog. Tum­blr is oper­at­ed by Oath (EMEA) Lim­it­ed, 5–7 Point Square, North Wall Quay, Dublin 1, Ire­land. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up, on which a Tum­blr com­po­nent (Tum­blr but­ton) has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly caused by the respec­tive Tum­blr com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing Tum­blr com­po­nent from Tum­blr. Fur­ther infor­ma­tion on Tum­blr but­tons is avail­able at https://www.tumblr.com/buttons. With­in the scope of this tech­ni­cal pro­ce­dure, Tum­blr receives knowl­edge of which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. The pur­pose of inte­grat­ing the Tum­blr com­po­nent is to enable our users to dis­sem­i­nate the con­tent of this web­site, to make this web­site known in the dig­i­tal world and to increase our vis­i­tor num­bers. If the data sub­ject is logged in to Tum­blr at the same time, Tum­blr recog­nis­es which spe­cif­ic sub­page of our web­site the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Tum­blr com­po­nent and assigned by Tum­blr to the respec­tive Tum­blr account of the data sub­ject. If the data sub­ject acti­vates one of the Tum­blr but­tons inte­grat­ed on our web­site, the data and infor­ma­tion thus trans­mit­ted will be assigned to the per­son­al Tum­blr user account of the data sub­ject and stored and processed by Tum­blr. Tum­blr always receives infor­ma­tion via the Tum­blr com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is simul­ta­ne­ous­ly logged in to Tum­blr at the time of call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Tum­blr com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Tum­blr, he or she can pre­vent the trans­mis­sion by log­ging out of his or her Tum­blr account before access­ing our web­site. The applic­a­ble data pro­tec­tion pro­vi­sions of Tum­blr are avail­able at https://www.tumblr.com/policy/en/privacy.

23. Data protection provisions on the use and application of Twitter

The con­troller has inte­grat­ed com­po­nents of Twit­ter on this web­site. Twit­ter is a mul­ti­lin­gual pub­licly acces­si­ble microblog­ging ser­vice on which users can pub­lish and dis­sem­i­nate so-called tweets, i.e. short mes­sages lim­it­ed to 280 char­ac­ters. These short mes­sages can be accessed by any­one, includ­ing peo­ple who are not reg­is­tered with Twit­ter. How­ev­er, the tweets are also dis­played to the so-called fol­low­ers of the respec­tive user. Fol­low­ers are oth­er Twit­ter users who fol­low the tweets of a user. Fur­ther­more, Twit­ter makes it pos­si­ble to address a broad audi­ence via hash­tags, links or retweets. Twit­ter Inter­na­tion­al Com­pa­ny, One Cum­ber­land Place, Fen­ian Street Dublin 2, D02 AX07, Ire­land. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up and on which a Twit­ter com­po­nent (Twit­ter but­ton) has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly caused by the respec­tive Twit­ter com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing Twit­ter com­po­nent from Twit­ter. Fur­ther infor­ma­tion on the Twit­ter but­tons can be found at https://about.twitter.com/de/resources/buttons. With­in the scope of this tech­ni­cal pro­ce­dure, Twit­ter receives infor­ma­tion about which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. The pur­pose of inte­grat­ing the Twit­ter com­po­nent is to enable our users to dis­sem­i­nate the con­tent of this web­site, to make this web­site known in the dig­i­tal world and to increase our vis­i­tor num­bers. If the data sub­ject is logged into Twit­ter at the same time, Twit­ter recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Twit­ter com­po­nent and assigned by Twit­ter to the respec­tive Twit­ter account of the data sub­ject. If the data sub­ject acti­vates one of the Twit­ter but­tons inte­grat­ed on our web­site, the data and infor­ma­tion thus trans­mit­ted are assigned to the per­son­al Twit­ter user account of the data sub­ject and stored and processed by Twit­ter. Twit­ter always receives infor­ma­tion via the Twit­ter com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is logged into Twit­ter at the same time as call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Twit­ter com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Twit­ter, he or she can pre­vent the trans­mis­sion by log­ging out of his or her Twit­ter account before access­ing our web­site. The applic­a­ble data pro­tec­tion pro­vi­sions of Twit­ter are avail­able at https://twitter.com/privacy?lang=de.

24. Data protection provisions on the use and application of Xing

The con­troller has inte­grat­ed com­po­nents of Xing on this web­site. Xing is an Inter­net-based social net­work that allows users to con­nect with exist­ing busi­ness con­tacts and to make new busi­ness con­tacts. Indi­vid­ual users can cre­ate a per­son­al pro­file of them­selves on Xing. Com­pa­nies can, for exam­ple, cre­ate com­pa­ny pro­files or pub­lish job offers on Xing. The oper­at­ing com­pa­ny of Xing is XING SE, Damm­torstraße 30, 20354 Ham­burg, Ger­many. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the con­troller is called up and on which a Xing com­po­nent (Xing plug-in) has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed by the respec­tive Xing com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing Xing com­po­nent from Xing. Fur­ther infor­ma­tion on the Xing plug-ins can be found at https://dev.xing.com/plugins. With­in the scope of this tech­ni­cal pro­ce­dure, Xing receives infor­ma­tion about which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged in to Xing at the same time, Xing recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing each time the data sub­ject calls up our web­site and for the entire dura­tion of the respec­tive stay on our web­site. This infor­ma­tion is col­lect­ed by the Xing com­po­nent and assigned by Xing to the respec­tive Xing account of the data sub­ject. If the data sub­ject acti­vates one of the Xing but­tons inte­grat­ed on our web­site, for exam­ple the “Share” but­ton, Xing assigns this infor­ma­tion to the per­son­al Xing user account of the data sub­ject and stores this per­son­al data. Xing always receives infor­ma­tion via the Xing com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is logged into Xing at the same time as call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on the Xing com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Xing, he or she can pre­vent the trans­mis­sion by log­ging out of his or her Xing account before access­ing our web­site. The data pro­tec­tion pro­vi­sions pub­lished by Xing, which can be accessed at https://www.xing.com/privacy, pro­vide infor­ma­tion on the col­lec­tion, pro­cess­ing and use of per­son­al data by Xing. Fur­ther­more, Xing has pub­lished data pro­tec­tion infor­ma­tion for the XING Share but­ton at https://www.xing.com/app/share?op=data_protection.

25. Data protection provisions on the use and application of YouTube

The con­troller has inte­grat­ed YouTube com­po­nents on this web­site. YouTube is an Inter­net video por­tal that allows video pub­lish­ers to post video clips free of charge and oth­er users to view, rate and com­ment on them, also free of charge. YouTube allows the pub­li­ca­tion of all kinds of videos, which is why com­plete film and tele­vi­sion pro­grammes, but also music videos, trail­ers or videos made by users them­selves can be accessed via the Inter­net por­tal. The oper­at­ing com­pa­ny of YouTube is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up and on which a YouTube com­po­nent (YouTube video) has been inte­grat­ed, the inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly caused by the respec­tive YouTube com­po­nent to down­load a rep­re­sen­ta­tion of the cor­re­spond­ing YouTube com­po­nent from YouTube. Fur­ther infor­ma­tion on YouTube can be found at https://www.youtube.com/yt/about/de/. With­in the scope of this tech­ni­cal pro­ce­dure, YouTube and Google receive infor­ma­tion about which spe­cif­ic sub-page of our web­site is vis­it­ed by the data sub­ject. If the data sub­ject is logged into YouTube at the same time, YouTube recog­nis­es which spe­cif­ic sub-page of our web­site the data sub­ject is vis­it­ing when a sub-page con­tain­ing a YouTube video is called up. This infor­ma­tion is col­lect­ed by YouTube and Google and assigned to the respec­tive YouTube account of the data sub­ject. YouTube and Google always receive infor­ma­tion via the YouTube com­po­nent that the data sub­ject has vis­it­ed our web­site if the data sub­ject is logged into YouTube at the same time as call­ing up our web­site; this takes place regard­less of whether the data sub­ject clicks on a YouTube video or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to YouTube and Google, he or she can pre­vent the trans­mis­sion by log­ging out of his or her YouTube account before access­ing our web­site. The data pro­tec­tion pro­vi­sions pub­lished by YouTube, which can be accessed at https://www.google.de/intl/de/policies/privacy/, pro­vide infor­ma­tion on the col­lec­tion, pro­cess­ing and use of per­son­al data by YouTube and Google.

26. Data protection provisions on the use and application of DoubleClick

The con­troller has inte­grat­ed com­po­nents of Dou­bleClick by Google on this web­site. Dou­bleClick is a brand of Google, under which main­ly spe­cial online mar­ket­ing solu­tions are mar­ket­ed to adver­tis­ing agen­cies and pub­lish­ers. It is oper­at­ed by Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land. Dou­bleClick by Google trans­mits data to the Dou­bleClick serv­er with each impres­sion as well as with clicks or oth­er activ­i­ties. Each of these data trans­fers trig­gers a cook­ie request to the brows­er of the data sub­ject. If the brows­er accepts this request, Dou­bleClick sets a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. What cook­ies are has already been explained above. The pur­pose of the cook­ie is the opti­mi­sa­tion and dis­play of adver­tis­ing. Among oth­er things, the cook­ie is used to serve and dis­play user-rel­e­vant adver­tis­ing and to cre­ate reports on adver­tis­ing cam­paigns or to improve them. Fur­ther­more, the cook­ie is used to avoid mul­ti­ple dis­plays of the same adver­tise­ment. Dou­bleClick uses a cook­ie ID, which is required to process the tech­ni­cal pro­ce­dure. The cook­ie ID is need­ed, for exam­ple, to dis­play an adver­tise­ment in a brows­er. Dou­bleClick can also use the cook­ie ID to record which adver­tise­ments have already been dis­played in a brows­er in order to avoid dupli­cate place­ments. Fur­ther­more, the cook­ie ID enables Dou­bleClick to record con­ver­sions. Con­ver­sions are record­ed, for exam­ple, when a Dou­bleClick ad has pre­vi­ous­ly been dis­played to a user and the user sub­se­quent­ly makes a pur­chase on the adver­tis­er’s web­site using the same inter­net brows­er. A Dou­bleClick cook­ie does not con­tain any per­son­al data. How­ev­er, a Dou­bleClick cook­ie may con­tain addi­tion­al cam­paign iden­ti­fiers. A cam­paign iden­ti­fi­er serves to iden­ti­fy the cam­paigns with which the user has already been in con­tact. Each time one of the indi­vid­ual pages of this web­site oper­at­ed by the data con­troller is called up and on which a Dou­bleClick com­po­nent has been inte­grat­ed, the inter­net brows­er on the data sub­jec­t’s infor­ma­tion tech­nol­o­gy sys­tem is auto­mat­i­cal­ly caused by the respec­tive Dou­bleClick com­po­nent to trans­mit data to Google for the pur­pose of online adver­tis­ing and the set­tle­ment of com­mis­sions. As part of this tech­ni­cal process, Google obtains knowl­edge of data that Google also uses to gen­er­ate com­mis­sion state­ments. Among oth­er things, Google can track that the data sub­ject has clicked on cer­tain links on our web­site. The data sub­ject can pre­vent the set­ting of cook­ies by our web­site, as already described above, at any time by means of an appro­pri­ate set­ting of the Inter­net brows­er used and thus per­ma­nent­ly object to the set­ting of cook­ies. Such a set­ting of the Inter­net brows­er used would also pre­vent Google from set­ting a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. In addi­tion, cook­ies already set by Google can be delet­ed at any time via an inter­net brows­er or oth­er soft­ware pro­grammes. Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Dou­bleClick by Google can be found at https://www.google.com/intl/de/policies/.

27. Legal basis for processing

Arti­cle 6 I lit. a DS-GVO serves as the legal basis for our com­pa­ny for pro­cess­ing oper­a­tions in which we obtain con­sent for a spe­cif­ic pro­cess­ing pur­pose. If the pro­cess­ing of per­son­al data is nec­es­sary for the per­for­mance of a con­tract to which the data sub­ject is a par­ty, as is the case, for exam­ple, with pro­cess­ing oper­a­tions that are nec­es­sary for the deliv­ery of goods or the pro­vi­sion of anoth­er ser­vice or con­sid­er­a­tion, the pro­cess­ing is based on Arti­cle 6 I lit. b DS-GVO. The same applies to pro­cess­ing oper­a­tions that are nec­es­sary for the imple­men­ta­tion of pre-con­trac­tu­al mea­sures, for exam­ple in the case of enquiries about our prod­ucts or ser­vices. If our com­pa­ny is sub­ject to a legal oblig­a­tion by which the pro­cess­ing of per­son­al data becomes nec­es­sary, such as for the ful­fil­ment of tax oblig­a­tions, the pro­cess­ing is based on Art. 6 I lit. c DS-GVO. In rare cas­es, the pro­cess­ing of per­son­al data might become nec­es­sary in order to pro­tect the vital inter­ests of the data sub­ject or anoth­er nat­ur­al per­son. This would be the case, for exam­ple, if a vis­i­tor were to be injured on our premis­es and as a result his or her name, age, health insur­ance details or oth­er vital infor­ma­tion had to be passed on to a doc­tor, hos­pi­tal or oth­er third par­ty. Then the pro­cess­ing would be based on Art. 6 I lit. d DS-GVO. Final­ly, pro­cess­ing oper­a­tions could be based on Art. 6 I lit. f DS-GVO. Pro­cess­ing oper­a­tions which are not cov­ered by any of the afore­men­tioned legal bases are based on this legal basis if the pro­cess­ing is nec­es­sary to pro­tect a legit­i­mate inter­est of our com­pa­ny or a third par­ty, pro­vid­ed that the inter­ests, fun­da­men­tal rights and free­doms of the data sub­ject are not over­rid­den. Such pro­cess­ing oper­a­tions are per­mit­ted to us in par­tic­u­lar because they were specif­i­cal­ly men­tioned by the Euro­pean leg­is­la­tor. In this respect, it took the view that a legit­i­mate inter­est could be assumed if the data sub­ject is a cus­tomer of the con­troller (recital 47, sen­tence 2 of the GDPR).

28. Legitimate interests in the processing pursued by the controller or a third party

If the pro­cess­ing of per­son­al data is based on Arti­cle 6 I lit. f of the GDPR, our legit­i­mate inter­est is the per­for­mance of our busi­ness activ­i­ties for the ben­e­fit of the well-being of all our employ­ees and our shareholders.

29. duration for which the personal data are stored

The cri­te­ri­on for the dura­tion of the stor­age of per­son­al data is the respec­tive statu­to­ry reten­tion peri­od. After expiry of the peri­od, the cor­re­spond­ing data is rou­tine­ly delet­ed, pro­vid­ed that it is no longer required for the ful­fil­ment of the con­tract or the ini­ti­a­tion of the contract.

30. Legal or contractual provisions for the provision of personal data; necessity for the conclusion of the contract; obligation of the data subject to provide the personal data; possible consequences of non-provision

We inform you that the pro­vi­sion of per­son­al data is some­times required by law (e.g. tax reg­u­la­tions) or may also result from con­trac­tu­al reg­u­la­tions (e.g. infor­ma­tion on the con­trac­tu­al part­ner). Some­times, in order to con­clude a con­tract, it may be nec­es­sary for a data sub­ject to pro­vide us with per­son­al data that must sub­se­quent­ly be processed by us. For exam­ple, the data sub­ject is oblig­ed to pro­vide us with per­son­al data if our com­pa­ny con­cludes a con­tract with him or her. Fail­ure to pro­vide the per­son­al data would mean that the con­tract with the data sub­ject could not be con­clud­ed. Before pro­vid­ing per­son­al data by the data sub­ject, the data sub­ject must con­tact one of our employ­ees. Our employ­ee will explain to the data sub­ject on a case-by-case basis whether the pro­vi­sion of the per­son­al data is required by law or con­tract or nec­es­sary for the con­clu­sion of the con­tract, whether there is an oblig­a­tion to pro­vide the per­son­al data and what the con­se­quences of not pro­vid­ing the per­son­al data would be.

31. existence of automated decision-making

As a respon­si­ble com­pa­ny, we do not use auto­mat­ed deci­sion-mak­ing or pro­fil­ing. This data pro­tec­tion dec­la­ra­tion was cre­at­ed by the data pro­tec­tion dec­la­ra­tion gen­er­a­tor of DGD Deutsche Gesellschaft für Daten­schutz GmbH, which acts as the exter­nal data pro­tec­tion offi­cer for Upper Bavaria, in coop­er­a­tion with the data pro­tec­tion lawyers of the law firm WILDE BEUGER SOLMECKE | Recht­san­wälte.