Privacy Policy

We are very delight­ed that you have shown inter­est in our enter­prise. Data pro­tec­tion is of a par­tic­u­lar­ly high pri­or­i­ty for the man­age­ment of the Elcul­tra UG (haf­tungs­beschränkt). The use of the Inter­net pages of the Elcul­tra UG (haf­tungs­beschränkt) 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 enter­prise ser­vices via our web­site, pro­cess­ing of per­son­al data could become nec­es­sary. If the pro­cess­ing of per­son­al data is nec­es­sary and there is no statu­to­ry basis for such pro­cess­ing, we gen­er­al­ly obtain con­sent from the data subject.

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 (GDPR), and in accor­dance with the coun­try-spe­cif­ic data pro­tec­tion reg­u­la­tions applic­a­ble to the Elcul­tra UG (haf­tungs­beschränkt). By means of this data pro­tec­tion dec­la­ra­tion, our enter­prise would like to inform the gen­er­al pub­lic of the nature, scope, and pur­pose of the per­son­al data we col­lect, use and process. Fur­ther­more, data sub­jects are informed, by means of this data pro­tec­tion dec­la­ra­tion, of the rights to which they are entitled.

As the con­troller, the Elcul­tra UG (haf­tungs­beschränkt) has imple­ment­ed numer­ous tech­ni­cal and orga­ni­za­tion­al mea­sures to ensure the most com­plete pro­tec­tion of per­son­al data processed through this web­site. How­ev­er, Inter­net-based data trans­mis­sions may in prin­ci­ple have secu­ri­ty gaps, so absolute pro­tec­tion may not be guar­an­teed. For this rea­son, every data sub­ject is free to trans­fer per­son­al data to us via alter­na­tive means, e.g. by telephone.

1. Definitions

The data pro­tec­tion dec­la­ra­tion of the Elcul­tra UG (haf­tungs­beschränkt) is based on the terms used by the Euro­pean leg­is­la­tor for the adop­tion of the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR). Our data pro­tec­tion dec­la­ra­tion should be leg­i­ble and under­stand­able for the gen­er­al pub­lic, as well as our cus­tomers and busi­ness part­ners. To ensure this, we would like to first explain the ter­mi­nol­o­gy used.

In this data pro­tec­tion dec­la­ra­tion, we use, inter alia, the fol­low­ing terms:

• a)    Personal data

  Per­son­al data means any infor­ma­tion relat­ing to an iden­ti­fied or iden­ti­fi­able nat­ur­al per­son (“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 is any iden­ti­fied or iden­ti­fi­able nat­ur­al per­son, whose per­son­al data is processed by the con­troller respon­si­ble for the processing.

• c)    Processing

  Pro­cess­ing is any oper­a­tion or set of oper­a­tions which is per­formed on per­son­al data or on sets of per­son­al data, whether or not by auto­mat­ed means, such as col­lec­tion, record­ing, organ­i­sa­tion, struc­tur­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 pro­cess­ing in the future.

• e)    Profiling

  Pro­fil­ing means any form of auto­mat­ed pro­cess­ing of per­son­al data con­sist­ing of the use of 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 con­cern­ing 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 movements.

• f)     Pseudonymisation

  Pseu­do­nymi­sa­tion is the pro­cess­ing of per­son­al data in such a man­ner 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 to 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 controller responsible for the processing

  Con­troller or con­troller respon­si­ble for the 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 nom­i­na­tion may be pro­vid­ed for by Union or Mem­ber State law.

• h)    Processor

  Proces­sor is 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

  Recip­i­ent is a nat­ur­al or legal per­son, pub­lic author­i­ty, agency or anoth­er body, to which the per­son­al data are dis­closed, whether a third par­ty or not. How­ev­er, pub­lic author­i­ties which may receive per­son­al data in the frame­work of a par­tic­u­lar inquiry in accor­dance with Union or Mem­ber State law shall not be regard­ed as recip­i­ents; the pro­cess­ing of those data by those pub­lic author­i­ties shall be in com­pli­ance with the applic­a­ble data pro­tec­tion rules accord­ing to the pur­pos­es of the processing.

• j)      Third party

  Third par­ty is a nat­ur­al or legal per­son, pub­lic author­i­ty, agency or body oth­er than the data sub­ject, con­troller, proces­sor and per­sons who, under the direct author­i­ty of the con­troller or proces­sor, are autho­rised to process per­son­al data.

• k)    Consent

  Con­sent of the data sub­ject is any freely giv­en, spe­cif­ic, informed and unam­bigu­ous indi­ca­tion of the data sub­jec­t’s wish­es by which he or she, by a state­ment or by a clear affir­ma­tive action, sig­ni­fies agree­ment to the pro­cess­ing of per­son­al data relat­ing to him or her.

2. Name and Address of the controller

Con­troller for the pur­pos­es of the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR), oth­er data pro­tec­tion laws applic­a­ble in Mem­ber states of the Euro­pean Union and oth­er pro­vi­sions relat­ed to data pro­tec­tion is:

Elcul­tra UG (haf­tungs­beschränkt)

Char­lot­ten­str. 14

52070 Aachen

Ger­many

Phone: +49 241 916 072–0

Email: [email protected]

Web­site: www.elcultra.com

3. Name and Address of the Data Protection Officer

The Data Pro­tec­tion Offi­cer of the con­troller is:

Beate Chris­tiane Foer­ster M.Sc.

Elcul­tra UG (haf­tungs­beschränkt)

Char­lot­ten­str. 14

52070 Aachen

Ger­many

Phone: +49 241 916 072–0

Email: [email protected]

Web­site: www.elcultra.com

Any data sub­ject may, at any time, con­tact our Data Pro­tec­tion Offi­cer direct­ly with all ques­tions and sug­ges­tions con­cern­ing data protection.

4. Cookies

The Inter­net pages of the Elcul­tra UG (haf­tungs­beschränkt) use cook­ies. Cook­ies are text files that are stored in a com­put­er sys­tem via an Inter­net browser.

Many Inter­net 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 char­ac­ter string through 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 allows vis­it­ed Inter­net sites and servers to dif­fer­en­ti­ate the indi­vid­ual brows­er of the dats 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 rec­og­nized and iden­ti­fied using the unique cook­ie ID.

Through the use of cook­ies, the Elcul­tra UG (haf­tungs­beschränkt) 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 setting.

By means of a cook­ie, the infor­ma­tion and offers on our web­site can be opti­mized with the user in mind. Cook­ies allow us, as pre­vi­ous­ly men­tioned, to rec­og­nize our web­site users. The pur­pose of this recog­ni­tion is to make it eas­i­er for users to uti­lize our web­site. The web­site user that uses cook­ies, e.g. does not have to enter access data each time the web­site is accessed, because this is tak­en over by the web­site, and the cook­ie is thus stored on the user’s com­put­er sys­tem. Anoth­er exam­ple is the cook­ie of a shop­ping cart in an online shop. The online store remem­bers the arti­cles that a cus­tomer has placed 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 cook­ies through our web­site by means of a cor­re­spond­ing set­ting of the Inter­net brows­er used, and may thus per­ma­nent­ly deny the set­ting of cook­ies. Fur­ther­more, already set cook­ies may be delet­ed at any time via an Inter­net brows­er or oth­er soft­ware pro­grams. This is pos­si­ble in all pop­u­lar 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 entire­ly usable.

5. Collection of general data and information

The web­site of the Elcul­tra UG (haf­tungs­beschränkt) col­lects a series of gen­er­al data and infor­ma­tion when a data sub­ject or auto­mat­ed sys­tem calls up the web­site. This gen­er­al data and infor­ma­tion are stored in the serv­er log files. Col­lect­ed may be (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 reach­es our web­site (so-called 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 provider of the access­ing sys­tem, and (8) any oth­er sim­i­lar data and infor­ma­tion that may be used in the event of attacks on our infor­ma­tion tech­nol­o­gy systems.

When using these gen­er­al data and infor­ma­tion, the Elcul­tra UG (haf­tungs­beschränkt) does not draw any con­clu­sions about the data sub­ject. Rather, this infor­ma­tion is need­ed to (1) deliv­er the con­tent of our web­site cor­rect­ly, (2) opti­mize the con­tent of our web­site as well as its adver­tise­ment, (3) ensure the long-term via­bil­i­ty of our infor­ma­tion tech­nol­o­gy sys­tems and web­site tech­nol­o­gy, and (4) pro­vide law enforce­ment author­i­ties with the infor­ma­tion nec­es­sary for crim­i­nal pros­e­cu­tion in case of a cyber-attack. There­fore, the Elcul­tra UG (haf­tungs­beschränkt) ana­lyzes anony­mous­ly col­lect­ed data and infor­ma­tion sta­tis­ti­cal­ly, with the aim of increas­ing the data pro­tec­tion and data secu­ri­ty of our enter­prise, and to ensure 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 all per­son­al data pro­vid­ed by a data subject.

6. Registration on our website

The data sub­ject has the pos­si­bil­i­ty to reg­is­ter on the web­site of the con­troller with the indi­ca­tion of per­son­al data. Which per­son­al data are trans­mit­ted to the con­troller is deter­mined by the respec­tive input mask used for the reg­is­tra­tion. The per­son­al data entered by the data sub­ject are col­lect­ed and stored exclu­sive­ly for inter­nal use by the con­troller, and for his own pur­pos­es. The con­troller may request trans­fer to one or more proces­sors (e.g. a par­cel ser­vice) that also uses per­son­al data for an inter­nal pur­pose which is attrib­ut­able to the controller.

By reg­is­ter­ing on the web­site of the con­troller, the IP address—assigned by the Inter­net ser­vice provider (ISP) and used by the data subject—date, and time of the reg­is­tra­tion are also stored. The stor­age of this data takes place against the back­ground that this is the only way to pre­vent the mis­use of our ser­vices, and, if nec­es­sary, to make it pos­si­ble to inves­ti­gate com­mit­ted offens­es. Inso­far, the stor­age of this data is nec­es­sary to secure the con­troller. This data is not passed on to third par­ties unless there is a statu­to­ry oblig­a­tion to pass on the data, or if the trans­fer serves the aim of crim­i­nal prosecution.

The reg­is­tra­tion of the data sub­ject, with the vol­un­tary indi­ca­tion of per­son­al data, is intend­ed to enable the con­troller to offer the data sub­ject con­tents or ser­vices that may only be offered to reg­is­tered users due to the nature of the mat­ter in ques­tion. Reg­is­tered per­sons are free to change the per­son­al data spec­i­fied dur­ing the reg­is­tra­tion at any time, or to have them com­plete­ly delet­ed from the data stock of the controller.

The data con­troller shall, at any time, pro­vide infor­ma­tion upon request to each data sub­ject as to what per­son­al data are stored about the data sub­ject. In addi­tion, the data con­troller shall cor­rect or erase per­son­al data at the request or indi­ca­tion of the data sub­ject, inso­far as there are no statu­to­ry stor­age oblig­a­tions. The entire­ty of the controller’s employ­ees are avail­able to the data sub­ject in this respect as con­tact persons.

7. Subscription to our newsletters

On the web­site of the Elcul­tra UG (haf­tungs­beschränkt), users are giv­en the oppor­tu­ni­ty to sub­scribe to our enter­prise’s newslet­ter. The input mask used for this pur­pose deter­mines what per­son­al data are trans­mit­ted, as well as when the newslet­ter is ordered from the controller.

The Elcul­tra UG (haf­tungs­beschränkt) informs its cus­tomers and busi­ness part­ners reg­u­lar­ly by means of a newslet­ter about enter­prise offers. The enter­prise’s newslet­ter may only be received by the data sub­ject if (1) the data sub­ject has a valid e‑mail address and (2) the data sub­ject reg­is­ters for the newslet­ter ship­ping. A con­fir­ma­tion e‑mail will be sent to the e‑mail address reg­is­tered by a data sub­ject for the first time for newslet­ter ship­ping, for legal rea­sons, in the dou­ble opt-in pro­ce­dure. This con­fir­ma­tion e‑mail is used to prove whether the own­er of the e‑mail address as the data sub­ject is autho­rized to receive the newsletter.

Dur­ing the reg­is­tra­tion for the newslet­ter, we also store the IP address of the com­put­er sys­tem assigned by the Inter­net ser­vice provider (ISP) and used by the data sub­ject at the time of the reg­is­tra­tion, as well as the date and time of the reg­is­tra­tion. The col­lec­tion of this data is nec­es­sary in order to under­stand the (pos­si­ble) mis­use of the e‑mail address of a data sub­ject at a lat­er date, and it there­fore serves the aim of the legal pro­tec­tion of the controller.

The per­son­al data col­lect­ed as part of a reg­is­tra­tion for the newslet­ter will only be used to send our newslet­ter. In addi­tion, sub­scribers to the newslet­ter may be informed by e‑mail, as long as this is nec­es­sary for the oper­a­tion of the newslet­ter ser­vice or a reg­is­tra­tion in ques­tion, as this could be the case in the event of mod­i­fi­ca­tions to the newslet­ter offer, or in the event of a change in tech­ni­cal cir­cum­stances. There will be no trans­fer of per­son­al data col­lect­ed by the newslet­ter ser­vice to third par­ties. The sub­scrip­tion to our newslet­ter may be ter­mi­nat­ed by the data sub­ject at any time. The con­sent to the stor­age of per­son­al data, which the data sub­ject has giv­en for ship­ping the newslet­ter, may be revoked at any time. For the pur­pose of revo­ca­tion of con­sent, a cor­re­spond­ing link is found in each newslet­ter. It is also pos­si­ble to unsub­scribe from the newslet­ter at any time direct­ly on the web­site of the con­troller, or to com­mu­ni­cate this to the con­troller in a dif­fer­ent way.

8. Newsletter-Tracking

The newslet­ter of the Elcul­tra UG (haf­tungs­beschränkt) con­tains so-called track­ing pix­els. A track­ing pix­el is a minia­ture graph­ic embed­ded in such e‑mails, which are sent in HTML for­mat to enable log file record­ing and analy­sis. This allows a sta­tis­ti­cal analy­sis of the suc­cess or fail­ure of online mar­ket­ing cam­paigns. Based on the embed­ded track­ing pix­el, the Elcul­tra UG (haf­tungs­beschränkt) may see if and when an e‑mail was opened by a data sub­ject, and which links in the e‑mail were called up by data subjects.

Such per­son­al data col­lect­ed in the track­ing pix­els con­tained in the newslet­ters are stored and ana­lyzed by the con­troller in order to opti­mize the ship­ping of the newslet­ter, as well as to adapt the con­tent of future newslet­ters even bet­ter to the inter­ests of the data sub­ject. These per­son­al data will not be passed on to third par­ties. Data sub­jects are at any time enti­tled to revoke the respec­tive sep­a­rate dec­la­ra­tion of con­sent issued by means of the dou­ble-opt-in pro­ce­dure. After a revo­ca­tion, these per­son­al data will be delet­ed by the con­troller. The Elcul­tra UG (haf­tungs­beschränkt) auto­mat­i­cal­ly regards a with­draw­al from the receipt of the newslet­ter as a revocation.

9. Contact possibility via the website

The web­site of the Elcul­tra UG (haf­tungs­beschränkt) con­tains infor­ma­tion that enables 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 via a con­tact form, the per­son­al data trans­mit­ted by the data sub­ject are auto­mat­i­cal­ly stored. Such per­son­al data trans­mit­ted on a vol­un­tary basis by a data sub­ject to the data con­troller are stored for the pur­pose of pro­cess­ing or con­tact­ing the data sub­ject. There is no trans­fer of this per­son­al data to third parties.

10. Comments function in the blog on the website

The Elcul­tra UG (haf­tungs­beschränkt) 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 web-based, pub­licly-acces­si­ble por­tal, through which one or more peo­ple called blog­gers or web-blog­gers may post arti­cles or write down thoughts in so-called blog­posts. Blog­posts may usu­al­ly be com­ment­ed by third parties.

If a data sub­ject leaves a com­ment on the blog pub­lished on this web­site, the com­ments made by the data sub­ject are also stored and pub­lished, as well as infor­ma­tion on the date of the com­men­tary and on the user’s (pseu­do­nym) cho­sen by the data sub­ject. In addi­tion, the IP address assigned by the Inter­net ser­vice provider (ISP) to the data sub­ject is also logged. This stor­age of the IP address takes place for secu­ri­ty rea­sons, and in case the data sub­ject vio­lates the rights of third par­ties, or posts ille­gal con­tent through a giv­en com­ment. The stor­age of these per­son­al data is, there­fore, in the own inter­est of the data con­troller, so that he can excul­pate in the event of an infringe­ment. This col­lect­ed per­son­al data will not be passed to third par­ties, unless such a trans­fer is required by law or serves the aim of the defense of the data controller.

11. Subscription to comments in the blog on the website

The com­ments made in the blog of the Elcul­tra UG (haf­tungs­beschränkt) may be sub­scribed to by third par­ties. In par­tic­u­lar, there is the pos­si­bil­i­ty that a com­menter sub­scribes to the com­ments fol­low­ing his com­ments on a par­tic­u­lar blog post.

If a data sub­ject decides to sub­scribe to the option, the con­troller will send an auto­mat­ic con­fir­ma­tion e‑mail to check the dou­ble opt-in pro­ce­dure as to whether the own­er of the spec­i­fied e‑mail address decid­ed in favor of this option. The option to sub­scribe to com­ments may be ter­mi­nat­ed at any time.

12. Routine erasure and blocking of personal data

The data con­troller shall process and store the 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 as far as this is grant­ed by the Euro­pean leg­is­la­tor or oth­er leg­is­la­tors in laws or reg­u­la­tions to which the con­troller is sub­ject to.

If the stor­age pur­pose is not applic­a­ble, or if a stor­age peri­od pre­scribed by the Euro­pean leg­is­la­tor or anoth­er com­pe­tent leg­is­la­tor expires, the per­son­al data are rou­tine­ly blocked or erased in accor­dance with legal requirements.

13. Rights of the data subject

• a) Right of confirmation

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to obtain from the con­troller the con­fir­ma­tion as to whether or not per­son­al data con­cern­ing him or her are being processed. If a data sub­ject wish­es to avail him­self of 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

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to obtain from the con­troller free infor­ma­tion about his or her per­son­al data stored at any time and a copy of this infor­ma­tion. Fur­ther­more, the Euro­pean direc­tives and reg­u­la­tions grant 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 concerned;
  • 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 recip­i­ents in third coun­tries or inter­na­tion­al organisations;
  • where pos­si­ble, the envis­aged peri­od for which the per­son­al data will be stored, or, if not pos­si­ble, the cri­te­ria used to deter­mine that period;
  • the exis­tence of the right to request from the con­troller rec­ti­fi­ca­tion or era­sure of per­son­al data, or restric­tion of pro­cess­ing of per­son­al data con­cern­ing 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;
  • where the per­son­al data are not col­lect­ed from the data sub­ject, any avail­able infor­ma­tion as to their source;
  • the exis­tence of auto­mat­ed deci­sion-mak­ing, includ­ing pro­fil­ing, referred to in Arti­cle 22(1) and (4) of the GDPR and, at least in those cas­es, mean­ing­ful infor­ma­tion about the log­ic involved, as well as the sig­nif­i­cance and envis­aged con­se­quences of such pro­cess­ing for the data subject.

  Fur­ther­more, the data sub­ject shall have a right to obtain infor­ma­tion as to whether per­son­al data are trans­ferred to a third coun­try or to an inter­na­tion­al organ­i­sa­tion. Where this is the case, the data sub­ject shall have the right to be informed of the appro­pri­ate safe­guards relat­ing to the transfer.

  If a data sub­ject wish­es to avail him­self of this right of access, he or she may, at any time, con­tact any employ­ee of the controller.

• c) Right to rectification

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to obtain from the con­troller with­out undue delay the rec­ti­fi­ca­tion of inac­cu­rate per­son­al data con­cern­ing him or her. Tak­ing into account the pur­pos­es of the pro­cess­ing, the data sub­ject shall have the right to have incom­plete per­son­al data com­plet­ed, includ­ing by means of pro­vid­ing a sup­ple­men­tary statement.

  If a data sub­ject wish­es to exer­cise this right to 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)

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to obtain from the con­troller the era­sure of per­son­al data con­cern­ing him or her with­out undue delay, and the con­troller shall have the oblig­a­tion to erase per­son­al data with­out undue delay where one of the fol­low­ing grounds applies, as long as the pro­cess­ing is not necessary:

  • The per­son­al data are no longer nec­es­sary in rela­tion to the pur­pos­es for which they were col­lect­ed or oth­er­wise processed.
  • The data sub­ject with­draws con­sent to which the pro­cess­ing is based accord­ing to point (a) of Arti­cle 6(1) of the GDPR, or point (a) of Arti­cle 9(2) of the GDPR, and where there is no oth­er legal ground for the processing.
  • The data sub­ject objects to the pro­cess­ing pur­suant to Arti­cle 21(1) of the GDPR 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) of the GDPR.
  • The per­son­al data have been unlaw­ful­ly processed.
  • The per­son­al data must be erased for com­pli­ance with a legal oblig­a­tion in 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 the offer of infor­ma­tion soci­ety ser­vices referred to in Arti­cle 8(1) of the GDPR.

  If one of the afore­men­tioned rea­sons applies, and a data sub­ject wish­es to request the era­sure of per­son­al data stored by the Elcul­tra UG (haf­tungs­beschränkt), he or she may, at any time, con­tact any employ­ee of the con­troller. An employ­ee of Elcul­tra UG (haf­tungs­beschränkt) shall prompt­ly ensure that the era­sure request is com­plied with immediately.

  Where the con­troller has made per­son­al data pub­lic and is oblig­ed pur­suant to Arti­cle 17(1) to erase the per­son­al data, the con­troller, tak­ing account of avail­able tech­nol­o­gy and the cost of imple­men­ta­tion, shall take rea­son­able steps, includ­ing tech­ni­cal mea­sures, to inform oth­er con­trollers pro­cess­ing the per­son­al data that the data sub­ject has request­ed era­sure by such con­trollers of any links to, or copy or repli­ca­tion of, those per­son­al data, as far as pro­cess­ing is not required. An employ­ees of the Elcul­tra UG (haf­tungs­beschränkt) will arrange the nec­es­sary mea­sures in indi­vid­ual cases.

• e) Right of restriction of processing

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to obtain from the con­troller restric­tion of pro­cess­ing where one of the fol­low­ing applies:

  • 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 and the data sub­ject oppos­es the era­sure of the per­son­al data and requests instead the restric­tion of their use instead.
  • The con­troller no longer needs the per­son­al data for the pur­pos­es of the pro­cess­ing, but they are required by the data sub­ject for the estab­lish­ment, exer­cise or defence of legal claims.
  • The data sub­ject has object­ed to pro­cess­ing pur­suant to Arti­cle 21(1) of the GDPR pend­ing the ver­i­fi­ca­tion 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 the pro­cess­ing of per­son­al data stored by the Elcul­tra UG (haf­tungs­beschränkt), he or she may at any time con­tact any employ­ee of the con­troller. The employ­ee of the Elcul­tra UG (haf­tungs­beschränkt) will arrange the restric­tion of the processing.

• f) Right to data portability

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor, to receive the per­son­al data con­cern­ing him or her, which was pro­vid­ed to a con­troller, in a struc­tured, com­mon­ly used and machine-read­able for­mat. He or she shall have the right to trans­mit those data to anoth­er con­troller with­out hin­drance from the con­troller to which the per­son­al data have been pro­vid­ed, as long as the pro­cess­ing is based on con­sent pur­suant to point (a) of Arti­cle 6(1) of the GDPR or point (a) of Arti­cle 9(2) of the GDPR, or on a con­tract pur­suant to point (b) of Arti­cle 6(1) of the GDPR, and the pro­cess­ing is car­ried out by auto­mat­ed means, as long as the pro­cess­ing is not 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 controller.

  Fur­ther­more, in exer­cis­ing his or her 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 have per­son­al data trans­mit­ted direct­ly from one con­troller to anoth­er, where tech­ni­cal­ly fea­si­ble and when doing so does not adverse­ly affect the rights and free­doms of others.

  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 the Elcul­tra UG (haf­tungs­beschränkt).

• g) Right to object

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to object, on grounds relat­ing to his or her par­tic­u­lar sit­u­a­tion, at any time, to pro­cess­ing of per­son­al data con­cern­ing him or her, which is based on point (e) or (f) of Arti­cle 6(1) of the GDPR. This also applies to pro­fil­ing based on these provisions.

  The Elcul­tra UG (haf­tungs­beschränkt) 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 estab­lish­ment, exer­cise or defence of legal claims.

  If the Elcul­tra UG (haf­tungs­beschränkt) process­es per­son­al data for direct mar­ket­ing pur­pos­es, the data sub­ject shall have the right to object at any time to pro­cess­ing of per­son­al data con­cern­ing him or her for such mar­ket­ing. This applies to pro­fil­ing to the extent that it is relat­ed to such direct mar­ket­ing. If the data sub­ject objects to the Elcul­tra UG (haf­tungs­beschränkt) to the pro­cess­ing for direct mar­ket­ing pur­pos­es, the Elcul­tra UG (haf­tungs­beschränkt) will no longer process the per­son­al data for these purposes.

  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 by the Elcul­tra UG (haf­tungs­beschränkt) 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 GDPR, unless the pro­cess­ing is nec­es­sary for the per­for­mance of a task car­ried out for rea­sons of pub­lic interest.

  In order to exer­cise the right to object, the data sub­ject may con­tact any employ­ee of the Elcul­tra UG (haf­tungs­beschränkt). In addi­tion, the data sub­ject is free in the con­text of the use of infor­ma­tion soci­ety ser­vices, and notwith­stand­ing Direc­tive 2002/58/EC, to use his or her right to object by auto­mat­ed means using tech­ni­cal specifications.

• h) Automated individual decision-making, including profiling

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor 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, as long as the deci­sion (1) is not is nec­es­sary for enter­ing into, or the per­for­mance of, a con­tract between the data sub­ject and a data con­troller, or (2) is not autho­rised by Union or Mem­ber State law to which the con­troller is sub­ject and which also lays down suit­able mea­sures to safe­guard the data sub­jec­t’s rights and free­doms and legit­i­mate inter­ests, or (3) is not based on the data sub­jec­t’s explic­it consent.

  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 a data con­troller, or (2) it is based on the data sub­jec­t’s explic­it con­sent, the Elcul­tra UG (haf­tungs­beschränkt) 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, at least the right to obtain human inter­ven­tion on the part of the con­troller, to express his or her point of view and con­test the decision.

  If the data sub­ject wish­es to exer­cise the rights con­cern­ing auto­mat­ed indi­vid­ual deci­sion-mak­ing, he or she may, at any time, con­tact any employ­ee of the Elcul­tra UG (haf­tungs­beschränkt).

• i) Right to withdraw data protection consent

  Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to with­draw his or her con­sent to pro­cess­ing of his or her per­son­al data at any time.

  If the data sub­ject wish­es to exer­cise the right to with­draw the con­sent, he or she may, at any time, con­tact any employ­ee of the Elcul­tra UG (haf­tungs­beschränkt).

14. Data protection for applications and the application procedures

The data con­troller shall col­lect and process the per­son­al data of appli­cants for the pur­pose of the pro­cess­ing of the appli­ca­tion pro­ce­dure. The pro­cess­ing may also be car­ried out elec­tron­i­cal­ly. This is the case, in par­tic­u­lar, if an appli­cant sub­mits cor­re­spond­ing appli­ca­tion doc­u­ments by e‑mail or by means of a web form on the web­site to the con­troller. If the data con­troller con­cludes an employ­ment con­tract with an appli­cant, the sub­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 legal require­ments. If no employ­ment con­tract is con­clud­ed with the appli­cant by the con­troller, the appli­ca­tion doc­u­ments shall be auto­mat­i­cal­ly erased two months after noti­fi­ca­tion of the refusal deci­sion, pro­vid­ed that no oth­er legit­i­mate inter­ests of the con­troller are opposed to the era­sure. Oth­er legit­i­mate inter­est in this rela­tion is, e.g. a bur­den of proof in a pro­ce­dure under the Gen­er­al Equal Treat­ment Act (AGG).

15. Data Protection provisions about the application and use of AddThis

On this web­site, the data con­troller has inte­grat­ed com­po­nents of the enter­prise AddThis. AddThis is a so-called book­mark­ing provider. The ser­vice allows for sim­pli­fied book­mark­ing of Inter­net pages via but­tons. By click­ing on the AddThis com­po­nent with the mouse, or by click­ing on it, a list of book­mark­ing and shar­ing ser­vices is dis­played. AddThis is used on over 15 mil­lion web­sites, and the but­tons are dis­played, accord­ing to the infor­ma­tion of the oper­at­ing enter­prise, over 20 bil­lion times a year.

The oper­at­ing com­pa­ny of AddThis is AddThis, Inc. 1595 Spring Hill Road, Suite 300, Vien­na, VA 22182, Unit­ed States.

By call­ing up one of the indi­vid­ual pages of the web­site, which is oper­at­ed by the con­troller, and on which an AddThis com­po­nent has been inte­grat­ed, the Inter­net brows­er of the data sub­ject is auto­mat­i­cal­ly prompt­ed by the respec­tive AddThis com­po­nent to down­load data from the web­site www.addthis.com. With­in the frame­work of this tech­ni­cal pro­ce­dure, AddThis is informed of the vis­it and the spe­cif­ic indi­vid­ual page of this web­site that was used by the data sub­ject with the help of infor­ma­tion tech­nol­o­gy. In addi­tion, AddThis is informed about the IP address of the com­put­er sys­tem assigned by the Inter­net ser­vice provider (ISP) and used by the data sub­ject, the brows­er type and lan­guage, the web page accessed before our web­site, the date and the time of the vis­it to our web­site. AddThis uses this data to cre­ate anony­mous user pro­files. The data and infor­ma­tion trans­mit­ted to AddThis in this way will enable the enter­prise AddThis, as well as affil­i­ates or their part­ner-enter­pris­es, to con­tact vis­i­tors of the web pages of the con­troller with per­son­al­ized and inter­est-based advertising.

AddThis dis­plays per­son­al­ized and inter­est-based adver­tis­ing on the basis of a cook­ie set by the enter­prise. This cook­ie ana­lyzes the indi­vid­ual surf­ing behav­ior of the com­put­er sys­tem used by the data sub­ject. The cook­ie saves the com­put­er-based out­go­ing vis­its to Inter­net pages.

The data sub­ject may, at any time, pre­vent the set­ting of cook­ies through our web­site by means of a cor­re­spond­ing set­ting of the Inter­net brows­er used, and thus per­ma­nent­ly deny the set­ting of cook­ies. Such a set­ting of the Inter­net brows­er used would also pre­vent AddThis from set­ting a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. Cook­ies may also be delet­ed by AddThis at any time via an Inter­net brows­er or oth­er soft­ware programs.

The data sub­ject also has the pos­si­bil­i­ty of object­ing per­ma­nent­ly to the pro­cess­ing of per­son­al data by AddThis. For this pur­pose, the data sub­ject must click on the opt-out but­ton under the link http://www.addthis.com/privacy/opt-out, which sets an opt-out cook­ie. The opt-out cook­ie used for this pur­pose is placed on the infor­ma­tion tech­nol­o­gy sys­tem used by the data sub­ject. If the data sub­ject deletes the cook­ies from his sys­tem, then the data sub­ject must call up the link again and set a new opt-out cookie.

With the set­ting of the opt-out cook­ie, how­ev­er, the pos­si­bil­i­ty exists that the web­sites of the con­troller are not ful­ly usable any­more by the data subject.

The applic­a­ble data pro­tec­tion pro­vi­sions of AddThis may be accessed under http://www.addthis.com/privacy/privacy-policy.

16. Data protection provisions about the application and use of Affilinet

On this web­site, the con­troller has inte­grat­ed com­po­nents of the enter­prise Affi­l­inet. Affi­l­inet is a Ger­man affil­i­ate net­work, which offers affil­i­ate marketing.

Affil­i­ate mar­ket­ing is a web-based form of dis­tri­b­u­tion, which allows com­mer­cial oper­a­tors of Inter­net sites, the so-called mer­chants or adver­tis­ers, to show adver­tis­ing, which will be paid most­ly through click or sale com­mis­sions, on third-par­ty Inter­net sites that are also called affil­i­ates or pub­lish­ers. The Mer­chant pro­vides through the affil­i­ate net­work an adver­tis­ing medi­um, such as an adver­tis­ing ban­ner or oth­er suit­able means of Inter­net adver­tis­ing, which is sub­se­quent­ly inte­grat­ed by an affil­i­ate on its own Inter­net pages or via oth­er chan­nels such as key­word adver­tis­ing or e‑mail marketing.

The oper­at­ing com­pa­ny of Affi­l­inet is the Affi­l­inet GmbH, Sap­poro arc 6–8, 80637 Munich, Germany.

Affi­l­inet sets a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. The def­i­n­i­tion of cook­ies is explained above. The track­ing cook­ie by Affi­l­inet stores no per­son­al data. Only the iden­ti­fi­ca­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tomer, as well as the ordi­nal num­ber of the vis­i­tor of a web­site and the clicked adver­tis­ing medi­um are stored. The pur­pose of this data stor­age is the pro­cess­ing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are processed through the affil­i­ate net­work, that is Affilinet.

The data sub­ject may, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the Inter­net brows­er used and, thus, per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net brows­er used would also pre­vent Affi­l­inet 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 in use by Affi­l­inet may be delet­ed at any time via a web brows­er or oth­er soft­ware programs.

The applic­a­ble data pro­tec­tion pro­vi­sions of Affi­l­inet may be accessed under https://www.affili.net/uk/footeritem/privacy-policy.

17. Data protection provisions about the application and use of Facebook

On this web­site, the con­troller has inte­grat­ed com­po­nents of the enter­prise Face­book. Face­book is a social network.

A social net­work is a place for social meet­ings on the Inter­net, an online com­mu­ni­ty, which usu­al­ly allows users to com­mu­ni­cate with each oth­er and inter­act in a vir­tu­al space. A social net­work may serve as a plat­form for the exchange of opin­ions and expe­ri­ences, or enable the Inter­net com­mu­ni­ty to pro­vide per­son­al or busi­ness-relat­ed infor­ma­tion. Face­book allows social net­work users to include the cre­ation of pri­vate pro­files, upload pho­tos, and net­work through friend requests.

The oper­at­ing com­pa­ny of Face­book is Face­book, Inc., 1 Hack­er Way, Men­lo Park, CA 94025, Unit­ed States. If a per­son lives out­side of the Unit­ed States or Cana­da, the con­troller is the Face­book Ire­land Ltd., 4 Grand Canal Square, Grand Canal Har­bour, Dublin 2, Ireland.

With each call-up to one of the indi­vid­ual pages of this Inter­net web­site, which is oper­at­ed by the con­troller and into which a Face­book com­po­nent (Face­book plug-ins) was inte­grat­ed, the web 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 to down­load dis­play of the cor­re­spond­ing Face­book com­po­nent from Face­book through the Face­book com­po­nent. An overview of all the Face­book Plug-ins may be accessed under https://developers.facebook.com/docs/plugins/. Dur­ing the course of this tech­ni­cal pro­ce­dure, Face­book is made aware of what spe­cif­ic sub-site of our web­site was vis­it­ed by the data subject.

If the data sub­ject is logged 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 entire dura­tion of their stay on our Inter­net site—which spe­cif­ic sub-site of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the Face­book com­po­nent and asso­ci­at­ed with the respec­tive Face­book account of the data sub­ject. If the data sub­ject clicks on one of the Face­book but­tons inte­grat­ed into our web­site, e.g. the “Like” but­ton, or if the data sub­ject sub­mits a com­ment, then Face­book match­es this infor­ma­tion with the per­son­al Face­book user account of the data sub­ject and stores the per­son­al data.

Face­book always receives, through the Face­book com­po­nent, infor­ma­tion about a vis­it to our web­site by the data sub­ject, when­ev­er the data sub­ject is logged in at the same time on Face­book dur­ing the time of the call-up to our web­site. This occurs regard­less of whether the data sub­ject clicks on the Face­book com­po­nent or not. If such a trans­mis­sion of infor­ma­tion to Face­book is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Face­book account before a call-up to our web­site is made.

The data pro­tec­tion guide­line pub­lished by Face­book, which is avail­able at https://facebook.com/about/privacy/, pro­vides infor­ma­tion about the col­lec­tion, pro­cess­ing and use of per­son­al data by Face­book. In addi­tion, it is explained there what set­ting options Face­book offers to pro­tect the pri­va­cy of the data sub­ject. In addi­tion, dif­fer­ent con­fig­u­ra­tion options are made avail­able to allow the elim­i­na­tion of data trans­mis­sion to Face­book. These appli­ca­tions may be used by the data sub­ject to elim­i­nate a data trans­mis­sion to Facebook.

18. Data protection provisions about the application and use of functions of the Amazon Partner program

On this web­site, the con­troller has inte­grat­ed Ama­zon com­po­nents as a par­tic­i­pant in the Ama­zon part­ner pro­gram. The Ama­zon com­po­nents were cre­at­ed by Ama­zon with the aim to medi­ate cus­tomers through adver­tise­ments on var­i­ous web­sites of the Ama­zon group, in par­tic­u­lar Amazon.co.uk, Local.Amazon.co.uk, Amazon.de, BuyVIP.com, Amazon.fr, Amazon.it and Amazon.es in return for the pay­ment of a com­mis­sion. By using the Ama­zon com­po­nents, the con­troller may gen­er­ate adver­tis­ing revenue.

The oper­at­ing com­pa­ny of this Ama­zon com­po­nent is Ama­zon EU S.à.r.l, 5 Rue Plaetis, L‑2338 Lux­em­bourg, Luxembourg.

Ama­zon sets a cook­ie the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. The def­i­n­i­tion of cook­ies is explained above. With each sin­gle call-up to one of the indi­vid­ual pages of this Inter­net web­site, which is oper­at­ed by the con­troller and in which an Ama­zon com­po­nent was inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject will auto­mat­i­cal­ly sub­mit data for the pur­pose of online adver­tis­ing and the set­tle­ment of com­mis­sions to Ama­zon through the respec­tive Ama­zon com­po­nent. Dur­ing the course of this tech­ni­cal pro­ce­dure, Ama­zon receives per­son­al infor­ma­tion that is used to trace the ori­gin of orders from Ama­zon, and as a result, to allow the account­ing of a com­mis­sion. Among oth­er things, Ama­zon may under­stand that the data sub­ject has clicked on an affil­i­ate link on our website.

The data sub­ject may, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the web brows­er used, and thus per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net brows­er used would also pre­vent Ama­zon 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 in use by Ama­zon may be delet­ed at any­time via a web brows­er or oth­er soft­ware programs.

Fur­ther infor­ma­tion and the actu­al data pro­tec­tion pro­vi­sions of Ama­zon may be retrieved under https://www.amazon.de/gp/help/customer/display.html?nodeId=3312401&language=en_GB.

19. Data protection provisions about the application and use of Google AdSense

On this web­site, the con­troller has inte­grat­ed Google AdSense. Google AdSense is an online ser­vice which allows the place­ment of adver­tis­ing on third-par­ty sites. Google AdSense is based on an algo­rithm that selects adver­tise­ments dis­played on third-par­ty sites to match with the con­tent of the respec­tive third-par­ty site. Google AdSense allows an inter­est-based tar­get­ing of the Inter­net user, which is imple­ment­ed by means of gen­er­at­ing indi­vid­ual user profiles.

The oper­at­ing com­pa­ny of Google’s AdSense com­po­nent is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ireland.

The pur­pose of Google’s AdSense com­po­nent is the inte­gra­tion of adver­tise­ments on our web­site. Google AdSense places a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. The def­i­n­i­tion of cook­ies is explained above. With the set­ting of the cook­ie, Alpha­bet Inc. is enabled to ana­lyze the use of our web­site. With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and into which a Google AdSense com­po­nent is inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject will auto­mat­i­cal­ly sub­mit data through the Google AdSense com­po­nent for the pur­pose of online adver­tis­ing and the set­tle­ment of com­mis­sions to Alpha­bet Inc. Dur­ing the course of this tech­ni­cal pro­ce­dure, the enter­prise Alpha­bet Inc. gains knowl­edge of per­son­al data, such as the IP address of the data sub­ject, which serves Alpha­bet Inc., inter alia, to under­stand the ori­gin of vis­i­tors and clicks and sub­se­quent­ly cre­ate com­mis­sion settlements.

The data sub­ject may, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the web brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to 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. Addi­tion­al­ly, cook­ies already in use by Alpha­bet Inc. may be delet­ed at any time via a web brows­er or oth­er soft­ware programs.

Fur­ther­more, 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 web pages to enable a log file record­ing and a log file analy­sis through which a sta­tis­ti­cal analy­sis may be per­formed. Based on the embed­ded track­ing pix­els, Alpha­bet Inc. is able to deter­mine if and when a web­site was opened by a data sub­ject, and which links were clicked on by the data sub­ject. Track­ing pix­els serve, inter alia, to ana­lyze the flow of vis­i­tors on a website.

Through Google AdSense, per­son­al data and information—which also includes the IP address, and is nec­es­sary for the col­lec­tion and account­ing of the dis­played advertisements—is trans­mit­ted to Alpha­bet Inc. in the Unit­ed States of Amer­i­ca. These per­son­al data will be stored and processed in the Unit­ed States of Amer­i­ca. The Alpha­bet Inc. may dis­close the col­lect­ed per­son­al data through this tech­ni­cal pro­ce­dure to third parties.

Google AdSense is fur­ther explained under the fol­low­ing link https://www.google.com/intl/en/adsense/start/.

20. Data protection provisions about the application and use of Google Analytics (with anonymization function)

On this web­site, the con­troller has inte­grat­ed the com­po­nent of Google Ana­lyt­ics (with the anonymiz­er func­tion). Google Ana­lyt­ics is a web ana­lyt­ics ser­vice. Web ana­lyt­ics is the col­lec­tion, gath­er­ing, and analy­sis of data about the behav­ior of vis­i­tors to web­sites. A web analy­sis ser­vice col­lects, inter alia, data about the web­site from which a per­son has come (the so-called refer­rer), which sub-pages were vis­it­ed, or how often and for what dura­tion a sub-page was viewed. Web ana­lyt­ics are main­ly used for the opti­miza­tion of a web­site and in order to car­ry out a cost-ben­e­fit analy­sis of Inter­net advertising.

The oper­a­tor 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, Ireland.

For the web ana­lyt­ics through Google Ana­lyt­ics the con­troller uses the appli­ca­tion “_gat. _anonymizeIp”. By means of this appli­ca­tion the IP address of the Inter­net con­nec­tion of the data sub­ject is abridged by Google and anonymised when access­ing our web­sites from a Mem­ber State of the Euro­pean Union or anoth­er Con­tract­ing State 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 ana­lyze the traf­fic on our web­site. Google uses the col­lect­ed data and infor­ma­tion, inter alia, to eval­u­ate the use of our web­site and to pro­vide online reports, which show the activ­i­ties on our web­sites, and to pro­vide oth­er ser­vices con­cern­ing the use of our Inter­net site for us.

Google Ana­lyt­ics places a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. The def­i­n­i­tion of cook­ies is explained above. With the set­ting of the cook­ie, Google is enabled to ana­lyze the use of our web­site. With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and into which a Google Ana­lyt­ics com­po­nent was inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject will auto­mat­i­cal­ly sub­mit data through the Google Ana­lyt­ics com­po­nent for the pur­pose of online adver­tis­ing and the set­tle­ment of com­mis­sions to Google. Dur­ing the course of this tech­ni­cal pro­ce­dure, the enter­prise Google gains knowl­edge of per­son­al infor­ma­tion, such as the IP address of the data sub­ject, which serves Google, inter alia, to under­stand the ori­gin of vis­i­tors and clicks, and sub­se­quent­ly cre­ate com­mis­sion settlements.

The cook­ie is used to store per­son­al infor­ma­tion, such as the access time, the loca­tion from which the access was made, and the fre­quen­cy of vis­its of our web­site by the data sub­ject. With each vis­it to our Inter­net site, such per­son­al data, includ­ing the IP address of the Inter­net access used by the data sub­ject, will be trans­mit­ted to Google in the Unit­ed States of Amer­i­ca. These per­son­al data are stored by Google in the Unit­ed States of Amer­i­ca. Google may pass these per­son­al data col­lect­ed through the tech­ni­cal pro­ce­dure to third parties.

The data sub­ject may, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the web brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net brows­er used would also pre­vent Google Ana­lyt­ics 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 in use by Google Ana­lyt­ics may be delet­ed at any time via a web brows­er or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­si­bil­i­ty of object­ing to a col­lec­tion of data that are gen­er­at­ed by Google Ana­lyt­ics, which is relat­ed to the use of this web­site, as well as the pro­cess­ing of this data by Google and the chance to pre­clude any such. For this pur­pose, the data sub­ject must down­load a brows­er add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This brows­er add-on tells Google Ana­lyt­ics through a JavaScript, that any data and infor­ma­tion about the vis­its of Inter­net pages may not be trans­mit­ted to Google Ana­lyt­ics. The instal­la­tion of the brows­er add-ons is con­sid­ered an objec­tion by Google. If the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is lat­er delet­ed, for­mat­ted, or new­ly installed, then the data sub­ject must rein­stall the brows­er add-ons to dis­able Google Ana­lyt­ics. If the brows­er add-on was unin­stalled by the data sub­ject or any oth­er per­son who is attrib­ut­able to their sphere of com­pe­tence, or is dis­abled, it is pos­si­ble to exe­cute the rein­stal­la­tion or reac­ti­va­tion of the brows­er add-ons.

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/ and under http://www.google.com/analytics/terms/us.html. Google Ana­lyt­ics is fur­ther explained under the fol­low­ing Link https://www.google.com/analytics/.

21. Data protection provisions about the application and use of Google Remarketing

On this web­site, the con­troller has inte­grat­ed Google Remar­ket­ing ser­vices. Google Remar­ket­ing is a fea­ture of Google AdWords, which allows an enter­prise to dis­play adver­tis­ing to Inter­net users who have pre­vi­ous­ly resided on the enter­prise’s Inter­net site. The inte­gra­tion of Google Remar­ket­ing there­fore allows an enter­prise to cre­ate user-based adver­tis­ing and thus shows rel­e­vant adver­tise­ments to inter­est­ed Inter­net users.

The oper­at­ing com­pa­ny of the Google Remar­ket­ing ser­vices is the Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ireland.

The pur­pose of Google Remar­ket­ing is the inser­tion of inter­est-rel­e­vant adver­tis­ing. Google Remar­ket­ing allows us to dis­play ads on the Google net­work or on oth­er web­sites, which are based on indi­vid­ual needs and matched to the 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. The def­i­n­i­tion of cook­ies is explained above. With the set­ting of the cook­ie, Google enables a recog­ni­tion of the vis­i­tor of our web­site if he calls up con­sec­u­tive web pages, which are also a mem­ber of the Google adver­tis­ing net­work. With each call-up to an Inter­net site on which the ser­vice has been inte­grat­ed by Google Remar­ket­ing, the web brows­er of the data sub­ject iden­ti­fies auto­mat­i­cal­ly with Google. Dur­ing the course of this tech­ni­cal pro­ce­dure, Google receives per­son­al infor­ma­tion, such as the IP address or the surf­ing behav­iour of the user, which Google uses, inter alia, for the inser­tion of inter­est rel­e­vant advertising.

The cook­ie is used to store per­son­al infor­ma­tion, e.g. the Inter­net pages vis­it­ed by the data sub­ject. Each time we vis­it our Inter­net pages, per­son­al data, includ­ing the IP address of the Inter­net access used by the data sub­ject, is trans­mit­ted to Google in the Unit­ed States of Amer­i­ca. These per­son­al data are stored by Google in the Unit­ed States of Amer­i­ca. Google may pass these per­son­al data col­lect­ed through the tech­ni­cal pro­ce­dure to third parties.

The data sub­ject may, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the web brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to 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 in use by Google may be delet­ed at any time via a web brows­er or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­si­bil­i­ty of object­ing to the inter­est-based adver­tis­ing by Google. For this pur­pose, the data sub­ject must call up the link to www.google.de/settings/ads and make the desired set­tings on each Inter­net brows­er used by the data subject.

Fur­ther infor­ma­tion and the actu­al data pro­tec­tion pro­vi­sions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/.

22. Data protection provisions about the application and use of Google+

On this web­site, the con­troller has inte­grat­ed the Google+ but­ton as a com­po­nent. Google+ is a so-called social net­work. A social net­work is a social meet­ing place on the Inter­net, an online com­mu­ni­ty, which usu­al­ly allows users to com­mu­ni­cate with each oth­er and inter­act in a vir­tu­al space. A social net­work may serve as a plat­form for the exchange of opin­ions and expe­ri­ences, or enable the Inter­net com­mu­ni­ty to pro­vide per­son­al or busi­ness-relat­ed infor­ma­tion. Google+ allows users of the social net­work to include the cre­ation of pri­vate pro­files, upload pho­tos and net­work through 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, Ireland.

With each call-up to 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 auto­mat­i­cal­ly down­loads a dis­play of the cor­re­spond­ing Google+ but­ton of Google through the respec­tive Google+ but­ton com­po­nent. Dur­ing the course of this tech­ni­cal pro­ce­dure, Google is made aware of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data sub­ject. More detailed infor­ma­tion about Google+ is avail­able under https://developers.google.com/+/.

If the data sub­ject is logged in at the same time to Google+, Google rec­og­nizes with each call-up to our web­site by the data sub­ject and for the entire dura­tion of his or her stay on our Inter­net site, which spe­cif­ic sub-pages of our Inter­net page were vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the Google+ but­ton and Google match­es this with the respec­tive Google+ account asso­ci­at­ed with the data subject.

If the data sub­ject clicks on the Google+ but­ton inte­grat­ed on our web­site and thus gives a Google+ 1 rec­om­men­da­tion, then Google assigns this infor­ma­tion to the per­son­al Google+ user account of the data sub­ject and stores the per­son­al data. Google stores the Google+ 1 rec­om­men­da­tion of the data sub­ject, mak­ing 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. Sub­se­quent­ly, a Google+ 1 rec­om­men­da­tion giv­en by the data sub­ject on this web­site togeth­er with oth­er per­son­al data, such as the Google+ account name used by the data sub­ject and the stored pho­to, is stored and processed on oth­er Google ser­vices, such as search-engine results of the Google search engine, the Google account of the data sub­ject or in oth­er places, e.g. on Inter­net pages, or in rela­tion to adver­tise­ments. Google is also able to link the vis­it to this web­site with oth­er per­son­al data stored on Google. Google fur­ther records this per­son­al infor­ma­tion with the pur­pose of improv­ing or opti­miz­ing the var­i­ous Google services.

Through the Google+ but­ton, Google receives infor­ma­tion that the data sub­ject vis­it­ed our web­site, if the data sub­ject at the time of the call-up to our web­site is logged in to Google+. This occurs regard­less of whether the data sub­ject clicks or doesn’t click on the Google+ button.

If the data sub­ject does not wish to trans­mit per­son­al data to Google, he or she may pre­vent such trans­mis­sion by log­ging out of his Google+ account before call­ing up our website.

Fur­ther infor­ma­tion and the data pro­tec­tion pro­vi­sions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/. More ref­er­ences from Google about the Google+ 1 but­ton may be obtained under https://developers.google.com/+/web/buttons-policy.

23. Data protection provisions about the application and use of Google-AdWords

On this web­site, the con­troller has inte­grat­ed Google AdWords. Google AdWords is a ser­vice for Inter­net adver­tis­ing that allows the adver­tis­er to place ads in Google search engine results and the Google adver­tis­ing net­work. Google AdWords allows an adver­tis­er to pre-define spe­cif­ic key­words with the help of which an ad on Google’s search results only then dis­played, when the user uti­lizes the search engine to retrieve a key­word-rel­e­vant search result. In the Google Adver­tis­ing Net­work, the ads are dis­trib­uted on rel­e­vant web pages using an auto­mat­ic algo­rithm, tak­ing into account the pre­vi­ous­ly defined keywords.

The oper­at­ing com­pa­ny of Google AdWords is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ireland.

The pur­pose of Google AdWords is the pro­mo­tion of our web­site by the inclu­sion of rel­e­vant adver­tis­ing on the web­sites of third par­ties and in the search engine results of the search engine Google and an inser­tion of third-par­ty adver­tis­ing on our website.

If a data sub­ject reach­es our web­site via a Google ad, a con­ver­sion cook­ie is filed on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject through Google. The def­i­n­i­tion of cook­ies is explained above. A con­ver­sion cook­ie los­es its valid­i­ty after 30 days and is not used to iden­ti­fy the data sub­ject. If the cook­ie has not expired, the con­ver­sion cook­ie is used to check whether cer­tain sub-pages, e.g, the shop­ping cart from an online shop sys­tem, were called up on our web­site. Through the con­ver­sion cook­ie, both Google and the con­troller can under­stand whether a per­son who reached an AdWords ad on our web­site gen­er­at­ed sales, that is, exe­cut­ed or can­celed a sale of goods.

The data and infor­ma­tion col­lect­ed through the use of the con­ver­sion cook­ie is used by Google to cre­ate vis­it sta­tis­tics for our web­site. These vis­it sta­tis­tics are used in order to deter­mine the total num­ber of users who have been served through AdWords ads to ascer­tain the suc­cess or fail­ure of each AdWords ad and to opti­mize our AdWords ads in the future. Nei­ther our com­pa­ny nor oth­er Google AdWords adver­tis­ers receive infor­ma­tion from Google that could iden­ti­fy the data subject.

The con­ver­sion cook­ie stores per­son­al infor­ma­tion, e.g. the Inter­net pages vis­it­ed by the data sub­ject. Each time we vis­it our Inter­net pages, per­son­al data, includ­ing the IP address of the Inter­net access used by the data sub­ject, is trans­mit­ted to Google in the Unit­ed States of Amer­i­ca. These per­son­al data are stored by Google in the Unit­ed States of Amer­i­ca. Google may pass these per­son­al data col­lect­ed through the tech­ni­cal pro­ce­dure to third parties.

The data sub­ject may, at any time, pre­vent the set­ting of cook­ies by our web­site, as stat­ed above, by means of a cor­re­spond­ing set­ting of the Inter­net brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such a set­ting of the Inter­net brows­er used would also pre­vent Google from plac­ing 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 set by Google AdWords may be delet­ed at any time via the Inter­net brows­er or oth­er soft­ware programs.

The data sub­ject has a pos­si­bil­i­ty of object­ing to the inter­est based adver­tise­ment of Google. There­fore, the data sub­ject must access from each of the browsers in use the link www.google.de/settings/ads and set the desired settings.

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/.

24. Data protection provisions about the application and use of Instagram

On this web­site, the con­troller has inte­grat­ed com­po­nents of the ser­vice Insta­gram. Insta­gram is a ser­vice that may be qual­i­fied as an audio­vi­su­al plat­form, which allows users to share pho­tos and videos, as well as dis­sem­i­nate such data in oth­er social networks.

The oper­at­ing com­pa­ny of the ser­vices offered by Insta­gram is Insta­gram LLC, 1 Hack­er Way, Build­ing 14 First Floor, Men­lo Park, CA, UNITED STATES.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which an Insta­gram com­po­nent (Ins­ta but­ton) was 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 to the down­load of a dis­play of the cor­re­spond­ing Insta­gram com­po­nent of Insta­gram. Dur­ing the course of this tech­ni­cal pro­ce­dure, Insta­gram becomes aware of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data subject.

If the data sub­ject is logged in at the same time on Insta­gram, Insta­gram detects with every call-up to our web­site by the data subject—and for the entire dura­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the Insta­gram com­po­nent and is asso­ci­at­ed with the respec­tive Insta­gram account of the data sub­ject. If the data sub­ject clicks on one of the Insta­gram but­tons inte­grat­ed on our web­site, then Insta­gram match­es this infor­ma­tion with the per­son­al Insta­gram user account of the data sub­ject and stores the per­son­al data.

Insta­gram receives infor­ma­tion via the Insta­gram com­po­nent that the data sub­ject has vis­it­ed our web­site pro­vid­ed that the data sub­ject is logged in at Insta­gram at the time of the call to our web­site. This occurs regard­less of whether the per­son clicks on the Insta­gram but­ton or not. If such a trans­mis­sion of infor­ma­tion to Insta­gram is not desir­able for the data sub­ject, then he or she can pre­vent this by log­ging off from their Insta­gram account before a call-up to our web­site is made.

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Insta­gram may be retrieved under https://help.instagram.com/155833707900388 and https://www.instagram.com/about/legal/privacy/.

25. Data protection provisions about the application and use of Jetpack for WordPress

On this web­site, the con­troller has inte­grat­ed Jet­pack. Jet­pack is a Word­Press plug-in, which pro­vides addi­tion­al fea­tures to the oper­a­tor of a web­site based on Word­Press. Jet­pack allows the Inter­net site oper­a­tor, inter alia, an overview of the vis­i­tors of the site. By dis­play­ing relat­ed posts and pub­li­ca­tions, or the abil­i­ty to share con­tent on the page, it is also pos­si­ble to increase vis­i­tor num­bers. In addi­tion, secu­ri­ty fea­tures are inte­grat­ed into Jet­pack, so a Jet­pack-using site is bet­ter pro­tect­ed against brute-force attacks. Jet­pack also opti­mizes and accel­er­ates the load­ing of images on the website.

The oper­at­ing com­pa­ny of Jet­pack Plug-Ins for Word­Press is the Automat­tic Inc., 132 Hawthorne Street, San Fran­cis­co, CA 94107, UNITED STATES. The oper­at­ing enter­prise uses the track­ing tech­nol­o­gy cre­at­ed by Quant­cast Inc., 201 Third Street, San Fran­cis­co, CA 94103, UNITED STATES.

Jet­pack sets a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem used by the data sub­ject. The def­i­n­i­tion of cook­ies is explained above. With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a Jet­pack com­po­nent was 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 to sub­mit data through the Jet­pack com­po­nent for analy­sis pur­pos­es to Automat­tic. Dur­ing the course of this tech­ni­cal pro­ce­dure Automat­tic receives data that is used to cre­ate an overview of web­site vis­its. The data obtained in this way serves the analy­sis of the behav­iour of the data sub­ject, which has access to the Inter­net page of the con­troller and is ana­lyzed with the aim to opti­mize the web­site. The data col­lect­ed through the Jet­pack com­po­nent is not used to iden­ti­fy the data sub­ject with­out a pri­or obtain­ing of a sep­a­rate express con­sent of the data sub­ject. The data comes also to the notice of Quant­cast. Quant­cast uses the data for the same pur­pos­es as Automattic.

The data sub­ject can, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the web brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net brows­er used would also pre­vent Automattic/Quantcast 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 in use by Automattic/Quantcast may be delet­ed at any time via a web brows­er or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­si­bil­i­ty of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­at­ed by the Jet­pack cook­ie as well as the pro­cess­ing of these data by Automattic/Quantcast and the chance to pre­clude any such. For this pur­pose, the data sub­ject must press the ‘opt-out’ but­ton under the link https://www.quantcast.com/opt-out/ which sets an opt-out cook­ie. The opt-out cook­ie set with this pur­pose is placed on the infor­ma­tion tech­nol­o­gy sys­tem used by the data sub­ject. If the cook­ies are delet­ed on the sys­tem of the data sub­ject, then the data sub­ject must call up the link again and set a new opt-out cookie.

With the set­ting of the opt-out cook­ie, how­ev­er, the pos­si­bil­i­ty exists that the web­sites of the con­troller are not ful­ly usable any­more by the data subject.

The applic­a­ble data pro­tec­tion pro­vi­sions of Automat­tic may be accessed under https://automattic.com/privacy/. The applic­a­ble data pro­tec­tion pro­vi­sions of Quant­cast can be accessed under https://www.quantcast.com/privacy/.

26. Data protection provisions about the application and use 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 a web-based social net­work that enables users with exist­ing busi­ness con­tacts to con­nect and to make new busi­ness con­tacts. Over 400 mil­lion reg­is­tered peo­ple in more than 200 coun­tries use LinkedIn. Thus, LinkedIn is 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, UNITED STATES. For pri­va­cy mat­ters out­side of the UNITED STATES LinkedIn Ire­land, Pri­va­cy Pol­i­cy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ire­land, is responsible.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a LinkedIn com­po­nent (LinkedIn plug-in) was 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 to the down­load of a dis­play of the cor­re­spond­ing LinkedIn com­po­nent of LinkedIn. Fur­ther infor­ma­tion about the LinkedIn plug-in may be accessed under https://developer.linkedin.com/plugins. Dur­ing the course of this tech­ni­cal pro­ce­dure, LinkedIn gains knowl­edge of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data subject.

If the data sub­ject is logged in at the same time on LinkedIn, LinkedIn detects with every call-up to our web­site by the data subject—and for the entire dura­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the LinkedIn com­po­nent and asso­ci­at­ed with the respec­tive LinkedIn account of the data sub­ject. If the data sub­ject clicks on one of the LinkedIn but­tons inte­grat­ed on our web­site, then LinkedIn assigns this infor­ma­tion to the per­son­al LinkedIn user account of the data sub­ject and stores the per­son­al data.

LinkedIn receives infor­ma­tion via the LinkedIn com­po­nent that the data sub­ject has vis­it­ed our web­site, pro­vid­ed that the data sub­ject is logged in at LinkedIn at the time of the call-up to our web­site. This occurs regard­less of whether the per­son clicks on the LinkedIn but­ton or not. If such a trans­mis­sion of infor­ma­tion to LinkedIn is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their LinkedIn account before a call-up to our web­site is made.

LinkedIn pro­vides under https://www.linkedin.com/psettings/guest-controls the pos­si­bil­i­ty to unsub­scribe from e‑mail mes­sages, SMS mes­sages and tar­get­ed ads, as well as the abil­i­ty to man­age ad set­tings. LinkedIn also uses affil­i­ates such as Eire, Google Ana­lyt­ics, BlueKai, Dou­bleClick, Nielsen, Com­score, Elo­qua, and Lotame. The set­ting of such cook­ies may be denied under https://www.linkedin.com/legal/cookie-policy. The applic­a­ble pri­va­cy pol­i­cy for LinkedIn is avail­able under https://www.linkedin.com/legal/privacy-policy. The LinkedIn Cook­ie Pol­i­cy is avail­able under https://www.linkedin.com/legal/cookie-policy.

27. Data protection provisions about the application and use of Myspace

On this web­site, the con­troller has inte­grat­ed com­po­nents of MySpace LLC. MySpace is a so-called social net­work. A social net­work is an Inter­net social meet­ing place, an online com­mu­ni­ty that allows users to com­mu­ni­cate and inter­act with each oth­er in a vir­tu­al space. A social net­work can serve as a plat­form for the exchange of opin­ions and expe­ri­ences or allow 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 to cre­ate free blogs or groups of users, includ­ing pho­tos and videos.

The oper­at­ing com­pa­ny of MySpace is MySpace LLC, 8391 Bev­er­ly Blvd., #349, Los Ange­les, Cal­i­for­nia 90048, UNITED STATES.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a MySpace com­po­nent (MySpace plug-in) was 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 to the down­load through the respec­tive MySpace com­po­nent a dis­play of the cor­re­spond­ing MySpace com­po­nent of MySpace. Fur­ther infor­ma­tion about MySpace is avail­able under https://myspace.com. Dur­ing the course of this tech­ni­cal pro­ce­dure, MySpace gains knowl­edge of what spe­cif­ic sub-page of our web­site is vis­it­ed by the data subject.

If the data sub­ject is logged in at the same time on MySpace, MySpace detects with every call-up to our web­site by the data subject—and for the entire dura­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the MySpace com­po­nent and asso­ci­at­ed with the respec­tive MySpace account of the data sub­ject. If the data sub­ject clicks on one of the MySpace but­tons, inte­grat­ed on our web­site, then MySpace assigns this infor­ma­tion with the per­son­al MySpace user account of the data sub­ject and stores the per­son­al data.

MySpace receives infor­ma­tion via the MySpace com­po­nent that the data sub­ject has vis­it­ed our web­site, pro­vid­ed that the data sub­ject is logged in at MySpace at the time of the call to our web­site. This occurs regard­less of whether the per­son clicks on the MySpace com­po­nent or not. If such a trans­mis­sion of infor­ma­tion to MySpace is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their MySpace account before a call-up to our web­site is made.

The data pro­tec­tion guide­line pub­lished by MySpace, which is avail­able under 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.

28. Data protection provisions about the application and use of Pinterest

On this web­site, the con­troller has inte­grat­ed com­po­nents of Pin­ter­est Inc. Pin­ter­est is a so-called social net­work. A social net­work is an Inter­net social meet­ing place, an online com­mu­ni­ty that allows users to com­mu­ni­cate and inter­act with each oth­er in a vir­tu­al space. A social net­work may serve as a plat­form for the exchange of opin­ions and expe­ri­ences, or allow the Inter­net com­mu­ni­ty to pro­vide per­son­al or com­pa­ny-relat­ed infor­ma­tion. Pin­ter­est enables the users of the social net­work to pub­lish, inter alia, pic­ture col­lec­tions and indi­vid­ual pic­tures as well as descrip­tions on vir­tu­al pin­boards (so-called pins), which can then be shared by oth­er user’s (so-called re-pins) or com­ment­ed on.

The oper­at­ing com­pa­ny of Pin­ter­est is Pin­ter­est Inc., 808 Bran­nan Street, San Fran­cis­co, CA 94103, UNITED STATES.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a Pin­ter­est com­po­nent (Pin­ter­est plug-in) was inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject auto­mat­i­cal­ly prompt­ed to down­load through the respec­tive Pin­ter­est com­po­nent a dis­play of the cor­re­spond­ing Pin­ter­est com­po­nent. Fur­ther infor­ma­tion on Pin­ter­est is avail­able under https://pinterest.com/. Dur­ing the course of this tech­ni­cal pro­ce­dure, Pin­ter­est gains knowl­edge of what spe­cif­ic sub-page of our web­site is vis­it­ed by the data subject.

If the data sub­ject is logged in at the same time on Pin­ter­est, Pin­ter­est detects with every call-up to our web­site by the data subject—and for the entire dura­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the Pin­ter­est com­po­nent and asso­ci­at­ed with the respec­tive Pin­ter­est account of the data sub­ject. If the data sub­ject clicks on one of the Pin­ter­est but­tons, inte­grat­ed on our web­site, then 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 the per­son­al data.

Pin­ter­est receives infor­ma­tion via the Pin­ter­est com­po­nent that the data sub­ject has vis­it­ed our web­site, pro­vid­ed that the data sub­ject is logged in at Pin­ter­est at the time of the call-up to our web­site. This occurs regard­less of whether the per­son clicks on the Pin­ter­est com­po­nent or not. If such a trans­mis­sion of infor­ma­tion to Pin­ter­est is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Pin­ter­est account before a call-up to our web­site is made.

The data pro­tec­tion guide­line pub­lished by Pin­ter­est, which is avail­able under 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.

29. Data protection provisions about the application and use of Shariff

On this web­site, the con­troller has inte­grat­ed the com­po­nent of Shar­iff. The Shar­iff com­po­nent pro­vides social media but­tons that are com­pli­ant with data pro­tec­tion. Shar­iff was devel­oped for the Ger­man com­put­er mag­a­zine c’t and is pub­lished by GitHub, Inc.

The devel­op­ers of the com­po­nent is GitHub, Inc. 88 Col­in P. Kel­ly Junior Street, San Fran­cis­co, CA 94107, Unit­ed States.

Typ­i­cal­ly, the but­ton solu­tions pro­vid­ed by the social net­works already trans­mits per­son­al data to the respec­tive social net­work, when a user vis­its a web­site in which a social media but­ton was inte­grat­ed. By using the Shar­iff com­po­nent, per­son­al data is only trans­ferred to social net­works, when the vis­i­tor active­ly acti­vates one of the social media but­tons. Fur­ther infor­ma­tion on the Shar­iff com­po­nent may be found in the com­put­er mag­a­zine c’t under http://www.heise.de/newsticker/meldung/Datenschutz-und-Social-Media-Der-ct-Shariff-ist-im-Usatz-2470103. Html pro­vid­ed. The use of the Shar­iff com­po­nent is intend­ed to pro­tect the per­son­al data of the vis­i­tors of our web­site and to enable us to inte­grate a but­ton solu­tion for social net­works on this website.

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of GitHub are retriev­able under https://help.github.com/articles/github-privacy-policy/.

30. Data protection provisions about the application and use of SlideShare

On this web­site, the con­troller has inte­grat­ed SlideShare com­po­nents. LinkedIn SlideShare as a file host­ing ser­vice allows you to exchange 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 pop­u­lar for­mats, with the doc­u­ments either pub­licly-acces­si­ble or private-labeled.

The oper­at­ing com­pa­ny of SlideShare is LinkedIn Cor­po­ra­tion, 2029 Stier­lin Court Moun­tain View, CA 94043, Unit­ed States. For pri­va­cy mat­ters out­side of the Unit­ed States the LinkedIn Ire­land, Pri­va­cy Pol­i­cy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ire­land, is responsible.

LinkedIn SlideShare pro­vides so-called embed­ded codes for the media con­tent (e.g. pre­sen­ta­tions, PDF files, videos, pho­tos, etc.) stored there. Embed­ded codes are pro­gram codes that are embed­ded in the Inter­net pages to dis­play exter­nal con­tent on their own web­site. Embed­ded codes allow con­tent to be repro­duced on its own web­site with­out stor­ing it on its own serv­er, pos­si­bly vio­lat­ing the right of repro­duc­tion of the respec­tive author of the con­tent. A fur­ther advan­tage of the use of an embed­ded code is that the respec­tive oper­a­tor of a web­site does not use its own stor­age space and the own serv­er is there­by relieved. An embed­ded code may be inte­grat­ed at any point on anoth­er web­site so that an exter­nal con­tent may also be insert­ed with­in the own text. The pur­pose of using LinkedIn SlideShare is to relieve our serv­er and to avoid copy­right infringe­ments, while at the same time using third-par­ty content.

With each call-up to our Inter­net site, which is equipped with a SlideShare com­po­nent (embed­ded code), this com­po­nent prompts the brows­er that you are using to down­load the accord­ing embed­ded data from SlideShare. Dur­ing the course of this tech­ni­cal pro­ce­dure, LinkedIn gains knowl­edge of which spe­cif­ic sub-page of our web­site is vis­it­ed by the data subject.

If the data sub­ject is logged in on SlideShare at the same time, SlideShare rec­og­nizes with each call-up to our web­site by the data sub­ject and for the entire dura­tion of their stay on our Inter­net site which spe­cif­ic sub-page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed by SlideShare and assigned to the respec­tive SlideShare account of the data sub­ject through LinkedIn.

LinkedIn obtains infor­ma­tion via the SlideShare com­po­nent that the data sub­ject has vis­it­ed our web­site, pro­vid­ed that the data sub­ject is logged in at SlideShare at the time of the call-up to our web­site. This occurs regard­less of whether the per­son clicks on the embed­ded media data or not. If such a trans­mis­sion of infor­ma­tion to SlideShare is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their SlideShare account before a call-up to our web­site is made.

LinkedIn also uses affil­i­ates such as Eire, Google Ana­lyt­ics, BlueKai, Dou­bleClick, Nielsen, Com­score, Elo­qua, and Lotame. The set­ting of such cook­ies may be denied under https://www.linkedin.com/legal/cookie-policy. The applic­a­ble data pro­tec­tion pro­vi­sions for LinkedIn is avail­able under https://www.linkedin.com/legal/privacy-policy.

31. Data protection provisions about the application and use of Tumblr

On this web­site, the con­troller has inte­grat­ed com­po­nents of Tum­blr. Tum­blr is a plat­form that allows users to cre­ate and run a blog. A blog is a web-based, gen­er­al­ly pub­licly-acces­si­ble por­tal on which one or more peo­ple called blog­gers or web blog­gers may post arti­cles or write down thoughts in so-called blog­posts. For exam­ple, in a Tum­blr blog the user can pub­lish text, images, links, and videos, and spread them in the dig­i­tal space. Fur­ther­more, Tum­blr users may import con­tent from oth­er web­sites into their own blog.

The oper­at­ing com­pa­ny of Tum­blr is Tum­blr, Inc., 35 East 21st St, Ground Floor, New York, NY 10010, UNITED STATES.

Through each call to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and 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 caus­es auto­mat­i­cal­ly the down­load of a dis­play of the cor­re­spond­ing Tum­blr com­po­nent of Tum­blr. Learn more about the Tum­blr-but­tons that are avail­able under https://www.tumblr.com/buttons. Dur­ing the course of this tech­ni­cal pro­ce­dure, Tum­blr becomes aware of what con­crete sub-page of our web­site was vis­it­ed by the data sub­ject. The pur­pose of the inte­gra­tion of the Tum­blr com­po­nent is a retrans­mis­sion of the con­tents of this web­site to allow our users to intro­duce this web page to the dig­i­tal world and to increase our vis­i­tor numbers.

If the data sub­ject is logged in at Tum­blr, Tum­blr detects with every call-up to our web­site by the data subject—and for the entire dura­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the Tum­blr com­po­nent and asso­ci­at­ed with the respec­tive Tum­blr account of the data sub­ject. If the data sub­ject clicks on one of the Tum­blr but­tons, inte­grat­ed on our web­site, then Tum­blr assigns this infor­ma­tion to the per­son­al Tum­blr user account of the data sub­ject and stores the per­son­al data.

Tum­blr receives infor­ma­tion via the Tum­blr com­po­nent that the data sub­ject has vis­it­ed our web­site, pro­vid­ed that the data sub­ject is logged in at Tum­blr at the time of the call-up to our web­site. This occurs regard­less of whether the per­son clicks on the Tum­blr com­po­nent or not. If such a trans­fer of infor­ma­tion to Tum­blr is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Tum­blr account before a call-up to our web­site is made.

The applic­a­ble data pro­tec­tion pro­vi­sions of Tum­blr may be accessed under https://www.tumblr.com/policy/en/privacy.

32. Data protection provisions about the application and use of Twitter

On this web­site, the con­troller has inte­grat­ed com­po­nents of Twit­ter. Twit­ter is a mul­ti­lin­gual, pub­licly-acces­si­ble microblog­ging ser­vice on which users may pub­lish and spread so-called ‘tweets,’ e.g. short mes­sages, which are lim­it­ed to 280 char­ac­ters. These short mes­sages are avail­able for every­one, includ­ing those who are not logged on to Twit­ter. The tweets are also dis­played to so-called fol­low­ers of the respec­tive user. Fol­low­ers are oth­er Twit­ter users who fol­low a user’s tweets. Fur­ther­more, Twit­ter allows you to address a wide audi­ence via hash­tags, links or retweets.

The oper­at­ing 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­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a Twit­ter com­po­nent (Twit­ter but­ton) was 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 to down­load a dis­play of the cor­re­spond­ing Twit­ter com­po­nent of Twit­ter. Fur­ther infor­ma­tion about the Twit­ter but­tons is avail­able under https://about.twitter.com/de/resources/buttons. Dur­ing the course of this tech­ni­cal pro­ce­dure, Twit­ter gains knowl­edge of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data sub­ject. The pur­pose of the inte­gra­tion of the Twit­ter com­po­nent is a retrans­mis­sion of the con­tents of this web­site to allow our users to intro­duce this web page to the dig­i­tal world and increase our vis­i­tor numbers.

If the data sub­ject is logged 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 entire dura­tion of their stay on our Inter­net site which spe­cif­ic sub-page of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the Twit­ter com­po­nent and asso­ci­at­ed with the respec­tive Twit­ter account of the data sub­ject. If the data sub­ject clicks on one of the Twit­ter but­tons inte­grat­ed on our web­site, then Twit­ter assigns this infor­ma­tion to the per­son­al Twit­ter user account of the data sub­ject and stores the per­son­al data.

Twit­ter receives infor­ma­tion via the Twit­ter com­po­nent that the data sub­ject has vis­it­ed our web­site, pro­vid­ed that the data sub­ject is logged in on Twit­ter at the time of the call-up to our web­site. This occurs regard­less of whether the per­son clicks on the Twit­ter com­po­nent or not. If such a trans­mis­sion of infor­ma­tion to Twit­ter is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Twit­ter account before a call-up to our web­site is made.

The applic­a­ble data pro­tec­tion pro­vi­sions of Twit­ter may be accessed under https://twitter.com/privacy?lang=en .

33. Data protection provisions about the application and use of Xing

On this web­site, the con­troller has inte­grat­ed com­po­nents of XING. XING is an Inter­net-based social net­work that enables users to con­nect with exist­ing busi­ness con­tacts and to cre­ate new busi­ness con­tacts. The indi­vid­ual users can cre­ate a per­son­al pro­file of them­selves at XING. Com­pa­nies may, e.g. cre­ate com­pa­ny pro­files or pub­lish jobs on XING.

The oper­at­ing com­pa­ny of XING is XING SE, Damm­torstraße 30, 20354 Ham­burg, Germany.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a XING com­po­nent (XING plug-in) was 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 to down­load a dis­play of the cor­re­spond­ing XING com­po­nent of XING. Fur­ther infor­ma­tion about the XING plug-in the may be accessed under https://dev.xing.com/plugins. Dur­ing the course of this tech­ni­cal pro­ce­dure, XING gains knowl­edge of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data subject.

If the data sub­ject is logged in at the same time on XING, XING detects with every call-up to our web­site by the data subject—and for the entire dura­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed through the XING com­po­nent and asso­ci­at­ed with the respec­tive XING account of the data sub­ject. If the data sub­ject clicks on the XING but­ton inte­grat­ed on our Inter­net site, e.g. the “Share”-button, then XING assigns this infor­ma­tion to the per­son­al XING user account of the data sub­ject and stores the per­son­al data.

XING receives infor­ma­tion via the XING com­po­nent that the data sub­ject has vis­it­ed our web­site, pro­vid­ed that the data sub­ject is logged in at XING at the time of the call to our web­site. This occurs regard­less of whether the per­son clicks on the XING com­po­nent or not. If such a trans­mis­sion of infor­ma­tion to XING is not desir­able for the data sub­ject, then he or she can pre­vent this by log­ging off from their XING account before a call-up to our web­site is made.

The data pro­tec­tion pro­vi­sions pub­lished by XING, which is avail­able under 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. In addi­tion, XING has pub­lished pri­va­cy notices for the XING share but­ton under https://www.xing.com/app/share?op=data_protection.

34. Data protection provisions about the application and use of YouTube

On this web­site, the con­troller has inte­grat­ed com­po­nents of YouTube. YouTube is an Inter­net video por­tal that enables video pub­lish­ers to set video clips and oth­er users free of charge, which also pro­vides free view­ing, review and com­ment­ing on them. YouTube allows you to pub­lish all kinds of videos, so you can access both full movies and TV broad­casts, as well as music videos, trail­ers, and videos made by users via the Inter­net portal.

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, Ireland.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a YouTube com­po­nent (YouTube video) was 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 to down­load a dis­play of the cor­re­spond­ing YouTube com­po­nent. Fur­ther infor­ma­tion about YouTube may be obtained under https://www.youtube.com/yt/about/en/. Dur­ing the course of this tech­ni­cal pro­ce­dure, YouTube and Google gain knowl­edge of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data subject.

If the data sub­ject is logged in on YouTube, YouTube rec­og­nizes with each call-up to a sub-page that con­tains a YouTube video, which spe­cif­ic sub-page of our Inter­net site was vis­it­ed by the data sub­ject. This infor­ma­tion is col­lect­ed by YouTube and Google and assigned to the respec­tive YouTube account of the data subject.

YouTube and Google will receive infor­ma­tion through the YouTube com­po­nent that the data sub­ject has vis­it­ed our web­site, if the data sub­ject at the time of the call to our web­site is logged in on YouTube; this occurs regard­less of whether the per­son clicks on a YouTube video or not. If such a trans­mis­sion of this infor­ma­tion to YouTube and Google is not desir­able for the data sub­ject, the deliv­ery may be pre­vent­ed if the data sub­ject logs off from their own YouTube account before a call-up to our web­site is made.

YouTube’s data pro­tec­tion pro­vi­sions, avail­able at https://www.google.com/intl/en/policies/privacy/, pro­vide infor­ma­tion about the col­lec­tion, pro­cess­ing and use of per­son­al data by YouTube and Google.

35. Data protection provisions about the application and use of DoubleClick

On this web­site, the con­troller has inte­grat­ed com­po­nents of Dou­bleClick by Google. Dou­bleClick is a trade­mark of Google, under which pre­dom­i­nant­ly spe­cial online mar­ket­ing solu­tions are mar­ket­ed to adver­tis­ing agen­cies and publishers.

The oper­at­ing com­pa­ny of Dou­bleClick by Google is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ireland.

Dou­bleClick by Google trans­mits data to the Dou­bleClick serv­er with each impres­sion, clicks, or oth­er activ­i­ty. Each of these data trans­fers trig­gers a cook­ie request to the data sub­jec­t’s brows­er. If the brows­er accepts this request, Dou­bleClick uses a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. The def­i­n­i­tion of cook­ies is explained above. The pur­pose of the cook­ie is the opti­miza­tion and dis­play of adver­tis­ing. The cook­ie is used, inter alia, to dis­play and place user-rel­e­vant adver­tis­ing as well as to cre­ate or improve reports on adver­tis­ing cam­paigns. Fur­ther­more, the cook­ie serves to avoid mul­ti­ple dis­play of the same advertisement.

Dou­bleClick uses a cook­ie ID that is required to exe­cute the tech­ni­cal process. For exam­ple, the cook­ie ID is required to dis­play an adver­tise­ment in a brows­er. Dou­bleClick may 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­ca­tions. It is also pos­si­ble for Dou­bleClick to track con­ver­sions through the cook­ie ID. For instance, con­ver­sions are cap­tured, when a user has pre­vi­ous­ly been shown a Dou­bleClick adver­tis­ing ad, and he or she sub­se­quent­ly makes a pur­chase on the adver­tis­er’s web­site using the same Inter­net browser.

A cook­ie from Dou­bleClick 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 IDs. A cam­paign ID is used to iden­ti­fy cam­paigns that the user has already been in con­tact with.

With each call-up to one of the indi­vid­ual pages of this web­site, which is oper­at­ed by the con­troller and on which a Dou­bleClick com­po­nent was 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 Dou­bleClick com­po­nent to send data for the pur­pose of online adver­tis­ing and billing of com­mis­sions to Google. Dur­ing the course of this tech­ni­cal pro­ce­dure, Google gains knowl­edge of any data that Google may use to cre­ate com­mis­sion cal­cu­la­tions. Google may, inter alia, under­stand that the data sub­ject has clicked on cer­tain links on our website.

The data sub­ject may, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the web brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to 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 in use by Google may be delet­ed at any time via a web brows­er or oth­er soft­ware programs.

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Dou­bleClick may be retrieved under Dou­bleClick by Google https://www.google.com/intl/en/policies/.

36. Payment Method: Data protection provisions about the use of Klarna as a payment processor

On this web­site, the con­troller has inte­grat­ed Klar­na com­po­nents. Klar­na is an online pay­ment ser­vice provider, which allows pur­chas­es on an account or a flex­i­ble install­ment pay­ment. Klar­na also offers oth­er ser­vices, such as buy­er pro­tec­tion and iden­ti­ty or cred­it­wor­thi­ness checks.

The oper­at­ing com­pa­ny of Klar­na is Klar­na AB, Sveavä­gen 46, 111 34 Stock­holm, Sweden.

If the data sub­ject selects the “pur­chase on account” or “install­ment pur­chase” dur­ing the order­ing process in our online shop as a pay­ment option, the data of the data sub­ject is auto­mat­i­cal­ly trans­mit­ted to Klar­na. By select­ing one of these pay­ment options, the data sub­ject agrees to this trans­mis­sion of per­son­al data required for the pro­cess­ing of the invoice or install­ment pur­chase, or iden­ti­ty and cred­it­wor­thi­ness checks.

The per­son­al data trans­mit­ted to Klar­na is usu­al­ly first name, sur­name, address, date of birth, sex, email address, IP address, tele­phone num­ber, mobile phone num­ber, as well as oth­er data nec­es­sary for the pro­cess­ing of an invoice or install­ment pur­chase. The pro­cess­ing of the pur­chase con­tract also requires such per­son­al data, which are in con­nec­tion with the respec­tive order. In par­tic­u­lar, the exchange of pay­ment infor­ma­tion such as bank details, card num­ber, date of valid­i­ty and CVC code, cumu­la­tive num­ber, item num­ber, data on goods and ser­vices, prices and tax­es, infor­ma­tion on the pre­vi­ous pur­chase behav­ior or oth­er details of the finan­cial sit­u­a­tion of the data subject.

The pur­pose of the trans­mis­sion of the data is, in par­tic­u­lar, the iden­ti­fi­ca­tion check, pay­ment admin­is­tra­tion, and­fraud pre­ven­tion. The con­troller shall pro­vide Klar­na with per­son­al data, in par­tic­u­lar, if a legit­i­mate inter­est in the trans­mis­sion exists. The per­son­al data exchanged between Klar­na and the data sub­ject for the data pro­cess­ing shall be trans­mit­ted by Klar­na to eco­nom­ic agen­cies. This trans­mis­sion is intend­ed for iden­ti­ty and cred­it­wor­thi­ness checks.

Klar­na shall also pass on the per­son­al data to affil­i­ates (Klar­na Group) and ser­vice providers or sub­con­trac­tors as far as this is nec­es­sary to ful­fill con­trac­tu­al oblig­a­tions or to process the data in the order.

Klar­na col­lects and uses data and infor­ma­tion on the pre­vi­ous pay­ment behav­ior of the data sub­ject as well as prob­a­bil­i­ty val­ues for their behav­ior in the future (so-called scor­ing) in order to decide on the rea­son­ing, imple­men­ta­tion or ter­mi­na­tion of a con­trac­tu­al rela­tion­ship. The cal­cu­la­tion of scor­ing is car­ried out on the basis of sci­en­tif­i­cal­ly-rec­og­nized math­e­mat­i­cal-sta­tis­ti­cal methods.

The data sub­ject is able to revoke the con­sent to the han­dling of per­son­al data at any time from Klar­na. A revo­ca­tion shall not have any effect on per­son­al data which must be processed, used or trans­mit­ted in accor­dance with (con­trac­tu­al) pay­ment processing.

The applic­a­ble data pro­tec­tion pro­vi­sions of Klar­na may be retrieved under https://cdn.klarna.com/1.0/shared/content/policy/data/de_de/data_protection.pdf.

37. Payment Method: Data protection provisions about the use of PayPal as a payment processor

On this web­site, the con­troller has inte­grat­ed com­po­nents of Pay­Pal. Pay­Pal is an online pay­ment ser­vice provider. Pay­ments are processed via so-called Pay­Pal accounts, which rep­re­sent vir­tu­al pri­vate or busi­ness accounts. Pay­Pal is also able to process vir­tu­al pay­ments through cred­it cards when a user does not have a Pay­Pal account. A Pay­Pal account is man­aged via an e‑mail address, which is why there are no clas­sic account num­bers. Pay­Pal makes it pos­si­ble to trig­ger online pay­ments to third par­ties or to receive pay­ments. Pay­Pal also accepts trustee func­tions and offers buy­er pro­tec­tion services.

The Euro­pean oper­at­ing com­pa­ny of Pay­Pal is Pay­Pal (Europe) S.à.r.l. & Cie. S.C.A., 22–24 Boule­vard Roy­al, 2449 Lux­em­bourg, Luxembourg.

If the data sub­ject choos­es “Pay­Pal” as the pay­ment option in the online shop dur­ing the order­ing process, we auto­mat­i­cal­ly trans­mit the data of the data sub­ject to Pay­Pal. By select­ing this pay­ment option, the data sub­ject agrees to the trans­fer of per­son­al data required for pay­ment processing.

The per­son­al data trans­mit­ted to Pay­Pal is usu­al­ly first name, last name, address, email address, IP address, tele­phone num­ber, mobile phone num­ber, or oth­er data nec­es­sary for pay­ment pro­cess­ing. The pro­cess­ing of the pur­chase con­tract also requires such per­son­al data, which are in con­nec­tion with the respec­tive order.

The trans­mis­sion of the data is aimed at pay­ment pro­cess­ing and fraud pre­ven­tion. The con­troller will trans­fer per­son­al data to Pay­Pal, in par­tic­u­lar, if a legit­i­mate inter­est in the trans­mis­sion is giv­en. The per­son­al data exchanged between Pay­Pal and the con­troller for the pro­cess­ing of the data will be trans­mit­ted by Pay­Pal to eco­nom­ic cred­it agen­cies. This trans­mis­sion is intend­ed for iden­ti­ty and cred­it­wor­thi­ness checks.

Pay­Pal will, if nec­es­sary, pass on per­son­al data to affil­i­ates and ser­vice providers or sub­con­trac­tors to the extent that this is nec­es­sary to ful­fill con­trac­tu­al oblig­a­tions or for data to be processed in the order.

The data sub­ject has the pos­si­bil­i­ty to revoke con­sent for the han­dling of per­son­al data at any time from Pay­Pal. A revo­ca­tion shall not have any effect on per­son­al data which must be processed, used or trans­mit­ted in accor­dance with (con­trac­tu­al) pay­ment processing.

The applic­a­ble data pro­tec­tion pro­vi­sions of Pay­Pal may be retrieved under https://www.paypal.com/us/webapps/mpp/ua/privacy-full.

38. Payment Method: Data protection provisions about the use of Skrill as a payment processor

On this web­site, the con­troller has inte­grat­ed com­po­nents by Skrill. Skrill is an online pay­ment ser­vice provider. Pay­ments are made via the so-called Skrill wal­let, which is a vir­tu­al elec­tron­ic wal­let. Skrill also offers the pos­si­bil­i­ty to make vir­tu­al pay­ments via cred­it cards. A Skrill wal­let is man­aged via an e‑mail address. Skrill makes it pos­si­ble to trig­ger online pay­ments to third par­ties or to receive payments.

The oper­at­ing com­pa­ny of Skrill is Skrill Lim­it­ed, Floor 27, 25 Cana­da Square, Lon­don, E14 5LQ, Unit­ed Kingdom.

If the data sub­ject choos­es “Skrill” as the pay­ment option dur­ing the order­ing process in our online-shop, the data will be trans­mit­ted auto­mat­i­cal­ly to Skrill. By select­ing this pay­ment option, the data sub­ject agrees to the trans­mis­sion of per­son­al data required for pay­ment processing.

The per­son­al data exchanged with Skrill is the pur­chase sum and e‑mail address, which are both nec­es­sary for pay­ment pro­cess­ing. The trans­mis­sion of data is aimed at pay­ment pro­cess­ing and fraud pre­ven­tion. The con­troller will also pro­vide Skrill with oth­er per­son­al data in the case, if a legit­i­mate inter­est in the trans­mis­sion exists. The per­son­al data exchanged between Skrill and the data sub­ject shall be trans­mit­ted by Skrill to the eco­nom­ic agen­cies. This trans­mis­sion is intend­ed for iden­ti­ty and cred­it­wor­thi­ness checks.

If nec­es­sary, Skrill will pass on per­son­al data to affil­i­ates and ser­vice providers or sub­con­trac­tors to the extent nec­es­sary to ful­fill con­trac­tu­al oblig­a­tions or to process the data in the order.

The data sub­ject has the pos­si­bil­i­ty to revoke the con­sent to the han­dling of per­son­al data at any time from Skrill. A revo­ca­tion shall not have any effect on per­son­al data which must be processed, used or trans­mit­ted in accor­dance with (con­trac­tu­al) pay­ment processing.

The applic­a­ble data pro­tec­tion pro­vi­sions of Skrill may be retrieved under https://www.skrill.com/en/footer/privacypolicy/.

39. Payment Method: Data protection provisions about the use of Sofortüberweisung as a payment processor

On this web­site, the con­troller has inte­grat­ed com­po­nents of Sofortüber­weisung. Sofortüber­weisung is a pay­ment ser­vice that allows cash­less pay­ment of prod­ucts and ser­vices on the Inter­net. Sofortüber­weisung is a tech­ni­cal pro­ce­dure by which the online deal­er imme­di­ate­ly receives a pay­ment con­fir­ma­tion. This enables a trad­er to deliv­er goods, ser­vices or down­loads to the cus­tomer imme­di­ate­ly after ordering.

The oper­at­ing com­pa­ny of Sofortüber­weisung is SOFORT GmbH, Fußbergstraße 1, 82131 Gaut­ing, Germany.

If the data sub­ject choos­es “imme­di­ate trans­fer” as the pay­ment option in our online shop dur­ing the order­ing process, the data of the data sub­ject will be trans­mit­ted to Sofortüber­weisung. By select­ing this pay­ment option, the data sub­ject agrees to the trans­mis­sion of per­son­al data required for pay­ment processing.

In the case of pur­chase pro­cess­ing via direct trans­fer, the buy­er sends the PIN and the TAN to Sofort GmbH. Sofortüber­weisung then car­ries out a trans­fer to the online mer­chant after tech­ni­cal ver­i­fi­ca­tion of the account sta­tus and retrieval of addi­tion­al data to check the account assign­ment. The online trad­er is then auto­mat­i­cal­ly informed of the exe­cu­tion of the finan­cial transaction.

The per­son­al data exchanged with Sofortüber­weisung is the first name, last name, address, email address, IP address, tele­phone num­ber, mobile phone num­ber, or oth­er data nec­es­sary for pay­ment pro­cess­ing. The trans­mis­sion of the data is aimed at pay­ment pro­cess­ing and fraud pre­ven­tion. The con­troller shall imme­di­ate­ly trans­fer oth­er per­son­al data, even if a legit­i­mate inter­est in the trans­mis­sion exists. The per­son­al data exchanged between Sofortüber­weisung and the con­troller shall be trans­mit­ted by Sofortüber­weisung to eco­nom­ic cred­it agen­cies. This trans­mis­sion is intend­ed for iden­ti­ty and cred­it­wor­thi­ness checks.

Sofortüber­weisung pro­vides per­son­al data to affil­i­at­ed com­pa­nies and ser­vice providers or sub­con­trac­tors as far as this is nec­es­sary for the ful­fill­ment of con­trac­tu­al oblig­a­tions or data in order to be processed.

The data sub­ject has the pos­si­bil­i­ty to revoke the con­sent to the han­dling of per­son­al data at any time from Sofortüber­weisung. A revo­ca­tion shall not have any effect on per­son­al data which must be processed, used or trans­mit­ted in accor­dance with (con­trac­tu­al) pay­ment processing.

The applic­a­ble data pro­tec­tion pro­vi­sions of Sofortüber­weisung may be retrieved under https://www.sofort.com/eng-DE/datenschutzerklaerung-sofort-gmbh/.

40. Legal basis for the processing

Art. 6(1) lit. a GDPR serves as the legal basis for pro­cess­ing oper­a­tions for 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 par­ty, as is the case, for exam­ple, when pro­cess­ing oper­a­tions are nec­es­sary for the sup­ply of goods or to pro­vide any oth­er ser­vice, the pro­cess­ing is based on Arti­cle 6(1) lit. b GDPR. The same applies to such pro­cess­ing oper­a­tions which are nec­es­sary for car­ry­ing out pre-con­trac­tu­al mea­sures, for exam­ple in the case of inquiries con­cern­ing our prod­ucts or ser­vices. Is our com­pa­ny sub­ject to a legal oblig­a­tion by which pro­cess­ing of per­son­al data is required, such as for the ful­fill­ment of tax oblig­a­tions, the pro­cess­ing is based on Art. 6(1) lit. c GDPR.
In rare cas­es, the pro­cess­ing of per­son­al data may be nec­es­sary to pro­tect the vital inter­ests of the data sub­ject or of anoth­er nat­ur­al per­son. This would be the case, for exam­ple, if a vis­i­tor were injured in our com­pa­ny and his name, age, health insur­ance data or oth­er vital infor­ma­tion would have 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(1) lit. d GDPR.
Final­ly, pro­cess­ing oper­a­tions could be based on Arti­cle 6(1) lit. f GDPR. This legal basis is used for pro­cess­ing oper­a­tions which are not cov­ered by any of the above­men­tioned legal grounds, if pro­cess­ing is nec­es­sary for the pur­pos­es of the legit­i­mate inter­ests pur­sued by our com­pa­ny or by a third par­ty, except where such inter­ests are over­rid­den by the inter­ests or fun­da­men­tal rights and free­doms of the data sub­ject which require pro­tec­tion of per­son­al data. Such pro­cess­ing oper­a­tions are par­tic­u­lar­ly per­mis­si­ble because they have been specif­i­cal­ly men­tioned by the Euro­pean leg­is­la­tor. He con­sid­ered that a legit­i­mate inter­est could be assumed if the data sub­ject is a client of the con­troller (Recital 47 Sen­tence 2 GDPR).

41. The legitimate interests pursued by the controller or by a third party

Where the pro­cess­ing of per­son­al data is based on Arti­cle 6(1) lit. f GDPR our legit­i­mate inter­est is to car­ry out our busi­ness in favor of the well-being of all our employ­ees and the shareholders.

42. Period for which the personal data will be stored

The cri­te­ria used to deter­mine the peri­od of stor­age of per­son­al data is the respec­tive statu­to­ry reten­tion peri­od. After expi­ra­tion of that peri­od, the cor­re­spond­ing data is rou­tine­ly delet­ed, as long as it is no longer nec­es­sary for the ful­fill­ment of the con­tract or the ini­ti­a­tion of a contract.

43. Provision of personal data as statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data

We clar­i­fy that the pro­vi­sion of per­son­al data is part­ly required by law (e.g. tax reg­u­la­tions) or can also result from con­trac­tu­al pro­vi­sions (e.g. infor­ma­tion on the con­trac­tu­al partner).

Some­times it may be nec­es­sary to con­clude a con­tract that the data sub­ject pro­vides us with per­son­al data, which must sub­se­quent­ly be processed by us. The data sub­ject is, for exam­ple, oblig­ed to pro­vide us with per­son­al data when our com­pa­ny signs a con­tract with him or her. The non-pro­vi­sion of the per­son­al data would have the con­se­quence that the con­tract with the data sub­ject could not be concluded.

Before per­son­al data is pro­vid­ed by the data sub­ject, the data sub­ject must con­tact any employ­ee. The employ­ee clar­i­fies to the data sub­ject whether the pro­vi­sion of the per­son­al data is required by law or con­tract or is 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 the con­se­quences of non-pro­vi­sion of the per­son­al data.

44. Existence of automated decision-making

As a respon­si­ble com­pa­ny, we do not use auto­mat­ic deci­sion-mak­ing or profiling.