Data pro­tec­tion declaration

Data pro­tec­tion is a mat­ter of par­ti­cu­lar­ly high importance to our com­pa­ny. Our web­site may basi­cal­ly be used wit­hout indi­ca­ting any per­so­nal data. If a per­son con­cer­ned wants to make online use of spe­cial ser­vices of our com­pa­ny, the pro­ces­sing of per­so­nal data might beco­me neces­sa­ry. In case the pro­ces­sing is requi­red and the­re is no legal basis for such pro­ces­sing, we gene­ral­ly seek the rele­vant person’s approval.

The pro­ces­sing of per­so­nal data such as name, address, e‑mail address or pho­ne num­ber of a per­son con­cer­ned is always effec­ted in accordance with the Fede­ral Data Pro­tec­tion Act (BDSG), the EU Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR), effec­ti­ve from 25th May 2018, and other appli­ca­ble laws. With this data pro­tec­tion decla­ra­ti­on our com­pa­ny wants to explain kind, ran­ge and pur­po­se of the per­so­nal data pro­ces­sed by us and inform per­sons con­cer­ned about their rights.

Our com­pa­ny has imple­men­ted num­e­rous tech­ni­cal and orga­niz­sa­tio­nal mea­su­res to ensu­re a most com­ple­te pro­tec­tion of the pro­ces­sed per­so­nal data. Howe­ver, inter­net-based data trans­mis­si­ons may invol­ve secu­ri­ty gaps so that an abso­lu­te pro­tec­tion can­not be guaranteed.

1. Defi­ni­ti­ons

The data pro­tec­tion decla­ra­ti­on of our com­pa­ny is based on the EU GDPR. Our data pro­tec­tion decla­ra­ti­on is inten­ded to be easy to read and under­stand. To ensu­re this, we explain the used terms beforehand:

1.1 Per­so­nal data

Per­so­nal data is „all infor­ma­ti­on refer­ring to an iden­ti­fied or iden­ti­fia­ble natu­ral per­son“ (her­ein­af­ter refer­red to as „per­son con­cer­ned“); a per­son is con­side­red iden­ti­fia­ble when iden­ti­fied direct­ly or indi­rect­ly via assign­ment to an ID like a name, to an iden­ti­fi­ca­ti­on num­ber, loca­ti­on data, an online ID or one or seve­ral spe­cial fea­tures expres­sing the phy­si­cal, phy­sio­lo­gi­cal, gene­tic, men­tal, eco­no­mic­al, cul­tu­ral or social iden­ti­ty of this natu­ral per­son” (GDPR, art. 4, par. 1)

1.2 Per­son concerned

A per­son con­cer­ned is any iden­ti­fied or iden­ti­fia­ble natu­ral per­son who­se per­so­nal data are pro­ces­sed by the per­son respon­si­ble for the processing.

1.3 Pro­ces­sing

Pro­ces­sing is any pro­cess with or wit­hout the sup­port of an auto­ma­ted ope­ra­ti­on or any such set of ope­ra­ti­ons which is per­for­med on per­so­nal data such as coll­ec­tion, recor­ding, orga­niza­ti­on, arran­ge­ment, sto­rage, adapt­a­ti­on or altera­ti­on, retrie­val, con­sul­ta­ti­on, use, dis­clo­sure by trans­mis­si­on, dis­se­mi­na­ti­on or other­wi­se making available, ali­gnment or com­bi­na­ti­on, blo­cking, era­su­re or destruction.

1.4 Rest­ric­tions to processing

Rest­ric­tions to pro­ces­sing shall mean the mar­king of stored per­so­nal data with the aim of rest­ric­ting their future processing.

1.5 Pro­fil­ing

Pro­fil­ing is any form of auto­ma­ted pro­ces­sing of per­so­nal data whe­re the­se data are used in order to assess cer­tain per­so­nal aspects rela­ting to a natu­ral per­son, par­ti­cu­lar­ly to ana­ly­ze or pre­dict aspects refer­ring to job per­for­mance, eco­no­mic situa­ti­on, health, per­so­nal pre­fe­ren­ces, inte­rests, relia­bi­li­ty, beha­vi­or, whe­re­a­bouts or chan­ge of loca­ti­on of this natu­ral person.

1.6 Pseud­ony­mi­sa­ti­on

Pseud­ony­mi­sa­ti­on is the pro­ces­sing of per­so­nal data whe­re per­so­nal data can no lon­ger be assi­gned to a spe­ci­fic per­son wit­hout invol­ving addi­tio­nal infor­ma­ti­on. This addi­tio­nal infor­ma­ti­on is stored sepa­ra­te­ly and sub­ject to tech­ni­cal and orga­niza­tio­nal mea­su­res, thus ensu­ring that per­so­nal data can­not be assi­gned to an iden­ti­fied or iden­ti­fia­ble natu­ral person.

1.7 Per­son in char­ge or per­son respon­si­ble for the processing

Per­son in char­ge or per­son respon­si­ble for the pro­ces­sing is the natu­ral or legal per­son, aut­ho­ri­ty, insti­tu­ti­on or any other body which alo­ne or joint­ly with others deter­mi­nes the pur­po­ses and means of the pro­ces­sing of per­so­nal data.

1.8 Order processor

Order pro­ces­sor is a natu­ral or legal per­son, aut­ho­ri­ty, insti­tu­ti­on or any other body pro­ces­sing per­so­nal data on behalf of the per­son in charge.

1.9 Reci­pi­ent

Reci­pi­ent is a natu­ral or legal per­son, aut­ho­ri­ty, insti­tu­ti­on or any other body to whom per­so­nal data are dis­c­lo­sed, whe­ther third par­ty or not. Howe­ver, aut­ho­ri­ties which may recei­ve per­so­nal data in the frame­work of a par­ti­cu­lar inquiry in accordance with the Uni­on law or the law of the mem­ber sta­tes shall not be regard­ed as recipients.

1.10 Third party

Third par­ty is a natu­ral or legal per­son, aut­ho­ri­ty, insti­tu­ti­on or any other body except the per­son con­cer­ned, the per­son in char­ge, the order pro­ces­sor and the per­sons who, under the direct aut­ho­ri­ty of the per­son in char­ge or the pro­ces­sor, are aut­ho­ri­zed to pro­cess per­so­nal data.

1.11 Con­sent

Con­sent is any free­ly given spe­ci­fic and infor­med indi­ca­ti­on of wis­hes by which the per­son con­cer­ned signi­fies his/her agree­ment to the pro­ces­sing of per­so­nal data rela­ting to him/her.

2. Name and adress of the per­son respon­si­ble for processing

Per­son in char­ge within the mea­ning of the GDPR is:

Ver­ant­wort­li­cher im Sin­ne der DS-GVO ist:
TDS Riet­berg GmbH & Co. KG
Brü­nings­weg 23
33397 Rietberg

Tele­fon:  +49 52 44 98 85 — 30
Tele­fax:  +49 52 44 98 85 — 32
E‑Mail:     info@tds-rietberg.de
WEB:       www.tds-rietberg.de

3. Cont­act details of our exter­nal data pro­tec­tion officer

Com­pli­ance to the rele­vant rules rela­ting to data pro­tec­tion as descri­bed in the Fede­ral Data Pro­tec­tion Act (BDSG), the EU Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR) and other appli­ca­ble laws is ensu­red by the per­son in charge.

Pro­vi­ded that this data pro­tec­tion decla­ra­ti­on refers to the data pro­tec­tion offi­cer, the per­son in char­ge named in par. 2 of this decla­ra­ti­on shall sup­port the per­son con­cer­ned in adhe­ring to the data pro­tec­tion regu­la­ti­ons, par­ti­cu­lar­ly in pre­ser­ving and imple­men­ting the rights of the per­son con­cer­ned, and be available as a cont­act person.

4. Coo­kies

The Inter­net pages of the Car­te­sy use coo­kies. Coo­kies are text files that are stored in a com­pu­ter sys­tem via an Inter­net browser.

Many Inter­net sites and ser­vers use coo­kies. Many coo­kies con­tain a so-cal­led coo­kie ID. A coo­kie ID is a uni­que iden­ti­fier of the coo­kie. It con­sists of a cha­rac­ter string through which Inter­net pages and ser­vers can be assi­gned to the spe­ci­fic Inter­net brow­ser in which the coo­kie was stored. This allows visi­ted Inter­net sites and ser­vers to dif­fe­ren­tia­te the indi­vi­du­al brow­ser of the dats sub­ject from other Inter­net brow­sers that con­tain other coo­kies. A spe­ci­fic Inter­net brow­ser can be reco­gni­zed and iden­ti­fied using the uni­que coo­kie ID. Through the use of coo­kies, the Car­te­sy GmbH can pro­vi­de the users of this web­site with more user-fri­end­ly ser­vices that would not be pos­si­ble wit­hout the coo­kie setting.

By means of a coo­kie, the infor­ma­ti­on and offers on our web­site can be opti­mi­zed with the user in mind. Coo­kies allow us, as pre­vious­ly men­tio­ned, to reco­gni­ze our web­site users. The pur­po­se of this reco­gni­ti­on is to make it easier for users to uti­li­ze our web­site. The web­site user that uses coo­kies, e.g. does not have to enter access data each time the web­site is acces­sed, becau­se this is taken over by the web­site, and the coo­kie is thus stored on the user’s com­pu­ter sys­tem. Ano­ther exam­p­le is the coo­kie of a shop­ping cart in an online shop. The online store remem­bers the artic­les that a cus­to­mer has pla­ced in the vir­tu­al shop­ping cart via a cookie.

The data sub­ject may, at any time, pre­vent the set­ting of coo­kies through our web­site by means of a cor­re­spon­ding set­ting of the Inter­net brow­ser used, and may thus per­ma­nent­ly deny the set­ting of coo­kies. Fur­ther­mo­re, alre­a­dy set coo­kies may be dele­ted at any time via an Inter­net brow­ser or other soft­ware pro­grams. This is pos­si­ble in all popu­lar Inter­net brow­sers. If the data sub­ject deac­ti­va­tes the set­ting of coo­kies in the Inter­net brow­ser used, not all func­tions of our web­site may be enti­re­ly usable.

5. Coll­ec­tion of gene­ral data and information

The web­site of the Car­te­sy mbH coll­ects a series of gene­ral data and infor­ma­ti­on when a data sub­ject or auto­ma­ted sys­tem calls up the web­site. This gene­ral data and infor­ma­ti­on are stored in the ser­ver log files. Coll­ec­ted may be (1) the brow­ser types and ver­si­ons used, (2) the ope­ra­ting sys­tem used by the acces­sing sys­tem, (3) the web­site from which an acces­sing sys­tem rea­ches our web­site (so-cal­led refer­rers), (4) the sub-web­sites, (5) the date and time of access to the Inter­net site, (6) an Inter­net pro­to­col address (IP address), (7) the Inter­net ser­vice pro­vi­der of the acces­sing sys­tem, and (8) any other simi­lar data and infor­ma­ti­on that may be used in the event of attacks on our infor­ma­ti­on tech­no­lo­gy systems.

When using the­se gene­ral data and infor­ma­ti­on, the Car­te­sy GmbH does not draw any con­clu­si­ons about the data sub­ject. Rather, this infor­ma­ti­on is nee­ded to (1) deli­ver the con­tent of our web­site cor­rect­ly, (2) opti­mi­ze the con­tent of our web­site as well as its adver­ti­se­ment, (3) ensu­re the long-term via­bi­li­ty of our infor­ma­ti­on tech­no­lo­gy sys­tems and web­site tech­no­lo­gy, and (4) pro­vi­de law enforce­ment aut­ho­ri­ties with the infor­ma­ti­on neces­sa­ry for cri­mi­nal pro­se­cu­ti­on in case of a cyber-attack. The­r­e­fo­re, the Car­te­sy GmbH ana­ly­zes anony­mously coll­ec­ted data and infor­ma­ti­on sta­tis­ti­cal­ly, with the aim of incre­asing the data pro­tec­tion and data secu­ri­ty of our enter­pri­se, and to ensu­re an opti­mal level of pro­tec­tion for the per­so­nal data we pro­cess. The anony­mous data of the ser­ver log files are stored sepa­ra­te­ly from all per­so­nal data pro­vi­ded by a data subject.

6. Cont­act pos­si­bi­li­ty via the website

The web­site of the Car­te­sy GmbH con­ta­ins infor­ma­ti­on that enables a quick elec­tro­nic cont­act to our enter­pri­se, as well as direct com­mu­ni­ca­ti­on with us, which also includes a gene­ral address of the so-cal­led elec­tro­nic mail (e‑mail address). If a data sub­ject cont­acts the con­trol­ler by e‑mail or via a cont­act form, the per­so­nal data trans­mit­ted by the data sub­ject are auto­ma­ti­cal­ly stored. Such per­so­nal data trans­mit­ted on a vol­un­t­a­ry basis by a data sub­ject to the data con­trol­ler are stored for the pur­po­se of pro­ces­sing or cont­ac­ting the data sub­ject. The­re is no trans­fer of this per­so­nal data to third parties.

7. Rou­ti­ne era­su­re and blo­cking of per­so­nal data

The data con­trol­ler shall pro­cess and store the per­so­nal data of the data sub­ject only for the peri­od neces­sa­ry to achie­ve the pur­po­se of sto­rage, or as far as this is gran­ted by the Euro­pean legis­la­tor or other legis­la­tors in laws or regu­la­ti­ons to which the con­trol­ler is sub­ject to.

If the sto­rage pur­po­se is not appli­ca­ble, or if a sto­rage peri­od pre­scri­bed by the Euro­pean legis­la­tor or ano­ther com­pe­tent legis­la­tor expi­res, the per­so­nal data are rou­ti­ne­ly blo­cked or era­sed in accordance with legal requirements.

8. Rights of the data subject

8.1 Right of confirmation

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to obtain from the con­trol­ler the con­fir­ma­ti­on as to whe­ther or not per­so­nal data con­cer­ning him or her are being pro­ces­sed. If a data sub­ject wis­hes to avail hims­elf of this right of con­fir­ma­ti­on, he or she may, at any time, cont­act any employee of the controller.

8.2 Right of access

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to obtain from the con­trol­ler free infor­ma­ti­on about his or her per­so­nal data stored at any time and a copy of this infor­ma­ti­on. Fur­ther­mo­re, the Euro­pean direc­ti­ves and regu­la­ti­ons grant the data sub­ject access to the fol­lo­wing information:

the pur­po­ses of the processing
the cate­go­ries of per­so­nal data concerned
the reci­pi­ents or cate­go­ries of reci­pi­ents to whom the per­so­nal data have been or will be dis­c­lo­sed, in par­ti­cu­lar reci­pi­ents in third count­ries or inter­na­tio­nal organisations
the exis­tence of the right to request from the con­trol­ler rec­ti­fi­ca­ti­on or era­su­re of per­so­nal data, or rest­ric­tion of pro­ces­sing of per­so­nal data con­cer­ning the data sub­ject, or to object to such processing
the exis­tence of the right to lodge a com­plaint with a super­vi­so­ry authority
whe­re the per­so­nal data are not coll­ec­ted from the data sub­ject, any available infor­ma­ti­on as to their source
the exis­tence of auto­ma­ted decis­i­on-making, inclu­ding pro­fil­ing, refer­red to in Artic­le 22(1) and (4) of the GDPR and, at least in tho­se cases, meaningful infor­ma­ti­on about the logic invol­ved, as well as the signi­fi­can­ce and envi­sa­ged con­se­quen­ces of such pro­ces­sing for the data subject
Fur­ther­mo­re, the data sub­ject shall have a right to obtain infor­ma­ti­on as to whe­ther per­so­nal data are trans­fer­red to a third coun­try or to an inter­na­tio­nal orga­ni­sa­ti­on. Whe­re this is the case, the data sub­ject shall have the right to be infor­med of the appro­pria­te safe­guards rela­ting to the transfer.

If a data sub­ject wis­hes to avail hims­elf of this right of access, he or she may, at any time, cont­act any employee of the controller.

8.3 Right of rectification

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to obtain from the con­trol­ler wit­hout undue delay the rec­ti­fi­ca­ti­on of inac­cu­ra­te per­so­nal data con­cer­ning him or her. Taking into account the pur­po­ses of the pro­ces­sing, the data sub­ject shall have the right to have incom­ple­te per­so­nal data com­ple­ted, inclu­ding by means of pro­vi­ding a sup­ple­men­ta­ry statement.

If a data sub­ject wis­hes to exer­cise this right to rec­ti­fi­ca­ti­on, he or she may, at any time, cont­act any employee of the controller.

8.4 Right to era­su­re (Right to be forgotten)

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to obtain from the con­trol­ler the era­su­re of per­so­nal data con­cer­ning him or her wit­hout undue delay, and the con­trol­ler shall have the obli­ga­ti­on to era­se per­so­nal data wit­hout undue delay whe­re one of the fol­lo­wing grounds appli­es, as long as the pro­ces­sing is not necessary

The per­so­nal data are no lon­ger neces­sa­ry in rela­ti­on to the pur­po­ses for which they were coll­ec­ted or other­wi­se processed.
The data sub­ject with­draws con­sent to which the pro­ces­sing is based accor­ding to point (a) of Artic­le 6(1) of the GDPR, or point (a) of Artic­le 9(2) of the GDPR, and whe­re the­re is no other legal ground for the processing.
The data sub­ject objects to the pro­ces­sing pur­su­ant to Artic­le 21(1) of the GDPR and the­re are no over­ri­ding legi­ti­ma­te grounds for the pro­ces­sing, or the data sub­ject objects to the pro­ces­sing pur­su­ant to Artic­le 21(2) of the GDPR.
The per­so­nal data have been unlawful­ly processed.
The per­so­nal data must be era­sed for com­pli­ance with a legal obli­ga­ti­on in Uni­on or Mem­ber Sta­te law to which the con­trol­ler is subject.
The per­so­nal data have been coll­ec­ted in rela­ti­on to the offer of infor­ma­ti­on socie­ty ser­vices refer­red to in Artic­le 8(1) of the GDPR.
If one of the afo­re­men­tio­ned reasons appli­es, and a data sub­ject wis­hes to request the era­su­re of per­so­nal data stored by the Feicht­ner Maschi­nen­bau, he or she may, at any time, cont­act any employee of the con­trol­ler. An employee of Car­te­sy GmbH shall prompt­ly ensu­re that the era­su­re request is com­pli­ed with immediately.

Whe­re the con­trol­ler has made per­so­nal data public and is obli­ged pur­su­ant to Artic­le 17(1) to era­se the per­so­nal data, the con­trol­ler, taking account of available tech­no­lo­gy and the cost of imple­men­ta­ti­on, shall take reasonable steps, inclu­ding tech­ni­cal mea­su­res, to inform other con­trol­lers pro­ces­sing the per­so­nal data that the data sub­ject has reques­ted era­su­re by such con­trol­lers of any links to, or copy or repli­ca­ti­on of, tho­se per­so­nal data, as far as pro­ces­sing is not requi­red. An employees of the Car­te­sy GmbH will arran­ge the neces­sa­ry mea­su­res in indi­vi­du­al cases.

8.5 Right of rest­ric­tion of processing

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to obtain from the con­trol­ler rest­ric­tion of pro­ces­sing whe­re one of the fol­lo­wing applies:

The accu­ra­cy of the per­so­nal data is con­tes­ted by the data sub­ject, for a peri­od enab­ling the con­trol­ler to veri­fy the accu­ra­cy of the per­so­nal data.
The pro­ces­sing is unlawful and the data sub­ject oppo­ses the era­su­re of the per­so­nal data and requests ins­tead the rest­ric­tion of their use instead.
The con­trol­ler no lon­ger needs the per­so­nal data for the pur­po­ses of the pro­ces­sing, but they are requi­red by the data sub­ject for the estab­lish­ment, exer­cise or defence of legal claims.
The data sub­ject has objec­ted to pro­ces­sing pur­su­ant to Artic­le 21(1) of the GDPR pen­ding the veri­fi­ca­ti­on whe­ther the legi­ti­ma­te grounds of the con­trol­ler over­ri­de tho­se of the data subject.
If one of the afo­re­men­tio­ned con­di­ti­ons is met, and a data sub­ject wis­hes to request the rest­ric­tion of the pro­ces­sing of per­so­nal data stored by the Car­te­sy GmbH, he or she may at any time cont­act any employee of the con­trol­ler. The employee of the Car­te­sy GmbH will arran­ge the rest­ric­tion of the processing.

8.6 Right to data portability

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor, to recei­ve the per­so­nal data con­cer­ning him or her, which was pro­vi­ded to a con­trol­ler, in a struc­tu­red, com­mon­ly used and machi­ne-rea­da­ble for­mat. He or she shall have the right to trans­mit tho­se data to ano­ther con­trol­ler wit­hout hin­drance from the con­trol­ler to which the per­so­nal data have been pro­vi­ded, as long as the pro­ces­sing is based on con­sent pur­su­ant to point (a) of Artic­le 6(1) of the GDPR or point (a) of Artic­le 9(2) of the GDPR, or on a con­tract pur­su­ant to point (b) of Artic­le 6(1) of the GDPR, and the pro­ces­sing is car­ri­ed out by auto­ma­ted means, as long as the pro­ces­sing is not neces­sa­ry for the per­for­mance of a task car­ri­ed out in the public inte­rest or in the exer­cise of offi­ci­al aut­ho­ri­ty ves­ted in the controller.

Fur­ther­mo­re, in exer­cis­ing his or her right to data por­ta­bi­li­ty pur­su­ant to Artic­le 20(1) of the GDPR, the data sub­ject shall have the right to have per­so­nal data trans­mit­ted direct­ly from one con­trol­ler to ano­ther, whe­re tech­ni­cal­ly fea­si­ble and when doing so does not adver­se­ly affect the rights and free­doms of other.

In order to assert the right to data por­ta­bi­li­ty, the data sub­ject may at any time cont­act any employee of the Car­te­sy GmbH.

8.7 Right to object

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to object, on grounds rela­ting to his or her par­ti­cu­lar situa­ti­on, at any time, to pro­ces­sing of per­so­nal data con­cer­ning him or her, which is based on point (e) or (f) of Artic­le 6(1) of the GDPR. This also appli­es to pro­fil­ing based on the­se provisions.

The Car­te­sy GmbH shall no lon­ger pro­cess the per­so­nal data in the event of the objec­tion, unless we can demons­tra­te com­pel­ling legi­ti­ma­te grounds for the pro­ces­sing which over­ri­de the inte­rests, rights and free­doms of the data sub­ject, or for the estab­lish­ment, exer­cise or defence of legal claims.

If the Car­te­sy GmbH pro­ces­ses per­so­nal data for direct mar­ke­ting pur­po­ses, the data sub­ject shall have the right to object at any time to pro­ces­sing of per­so­nal data con­cer­ning him or her for such mar­ke­ting. This appli­es to pro­fil­ing to the ext­ent that it is rela­ted to such direct mar­ke­ting. If the data sub­ject objects to the Feicht­ner Maschi­nen­bau to the pro­ces­sing for direct mar­ke­ting pur­po­ses, the Feicht­ner Maschi­nen­bau will no lon­ger pro­cess the per­so­nal data for the­se purposes.

In addi­ti­on, the data sub­ject has the right, on grounds rela­ting to his or her par­ti­cu­lar situa­ti­on, to object to pro­ces­sing of per­so­nal data con­cer­ning him or her by the Car­te­sy GmbH for sci­en­ti­fic or his­to­ri­cal rese­arch pur­po­ses, or for sta­tis­ti­cal pur­po­ses pur­su­ant to Artic­le 89(1) of the GDPR, unless the pro­ces­sing is neces­sa­ry for the per­for­mance of a task car­ri­ed out for reasons of public interest.

In order to exer­cise the right to object, the data sub­ject may cont­act any employee of the Car­te­sy GmbH. In addi­ti­on, the data sub­ject is free in the con­text of the use of infor­ma­ti­on socie­ty ser­vices, and not­wi­th­stan­ding Direc­ti­ve 2002/58/EC, to use his or her right to object by auto­ma­ted means using tech­ni­cal specifications.

8.8 Auto­ma­ted indi­vi­du­al decis­i­on-making, inclu­ding profiling

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor not to be sub­ject to a decis­i­on based sole­ly on auto­ma­ted pro­ces­sing, inclu­ding pro­fil­ing, which pro­du­ces legal effects con­cer­ning him or her, or simi­lar­ly signi­fi­cant­ly affects him or her, as long as the decis­i­on (1) is not is neces­sa­ry for ente­ring into, or the per­for­mance of, a con­tract bet­ween the data sub­ject and a data con­trol­ler, or (2) is not aut­ho­ri­sed by Uni­on or Mem­ber Sta­te law to which the con­trol­ler is sub­ject and which also lays down sui­ta­ble mea­su­res to safe­guard the data subject’s rights and free­doms and legi­ti­ma­te inte­rests, or (3) is not based on the data subject’s expli­cit consent.

If the decis­i­on (1) is neces­sa­ry for ente­ring into, or the per­for­mance of, a con­tract bet­ween the data sub­ject and a data con­trol­ler, or (2) it is based on the data subject’s expli­cit con­sent, the Feicht­ner Maschi­nen­bau shall imple­ment sui­ta­ble mea­su­res to safe­guard the data subject’s rights and free­doms and legi­ti­ma­te inte­rests, at least the right to obtain human inter­ven­ti­on on the part of the con­trol­ler, to express his or her point of view and con­test the decision.

If the data sub­ject wis­hes to exer­cise the rights con­cer­ning auto­ma­ted indi­vi­du­al decis­i­on-making, he or she may, at any time, cont­act any employee of the Car­te­sy GmbH.

8.9 Right to with­draw data pro­tec­tion consent

Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to with­draw his or her con­sent to pro­ces­sing of his or her per­so­nal data at any time. If the data sub­ject wis­hes to exer­cise the right to with­draw the con­sent, he or she may, at any time, cont­act any employee of the Car­te­sy GmbH.

9. Data pro­tec­tion for appli­ca­ti­ons and the appli­ca­ti­on procedure

The data con­trol­ler shall coll­ect and pro­cess the per­so­nal data of appli­cants for the pur­po­se of the pro­ces­sing of the appli­ca­ti­on pro­ce­du­re. The pro­ces­sing may also be car­ri­ed out elec­tro­ni­cal­ly. This is the case, in par­ti­cu­lar, if an appli­cant sub­mits cor­re­spon­ding appli­ca­ti­on docu­ments by e‑mail or by means of a web form on the web­site to the con­trol­ler. If the data con­trol­ler con­cludes an employ­ment con­tract with an appli­cant, the sub­mit­ted data will be stored for the pur­po­se of pro­ces­sing the employ­ment rela­ti­onship in com­pli­ance with legal requi­re­ments. If no employ­ment con­tract is con­cluded with the appli­cant by the con­trol­ler, the appli­ca­ti­on docu­ments shall be auto­ma­ti­cal­ly era­sed two months after noti­fi­ca­ti­on of the refu­sal decis­i­on, pro­vi­ded that no other legi­ti­ma­te inte­rests of the con­trol­ler are oppo­sed to the era­su­re. Other legi­ti­ma­te inte­rest in this rela­ti­on is, e.g. a bur­den of pro­of in a pro­ce­du­re under the Gene­ral Equal Tre­at­ment Act (AGG).

10 Data pro­tec­tion: Tracking-Tools

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Facebook

On this web­site, the con­trol­ler has inte­gra­ted com­pon­ents of the enter­pri­se Face­book. Face­book is a social net­work. A social net­work is a place for social mee­tings on the Inter­net, an online com­mu­ni­ty, which usual­ly allows users to com­mu­ni­ca­te with each other and inter­act in a vir­tu­al space. A social net­work may ser­ve as a plat­form for the exch­an­ge of opi­ni­ons and expe­ri­en­ces, or enable the Inter­net com­mu­ni­ty to pro­vi­de per­so­nal or busi­ness-rela­ted infor­ma­ti­on. Face­book allows social net­work users to include the crea­ti­on of pri­va­te pro­files, upload pho­tos, and net­work through fri­end requests.

The ope­ra­ting com­pa­ny of Face­book is Face­book, Inc., 1 Hacker Way, Men­lo Park, CA 94025, United Sta­tes. If a per­son lives out­side of the United Sta­tes or Cana­da, the con­trol­ler is the Face­book Ire­land Ltd., 4 Grand Canal Squa­re, Grand Canal Har­bour, Dub­lin 2, Ireland.

With each call-up to one of the indi­vi­du­al pages of this Inter­net web­site, which is ope­ra­ted by the con­trol­ler and into which a Face­book com­po­nent (Face­book plug-ins) was inte­gra­ted, the web brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject is auto­ma­ti­cal­ly prompt­ed to down­load dis­play of the cor­re­spon­ding Face­book com­po­nent from Face­book through the Face­book com­po­nent. An over­view of all the Face­book Plug-ins may be acces­sed under https://developers.facebook.com/docs/plugins/. During the cour­se of this tech­ni­cal pro­ce­du­re, Face­book is made awa­re of what spe­ci­fic sub-site of our web­site was visi­ted by the data subjec.

If the data sub­ject is log­ged in at the same time on Face­book, Face­book detects with every call-up to our web­site by the data subject—and for the enti­re dura­ti­on of their stay on our Inter­net site—which spe­ci­fic sub-site of our Inter­net page was visi­ted by the data sub­ject. This infor­ma­ti­on is coll­ec­ted through the Face­book com­po­nent and asso­cia­ted with the respec­ti­ve Face­book account of the data sub­ject. If the data sub­ject clicks on one of the Face­book but­tons inte­gra­ted into our web­site, e.g. the “Like” but­ton, or if the data sub­ject sub­mits a com­ment, then Face­book matches this infor­ma­ti­on with the per­so­nal Face­book user account of the data sub­ject and stores the per­so­nal data.

Face­book always recei­ves, through the Face­book com­po­nent, infor­ma­ti­on about a visit to our web­site by the data sub­ject, when­ever the data sub­ject is log­ged in at the same time on Face­book during the time of the call-up to our web­site. This occurs regard­less of whe­ther the data sub­ject clicks on the Face­book com­po­nent or not. If such a trans­mis­si­on of infor­ma­ti­on to Face­book is not desi­ra­ble for the data sub­ject, then he or she may pre­vent this by log­ging off from their Face­book account befo­re a call-up to our web­site is made.

The data pro­tec­tion gui­de­line published by Face­book, which is available at https://facebook.com/about/privacy/, pro­vi­des infor­ma­ti­on about the coll­ec­tion, pro­ces­sing and use of per­so­nal data by Face­book. In addi­ti­on, it is explai­ned the­re what set­ting opti­ons Face­book offers to pro­tect the pri­va­cy of the data sub­ject. In addi­ti­on, dif­fe­rent con­fi­gu­ra­ti­on opti­ons are made available to allow the eli­mi­na­ti­on of data trans­mis­si­on to Face­book, for exam­p­le, the Face­book blo­cker of the pro­vi­der Web­graph, which can be obtai­ned at http://webgraph.com/resources/facebookblocker/. The­se appli­ca­ti­ons may be used by the data sub­ject to eli­mi­na­te a data trans­mis­si­on to Facebook.

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Goog­le AdSense

On this web­site, the con­trol­ler has inte­gra­ted Goog­le AdSen­se. Goog­le AdSen­se is an online ser­vice which allows the pla­ce­ment of adver­ti­sing on third-par­ty sites. Goog­le AdSen­se is based on an algo­rithm that sel­ects adver­ti­se­ments dis­play­ed on third-par­ty sites to match with the con­tent of the respec­ti­ve third-par­ty site. Goog­le AdSen­se allows an inte­rest-based tar­ge­ting of the Inter­net user, which is imple­men­ted by means of gene­ra­ting indi­vi­du­al user profiles.

The ope­ra­ting com­pa­ny of Google’s AdSen­se com­po­nent is Alpha­bet Inc., 1600 Amphi­theat­re Pkwy, Moun­tain View, CA 94043–1351, United States.

The pur­po­se of Google’s AdSen­se com­po­nent is the inte­gra­ti­on of adver­ti­se­ments on our web­site. Goog­le AdSen­se places a coo­kie on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject. The defi­ni­ti­on of coo­kies is explai­ned abo­ve. With the set­ting of the coo­kie, Alpha­bet Inc. is enab­led to ana­ly­ze the use of our web­site. With each call-up to one of the indi­vi­du­al pages of this Inter­net site, which is ope­ra­ted by the con­trol­ler and into which a Goog­le AdSen­se com­po­nent is inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject will auto­ma­ti­cal­ly sub­mit data through the Goog­le AdSen­se com­po­nent for the pur­po­se of online adver­ti­sing and the sett­le­ment of com­mis­si­ons to Alpha­bet Inc. During the cour­se of this tech­ni­cal pro­ce­du­re, the enter­pri­se Alpha­bet Inc. gains know­ledge of per­so­nal data, such as the IP address of the data sub­ject, which ser­ves Alpha­bet Inc., inter alia, to under­stand the ori­gin of visi­tors and clicks and sub­se­quent­ly crea­te com­mis­si­on settlements.

The data sub­ject may, as sta­ted abo­ve, pre­vent the set­ting of coo­kies through our web­site at any time by means of a cor­re­spon­ding adjus­t­ment of the web brow­ser used and thus per­ma­nent­ly deny the set­ting of coo­kies. Such an adjus­t­ment to the Inter­net brow­ser used would also pre­vent Alpha­bet Inc. from set­ting a coo­kie on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject. Addi­tio­nal­ly, coo­kies alre­a­dy in use by Alpha­bet Inc. may be dele­ted at any time via a web brow­ser or other soft­ware programs.

Fur­ther­mo­re, Goog­le AdSen­se also uses so-cal­led track­ing pixels. A track­ing pixel is a minia­tu­re gra­phic that is embedded in web pages to enable a log file recor­ding and a log file ana­ly­sis through which a sta­tis­ti­cal ana­ly­sis may be per­for­med. Based on the embedded track­ing pixels, Alpha­bet Inc. is able to deter­mi­ne if and when a web­site was ope­ned by a data sub­ject, and which links were cli­cked on by the data sub­ject. Track­ing pixels ser­ve, inter alia, to ana­ly­ze the flow of visi­tors on a website.

Through Goog­le AdSen­se, per­so­nal data and information—which also includes the IP address, and is neces­sa­ry for the coll­ec­tion and accoun­ting of the dis­play­ed advertisements—is trans­mit­ted to Alpha­bet Inc. in the United Sta­tes of Ame­ri­ca. The­se per­so­nal data will be stored and pro­ces­sed in the United Sta­tes of Ame­ri­ca. The Alpha­bet Inc. may dis­c­lo­se the coll­ec­ted per­so­nal data through this tech­ni­cal pro­ce­du­re to third parties.

Goog­le AdSen­se is fur­ther explai­ned under the fol­lo­wing link https://www.google.com/intl/en/adsense/start/

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Goog­le Ana­ly­tics (with anony­mi­ze function)

On this web­site, the con­trol­ler has inte­gra­ted the com­po­nent of Goog­le Ana­ly­tics (with the anony­mi­zer func­tion). Goog­le Ana­ly­tics is a web ana­ly­tics ser­vice. Web ana­ly­tics is the coll­ec­tion, gathe­ring, and ana­ly­sis of data about the beha­vi­or of visi­tors to web­sites. A web ana­ly­sis ser­vice coll­ects, inter alia, data about the web­site from which a per­son has come (the so-cal­led refer­rer), which sub-pages were visi­ted, or how often and for what dura­ti­on a sub-page was view­ed. Web ana­ly­tics are main­ly used for the opti­miza­ti­on of a web­site and in order to car­ry out a cost-bene­fit ana­ly­sis of Inter­net advertising.

The ope­ra­tor of the Goog­le Ana­ly­tics com­po­nent is Goog­le Inc., 1600 Amphi­theat­re Pkwy, Moun­tain View, CA 94043–1351, United States.

For the web ana­ly­tics through Goog­le Ana­ly­tics the con­trol­ler uses the appli­ca­ti­on “_gat. _anonymizeIp”. By means of this appli­ca­ti­on the IP address of the Inter­net con­nec­tion of the data sub­ject is abrid­ged by Goog­le and anony­mi­sed when acces­sing our web­sites from a Mem­ber Sta­te of the Euro­pean Uni­on or ano­ther Con­trac­ting Sta­te to the Agree­ment on the Euro­pean Eco­no­mic Area.

The pur­po­se of the Goog­le Ana­ly­tics com­po­nent is to ana­ly­ze the traf­fic on our web­site. Goog­le uses the coll­ec­ted data and infor­ma­ti­on, inter alia, to eva­lua­te the use of our web­site and to pro­vi­de online reports, which show the acti­vi­ties on our web­sites, and to pro­vi­de other ser­vices con­cer­ning the use of our Inter­net site for us.

Goog­le Ana­ly­tics places a coo­kie on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject. The defi­ni­ti­on of coo­kies is explai­ned abo­ve. With the set­ting of the coo­kie, Goog­le is enab­led to ana­ly­ze the use of our web­site. With each call-up to one of the indi­vi­du­al pages of this Inter­net site, which is ope­ra­ted by the con­trol­ler and into which a Goog­le Ana­ly­tics com­po­nent was inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject will auto­ma­ti­cal­ly sub­mit data through the Goog­le Ana­ly­tics com­po­nent for the pur­po­se of online adver­ti­sing and the sett­le­ment of com­mis­si­ons to Goog­le. During the cour­se of this tech­ni­cal pro­ce­du­re, the enter­pri­se Goog­le gains know­ledge of per­so­nal infor­ma­ti­on, such as the IP address of the data sub­ject, which ser­ves Goog­le, inter alia, to under­stand the ori­gin of visi­tors and clicks, and sub­se­quent­ly crea­te com­mis­si­on settlements.

The coo­kie is used to store per­so­nal infor­ma­ti­on, such as the access time, the loca­ti­on from which the access was made, and the fre­quen­cy of visits of our web­site by the data sub­ject. With each visit to our Inter­net site, such per­so­nal data, inclu­ding the IP address of the Inter­net access used by the data sub­ject, will be trans­mit­ted to Goog­le in the United Sta­tes of Ame­ri­ca. The­se per­so­nal data are stored by Goog­le in the United Sta­tes of Ame­ri­ca. Goog­le may pass the­se per­so­nal data coll­ec­ted through the tech­ni­cal pro­ce­du­re to third parties.

The data sub­ject may, as sta­ted abo­ve, pre­vent the set­ting of coo­kies through our web­site at any time by means of a cor­re­spon­ding adjus­t­ment of the web brow­ser used and thus per­ma­nent­ly deny the set­ting of coo­kies. Such an adjus­t­ment to the Inter­net brow­ser used would also pre­vent Goog­le Ana­ly­tics from set­ting a coo­kie on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject. In addi­ti­on, coo­kies alre­a­dy in use by Goog­le Ana­ly­tics may be dele­ted at any time via a web brow­ser or other soft­ware programs.

In addi­ti­on, the data sub­ject has the pos­si­bi­li­ty of objec­ting to a coll­ec­tion of data that are gene­ra­ted by Goog­le Ana­ly­tics, which is rela­ted to the use of this web­site, as well as the pro­ces­sing of this data by Goog­le and the chan­ce to pre­clude any such. For this pur­po­se, the data sub­ject must down­load a brow­ser add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This brow­ser add-on tells Goog­le Ana­ly­tics through a Java­Script, that any data and infor­ma­ti­on about the visits of Inter­net pages may not be trans­mit­ted to Goog­le Ana­ly­tics. The instal­la­ti­on of the brow­ser add-ons is con­side­red an objec­tion by Goog­le. If the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject is later dele­ted, for­mat­ted, or new­ly instal­led, then the data sub­ject must reinstall the brow­ser add-ons to disable Goog­le Ana­ly­tics. If the brow­ser add-on was unin­stal­led by the data sub­ject or any other per­son who is attri­bu­ta­ble to their sphe­re of com­pe­tence, or is dis­ab­led, it is pos­si­ble to exe­cu­te the reinstal­la­ti­on or reac­ti­va­ti­on of the brow­ser add-ons.

Fur­ther infor­ma­ti­on and the appli­ca­ble data pro­tec­tion pro­vi­si­ons of Goog­le may be retrie­ved under https://www.google.com/intl/en/policies/privacy/ and under http://www.google.com/analytics/terms/us.html. Goog­le Ana­ly­tics is fur­ther explai­ned under the fol­lo­wing Link https://www.google.com/analytics/.

You can pre­vent the recor­ding by Goog­le Ana­ly­tics by cli­cking on the fol­lo­wing link. An opt-out-code is set, pre­ven­ting future recor­ding of your data when visi­ting this website.

​Disable Goog­le Analytics

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Goog­le Remarketing

On this web­site, the con­trol­ler has inte­gra­ted Goog­le Remar­ke­ting ser­vices. Goog­le Remar­ke­ting is a fea­ture of Goog­le AdWords, which allows an enter­pri­se to dis­play adver­ti­sing to Inter­net users who have pre­vious­ly resi­ded on the enterprise’s Inter­net site. The inte­gra­ti­on of Goog­le Remar­ke­ting the­r­e­fo­re allows an enter­pri­se to crea­te user-based adver­ti­sing and thus shows rele­vant adver­ti­se­ments to inte­res­ted Inter­net users.

The ope­ra­ting com­pa­ny of the Goog­le Remar­ke­ting ser­vices is the Goog­le Inc., 1600 Amphi­theat­re Pkwy, Moun­tain View, CA 94043–1351, United States.

The pur­po­se of Goog­le Remar­ke­ting is the inser­ti­on of inte­rest-rele­vant adver­ti­sing. Goog­le Remar­ke­ting allows us to dis­play ads on the Goog­le net­work or on other web­sites, which are based on indi­vi­du­al needs and matched to the inte­rests of Inter­net users.

Goog­le Remar­ke­ting sets a coo­kie on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject. The defi­ni­ti­on of coo­kies is explai­ned abo­ve. With the set­ting of the coo­kie, Goog­le enables a reco­gni­ti­on of the visi­tor of our web­site if he calls up con­se­cu­ti­ve web pages, which are also a mem­ber of the Goog­le adver­ti­sing net­work. With each call-up to an Inter­net site on which the ser­vice has been inte­gra­ted by Goog­le Remar­ke­ting, the web brow­ser of the data sub­ject iden­ti­fies auto­ma­ti­cal­ly with Goog­le. During the cour­se of this tech­ni­cal pro­ce­du­re, Goog­le recei­ves per­so­nal infor­ma­ti­on, such as the IP address or the sur­fing beha­viour of the user, which Goog­le uses, inter alia, for the inser­ti­on of inte­rest rele­vant advertising.

The coo­kie is used to store per­so­nal infor­ma­ti­on, e.g. the Inter­net pages visi­ted by the data sub­ject. Each time we visit our Inter­net pages, per­so­nal data, inclu­ding the IP address of the Inter­net access used by the data sub­ject, is trans­mit­ted to Goog­le in the United Sta­tes of Ame­ri­ca. The­se per­so­nal data are stored by Goog­le in the United Sta­tes of Ame­ri­ca. Goog­le may pass the­se per­so­nal data coll­ec­ted through the tech­ni­cal pro­ce­du­re to third parties.

The data sub­ject may, as sta­ted abo­ve, pre­vent the set­ting of coo­kies through our web­site at any time by means of a cor­re­spon­ding adjus­t­ment of the web brow­ser used and thus per­ma­nent­ly deny the set­ting of coo­kies. Such an adjus­t­ment to the Inter­net brow­ser used would also pre­vent Goog­le from set­ting a coo­kie on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject. In addi­ti­on, coo­kies alre­a­dy in use by Goog­le may be dele­ted at any time via a web brow­ser or other soft­ware programs.

In addi­ti­on, the data sub­ject has the pos­si­bi­li­ty of objec­ting to the inte­rest-based adver­ti­sing by Goog­le. For this pur­po­se, the data sub­ject must call up the link to www.google.de/settings/ads and make the desi­red set­tings on each Inter­net brow­ser used by the data subject.

Fur­ther infor­ma­ti­on and the actu­al data pro­tec­tion pro­vi­si­ons of Goog­le may be retrie­ved under https://www.google.com/intl/en/policies/privacy/..

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Google+

On this web­site, the con­trol­ler has inte­gra­ted the Goog­le+ but­ton as a com­po­nent. Goog­le+ is a so-cal­led social net­work. A social net­work is a social mee­ting place on the Inter­net, an online com­mu­ni­ty, which usual­ly allows users to com­mu­ni­ca­te with each other and inter­act in a vir­tu­al space. A social net­work may ser­ve as a plat­form for the exch­an­ge of opi­ni­ons and expe­ri­en­ces, or enable the Inter­net com­mu­ni­ty to pro­vi­de per­so­nal or busi­ness-rela­ted infor­ma­ti­on. Goog­le+ allows users of the social net­work to include the crea­ti­on of pri­va­te pro­files, upload pho­tos and net­work through fri­end requests.

The ope­ra­ting com­pa­ny of Goog­le+ is Goog­le Inc., 1600 Amphi­theat­re Pkwy, Moun­tain View, CA 94043–1351, UNITED STATES.

With each call-up to one of the indi­vi­du­al pages of this web­site, which is ope­ra­ted by the con­trol­ler and on which a Goog­le+ but­ton has been inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject auto­ma­ti­cal­ly down­loads a dis­play of the cor­re­spon­ding Goog­le+ but­ton of Goog­le through the respec­ti­ve Goog­le+ but­ton com­po­nent. During the cour­se of this tech­ni­cal pro­ce­du­re, Goog­le is made awa­re of what spe­ci­fic sub-page of our web­site was visi­ted by the data sub­ject. More detail­ed infor­ma­ti­on about Goog­le+ is available under https://developers.google.com/+/.

If the data sub­ject is log­ged in at the same time to Goog­le+, Goog­le reco­gni­zes with each call-up to our web­site by the data sub­ject and for the enti­re dura­ti­on of his or her stay on our Inter­net site, which spe­ci­fic sub-pages of our Inter­net page were visi­ted by the data sub­ject. This infor­ma­ti­on is coll­ec­ted through the Goog­le+ but­ton and Goog­le matches this with the respec­ti­ve Goog­le+ account asso­cia­ted with the data subject..

If the data sub­ject clicks on the Goog­le+ but­ton inte­gra­ted on our web­site and thus gives a Goog­le+ 1 recom­men­da­ti­on, then Goog­le assigns this infor­ma­ti­on to the per­so­nal Goog­le+ user account of the data sub­ject and stores the per­so­nal data. Goog­le stores the Goog­le+ 1 recom­men­da­ti­on of the data sub­ject, making it publicly available in accordance with the terms and con­di­ti­ons accept­ed by the data sub­ject in this regard. Sub­se­quent­ly, a Goog­le+ 1 recom­men­da­ti­on given by the data sub­ject on this web­site tog­e­ther with other per­so­nal data, such as the Goog­le+ account name used by the data sub­ject and the stored pho­to, is stored and pro­ces­sed on other Goog­le ser­vices, such as search-engi­ne results of the Goog­le search engi­ne, the Goog­le account of the data sub­ject or in other places, e.g. on Inter­net pages, or in rela­ti­on to adver­ti­se­ments. Goog­le is also able to link the visit to this web­site with other per­so­nal data stored on Goog­le. Goog­le fur­ther records this per­so­nal infor­ma­ti­on with the pur­po­se of impro­ving or opti­mi­zing the various Goog­le services.

Through the Goog­le+ but­ton, Goog­le recei­ves infor­ma­ti­on that the data sub­ject visi­ted our web­site, if the data sub­ject at the time of the call-up to our web­site is log­ged in to Goog­le+. This occurs regard­less of whe­ther the data sub­ject clicks or doesn’t click on the Goog­le+ button.

If the data sub­ject does not wish to trans­mit per­so­nal data to Goog­le, he or she may pre­vent such trans­mis­si­on by log­ging out of his Goog­le+ account befo­re cal­ling up our website.

Fur­ther infor­ma­ti­on and the data pro­tec­tion pro­vi­si­ons of Goog­le may be retrie­ved under https://www.google.com/intl/en/policies/privacy/. More refe­ren­ces from Goog­le about the Goog­le+ 1 but­ton may be obtai­ned under https://developers.google.com/+/web/buttons-policy.

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Google-AdWords

On this web­site, the con­trol­ler has inte­gra­ted Goog­le AdWords. Goog­le AdWords is a ser­vice for Inter­net adver­ti­sing that allows the adver­ti­ser to place ads in Goog­le search engi­ne results and the Goog­le adver­ti­sing net­work. Goog­le AdWords allows an adver­ti­ser to pre-defi­ne spe­ci­fic key­words with the help of which an ad on Google’s search results only then dis­play­ed, when the user uti­li­zes the search engi­ne to retrie­ve a key­word-rele­vant search result. In the Goog­le Adver­ti­sing Net­work, the ads are dis­tri­bu­ted on rele­vant web pages using an auto­ma­tic algo­rithm, taking into account the pre­vious­ly defi­ned keywords.

The ope­ra­ting com­pa­ny of Goog­le AdWords is Goog­le Inc., 1600 Amphi­theat­re Pkwy, Moun­tain View, CA 94043–1351, UNITED STATES.

The pur­po­se of Goog­le AdWords is the pro­mo­ti­on of our web­site by the inclu­si­on of rele­vant adver­ti­sing on the web­sites of third par­ties and in the search engi­ne results of the search engi­ne Goog­le and an inser­ti­on of third-par­ty adver­ti­sing on our website.

If a data sub­ject rea­ches our web­site via a Goog­le ad, a con­ver­si­on coo­kie is filed on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject through Goog­le. The defi­ni­ti­on of coo­kies is explai­ned abo­ve. A con­ver­si­on coo­kie loses its vali­di­ty after 30 days and is not used to iden­ti­fy the data sub­ject. If the coo­kie has not expi­red, the con­ver­si­on coo­kie is used to check whe­ther cer­tain sub-pages, e.g, the shop­ping cart from an online shop sys­tem, were cal­led up on our web­site. Through the con­ver­si­on coo­kie, both Goog­le and the con­trol­ler can under­stand whe­ther a per­son who rea­ched an AdWords ad on our web­site gene­ra­ted sales, that is, exe­cu­ted or can­ce­led a sale of goods.

The data and infor­ma­ti­on coll­ec­ted through the use of the con­ver­si­on coo­kie is used by Goog­le to crea­te visit sta­tis­tics for our web­site. The­se visit sta­tis­tics are used in order to deter­mi­ne the total num­ber of users who have been ser­ved through AdWords ads to ascer­tain the suc­cess or fail­ure of each AdWords ad and to opti­mi­ze our AdWords ads in the future. Neither our com­pa­ny nor other Goog­le AdWords adver­ti­sers recei­ve infor­ma­ti­on from Goog­le that could iden­ti­fy the data subject.

The con­ver­si­on coo­kie stores per­so­nal infor­ma­ti­on, e.g. the Inter­net pages visi­ted by the data sub­ject. Each time we visit our Inter­net pages, per­so­nal data, inclu­ding the IP address of the Inter­net access used by the data sub­ject, is trans­mit­ted to Goog­le in the United Sta­tes of Ame­ri­ca. The­se per­so­nal data are stored by Goog­le in the United Sta­tes of Ame­ri­ca. Goog­le may pass the­se per­so­nal data coll­ec­ted through the tech­ni­cal pro­ce­du­re to third parties.

The data sub­ject may, at any time, pre­vent the set­ting of coo­kies by our web­site, as sta­ted abo­ve, by means of a cor­re­spon­ding set­ting of the Inter­net brow­ser used and thus per­ma­nent­ly deny the set­ting of coo­kies. Such a set­ting of the Inter­net brow­ser used would also pre­vent Goog­le from pla­cing a con­ver­si­on coo­kie on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject. In addi­ti­on, a coo­kie set by Goog­le AdWords may be dele­ted at any time via the Inter­net brow­ser or other soft­ware programs.

The data sub­ject has a pos­si­bi­li­ty of objec­ting to the inte­rest based adver­ti­se­ment of Goog­le. The­r­e­fo­re, the data sub­ject must access from each of the brow­sers in use the link www.google.de/settings/ads and set the desi­red settings.

Fur­ther infor­ma­ti­on and the appli­ca­ble data pro­tec­tion pro­vi­si­ons of Goog­le may be retrie­ved under https://www.google.com/intl/en/policies/privacy/.

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of LinkedIn

The con­trol­ler has inte­gra­ted com­pon­ents of the Lin­ke­dIn Cor­po­ra­ti­on on this web­site. Lin­ke­dIn is a web-based social net­work that enables users with exis­ting busi­ness cont­acts to con­nect and to make new busi­ness cont­acts. Over 400 mil­li­on regis­tered peo­p­le in more than 200 count­ries use Lin­ke­dIn. Thus, Lin­ke­dIn is curr­ent­ly the lar­gest plat­form for busi­ness cont­acts and one of the most visi­ted web­sites in the world.

The ope­ra­ting com­pa­ny of Lin­ke­dIn is Lin­ke­dIn Cor­po­ra­ti­on, 2029 Stier­lin Court Moun­tain View, CA 94043, UNITED STATES. For pri­va­cy mat­ters out­side of the UNITED STATES Lin­ke­dIn Ire­land, Pri­va­cy Poli­cy Issues, Wil­ton Pla­za, Wil­ton Place, Dub­lin 2, Ire­land, is responsible.

With each call-up to one of the indi­vi­du­al pages of this Inter­net site, which is ope­ra­ted by the con­trol­ler and on which a Lin­ke­dIn com­po­nent (Lin­ke­dIn plug-in) was inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject is auto­ma­ti­cal­ly prompt­ed to the down­load of a dis­play of the cor­re­spon­ding Lin­ke­dIn com­po­nent of Lin­ke­dIn. Fur­ther infor­ma­ti­on about the Lin­ke­dIn plug-in may be acces­sed under https://developer.linkedin.com/plugins. During the cour­se of this tech­ni­cal pro­ce­du­re, Lin­ke­dIn gains know­ledge of what spe­ci­fic sub-page of our web­site was visi­ted by the data subject.

If the data sub­ject is log­ged in at the same time on Lin­ke­dIn, Lin­ke­dIn detects with every call-up to our web­site by the data subject—and for the enti­re dura­ti­on of their stay on our Inter­net site—which spe­ci­fic sub-page of our Inter­net page was visi­ted by the data sub­ject. This infor­ma­ti­on is coll­ec­ted through the Lin­ke­dIn com­po­nent and asso­cia­ted with the respec­ti­ve Lin­ke­dIn account of the data sub­ject. If the data sub­ject clicks on one of the Lin­ke­dIn but­tons inte­gra­ted on our web­site, then Lin­ke­dIn assigns this infor­ma­ti­on to the per­so­nal Lin­ke­dIn user account of the data sub­ject and stores the per­so­nal data.

Lin­ke­dIn recei­ves infor­ma­ti­on via the Lin­ke­dIn com­po­nent that the data sub­ject has visi­ted our web­site, pro­vi­ded that the data sub­ject is log­ged in at Lin­ke­dIn at the time of the call-up to our web­site. This occurs regard­less of whe­ther the per­son clicks on the Lin­ke­dIn but­ton or not. If such a trans­mis­si­on of infor­ma­ti­on to Lin­ke­dIn is not desi­ra­ble for the data sub­ject, then he or she may pre­vent this by log­ging off from their Lin­ke­dIn account befo­re a call-up to our web­site is made.

Lin­ke­dIn pro­vi­des under https://www.linkedin.com/psettings/guest-controls the pos­si­bi­li­ty to unsub­scri­be from e‑mail mes­sa­ges, SMS mes­sa­ges and tar­ge­ted ads, as well as the abili­ty to mana­ge ad set­tings. Lin­ke­dIn also uses affi­lia­tes such as Eire, Goog­le Ana­ly­tics, Blue­Kai, Dou­ble­Click, Niel­sen, Comscore, Elo­qua, and Lota­me. The set­ting of such coo­kies may be denied under https://www.linkedin.com/legal/cookie-policy. The appli­ca­ble pri­va­cy poli­cy for Lin­ke­dIn is available under https://www.linkedin.com/legal/privacy-policy. The Lin­ke­dIn Coo­kie Poli­cy is available under https://www.linkedin.com/legal/cookie-policy.

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Twitter

On this web­site, the con­trol­ler has inte­gra­ted com­pon­ents of Twit­ter. Twit­ter is a mul­ti­l­in­gu­al, publicly-acces­si­ble micro­blog­ging ser­vice on which users may publish and spread so-cal­led ‘tweets,’ e.g. short mes­sa­ges, which are limi­t­ed to 280 cha­rac­ters. The­se short mes­sa­ges are available for ever­yo­ne, inclu­ding tho­se who are not log­ged on to Twit­ter. The tweets are also dis­play­ed to so-cal­led fol­lo­wers of the respec­ti­ve user. Fol­lo­wers are other Twit­ter users who fol­low a user’s tweets. Fur­ther­mo­re, Twit­ter allows you to address a wide audi­ence via hash­tags, links or retweets.

The ope­ra­ting com­pa­ny of Twit­ter is Twit­ter, Inc., 1355 Mar­ket Street, Suite 900, San Fran­cis­co, CA 94103, UNITED STATES.

With each call-up to one of the indi­vi­du­al pages of this Inter­net site, which is ope­ra­ted by the con­trol­ler and on which a Twit­ter com­po­nent (Twit­ter but­ton) was inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject is auto­ma­ti­cal­ly prompt­ed to down­load a dis­play of the cor­re­spon­ding Twit­ter com­po­nent of Twit­ter. Fur­ther infor­ma­ti­on about the Twit­ter but­tons is available under https://about.twitter.com/de/resources/buttons. During the cour­se of this tech­ni­cal pro­ce­du­re, Twit­ter gains know­ledge of what spe­ci­fic sub-page of our web­site was visi­ted by the data sub­ject. The pur­po­se of the inte­gra­ti­on of the Twit­ter com­po­nent is a retrans­mis­si­on of the con­tents of this web­site to allow our users to intro­du­ce this web page to the digi­tal world and increase our visi­tor numbers.

If the data sub­ject is log­ged in at the same time on Twit­ter, Twit­ter detects with every call-up to our web­site by the data sub­ject and for the enti­re dura­ti­on of their stay on our Inter­net site which spe­ci­fic sub-page of our Inter­net page was visi­ted by the data sub­ject. This infor­ma­ti­on is coll­ec­ted through the Twit­ter com­po­nent and asso­cia­ted with the respec­ti­ve Twit­ter account of the data sub­ject. If the data sub­ject clicks on one of the Twit­ter but­tons inte­gra­ted on our web­site, then Twit­ter assigns this infor­ma­ti­on to the per­so­nal Twit­ter user account of the data sub­ject and stores the per­so­nal data.

Twit­ter recei­ves infor­ma­ti­on via the Twit­ter com­po­nent that the data sub­ject has visi­ted our web­site, pro­vi­ded that the data sub­ject is log­ged in on Twit­ter at the time of the call-up to our web­site. This occurs regard­less of whe­ther the per­son clicks on the Twit­ter com­po­nent or not. If such a trans­mis­si­on of infor­ma­ti­on to Twit­ter is not desi­ra­ble for the data sub­ject, then he or she may pre­vent this by log­ging off from their Twit­ter account befo­re a call-up to our web­site is made.

The appli­ca­ble data pro­tec­tion pro­vi­si­ons of Twit­ter may be acces­sed under https://twitter.com/privacy?lang=en.

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of Xing

On this web­site, the con­trol­ler has inte­gra­ted com­pon­ents of XING. XING is an Inter­net-based social net­work that enables users to con­nect with exis­ting busi­ness cont­acts and to crea­te new busi­ness cont­acts. The indi­vi­du­al users can crea­te a per­so­nal pro­fi­le of them­sel­ves at XING. Com­pa­nies may, e.g. crea­te com­pa­ny pro­files or publish jobs on XING

The ope­ra­ting com­pa­ny of XING is XING SE, Damm­tor­stra­ße 30, 20354 Ham­burg, Germany.

With each call-up to one of the indi­vi­du­al pages of this Inter­net site, which is ope­ra­ted by the con­trol­ler and on which a XING com­po­nent (XING plug-in) was inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject is auto­ma­ti­cal­ly prompt­ed to down­load a dis­play of the cor­re­spon­ding XING com­po­nent of XING. Fur­ther infor­ma­ti­on about the XING plug-in the may be acces­sed under https://dev.xing.com/plugins. During the cour­se of this tech­ni­cal pro­ce­du­re, XING gains know­ledge of what spe­ci­fic sub-page of our web­site was visi­ted by the data subject.

If the data sub­ject is log­ged in at the same time on XING, XING detects with every call-up to our web­site by the data subject—and for the enti­re dura­ti­on of their stay on our Inter­net site—which spe­ci­fic sub-page of our Inter­net page was visi­ted by the data sub­ject. This infor­ma­ti­on is coll­ec­ted through the XING com­po­nent and asso­cia­ted with the respec­ti­ve XING account of the data sub­ject. If the data sub­ject clicks on the XING but­ton inte­gra­ted on our Inter­net site, e.g. the “Share”-button, then XING assigns this infor­ma­ti­on to the per­so­nal XING user account of the data sub­ject and stores the per­so­nal data.

XING recei­ves infor­ma­ti­on via the XING com­po­nent that the data sub­ject has visi­ted our web­site, pro­vi­ded that the data sub­ject is log­ged in at XING at the time of the call to our web­site. This occurs regard­less of whe­ther the per­son clicks on the XING com­po­nent or not. If such a trans­mis­si­on of infor­ma­ti­on to XING is not desi­ra­ble for the data sub­ject, then he or she can pre­vent this by log­ging off from their XING account befo­re a call-up to our web­site is made.

The data pro­tec­tion pro­vi­si­ons published by XING, which is available under https://www.xing.com/privacy, pro­vi­de infor­ma­ti­on on the coll­ec­tion, pro­ces­sing and use of per­so­nal data by XING. In addi­ti­on, XING has published pri­va­cy noti­ces for the XING share but­ton under https://www.xing.com/app/share?op=data_protection.

Data pro­tec­tion pro­vi­si­ons about the appli­ca­ti­on and use of YouTube

On this web­site, the con­trol­ler has inte­gra­ted com­pon­ents of You­Tube. You­Tube is an Inter­net video por­tal that enables video publishers to set video clips and other users free of char­ge, which also pro­vi­des free vie­w­ing, review and com­men­ting on them. You­Tube allows you to publish all kinds of vide­os, so you can access both full movies and TV broad­casts, as well as music vide­os, trai­lers, and vide­os made by users via the Inter­net portal

The ope­ra­ting com­pa­ny of You­Tube is You­Tube, LLC, 901 Cher­ry Ave., San Bru­no, CA 94066, UNITED STATES. The You­Tube, LLC is a sub­si­dia­ry of Goog­le Inc., 1600 Amphi­theat­re Pkwy, Moun­tain View, CA 94043–1351, UNITED STATES.

With each call-up to one of the indi­vi­du­al pages of this Inter­net site, which is ope­ra­ted by the con­trol­ler and on which a You­Tube com­po­nent (You­Tube video) was inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject is auto­ma­ti­cal­ly prompt­ed to down­load a dis­play of the cor­re­spon­ding You­Tube com­po­nent. Fur­ther infor­ma­ti­on about You­Tube may be obtai­ned under https://www.youtube.com/yt/about/en/. During the cour­se of this tech­ni­cal pro­ce­du­re, You­Tube and Goog­le gain know­ledge of what spe­ci­fic sub-page of our web­site was visi­ted by the data subject.

If the data sub­ject is log­ged in on You­Tube, You­Tube reco­gni­zes with each call-up to a sub-page that con­ta­ins a You­Tube video, which spe­ci­fic sub-page of our Inter­net site was visi­ted by the data sub­ject. This infor­ma­ti­on is coll­ec­ted by You­Tube and Goog­le and assi­gned to the respec­ti­ve You­Tube account of the data subject.

You­Tube and Goog­le will recei­ve infor­ma­ti­on through the You­Tube com­po­nent that the data sub­ject has visi­ted our web­site, if the data sub­ject at the time of the call to our web­site is log­ged in on You­Tube; this occurs regard­less of whe­ther the per­son clicks on a You­Tube video or not. If such a trans­mis­si­on of this infor­ma­ti­on to You­Tube and Goog­le is not desi­ra­ble for the data sub­ject, the deli­very may be pre­ven­ted if the data sub­ject logs off from their own You­Tube account befo­re a call-up to our web­site is made.

YouTube’s data pro­tec­tion pro­vi­si­ons, available at https://www.google.com/intl/en/policies/privacy/, pro­vi­de infor­ma­ti­on about the coll­ec­tion, pro­ces­sing and use of per­so­nal data by You­Tube and Google.

11 Respon­si­ble Data Pro­tec­tion Authority

Lan­des­be­auf­trag­te für Daten­schutz und Informationsfreiheit

Nord­rhein-West­fa­len

Post­fach 20 04 44

40102 Düs­sel­dorf

Pho­ne: 0211/38424–0

Fax: 0211/38424–10

E‑Mail: poststelle@ldi.nrw.de

Home­page: https://www.ldi.nrw.de

12 Chan­ge to the Pri­va­cy Policy

We reser­ve the right to chan­ge our secu­ri­ty and pri­va­cy poli­cy as requi­red by tech­ni­cal deve­lo­p­ments. In the­se cases, we will also adjust our pri­va­cy poli­cy accor­din­gly. Plea­se note the cur­rent ver­si­on of our pri­va­cy policy..

(04/2018)

5. Spe­cial terms and conditions

Inso­far as spe­cial con­di­ti­ons for indi­vi­du­al uses of this web­site devia­te from the afo­re­men­tio­ned para­graphs, this shall be express­ly sta­ted at the appro­pria­te place. In this case, the spe­cial con­di­ti­ons of use app­ly in each indi­vi­du­al case.

Source: Imprint tem­p­la­te of JuraForum.de

6. Image Rights

The lis­ted image rights and copy­rights app­ly to the domains tds-rietberg.de and their subdomains.