Pri­vacy Policy

We are very delighted that you have shown interest in our enter­prise. Data pro­tec­tion is of a par­tic­u­larly high pri­or­ity for the man­age­ment of the ASW Andreas Heuel GmbH. The use of the Inter­net pages of the ASW Andreas Heuel GmbH is pos­sible without any indic­a­tion of per­son­al data; how­ever, if a data sub­ject wants to use spe­cial enter­prise ser­vices via our web­site, pro­cessing of per­son­al data could become neces­sary. If the pro­cessing of per­son­al data is neces­sary and there is no stat­utory basis for such pro­cessing, we gen­er­ally obtain con­sent from the data subject.

The pro­cessing 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 accord­ance with the coun­try-spe­cif­ic data pro­tec­tion reg­u­la­tions applic­able to the ASW Andreas Heuel GmbH. By means of this data pro­tec­tion declar­a­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 pro­cess. Fur­ther­more, data sub­jects are informed, by means of this data pro­tec­tion declar­a­tion, of the rights to which they are entitled.

As the con­trol­ler, the ASW Andreas Heuel GmbH has imple­men­ted numer­ous tech­nic­al and organ­iz­a­tion­al meas­ures to ensure the most com­plete pro­tec­tion of per­son­al data pro­cessed through this web­site. How­ever, Inter­net-based data trans­mis­sions may in prin­ciple have secur­ity gaps, so abso­lute pro­tec­tion may not be guar­an­teed. For this reas­on, every data sub­ject is free to trans­fer per­son­al data to us via altern­at­ive means, e.g. by telephone.

1. Defin­i­tions

The data pro­tec­tion declar­a­tion of the ASW Andreas Heuel GmbH is based on the terms used by the European legis­lat­or for the adop­tion of the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR). Our data pro­tec­tion declar­a­tion should be legible and under­stand­able for the gen­er­al pub­lic, as well as our cus­tom­ers and busi­ness part­ners. To ensure this, we would like to first explain the ter­min­o­logy used.

In this data pro­tec­tion declar­a­tion, we use, inter alia, the fol­low­ing terms:

  • a) Per­son­al data

    Per­son­al data means any inform­a­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, dir­ectly or indir­ectly, in par­tic­u­lar by ref­er­ence to an iden­ti­fi­er such as a name, an iden­ti­fic­a­tion num­ber, loc­a­tion data, an online iden­ti­fi­er or to one or more factors spe­cif­ic to the phys­ic­al, physiolo­gic­al, genet­ic, men­tal, eco­nom­ic, cul­tur­al or social iden­tity 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 pro­cessed by the con­trol­ler respons­ible for the processing.

  • c) Pro­cessing

    Pro­cessing 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, wheth­er or not by auto­mated means, such as col­lec­tion, record­ing, organ­isa­tion, struc­tur­ing, stor­age, adapt­a­tion or alter­a­tion, retriev­al, con­sulta­tion, use, dis­clos­ure by trans­mis­sion, dis­sem­in­a­tion or oth­er­wise mak­ing avail­able, align­ment or com­bin­a­tion, restric­tion, eras­ure or destruction.

  • d) Restric­tion of processing

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

  • e) Pro­fil­ing

    Pro­fil­ing means any form of auto­mated pro­cessing 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 ana­lyse or pre­dict aspects con­cern­ing that nat­ur­al per­son’s per­form­ance at work, eco­nom­ic situ­ation, health, per­son­al pref­er­ences, interests, reli­ab­il­ity, beha­viour, loc­a­tion or movements.

  • f) Pseud­onymisa­tion

    Pseud­onymisa­tion is the pro­cessing 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 without the use of addi­tion­al inform­a­tion, provided that such addi­tion­al inform­a­tion is kept sep­ar­ately and is sub­ject to tech­nic­al and organ­isa­tion­al meas­ures 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) Con­trol­ler or con­trol­ler respons­ible for the processing

    Con­trol­ler or con­trol­ler respons­ible for the pro­cessing is the nat­ur­al or leg­al per­son, pub­lic author­ity, agency or oth­er body which, alone or jointly with oth­ers, determ­ines the pur­poses and means of the pro­cessing of per­son­al data; where the pur­poses and means of such pro­cessing are determ­ined by Uni­on or Mem­ber State law, the con­trol­ler or the spe­cif­ic cri­ter­ia for its nom­in­a­tion may be provided for by Uni­on or Mem­ber State law.

  • h) Pro­cessor

    Pro­cessor is a nat­ur­al or leg­al per­son, pub­lic author­ity, agency or oth­er body which pro­cesses per­son­al data on behalf of the controller.

  • i) Recip­i­ent

    Recip­i­ent is a nat­ur­al or leg­al per­son, pub­lic author­ity, agency or anoth­er body, to which the per­son­al data are dis­closed, wheth­er a third party or not. How­ever, pub­lic author­it­ies which may receive per­son­al data in the frame­work of a par­tic­u­lar inquiry in accord­ance with Uni­on or Mem­ber State law shall not be regarded as recip­i­ents; the pro­cessing of those data by those pub­lic author­it­ies shall be in com­pli­ance with the applic­able data pro­tec­tion rules accord­ing to the pur­poses of the processing.

  • j) Third party

    Third party is a nat­ur­al or leg­al per­son, pub­lic author­ity, agency or body oth­er than the data sub­ject, con­trol­ler, pro­cessor and per­sons who, under the dir­ect author­ity of the con­trol­ler or pro­cessor, are author­ised to pro­cess per­son­al data.

  • k) Con­sent

    Con­sent of the data sub­ject is any freely giv­en, spe­cif­ic, informed and unam­bigu­ous indic­a­tion of the data sub­ject’s wishes by which he or she, by a state­ment or by a clear affirm­at­ive action, sig­ni­fies agree­ment to the pro­cessing of per­son­al data relat­ing to him or her.

2. Name and Address of the controller

Con­trol­ler for the pur­poses of the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR), oth­er data pro­tec­tion laws applic­able in Mem­ber states of the European Uni­on and oth­er pro­vi­sions related to data pro­tec­tion is:

ASW Andreas Heuel GmbH

Rönt­gen­straße 10

D – 57439 Attendorn

Deutsch­land

Phone: +49 (0) 27 22.93 63.0

Email: info@asw-wekador.de

Web­site: www.asw-wekador.de

3. Name and Address of the Data Pro­tec­tion Officer

The Data Pro­tec­tion Officer of the con­trol­ler is:

Andreas Heuel

ASW Andreas Heuel GmbH

Rönt­gen­straße 10

D – 57439 Attendorn

Deutsch­land

Phone: +49 (0) 27 22.93 63.0

Email: info@asw-wekador.de

Web­site: www.asw-wekador.de

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

4. Cook­ies

The Inter­net pages of the ASW Andreas Heuel GmbH use cook­ies. Cook­ies are text files that are stored in a com­puter sys­tem via an Inter­net browser.

Many Inter­net sites and serv­ers 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 serv­ers can be assigned to the spe­cif­ic Inter­net browser in which the cook­ie was stored. This allows vis­ited Inter­net sites and serv­ers to dif­fer­en­ti­ate the indi­vidu­al browser of the dats sub­ject from oth­er Inter­net browsers that con­tain oth­er cook­ies. A spe­cif­ic Inter­net browser can be recog­nized and iden­ti­fied using the unique cook­ie ID.

Through the use of cook­ies, the ASW Andreas Heuel GmbH can provide the users of this web­site with more user-friendly ser­vices that would not be pos­sible without the cook­ie setting.

By means of a cook­ie, the inform­a­tion and offers on our web­site can be optim­ized with the user in mind. Cook­ies allow us, as pre­vi­ously men­tioned, to recog­nize our web­site users. The pur­pose of this recog­ni­tion is to make it easi­er for users to util­ize 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 taken over by the web­site, and the cook­ie is thus stored on the user­’s com­puter sys­tem. Anoth­er example is the cook­ie of a shop­ping cart in an online shop. The online store remem­bers the art­icles that a cus­tom­er 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­res­pond­ing set­ting of the Inter­net browser used, and may thus per­man­ently deny the set­ting of cook­ies. Fur­ther­more, already set cook­ies may be deleted at any time via an Inter­net browser or oth­er soft­ware pro­grams. This is pos­sible in all pop­u­lar Inter­net browsers. If the data sub­ject deac­tiv­ates the set­ting of cook­ies in the Inter­net browser used, not all func­tions of our web­site may be entirely usable.

5. Col­lec­tion of gen­er­al data and information

The web­site of the ASW Andreas Heuel GmbH col­lects a series of gen­er­al data and inform­a­tion when a data sub­ject or auto­mated sys­tem calls up the web­site. This gen­er­al data and inform­a­tion are stored in the serv­er log files. Col­lec­ted may be (1) the browser 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 reaches 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­tocol address (IP address), (7) the Inter­net ser­vice pro­vider of the access­ing sys­tem, and (8) any oth­er sim­il­ar data and inform­a­tion that may be used in the event of attacks on our inform­a­tion tech­no­logy systems.

When using these gen­er­al data and inform­a­tion, the ASW Andreas Heuel GmbH does not draw any con­clu­sions about the data sub­ject. Rather, this inform­a­tion is needed to (1) deliv­er the con­tent of our web­site cor­rectly, (2) optim­ize the con­tent of our web­site as well as its advert­ise­ment, (3) ensure the long-term viab­il­ity of our inform­a­tion tech­no­logy sys­tems and web­site tech­no­logy, and (4) provide law enforce­ment author­it­ies with the inform­a­tion neces­sary for crim­in­al pro­sec­u­tion in case of a cyber-attack. There­fore, the ASW Andreas Heuel GmbH ana­lyzes anonym­ously col­lec­ted data and inform­a­tion stat­ist­ic­ally, with the aim of increas­ing the data pro­tec­tion and data secur­ity of our enter­prise, and to ensure an optim­al level of pro­tec­tion for the per­son­al data we pro­cess. The anonym­ous data of the serv­er log files are stored sep­ar­ately from all per­son­al data provided by a data subject.

6. Regis­tra­tion on our website

The data sub­ject has the pos­sib­il­ity to register on the web­site of the con­trol­ler with the indic­a­tion of per­son­al data. Which per­son­al data are trans­mit­ted to the con­trol­ler is determ­ined by the respect­ive input mask used for the regis­tra­tion. The per­son­al data entered by the data sub­ject are col­lec­ted and stored exclus­ively for intern­al use by the con­trol­ler, and for his own pur­poses. The con­trol­ler may request trans­fer to one or more pro­cessors (e.g. a par­cel ser­vice) that also uses per­son­al data for an intern­al pur­pose which is attrib­ut­able to the controller.

By regis­ter­ing on the web­site of the con­trol­ler, the IP address—assigned by the Inter­net ser­vice pro­vider (ISP) and used by the data subject—date, and time of the regis­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 neces­sary, to make it pos­sible to invest­ig­ate com­mit­ted offenses. Inso­far, the stor­age of this data is neces­sary to secure the con­trol­ler. This data is not passed on to third parties unless there is a stat­utory oblig­a­tion to pass on the data, or if the trans­fer serves the aim of crim­in­al prosecution.

The regis­tra­tion of the data sub­ject, with the vol­un­tary indic­a­tion of per­son­al data, is inten­ded to enable the con­trol­ler to offer the data sub­ject con­tents or ser­vices that may only be offered to registered users due to the nature of the mat­ter in ques­tion. Registered per­sons are free to change the per­son­al data spe­cified dur­ing the regis­tra­tion at any time, or to have them com­pletely deleted from the data stock of the controller.

The data con­trol­ler shall, at any time, provide inform­a­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­trol­ler shall cor­rect or erase per­son­al data at the request or indic­a­tion of the data sub­ject, inso­far as there are no stat­utory stor­age oblig­a­tions. The entirety of the controller’s employ­ees are avail­able to the data sub­ject in this respect as con­tact persons.

7. Sub­scrip­tion to our newsletters

On the web­site of the ASW Andreas Heuel GmbH, users are giv­en the oppor­tun­ity to sub­scribe to our enter­prise’s news­let­ter. The input mask used for this pur­pose determ­ines what per­son­al data are trans­mit­ted, as well as when the news­let­ter is ordered from the controller.

The ASW Andreas Heuel GmbH informs its cus­tom­ers and busi­ness part­ners reg­u­larly by means of a news­let­ter about enter­prise offers. The enter­prise’s news­let­ter may only be received by the data sub­ject if (1) the data sub­ject has a val­id e‑mail address and (2) the data sub­ject registers for the news­let­ter ship­ping. A con­firm­a­tion e‑mail will be sent to the e‑mail address registered by a data sub­ject for the first time for news­let­ter ship­ping, for leg­al reas­ons, in the double opt-in pro­ced­ure. This con­firm­a­tion e‑mail is used to prove wheth­er the own­er of the e‑mail address as the data sub­ject is author­ized to receive the newsletter.

Dur­ing the regis­tra­tion for the news­let­ter, we also store the IP address of the com­puter sys­tem assigned by the Inter­net ser­vice pro­vider (ISP) and used by the data sub­ject at the time of the regis­tra­tion, as well as the date and time of the regis­tra­tion. The col­lec­tion of this data is neces­sary in order to under­stand the (pos­sible) mis­use of the e‑mail address of a data sub­ject at a later date, and it there­fore serves the aim of the leg­al pro­tec­tion of the controller.

The per­son­al data col­lec­ted as part of a regis­tra­tion for the news­let­ter will only be used to send our news­let­ter. In addi­tion, sub­scribers to the news­let­ter may be informed by e‑mail, as long as this is neces­sary for the oper­a­tion of the news­let­ter ser­vice or a regis­tra­tion in ques­tion, as this could be the case in the event of modi­fic­a­tions to the news­let­ter offer, or in the event of a change in tech­nic­al cir­cum­stances. There will be no trans­fer of per­son­al data col­lec­ted by the news­let­ter ser­vice to third parties. The sub­scrip­tion to our news­let­ter may be ter­min­ated 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 news­let­ter, may be revoked at any time. For the pur­pose of revoc­a­tion of con­sent, a cor­res­pond­ing link is found in each news­let­ter. It is also pos­sible to unsub­scribe from the news­let­ter at any time dir­ectly on the web­site of the con­trol­ler, or to com­mu­nic­ate this to the con­trol­ler in a dif­fer­ent way.

8. News­let­ter-Track­ing

The news­let­ter of the ASW Andreas Heuel GmbH con­tains so-called track­ing pixels. A track­ing pixel is a mini­ature graph­ic embed­ded in such e‑mails, which are sent in HTML format to enable log file record­ing and ana­lys­is. This allows a stat­ist­ic­al ana­lys­is of the suc­cess or fail­ure of online mar­ket­ing cam­paigns. Based on the embed­ded track­ing pixel, the ASW Andreas Heuel GmbH 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­lec­ted in the track­ing pixels con­tained in the news­let­ters are stored and ana­lyzed by the con­trol­ler in order to optim­ize the ship­ping of the news­let­ter, as well as to adapt the con­tent of future news­let­ters even bet­ter to the interests of the data sub­ject. These per­son­al data will not be passed on to third parties. Data sub­jects are at any time entitled to revoke the respect­ive sep­ar­ate declar­a­tion of con­sent issued by means of the double-opt-in pro­ced­ure. After a revoc­a­tion, these per­son­al data will be deleted by the con­trol­ler. The ASW Andreas Heuel GmbH auto­mat­ic­ally regards a with­draw­al from the receipt of the news­let­ter as a revocation.

9. Con­tact pos­sib­il­ity via the website

The web­site of the ASW Andreas Heuel GmbH con­tains inform­a­tion that enables a quick elec­tron­ic con­tact to our enter­prise, as well as dir­ect com­mu­nic­a­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­trol­ler 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­ic­ally stored. Such per­son­al data trans­mit­ted on a vol­un­tary basis by a data sub­ject to the data con­trol­ler are stored for the pur­pose of pro­cessing or con­tact­ing the data sub­ject. There is no trans­fer of this per­son­al data to third parties.

10. Com­ments func­tion in the blog on the website

The ASW Andreas Heuel GmbH offers users the pos­sib­il­ity to leave indi­vidu­al com­ments on indi­vidu­al blog con­tri­bu­tions on a blog, which is on the web­site of the con­trol­ler. A blog is a web-based, pub­licly-access­ible portal, through which one or more people called blog­gers or web-blog­gers may post art­icles or write down thoughts in so-called blo­g­posts. Blo­g­posts may usu­ally be com­men­ted 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 inform­a­tion on the date of the com­ment­ary and on the user­’s (pseud­onym) chosen by the data sub­ject. In addi­tion, the IP address assigned by the Inter­net ser­vice pro­vider (ISP) to the data sub­ject is also logged. This stor­age of the IP address takes place for secur­ity reas­ons, and in case the data sub­ject viol­ates the rights of third parties, or posts illeg­al con­tent through a giv­en com­ment. The stor­age of these per­son­al data is, there­fore, in the own interest of the data con­trol­ler, so that he can exculp­ate in the event of an infringe­ment. This col­lec­ted per­son­al data will not be passed to third parties, unless such a trans­fer is required by law or serves the aim of the defense of the data controller.

11. Sub­scrip­tion to com­ments in the blog on the website

The com­ments made in the blog of the ASW Andreas Heuel GmbH may be sub­scribed to by third parties. In par­tic­u­lar, there is the pos­sib­il­ity 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­trol­ler will send an auto­mat­ic con­firm­a­tion e‑mail to check the double opt-in pro­ced­ure as to wheth­er the own­er of the spe­cified e‑mail address decided in favor of this option. The option to sub­scribe to com­ments may be ter­min­ated at any time.

12. Routine eras­ure and block­ing of per­son­al data

The data con­trol­ler shall pro­cess and store the per­son­al data of the data sub­ject only for the peri­od neces­sary to achieve the pur­pose of stor­age, or as far as this is gran­ted by the European legis­lat­or or oth­er legis­lat­ors in laws or reg­u­la­tions to which the con­trol­ler is sub­ject to.

If the stor­age pur­pose is not applic­able, or if a stor­age peri­od pre­scribed by the European legis­lat­or or anoth­er com­pet­ent legis­lat­or expires, the per­son­al data are routinely blocked or erased in accord­ance with leg­al requirements.

13. Rights of the data subject

  • a) Right of confirmation

    Each data sub­ject shall have the right gran­ted by the European legis­lat­or to obtain from the con­trol­ler the con­firm­a­tion as to wheth­er or not per­son­al data con­cern­ing him or her are being pro­cessed. If a data sub­ject wishes to avail him­self of this right of con­firm­a­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 gran­ted by the European legis­lat­or to obtain from the con­trol­ler free inform­a­tion about his or her per­son­al data stored at any time and a copy of this inform­a­tion. Fur­ther­more, the European dir­ect­ives and reg­u­la­tions grant the data sub­ject access to the fol­low­ing information:

    • the pur­poses of the processing;
    • the cat­egor­ies of per­son­al data concerned;
    • the recip­i­ents or cat­egor­ies 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­sible, the envis­aged peri­od for which the per­son­al data will be stored, or, if not pos­sible, the cri­ter­ia used to determ­ine that period;
    • the exist­ence of the right to request from the con­trol­ler rec­ti­fic­a­tion or eras­ure of per­son­al data, or restric­tion of pro­cessing of per­son­al data con­cern­ing the data sub­ject, or to object to such processing;
    • the exist­ence of the right to lodge a com­plaint with a super­vis­ory authority;
    • where the per­son­al data are not col­lec­ted from the data sub­ject, any avail­able inform­a­tion as to their source;
    • the exist­ence of auto­mated decision-mak­ing, includ­ing pro­fil­ing, referred to in Art­icle 22(1) and (4) of the GDPR and, at least in those cases, mean­ing­ful inform­a­tion about the logic involved, as well as the sig­ni­fic­ance and envis­aged con­sequences of such pro­cessing for the data subject.

    Fur­ther­more, the data sub­ject shall have a right to obtain inform­a­tion as to wheth­er per­son­al data are trans­ferred to a third coun­try or to an inter­na­tion­al organ­isa­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 wishes 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 gran­ted by the European legis­lat­or to obtain from the con­trol­ler without undue delay the rec­ti­fic­a­tion of inac­cur­ate per­son­al data con­cern­ing him or her. Tak­ing into account the pur­poses of the pro­cessing, the data sub­ject shall have the right to have incom­plete per­son­al data com­pleted, includ­ing by means of provid­ing a sup­ple­ment­ary statement.

    If a data sub­ject wishes to exer­cise this right to rec­ti­fic­a­tion, he or she may, at any time, con­tact any employ­ee of the controller.

  • d) Right to eras­ure (Right to be forgotten)

    Each data sub­ject shall have the right gran­ted by the European legis­lat­or to obtain from the con­trol­ler the eras­ure of per­son­al data con­cern­ing him or her without undue delay, and the con­trol­ler shall have the oblig­a­tion to erase per­son­al data without undue delay where one of the fol­low­ing grounds applies, as long as the pro­cessing is not necessary:

    • The per­son­al data are no longer neces­sary in rela­tion to the pur­poses for which they were col­lec­ted or oth­er­wise processed.
    • The data sub­ject with­draws con­sent to which the pro­cessing is based accord­ing to point (a) of Art­icle 6(1) of the GDPR, or point (a) of Art­icle 9(2) of the GDPR, and where there is no oth­er leg­al ground for the processing.
    • The data sub­ject objects to the pro­cessing pur­su­ant to Art­icle 21(1) of the GDPR and there are no over­rid­ing legit­im­ate grounds for the pro­cessing, or the data sub­ject objects to the pro­cessing pur­su­ant to Art­icle 21(2) of the GDPR.
    • The per­son­al data have been unlaw­fully processed.
    • The per­son­al data must be erased for com­pli­ance with a leg­al oblig­a­tion in Uni­on or Mem­ber State law to which the con­trol­ler is subject.
    • The per­son­al data have been col­lec­ted in rela­tion to the offer of inform­a­tion soci­ety ser­vices referred to in Art­icle 8(1) of the GDPR.

    If one of the afore­men­tioned reas­ons applies, and a data sub­ject wishes to request the eras­ure of per­son­al data stored by the ASW Andreas Heuel GmbH, he or she may, at any time, con­tact any employ­ee of the con­trol­ler. An employ­ee of ASW Andreas Heuel GmbH shall promptly ensure that the eras­ure request is com­plied with immediately.

    Where the con­trol­ler has made per­son­al data pub­lic and is obliged pur­su­ant to Art­icle 17(1) to erase the per­son­al data, the con­trol­ler, tak­ing account of avail­able tech­no­logy and the cost of imple­ment­a­tion, shall take reas­on­able steps, includ­ing tech­nic­al meas­ures, to inform oth­er con­trol­lers pro­cessing the per­son­al data that the data sub­ject has reques­ted eras­ure by such con­trol­lers of any links to, or copy or rep­lic­a­tion of, those per­son­al data, as far as pro­cessing is not required. An employ­ees of the ASW Andreas Heuel GmbH will arrange the neces­sary meas­ures in indi­vidu­al cases.

  • e) Right of restric­tion of processing

    Each data sub­ject shall have the right gran­ted by the European legis­lat­or to obtain from the con­trol­ler restric­tion of pro­cessing where one of the fol­low­ing applies:

    • The accur­acy of the per­son­al data is con­tested by the data sub­ject, for a peri­od enabling the con­trol­ler to veri­fy the accur­acy of the per­son­al data.
    • The pro­cessing is unlaw­ful and the data sub­ject opposes the eras­ure of the per­son­al data and requests instead the restric­tion of their use instead.
    • The con­trol­ler no longer needs the per­son­al data for the pur­poses of the pro­cessing, but they are required by the data sub­ject for the estab­lish­ment, exer­cise or defence of leg­al claims.
    • The data sub­ject has objec­ted to pro­cessing pur­su­ant to Art­icle 21(1) of the GDPR pending the veri­fic­a­tion wheth­er the legit­im­ate grounds of the con­trol­ler over­ride those of the data subject.

    If one of the afore­men­tioned con­di­tions is met, and a data sub­ject wishes to request the restric­tion of the pro­cessing of per­son­al data stored by the ASW Andreas Heuel GmbH, he or she may at any time con­tact any employ­ee of the con­trol­ler. The employ­ee of the ASW Andreas Heuel GmbH will arrange the restric­tion of the processing.

  • f) Right to data portability

    Each data sub­ject shall have the right gran­ted by the European legis­lat­or, to receive the per­son­al data con­cern­ing him or her, which was provided to a con­trol­ler, in a struc­tured, com­monly used and machine-read­able format. He or she shall have the right to trans­mit those data to anoth­er con­trol­ler without hindrance from the con­trol­ler to which the per­son­al data have been provided, as long as the pro­cessing is based on con­sent pur­su­ant to point (a) of Art­icle 6(1) of the GDPR or point (a) of Art­icle 9(2) of the GDPR, or on a con­tract pur­su­ant to point (b) of Art­icle 6(1) of the GDPR, and the pro­cessing is car­ried out by auto­mated means, as long as the pro­cessing is not neces­sary for the per­form­ance of a task car­ried out in the pub­lic interest or in the exer­cise of offi­cial author­ity ves­ted in the controller.

    Fur­ther­more, in exer­cising his or her right to data port­ab­il­ity pur­su­ant to Art­icle 20(1) of the GDPR, the data sub­ject shall have the right to have per­son­al data trans­mit­ted dir­ectly from one con­trol­ler to anoth­er, where tech­nic­ally feas­ible and when doing so does not adversely affect the rights and freedoms of others.

    In order to assert the right to data port­ab­il­ity, the data sub­ject may at any time con­tact any employ­ee of the ASW Andreas Heuel GmbH.

  • g) Right to object

    Each data sub­ject shall have the right gran­ted by the European legis­lat­or to object, on grounds relat­ing to his or her par­tic­u­lar situ­ation, at any time, to pro­cessing of per­son­al data con­cern­ing him or her, which is based on point (e) or (f) of Art­icle 6(1) of the GDPR. This also applies to pro­fil­ing based on these provisions.

    The ASW Andreas Heuel GmbH shall no longer pro­cess the per­son­al data in the event of the objec­tion, unless we can demon­strate com­pel­ling legit­im­ate grounds for the pro­cessing which over­ride the interests, rights and freedoms of the data sub­ject, or for the estab­lish­ment, exer­cise or defence of leg­al claims.

    If the ASW Andreas Heuel GmbH pro­cesses per­son­al data for dir­ect mar­ket­ing pur­poses, the data sub­ject shall have the right to object at any time to pro­cessing 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 related to such dir­ect mar­ket­ing. If the data sub­ject objects to the ASW Andreas Heuel GmbH to the pro­cessing for dir­ect mar­ket­ing pur­poses, the ASW Andreas Heuel GmbH will no longer pro­cess 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 situ­ation, to object to pro­cessing of per­son­al data con­cern­ing him or her by the ASW Andreas Heuel GmbH for sci­entif­ic or his­tor­ic­al research pur­poses, or for stat­ist­ic­al pur­poses pur­su­ant to Art­icle 89(1) of the GDPR, unless the pro­cessing is neces­sary for the per­form­ance of a task car­ried out for reas­ons 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 ASW Andreas Heuel GmbH. In addi­tion, the data sub­ject is free in the con­text of the use of inform­a­tion soci­ety ser­vices, and not­with­stand­ing Dir­ect­ive 2002/58/EC, to use his or her right to object by auto­mated means using tech­nic­al specifications.

  • h) Auto­mated indi­vidu­al decision-mak­ing, includ­ing profiling

    Each data sub­ject shall have the right gran­ted by the European legis­lat­or not to be sub­ject to a decision based solely on auto­mated pro­cessing, includ­ing pro­fil­ing, which pro­duces leg­al effects con­cern­ing him or her, or sim­il­arly sig­ni­fic­antly affects him or her, as long as the decision (1) is not is neces­sary for enter­ing into, or the per­form­ance of, a con­tract between the data sub­ject and a data con­trol­ler, or (2) is not author­ised by Uni­on or Mem­ber State law to which the con­trol­ler is sub­ject and which also lays down suit­able meas­ures to safe­guard the data sub­ject’s rights and freedoms and legit­im­ate interests, or (3) is not based on the data sub­ject’s expli­cit consent.

    If the decision (1) is neces­sary for enter­ing into, or the per­form­ance of, a con­tract between the data sub­ject and a data con­trol­ler, or (2) it is based on the data sub­ject’s expli­cit con­sent, the ASW Andreas Heuel GmbH shall imple­ment suit­able meas­ures to safe­guard the data sub­ject’s rights and freedoms and legit­im­ate interests, at least the right to obtain human inter­ven­tion on the part of the con­trol­ler, to express his or her point of view and con­test the decision.

    If the data sub­ject wishes to exer­cise the rights con­cern­ing auto­mated indi­vidu­al decision-mak­ing, he or she may, at any time, con­tact any employ­ee of the ASW Andreas Heuel GmbH.

  • i) Right to with­draw data pro­tec­tion consent

    Each data sub­ject shall have the right gran­ted by the European legis­lat­or to with­draw his or her con­sent to pro­cessing of his or her per­son­al data at any time.

    f the data sub­ject wishes 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 ASW Andreas Heuel GmbH.

14. Data pro­tec­tion for applic­a­tions and the applic­a­tion procedures

The data con­trol­ler shall col­lect and pro­cess the per­son­al data of applic­ants for the pur­pose of the pro­cessing of the applic­a­tion pro­ced­ure. The pro­cessing may also be car­ried out elec­tron­ic­ally. This is the case, in par­tic­u­lar, if an applic­ant sub­mits cor­res­pond­ing applic­a­tion doc­u­ments by e‑mail or by means of a web form on the web­site to the con­trol­ler. If the data con­trol­ler con­cludes an employ­ment con­tract with an applic­ant, the sub­mit­ted data will be stored for the pur­pose of pro­cessing the employ­ment rela­tion­ship in com­pli­ance with leg­al require­ments. If no employ­ment con­tract is con­cluded with the applic­ant by the con­trol­ler, the applic­a­tion doc­u­ments shall be auto­mat­ic­ally erased two months after noti­fic­a­tion of the refus­al decision, provided that no oth­er legit­im­ate interests of the con­trol­ler are opposed to the eras­ure. Oth­er legit­im­ate interest in this rela­tion is, e.g. a bur­den of proof in a pro­ced­ure under the Gen­er­al Equal Treat­ment Act (AGG).

15. Data Pro­tec­tion pro­vi­sions about the applic­a­tion and use of AddThis

On this web­site, the data con­trol­ler has integ­rated com­pon­ents of the enter­prise AddThis. AddThis is a so-called book­mark­ing pro­vider. 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­pon­ent 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 inform­a­tion of the oper­at­ing enter­prise, over 20 bil­lion times a year.

The oper­at­ing com­pany of AddThis is AddThis, Inc. 1595 Spring Hill Road, Suite 300, Vienna, VA 22182, United States.

By call­ing up one of the indi­vidu­al pages of the web­site, which is oper­ated by the con­trol­ler, and on which an AddThis com­pon­ent has been integ­rated, the Inter­net browser of the data sub­ject is auto­mat­ic­ally promp­ted by the respect­ive AddThis com­pon­ent to down­load data from the web­site www.addthis.com. With­in the frame­work of this tech­nic­al pro­ced­ure, AddThis is informed of the vis­it and the spe­cif­ic indi­vidu­al page of this web­site that was used by the data sub­ject with the help of inform­a­tion tech­no­logy. In addi­tion, AddThis is informed about the IP address of the com­puter sys­tem assigned by the Inter­net ser­vice pro­vider (ISP) and used by the data sub­ject, the browser 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 anonym­ous user pro­files. The data and inform­a­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­prises, to con­tact vis­it­ors of the web pages of the con­trol­ler with per­son­al­ized and interest-based advertising.

AddThis dis­plays per­son­al­ized and interest-based advert­ising on the basis of a cook­ie set by the enter­prise. This cook­ie ana­lyzes the indi­vidu­al surf­ing beha­vi­or of the com­puter sys­tem used by the data sub­ject. The cook­ie saves the com­puter-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­res­pond­ing set­ting of the Inter­net browser used, and thus per­man­ently deny the set­ting of cook­ies. Such a set­ting of the Inter­net browser used would also pre­vent AddThis from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. Cook­ies may also be deleted by AddThis at any time via an Inter­net browser or oth­er soft­ware programs.

The data sub­ject also has the pos­sib­il­ity of object­ing per­man­ently to the pro­cessing 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 inform­a­tion tech­no­logy 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data subject.

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

16. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Adobe Ana­lyt­ics (Omni­ture) / Adobe mar­ket­ing cloud

On this web­site, the con­trol­ler has integ­rated com­pon­ents of the enter­prise Adobe. Adobe Ana­lyt­ics (Omni­ture) and Adobe Mar­ket­ing Cloud (here­in­after referred to as “Omni­ture”) is an instru­ment that allows for more effi­cient online mar­ket­ing and web ana­lys­is. Omni­ture is part of Adobe Mar­ket­ing Cloud. Adobe Mar­ket­ing Cloud enables real-time ana­lys­is of vis­it­or flows on Inter­net sites. The real-time ana­lys­is includes pro­ject reports and allows an ad-hoc ana­lys­is of site vis­it­ors. Cus­tom­er inter­ac­tions are presen­ted in such a way as to give the con­trol­ler a bet­ter over­view of users’ online activ­it­ies of this web­site by dis­play­ing the data in simple and inter­act­ive dash­boards and con­vert­ing them into reports. This enables the con­trol­ler to obtain inform­a­tion in real-time and to identi­fy prob­lems that occur more quickly.

The oper­at­ing com­pany for these ser­vices is Adobe Sys­tems Soft­ware Ire­land Lim­ited, 4–6 River­walk, City­w­est Busi­ness Cam­pus, Dub­lin 24, Repub­lic of Ireland.

Omni­ture sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject (cook­ies have already been explained in advance, which may be read above). The con­trol­ler ensures that the track­ing data trans­ferred to the Adobe data cen­ter is anonym­ized pri­or to geo­loca­tion. The anonym­iz­a­tion is imple­men­ted by repla­cing the last part of the IP address. The con­trol­ler has made serv­er-sided set­tings, which are used to anonym­ize the IP address of the data sub­ject pri­or to pro­cessing for geo­loca­tion and range meas­ure­ment. Adobe will use the data and inform­a­tion obtained via our web­site to ana­lyze the user beha­vi­or of the data sub­ject on behalf of the con­trol­ler. Adobe will also use the data to cre­ate reports on user activ­ity on our behalf, as well as provide oth­er ser­vices to our enter­prise related to the use of our web­site. The IP address of the data sub­ject is not merged with oth­er per­son­al data by Adobe.

As stated above, 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­res­pond­ing set­ting of the Inter­net browser used, and thus per­man­ently deny the set­ting of cook­ies. Such a set­ting of the Inter­net browser used would also pre­vent Omni­ture from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. Cook­ies may also be deleted by Omni­ture at any time via an Inter­net browser or oth­er soft­ware programs.

The data sub­ject also has the pos­sib­il­ity of object­ing to and pre­vent­ing the col­lec­tion of data gen­er­ated by the Adobe cook­ie on the use of this web­site and the pro­cessing of this data by Adobe. For this pur­pose, the data sub­ject must click on the opt-out but­ton under the link http://www.adobe.com/de/privacy/opt-out.html, which sets an opt-out cook­ie. The opt-out cook­ie used for this pur­pose is placed on the inform­a­tion tech­no­logy 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of Adobe may be accessed under http://www.adobe.com/privacy.html.

17. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Affilinet

On this web­site, the con­trol­ler has integ­rated com­pon­ents of the enter­prise Affilinet. Affilinet 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­bu­tion, which allows com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to show advert­ising, which will be paid mostly through click or sale com­mis­sions, on third-party Inter­net sites that are also called affil­i­ates or pub­lish­ers. The Mer­chant provides through the affil­i­ate net­work an advert­ising medi­um, such as an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on its own Inter­net pages or via oth­er chan­nels such as keyword advert­ising or e‑mail marketing.

The oper­at­ing com­pany of Affilinet is the Affilinet GmbH, Sap­poro arc 6–8, 80637 Munich, Germany.

Affilinet sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The track­ing cook­ie by Affilinet stores no per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of this data stor­age is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed through the affil­i­ate net­work, that is Affilinet.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the Inter­net browser used and, thus, per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Affilinet from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Affilinet may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of Affilinet may be accessed under https://www.affili.net/uk/footeritem/privacy-policy.

18. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Econda

On this web­site, the con­trol­ler has integ­rated com­pon­ents of the enter­prise Econda. Econda is a web ana­lyt­ics ser­vice. Web ana­lyt­ics is the col­lec­tion, gath­er­ing and ana­lys­is of data about the beha­vi­or of vis­it­ors of the web­sites. A web ana­lys­is ser­vice cap­tures, among oth­er things, data per­tain­ing to which web­site a per­son has arrived on via anoth­er web­site (the so-called refer­rer), which sub-site of the web­site was vis­ited, or how often and for what dur­a­tion a sub-site was viewed. Web ana­lyt­ics are mainly used for the optim­iz­a­tion of a web­site in order to carry out a cost-bene­fit ana­lys­is of Inter­net advertising.

The oper­at­ing com­pany of Econda is Econda GmbH, Eis­en­lohr­str. 43, 76135 Karls­ruhe, Germany.

Econda sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. With each call up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which an Econda com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to trans­mit data for mar­ket­ing and optim­isa­tion pur­poses to Econda through the Econda com­pon­ent. Dur­ing the course of this tech­nic­al pro­ced­ure, Econda obtains data that is used to cre­ate pseud­onym­ous user pro­files. The user pro­files cre­ated in such a way are used to ana­lyze the beha­vi­or of the data sub­ject who has accessed the web­site of the con­trol­ler and are eval­u­ated with the aim of improv­ing and optim­iz­ing the web­site. The data col­lec­ted via the Econda com­pon­ent is not used to identi­fy the data sub­ject without first obtain­ing sep­ar­ate and expli­cit con­sent from the data sub­ject. These data will not be merged with per­son­al data or with oth­er data that con­tain the same pseudonym.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the Inter­net browser used, and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Econda from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already set by Econda may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by the Econda cook­ie as well as the pro­cessing of these data by Econda and the chance to pre­clude any such. For this pur­pose, the data sub­ject must press the ‘sub­mit’ but­ton under the link http://www.econda.com/econda/enterprise/data-protection/revocation-of-data-storage/, which sets the opt-out cook­ie. The opt-out cook­ie used for this pur­pose is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies are deleted from 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of Econda may be accessed under http://www.econda.com/econda/enterprise/data-protection/data-privacy-statement/.

19. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Etracker

On this web­site, the con­trol­ler has integ­rated com­pon­ents of the enter­prise Etrack­er. Etrack­er is a Web ana­lyt­ics ser­vice. Web ana­lyt­ics is the col­lec­tion, gath­er­ing and ana­lys­is of data about the beha­vi­or of vis­it­ors to web­sites. A web ana­lys­is ser­vice cap­tures, among oth­er things, data about from which web­site a per­son has arrived on anoth­er web­site (the so-called refer­rer), which sub-sites of the web­site were vis­ited or how often and for what dur­a­tion a sub-site was viewed. Web ana­lyt­ics are mainly used for the optim­iz­a­tion of a web­site and in order to carry out a cost-bene­fit ana­lys­is of Inter­net advertising.

The oper­at­ing com­pany of Etrack­er is Etrack­er GmbH, Erste Brunnen­straße 1, 20459 Ham­burg, Germany.

Etrack­er sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and into which an Etrack­er com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to trans­mit data for mar­ket­ing and optim­isa­tion pur­poses to Etrack­er through the Etrack­er com­pon­ent. Dur­ing the course of this tech­nic­al pro­ced­ure Etrack­er receives data that is used to cre­ate pseud­onym­ous user pro­files. The user pro­files cre­ated in such a way are used for the ana­lys­is of the beha­viour of the data sub­ject, which has accessed Inter­net page of the con­trol­ler and are eval­u­ated with the aim of improv­ing and optim­iz­ing the web­site. The data col­lec­ted through the Etrack­er com­pon­ent is not used without first obtain­ing of a sep­ar­ate and expli­cit con­sent of the data sub­ject to identi­fy the data sub­ject. This data is not merged with per­son­al data or oth­er data which con­tain the same pseudonym.

The data sub­ject may, as stated above, at any time pre­vent the set­ting of cook­ies through our web­site by means of a cor­res­pond­ing adjust­ment of the Inter­net browser used and, per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Etrack­er from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already set by Etrack­er may be deleted at any time via a Web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by the Etrack­er cook­ie as well as the pro­cessing of these data by Etrack­er and the chance to pre­clude such. For this pur­pose, the data sub­ject must press the ‘cook­ie-set’ but­ton under the link http://www.etracker.de/privacy?sid=58e31c864e66848984dfc79b8f6b51a9&id=privacy&et=V23Jbb&languageId=2, which sets an opt-out cook­ie. The opt-out cook­ie used for this pur­pose is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies are deleted from 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of Etrack­er may be accessed under https://www.etracker.com/de/datenschutz.html.

20. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Facebook

On this web­site, the con­trol­ler has integ­rated com­pon­ents 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­munity, which usu­ally allows users to com­mu­nic­ate 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 exper­i­ences, or enable the Inter­net com­munity to provide per­son­al or busi­ness-related inform­a­tion. Face­book allows social net­work users to include the cre­ation of private pro­files, upload pho­tos, and net­work through friend requests.

The oper­at­ing com­pany of Face­book is Face­book, Inc., 1 Hack­er Way, Menlo Park, CA 94025, United States. If a per­son lives out­side of the United States or Canada, the con­trol­ler is the Face­book Ire­land Ltd., 4 Grand Canal Square, Grand Canal Har­bour, Dub­lin 2, Ireland.

With each call-up to one of the indi­vidu­al pages of this Inter­net web­site, which is oper­ated by the con­trol­ler and into which a Face­book com­pon­ent (Face­book plug-ins) was integ­rated, the web browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to down­load dis­play of the cor­res­pond­ing Face­book com­pon­ent from Face­book through the Face­book com­pon­ent. An over­view of all the Face­book Plug-ins may be accessed under https://developers.facebook.com/docs/plugins/. Dur­ing the course of this tech­nic­al pro­ced­ure, Face­book is made aware of what spe­cif­ic sub-site of our web­site was vis­ited 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 dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-site of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Face­book com­pon­ent and asso­ci­ated with the respect­ive Face­book account of the data sub­ject. If the data sub­ject clicks on one of the Face­book but­tons integ­rated into our web­site, e.g. the “Like” but­ton, or if the data sub­ject sub­mits a com­ment, then Face­book matches this inform­a­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­pon­ent, inform­a­tion about a vis­it to our web­site by the data sub­ject, whenev­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 wheth­er the data sub­ject clicks on the Face­book com­pon­ent or not. If such a trans­mis­sion of inform­a­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 guideline pub­lished by Face­book, which is avail­able at https://facebook.com/about/privacy/, provides inform­a­tion about the col­lec­tion, pro­cessing 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­vacy of the data sub­ject. In addi­tion, dif­fer­ent con­fig­ur­a­tion options are made avail­able to allow the elim­in­a­tion of data trans­mis­sion to Face­book. These applic­a­tions may be used by the data sub­ject to elim­in­ate a data trans­mis­sion to Facebook.

21. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Flattr

On this web­site, the con­trol­ler has integ­rated com­pon­ents of the enter­prise Flat­tr. Flat­tr is a social pay­ment ser­vice from Sweden, which allows the user to dis­trib­ute dona­tions to media pro­viders on the Inter­net through depos­its on a cred­it account and by the pro­vi­sion of a monthly budget. The users of the ser­vice may instruct Flat­tr, by click­ing on a Flat­tr but­ton that is integ­rated on the web­site of a media pro­vider, to dis­trib­ute its fixed monthly budget to this media provider.

The oper­at­ing com­pany of Flat­tr is Flat­tr AB, Box 4111, 203 12 Malmo, Sweden.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and into which a Flat­tr com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to down­load a dis­play of the cor­res­pond­ing Flat­tr com­pon­ent from Flat­tr through the Flat­tr com­pon­ent. Dur­ing the course of this tech­nic­al pro­ced­ure, Flat­tr is made aware of what spe­cif­ic sub-sites of our web­site are vis­ited by the data subject.

If the data sub­ject is logged in at the same time at Flat­tr, Flat­tr detects with each call-up to our web­site by the data subject—and for the entire dur­a­tion of their stay on our Inter­net site—what spe­cif­ic sub-site of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted by the Flat­tr com­pon­ent and asso­ci­ated with the respect­ive Flat­tr account of the data sub­ject. If the data sub­ject clicks on the Flat­tr but­ton integ­rated into our web­site, then this inform­a­tion is trans­mit­ted to Flat­tr for billing pur­poses. The data sub­ject has already agreed to the trans­mis­sion of such inform­a­tion towards Flattr.

Fur­ther inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Flat­tr may be retrieved under https://flattr.com/privacy.

22. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of func­tions of the Amazon Part­ner program

On this web­site, the con­trol­ler has integ­rated Amazon com­pon­ents as a par­ti­cipant in the Amazon part­ner pro­gram. The Amazon com­pon­ents were cre­ated by Amazon with the aim to medi­ate cus­tom­ers through advert­ise­ments on vari­ous web­sites of the Amazon 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 Amazon com­pon­ents, the con­trol­ler may gen­er­ate advert­ising revenue.

The oper­at­ing com­pany of this Amazon com­pon­ent is Amazon EU S.à.r.l, 5 Rue Plaet­is, L‑2338 Lux­em­bourg, Luxembourg.

Amazon sets a cook­ie the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. With each single call-up to one of the indi­vidu­al pages of this Inter­net web­site, which is oper­ated by the con­trol­ler and in which an Amazon com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject will auto­mat­ic­ally sub­mit data for the pur­pose of online advert­ising and the set­tle­ment of com­mis­sions to Amazon through the respect­ive Amazon com­pon­ent. Dur­ing the course of this tech­nic­al pro­ced­ure, Amazon receives per­son­al inform­a­tion that is used to trace the ori­gin of orders from Amazon, and as a res­ult, to allow the account­ing of a com­mis­sion. Among oth­er things, Amazon 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 stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used, and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Amazon from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Amazon may be deleted at any­time via a web browser or oth­er soft­ware programs.

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

23. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of func­tions per­tain­ing to the col­lec­tion soci­ety WORT (VG WORT)

On this web­site, the con­trol­ler has integ­rated a track­ing pixel. A track­ing pixel is a thumb­nail image that is embed­ded in web pages to enable a log file record­ing and a log file ana­lys­is so that a stat­ist­ic­al ana­lys­is may be per­formed. The integ­rated track­ing pixels serve the Scal­able Cent­ral Meas­ure­ment Sys­tem (SZMS) of the col­lect­ing soci­ety WORT (VG Wort).

The Scal­able Cent­ral Meas­ure­ment Sys­tem is oper­ated by INFOn­line GmbH, For­um Bonn Nord, Brühler Str. 9, 53119 Bonn.

The Scal­able Cent­ral Meas­ure­ment Sys­tem is used to determ­ine with stat­ist­ic­al key fig­ures, the prob­ab­il­ity of the copy­ing of texts. The embed­ded track­ing pixel ensures that the col­lect­ing soci­ety WORT may detect wheth­er, when, and how vari­ous users (includ­ing the data sub­ject) opened our web­site and what con­tent was retrieved.

The data obtained using the Scal­able Cent­ral Meas­ure­ment Sys­tem is col­lec­ted anonym­ously. To cap­ture the traffic, either a so-called ses­sion cook­ie is cre­ated for the pur­pose of recog­ni­tion of the users of a web­site, that is a sig­na­ture, which con­sists of vari­ous auto­mat­ic­ally trans­mit­ted inform­a­tion, or altern­at­ive meth­ods are used. The IP address of the Inter­net con­nec­tion used by the data sub­ject is col­lec­ted only in anonymised form and pro­cessed. The data sub­ject is not iden­ti­fied at any time.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus con­tra­dict the set­ting of cook­ies per­man­ently. Such an adjust­ment to the Inter­net browser used would also pre­vent VG Wort from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by VG Wort may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data gen­er­ated by VG Wort related to the use of this web­site, as well as to the pro­cessing of these data through VG Wort 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 http://optout.ioam.de, which sets an opt-out cook­ie. The opt-out cook­ie used for this pur­pose is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies are deleted 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of INFOn­line may be accessed under https://www.infonline.de/datenschutz/.

24. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Getty Images Photos

On this web­site, the con­trol­ler has integ­rated com­pon­ents of the enter­prise Getty Images. Getty Images is an Amer­ic­an pic­ture agency. A pic­ture agency is an enter­prise which provides images and oth­er image mater­i­al on the mar­ket. Gen­er­ally, pic­ture agen­cies mar­ket pho­to­graphs, illus­tra­tions and foot­age. A pic­ture agency licenses dif­fer­ent cus­tom­ers, in par­tic­u­lar Inter­net web­site oper­at­ors, edit­ors of print and tele­vi­sion media and advert­ising agen­cies, the images used by them.

The oper­at­ing com­pany of the Getty Images com­pon­ents is Getty Images Inter­na­tion­al, 1st floor, The Her­bert Build­ing, The Park, Car­rick­mines, Dub­lin 18, Ireland.

Getty Images allows the embed­ding of stock images (where pos­sibly free of charge). Embed­ding is the inclu­sion or integ­ra­tion of any spe­cif­ic for­eign con­tent, e.g. text, video or image data provided by a for­eign web­site, and then appears on the own web­site. A so-called embed­ded code is used to embed. An embed­ded code is an HTML code that is integ­rated into a web­site from a web­site own­er. When an embed­ded code is integ­rated by a web­site own­er, the extern­al con­tent of the oth­er web­site is dis­played by default imme­di­ately, as long as a web­site is vis­ited. To dis­play third-party con­tent, the extern­al con­tent is loaded dir­ectly from the oth­er Inter­net site. Getty Images provides fur­ther inform­a­tion about the embed­ded of con­tent under http://www.gettyimages.de/resources/embed.

Through the tech­nic­al imple­ment­a­tion of the embed­ded code, which allows the image dis­play of the images of Getty Images, the IP address of the Inter­net con­nec­tion, through which the data sub­ject accesses our web­site, is trans­mit­ted to Getty Images. Fur­ther, Getty Images col­lects our web­site, browser type, browser lan­guage, and time and length of access. In addi­tion, Getty Images may col­lect nav­ig­a­tion inform­a­tion, which is inform­a­tion about which of our sub­pages have been vis­ited by the data sub­ject and which links have been clicked on, as well as oth­er inter­ac­tions that the data sub­ject has car­ried out when vis­it­ing our web­site. This data may be stored and ana­lyzed by Getty Images.

Fur­ther inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Getty Images may be retrieved under http://www.gettyimages.de/enterprise/privacy-policy.

25. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Google AdSense

On this web­site, the con­trol­ler has integ­rated Google AdSense. Google AdSense is an online ser­vice which allows the place­ment of advert­ising on third-party sites. Google AdSense is based on an algorithm that selects advert­ise­ments dis­played on third-party sites to match with the con­tent of the respect­ive third-party site. Google AdSense allows an interest-based tar­get­ing of the Inter­net user, which is imple­men­ted by means of gen­er­at­ing indi­vidu­al user profiles.

The oper­at­ing com­pany of Google’s AdSense com­pon­ent is Alpha­bet Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, United States.

The pur­pose of Google’s AdSense com­pon­ent is the integ­ra­tion of advert­ise­ments on our web­site. Google AdSense places a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­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­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and into which a Google AdSense com­pon­ent is integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject will auto­mat­ic­ally sub­mit data through the Google AdSense com­pon­ent for the pur­pose of online advert­ising and the set­tle­ment of com­mis­sions to Alpha­bet Inc. Dur­ing the course of this tech­nic­al pro­ced­ure, the enter­prise Alpha­bet Inc. gains know­ledge 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­it­ors and clicks and sub­sequently cre­ate com­mis­sion settlements.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Alpha­bet Inc. from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. Addi­tion­ally, cook­ies already in use by Alpha­bet Inc. may be deleted at any time via a web browser or oth­er soft­ware programs.

Fur­ther­more, Google AdSense also uses so-called track­ing pixels. A track­ing pixel is a mini­ature graph­ic that is embed­ded in web pages to enable a log file record­ing and a log file ana­lys­is through which a stat­ist­ic­al ana­lys­is may be per­formed. Based on the embed­ded track­ing pixels, Alpha­bet Inc. is able to determ­ine 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 pixels serve, inter alia, to ana­lyze the flow of vis­it­ors on a website.

Through Google AdSense, per­son­al data and information—which also includes the IP address, and is neces­sary for the col­lec­tion and account­ing of the dis­played advertisements—is trans­mit­ted to Alpha­bet Inc. in the United States of Amer­ica. These per­son­al data will be stored and pro­cessed in the United States of Amer­ica. The Alpha­bet Inc. may dis­close the col­lec­ted per­son­al data through this tech­nic­al pro­ced­ure to third parties.

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

26. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Google Ana­lyt­ics (with anonym­iz­a­tion function)

On this web­site, the con­trol­ler has integ­rated the com­pon­ent of Google Ana­lyt­ics (with the anonym­izer 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 ana­lys­is of data about the beha­vi­or of vis­it­ors to web­sites. A web ana­lys­is 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­ited, or how often and for what dur­a­tion a sub-page was viewed. Web ana­lyt­ics are mainly used for the optim­iz­a­tion of a web­site and in order to carry out a cost-bene­fit ana­lys­is of Inter­net advertising.

The oper­at­or of the Google Ana­lyt­ics com­pon­ent is Google Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, United States.

For the web ana­lyt­ics through Google Ana­lyt­ics the con­trol­ler uses the applic­a­tion “_gat. _anonymizeIp”. By means of this applic­a­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 European Uni­on or anoth­er Con­tract­ing State to the Agree­ment on the European Eco­nom­ic Area.

The pur­pose of the Google Ana­lyt­ics com­pon­ent is to ana­lyze the traffic on our web­site. Google uses the col­lec­ted data and inform­a­tion, inter alia, to eval­u­ate the use of our web­site and to provide online reports, which show the activ­it­ies on our web­sites, and to provide 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 inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­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­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and into which a Google Ana­lyt­ics com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject will auto­mat­ic­ally sub­mit data through the Google Ana­lyt­ics com­pon­ent for the pur­pose of online advert­ising and the set­tle­ment of com­mis­sions to Google. Dur­ing the course of this tech­nic­al pro­ced­ure, the enter­prise Google gains know­ledge of per­son­al inform­a­tion, such as the IP address of the data sub­ject, which serves Google, inter alia, to under­stand the ori­gin of vis­it­ors and clicks, and sub­sequently cre­ate com­mis­sion settlements.

The cook­ie is used to store per­son­al inform­a­tion, such as the access time, the loc­a­tion from which the access was made, and the fre­quency 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 United States of Amer­ica. These per­son­al data are stored by Google in the United States of Amer­ica. Google may pass these per­son­al data col­lec­ted through the tech­nic­al pro­ced­ure to third parties.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Google Ana­lyt­ics from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Google Ana­lyt­ics may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data that are gen­er­ated by Google Ana­lyt­ics, which is related to the use of this web­site, as well as the pro­cessing 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 browser add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This browser add-on tells Google Ana­lyt­ics through a JavaS­cript, that any data and inform­a­tion about the vis­its of Inter­net pages may not be trans­mit­ted to Google Ana­lyt­ics. The install­a­tion of the browser add-ons is con­sidered an objec­tion by Google. If the inform­a­tion tech­no­logy sys­tem of the data sub­ject is later deleted, format­ted, or newly installed, then the data sub­ject must rein­stall the browser add-ons to dis­able Google Ana­lyt­ics. If the browser 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­pet­ence, or is dis­abled, it is pos­sible to execute the rein­stall­a­tion or react­iv­a­tion of the browser add-ons.

Fur­ther inform­a­tion and the applic­able 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/.

27. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Google Remarketing

On this web­site, the con­trol­ler has integ­rated Google Remarket­ing ser­vices. Google Remarket­ing is a fea­ture of Google AdWords, which allows an enter­prise to dis­play advert­ising to Inter­net users who have pre­vi­ously resided on the enter­prise’s Inter­net site. The integ­ra­tion of Google Remarket­ing there­fore allows an enter­prise to cre­ate user-based advert­ising and thus shows rel­ev­ant advert­ise­ments to inter­ested Inter­net users.

The oper­at­ing com­pany of the Google Remarket­ing ser­vices is the Google Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, United States.

The pur­pose of Google Remarket­ing is the inser­tion of interest-rel­ev­ant advert­ising. Google Remarket­ing allows us to dis­play ads on the Google net­work or on oth­er web­sites, which are based on indi­vidu­al needs and matched to the interests of Inter­net users.

Google Remarket­ing sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­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­it­or of our web­site if he calls up con­sec­ut­ive web pages, which are also a mem­ber of the Google advert­ising net­work. With each call-up to an Inter­net site on which the ser­vice has been integ­rated by Google Remarket­ing, the web browser of the data sub­ject iden­ti­fies auto­mat­ic­ally with Google. Dur­ing the course of this tech­nic­al pro­ced­ure, Google receives per­son­al inform­a­tion, such as the IP address or the surf­ing beha­viour of the user, which Google uses, inter alia, for the inser­tion of interest rel­ev­ant advertising.

The cook­ie is used to store per­son­al inform­a­tion, e.g. the Inter­net pages vis­ited 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 United States of Amer­ica. These per­son­al data are stored by Google in the United States of Amer­ica. Google may pass these per­son­al data col­lec­ted through the tech­nic­al pro­ced­ure to third parties.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Google from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Google may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to the interest-based advert­ising 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 browser used by the data subject.

Fur­ther inform­a­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/.

28. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Google+

On this web­site, the con­trol­ler has integ­rated the Google+ but­ton as a com­pon­ent. 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­munity, which usu­ally allows users to com­mu­nic­ate 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 exper­i­ences, or enable the Inter­net com­munity to provide per­son­al or busi­ness-related inform­a­tion. Google+ allows users of the social net­work to include the cre­ation of private pro­files, upload pho­tos and net­work through friend requests.

The oper­at­ing com­pany of Google+ is Google Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, UNITED STATES.

With each call-up to one of the indi­vidu­al pages of this web­site, which is oper­ated by the con­trol­ler and on which a Google+ but­ton has been integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject auto­mat­ic­ally down­loads a dis­play of the cor­res­pond­ing Google+ but­ton of Google through the respect­ive Google+ but­ton com­pon­ent. Dur­ing the course of this tech­nic­al pro­ced­ure, Google is made aware of what spe­cif­ic sub-page of our web­site was vis­ited by the data sub­ject. More detailed inform­a­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 recog­nizes with each call-up to our web­site by the data sub­ject and for the entire dur­a­tion of his or her stay on our Inter­net site, which spe­cif­ic sub-pages of our Inter­net page were vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Google+ but­ton and Google matches this with the respect­ive Google+ account asso­ci­ated with the data subject.

If the data sub­ject clicks on the Google+ but­ton integ­rated on our web­site and thus gives a Google+ 1 recom­mend­a­tion, then Google assigns this inform­a­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 recom­mend­a­tion of the data sub­ject, mak­ing it pub­licly avail­able in accord­ance with the terms and con­di­tions accep­ted by the data sub­ject in this regard. Sub­sequently, a Google+ 1 recom­mend­a­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 photo, is stored and pro­cessed on oth­er Google ser­vices, such as search-engine res­ults 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 advert­ise­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 inform­a­tion with the pur­pose of improv­ing or optim­iz­ing the vari­ous Google services.

Through the Google+ but­ton, Google receives inform­a­tion that the data sub­ject vis­ited 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 wheth­er 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 inform­a­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.

29. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Google-AdWords

On this web­site, the con­trol­ler has integ­rated Google AdWords. Google AdWords is a ser­vice for Inter­net advert­ising that allows the advert­iser to place ads in Google search engine res­ults and the Google advert­ising net­work. Google AdWords allows an advert­iser to pre-define spe­cif­ic keywords with the help of which an ad on Google’s search res­ults only then dis­played, when the user util­izes the search engine to retrieve a keyword-rel­ev­ant search res­ult. In the Google Advert­ising Net­work, the ads are dis­trib­uted on rel­ev­ant web pages using an auto­mat­ic algorithm, tak­ing into account the pre­vi­ously defined keywords.

The oper­at­ing com­pany of Google AdWords is Google Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, UNITED STATES.

The pur­pose of Google AdWords is the pro­mo­tion of our web­site by the inclu­sion of rel­ev­ant advert­ising on the web­sites of third parties and in the search engine res­ults of the search engine Google and an inser­tion of third-party advert­ising on our website.

If a data sub­ject reaches our web­site via a Google ad, a con­ver­sion cook­ie is filed on the inform­a­tion tech­no­logy sys­tem of the data sub­ject through Google. The defin­i­tion of cook­ies is explained above. A con­ver­sion cook­ie loses its valid­ity after 30 days and is not used to identi­fy the data sub­ject. If the cook­ie has not expired, the con­ver­sion cook­ie is used to check wheth­er 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­trol­ler can under­stand wheth­er a per­son who reached an AdWords ad on our web­site gen­er­ated sales, that is, executed or can­celed a sale of goods.

The data and inform­a­tion col­lec­ted through the use of the con­ver­sion cook­ie is used by Google to cre­ate vis­it stat­ist­ics for our web­site. These vis­it stat­ist­ics are used in order to determ­ine 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 optim­ize our AdWords ads in the future. Neither our com­pany nor oth­er Google AdWords advert­isers receive inform­a­tion from Google that could identi­fy the data subject.

The con­ver­sion cook­ie stores per­son­al inform­a­tion, e.g. the Inter­net pages vis­ited 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 United States of Amer­ica. These per­son­al data are stored by Google in the United States of Amer­ica. Google may pass these per­son­al data col­lec­ted through the tech­nic­al pro­ced­ure to third parties.

The data sub­ject may, at any time, pre­vent the set­ting of cook­ies by our web­site, as stated above, by means of a cor­res­pond­ing set­ting of the Inter­net browser used and thus per­man­ently deny the set­ting of cook­ies. Such a set­ting of the Inter­net browser used would also pre­vent Google from pla­cing a con­ver­sion cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, a cook­ie set by Google AdWords may be deleted at any time via the Inter­net browser or oth­er soft­ware programs.

The data sub­ject has a pos­sib­il­ity of object­ing to the interest based advert­ise­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 inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/.

30. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Instagram

On this web­site, the con­trol­ler has integ­rated com­pon­ents of the ser­vice Ins­tagram. Ins­tagram is a ser­vice that may be qual­i­fied as an audi­ovisu­al plat­form, which allows users to share pho­tos and videos, as well as dis­sem­in­ate such data in oth­er social networks.

The oper­at­ing com­pany of the ser­vices offered by Ins­tagram is Ins­tagram LLC, 1 Hack­er Way, Build­ing 14 First Floor, Menlo Park, CA, UNITED STATES.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which an Ins­tagram com­pon­ent (Insta but­ton) was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to the down­load of a dis­play of the cor­res­pond­ing Ins­tagram com­pon­ent of Ins­tagram. Dur­ing the course of this tech­nic­al pro­ced­ure, Ins­tagram becomes aware of what spe­cif­ic sub-page of our web­site was vis­ited by the data subject.

If the data sub­ject is logged in at the same time on Ins­tagram, Ins­tagram detects with every call-up to our web­site by the data subject—and for the entire dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Ins­tagram com­pon­ent and is asso­ci­ated with the respect­ive Ins­tagram account of the data sub­ject. If the data sub­ject clicks on one of the Ins­tagram but­tons integ­rated on our web­site, then Ins­tagram matches this inform­a­tion with the per­son­al Ins­tagram user account of the data sub­ject and stores the per­son­al data.

Ins­tagram receives inform­a­tion via the Ins­tagram com­pon­ent that the data sub­ject has vis­ited our web­site provided that the data sub­ject is logged in at Ins­tagram at the time of the call to our web­site. This occurs regard­less of wheth­er the per­son clicks on the Ins­tagram but­ton or not. If such a trans­mis­sion of inform­a­tion to Ins­tagram is not desir­able for the data sub­ject, then he or she can pre­vent this by log­ging off from their Ins­tagram account before a call-up to our web­site is made.

Fur­ther inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Ins­tagram may be retrieved under https://help.instagram.com/155833707900388 and https://www.instagram.com/about/legal/privacy/.

31. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Jet­pack for WordPress

On this web­site, the con­trol­ler has integ­rated Jet­pack. Jet­pack is a Word­Press plug-in, which provides addi­tion­al fea­tures to the oper­at­or of a web­site based on Word­Press. Jet­pack allows the Inter­net site oper­at­or, inter alia, an over­view of the vis­it­ors of the site. By dis­play­ing related posts and pub­lic­a­tions, or the abil­ity to share con­tent on the page, it is also pos­sible to increase vis­it­or num­bers. In addi­tion, secur­ity fea­tures are integ­rated into Jet­pack, so a Jet­pack-using site is bet­ter pro­tec­ted against brute-force attacks. Jet­pack also optim­izes and accel­er­ates the load­ing of images on the website.

The oper­at­ing com­pany of Jet­pack Plug-Ins for Word­Press is the Auto­mat­tic Inc., 132 Hawthorne Street, San Fran­cisco, CA 94107, UNITED STATES. The oper­at­ing enter­prise uses the track­ing tech­no­logy cre­ated by Quant­cast Inc., 201 Third Street, San Fran­cisco, CA 94103, UNITED STATES.

Jet­pack sets a cook­ie on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. The defin­i­tion of cook­ies is explained above. With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a Jet­pack com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to sub­mit data through the Jet­pack com­pon­ent for ana­lys­is pur­poses to Auto­mat­tic. Dur­ing the course of this tech­nic­al pro­ced­ure Auto­mat­tic receives data that is used to cre­ate an over­view of web­site vis­its. The data obtained in this way serves the ana­lys­is of the beha­viour of the data sub­ject, which has access to the Inter­net page of the con­trol­ler and is ana­lyzed with the aim to optim­ize the web­site. The data col­lec­ted through the Jet­pack com­pon­ent is not used to identi­fy the data sub­ject without a pri­or obtain­ing of a sep­ar­ate 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­poses as Automattic.

The data sub­ject can, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Automattic/Quantcast from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Automattic/Quantcast may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by the Jet­pack cook­ie as well as the pro­cessing 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 inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies are deleted 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data subject.

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

32. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of LinkedIn

The con­trol­ler has integ­rated com­pon­ents of the Linked­In Cor­por­a­tion on this web­site. Linked­In 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 registered people in more than 200 coun­tries use Linked­In. Thus, Linked­In is cur­rently the largest plat­form for busi­ness con­tacts and one of the most vis­ited web­sites in the world.

The oper­at­ing com­pany of Linked­In is Linked­In Cor­por­a­tion, 2029 Sti­er­lin Court Moun­tain View, CA 94043, UNITED STATES. For pri­vacy mat­ters out­side of the UNITED STATES Linked­In Ire­land, Pri­vacy Policy Issues, Wilton Plaza, Wilton Place, Dub­lin 2, Ire­land, is responsible.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a Linked­In com­pon­ent (Linked­In plug-in) was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to the down­load of a dis­play of the cor­res­pond­ing Linked­In com­pon­ent of Linked­In. Fur­ther inform­a­tion about the Linked­In plug-in may be accessed under https://developer.linkedin.com/plugins. Dur­ing the course of this tech­nic­al pro­ced­ure, Linked­In gains know­ledge of what spe­cif­ic sub-page of our web­site was vis­ited by the data subject.

If the data sub­ject is logged in at the same time on Linked­In, Linked­In detects with every call-up to our web­site by the data subject—and for the entire dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Linked­In com­pon­ent and asso­ci­ated with the respect­ive Linked­In account of the data sub­ject. If the data sub­ject clicks on one of the Linked­In but­tons integ­rated on our web­site, then Linked­In assigns this inform­a­tion to the per­son­al Linked­In user account of the data sub­ject and stores the per­son­al data.

Linked­In receives inform­a­tion via the Linked­In com­pon­ent that the data sub­ject has vis­ited our web­site, provided that the data sub­ject is logged in at Linked­In at the time of the call-up to our web­site. This occurs regard­less of wheth­er the per­son clicks on the Linked­In but­ton or not. If such a trans­mis­sion of inform­a­tion to Linked­In is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Linked­In account before a call-up to our web­site is made.

Linked­In provides under https://www.linkedin.com/psettings/guest-controls the pos­sib­il­ity to unsub­scribe from e‑mail mes­sages, SMS mes­sages and tar­geted ads, as well as the abil­ity to man­age ad set­tings. Linked­In also uses affil­i­ates such as Eire, Google Ana­lyt­ics, BlueKai, Double­Click, Nielsen, Com­score, Elo­qua, and Lot­ame. The set­ting of such cook­ies may be denied under https://www.linkedin.com/legal/cookie-policy. The applic­able pri­vacy policy for Linked­In is avail­able under https://www.linkedin.com/legal/privacy-policy. The Linked­In Cook­ie Policy is avail­able under https://www.linkedin.com/legal/cookie-policy.

33. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of LiveZilla

On this web­site, the con­trol­ler has integ­rated the LiveZ­illa com­pon­ent. LiveZ­illa is a live sup­port help desk soft­ware that enables dir­ect com­mu­nic­a­tion in real time (so-called live chat) with vis­it­ors of their own Inter­net page.

The developer of the LiveZ­illa com­pon­ent is LiveZ­illa GmbH, Byk-Gulden-Straße 18, 78224 Sin­gen, Germany.

With each single call-up to our web­site, which is equipped with a LiveZ­illa com­pon­ent, this com­pon­ent col­lects data with the pur­pose of oper­at­ing the live chat sys­tem and ana­lyz­ing the oper­a­tion of the sys­tem. Fur­ther inform­a­tion about LiveZ­illa may be retrieved under http://www.livezilla.net/home/en/.

The LiveZ­illa com­pon­ent sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. Pseud­onymised user pro­files may be cre­ated with the help of the LiveZ­illa cook­ie. Such pseud­onymised usage pro­files may be used by the con­trol­ler to con­duct an ana­lys­is of vis­it­or beha­vi­or as well as ana­lyze and main­tain a prop­er oper­a­tion of the live chat sys­tem. The ana­lys­is is also improv­ing our offers. The data col­lec­ted through the LiveZ­illa com­pon­ent is not used to identi­fy the data sub­ject without first obtain­ing of a sep­ar­ate express con­sent of the data sub­ject. These data are not merged with per­son­al data or oth­er data which con­tain the same pseudonym.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent the LiveZ­illa com­pon­ent from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by the LiveZ­illa com­pon­ent may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of LiveZ­illa GmbH may be accessed under https://www.livezilla.net/disclaimer/en/.

34. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Myspace

On this web­site, the con­trol­ler has integ­rated com­pon­ents 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­munity that allows users to com­mu­nic­ate 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 exper­i­ences or allow the Inter­net com­munity to provide per­son­al or com­pany-related inform­a­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­pany of MySpace is MySpace LLC, 8391 Beverly Blvd., #349, Los Angeles, Cali­for­nia 90048, UNITED STATES.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a MySpace com­pon­ent (MySpace plug-in) was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to the down­load through the respect­ive MySpace com­pon­ent a dis­play of the cor­res­pond­ing MySpace com­pon­ent of MySpace. Fur­ther inform­a­tion about MySpace is avail­able under https://myspace.com. Dur­ing the course of this tech­nic­al pro­ced­ure, MySpace gains know­ledge of what spe­cif­ic sub-page of our web­site is vis­ited 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 dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the MySpace com­pon­ent and asso­ci­ated with the respect­ive MySpace account of the data sub­ject. If the data sub­ject clicks on one of the MySpace but­tons, integ­rated on our web­site, then MySpace assigns this inform­a­tion with the per­son­al MySpace user account of the data sub­ject and stores the per­son­al data.

MySpace receives inform­a­tion via the MySpace com­pon­ent that the data sub­ject has vis­ited our web­site, provided 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 wheth­er the per­son clicks on the MySpace com­pon­ent or not. If such a trans­mis­sion of inform­a­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 guideline pub­lished by MySpace, which is avail­able under https://myspace.com/pages/privacy, provides inform­a­tion on the col­lec­tion, pro­cessing and use of per­son­al data by MySpace.

35. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Pinterest

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Pin­terest Inc. Pin­terest is a so-called social net­work. A social net­work is an Inter­net social meet­ing place, an online com­munity that allows users to com­mu­nic­ate 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 exper­i­ences, or allow the Inter­net com­munity to provide per­son­al or com­pany-related inform­a­tion. Pin­terest enables the users of the social net­work to pub­lish, inter alia, pic­ture col­lec­tions and indi­vidu­al 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­men­ted on.

The oper­at­ing com­pany of Pin­terest is Pin­terest Inc., 808 Bran­nan Street, San Fran­cisco, CA 94103, UNITED STATES.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a Pin­terest com­pon­ent (Pin­terest plug-in) was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject auto­mat­ic­ally promp­ted to down­load through the respect­ive Pin­terest com­pon­ent a dis­play of the cor­res­pond­ing Pin­terest com­pon­ent. Fur­ther inform­a­tion on Pin­terest is avail­able under https://pinterest.com/. Dur­ing the course of this tech­nic­al pro­ced­ure, Pin­terest gains know­ledge of what spe­cif­ic sub-page of our web­site is vis­ited by the data subject.

If the data sub­ject is logged in at the same time on Pin­terest, Pin­terest detects with every call-up to our web­site by the data subject—and for the entire dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Pin­terest com­pon­ent and asso­ci­ated with the respect­ive Pin­terest account of the data sub­ject. If the data sub­ject clicks on one of the Pin­terest but­tons, integ­rated on our web­site, then Pin­terest assigns this inform­a­tion to the per­son­al Pin­terest user account of the data sub­ject and stores the per­son­al data.

Pin­terest receives inform­a­tion via the Pin­terest com­pon­ent that the data sub­ject has vis­ited our web­site, provided that the data sub­ject is logged in at Pin­terest at the time of the call-up to our web­site. This occurs regard­less of wheth­er the per­son clicks on the Pin­terest com­pon­ent or not. If such a trans­mis­sion of inform­a­tion to Pin­terest is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Pin­terest account before a call-up to our web­site is made.

The data pro­tec­tion guideline pub­lished by Pin­terest, which is avail­able under https://about.pinterest.com/privacy-policy, provides inform­a­tion on the col­lec­tion, pro­cessing and use of per­son­al data by Pinterest.

36. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Matomo

On this web­site, the con­trol­ler has integ­rated the Mat­omo com­pon­ent. Mat­omo is an open-source soft­ware tool for web ana­lys­is. Web ana­lys­is is the col­lec­tion, gath­er­ing and eval­u­ation of data on the beha­vi­or of vis­it­ors from Inter­net sites. A web ana­lys­is tool col­lects, inter alia, data on the web­site from which a data sub­ject came to a web­site (so-called refer­rer), which pages of the web­site were accessed or how often and for which peri­od of time a sub-page was viewed. A web ana­lys­is is mainly used for the optim­iz­a­tion of a web­site and the cost-bene­fit ana­lys­is of Inter­net advertising.

The soft­ware is oper­ated on the serv­er of the con­trol­ler, the data pro­tec­tion-sens­it­ive log files are stored exclus­ively on this server.

The pur­pose of the Mat­omo com­pon­ent is the ana­lys­is of the vis­it­or flows on our web­site. The con­trol­ler uses the obtained data and inform­a­tion, inter alia, to eval­u­ate the use of this web­site in order to com­pile online reports, which show the activ­it­ies on our Inter­net pages.

Mat­omo sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. With the set­ting of the cook­ie, an ana­lys­is of the use of our web­site is enabled. With each call-up to one of the indi­vidu­al pages of this web­site, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally through the Mat­omo com­pon­ent promp­ted to sub­mit data for the pur­pose of online ana­lys­is to our serv­er. Dur­ing the course of this tech­nic­al pro­ced­ure, we obtain know­ledge about per­son­al inform­a­tion, such as the IP address of the data sub­ject, which serves to under­stand the ori­gin of vis­it­ors and clicks.

The cook­ie is used to store per­son­al inform­a­tion, such as the access time, the loc­a­tion from which access was made, and the fre­quency of vis­its to our web­site. With each vis­it of our Inter­net pages, these per­son­al data, includ­ing the IP address of the Inter­net access used by the data sub­ject, are trans­ferred to our serv­er. These per­son­al data will be stored by us. We do not for­ward this per­son­al data to third parties.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the used Inter­net browser would also pre­vent Mat­omo from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Mat­omo may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by Mat­omo as well as the pro­cessing of these data by Mat­omo and the chance to pre­clude any such. For this, the data sub­ject must set an opt-out cook­ie. The opt-out cook­ie that is set for this pur­pose is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies are deleted 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 each set­ting of the opt-out cook­ie, how­ever, there is the pos­sib­il­ity that the web­sites of the con­trol­ler are no longer fully usable for the data subject.

Fur­ther inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Mat­omo may be retrieved under https://matomo.org/privacy/.

37. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Shariff

On this web­site, the con­trol­ler has integ­rated the com­pon­ent of Shar­iff. The Shar­iff com­pon­ent provides social media but­tons that are com­pli­ant with data pro­tec­tion. Shar­iff was developed for the Ger­man com­puter magazine c’t and is pub­lished by Git­Hub, Inc.

The developers of the com­pon­ent is Git­Hub, Inc. 88 Colin P. Kelly Juni­or Street, San Fran­cisco, CA 94107, United States.

Typ­ic­ally, the but­ton solu­tions provided by the social net­works already trans­mits per­son­al data to the respect­ive social net­work, when a user vis­its a web­site in which a social media but­ton was integ­rated. By using the Shar­iff com­pon­ent, per­son­al data is only trans­ferred to social net­works, when the vis­it­or act­ively activ­ates one of the social media but­tons. Fur­ther inform­a­tion on the Shar­iff com­pon­ent may be found in the com­puter magazine c’t under http://www.heise.de/newsticker/meldung/Datenschutz-und-Social-Media-Der-ct-Shariff-ist-im-Usatz-2470103. Html provided. The use of the Shar­iff com­pon­ent is inten­ded to pro­tect the per­son­al data of the vis­it­ors of our web­site and to enable us to integ­rate a but­ton solu­tion for social net­works on this website.

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

38. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of SlideShare

On this web­site, the con­trol­ler has integ­rated Slide­Share com­pon­ents. Linked­In Slide­Share as a file host­ing ser­vice allows you to exchange and archive present­a­tions and oth­er doc­u­ments, such as PDF files, videos, and webinars. The file host­ing ser­vice allows users to upload media con­tent in all pop­u­lar formats, with the doc­u­ments either pub­licly-access­ible or private-labeled.

The oper­at­ing com­pany of Slide­Share is Linked­In Cor­por­a­tion, 2029 Sti­er­lin Court Moun­tain View, CA 94043, United States. For pri­vacy mat­ters out­side of the United States the Linked­In Ire­land, Pri­vacy Policy Issues, Wilton Plaza, Wilton Place, Dub­lin 2, Ire­land, is responsible.

Linked­In Slide­Share provides so-called embed­ded codes for the media con­tent (e.g. present­a­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 extern­al con­tent on their own web­site. Embed­ded codes allow con­tent to be repro­duced on its own web­site without stor­ing it on its own serv­er, pos­sibly viol­at­ing the right of repro­duc­tion of the respect­ive author of the con­tent. A fur­ther advant­age of the use of an embed­ded code is that the respect­ive oper­at­or of a web­site does not use its own stor­age space and the own serv­er is thereby relieved. An embed­ded code may be integ­rated at any point on anoth­er web­site so that an extern­al con­tent may also be inser­ted with­in the own text. The pur­pose of using Linked­In Slide­Share is to relieve our serv­er and to avoid copy­right infringe­ments, while at the same time using third-party content.

With each call-up to our Inter­net site, which is equipped with a Slide­Share com­pon­ent (embed­ded code), this com­pon­ent prompts the browser that you are using to down­load the accord­ing embed­ded data from Slide­Share. Dur­ing the course of this tech­nic­al pro­ced­ure, Linked­In gains know­ledge of which spe­cif­ic sub-page of our web­site is vis­ited by the data subject.

If the data sub­ject is logged in on Slide­Share at the same time, Slide­Share recog­nizes with each call-up to our web­site by the data sub­ject and for the entire dur­a­tion of their stay on our Inter­net site which spe­cif­ic sub-page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted by Slide­Share and assigned to the respect­ive Slide­Share account of the data sub­ject through LinkedIn.

Linked­In obtains inform­a­tion via the Slide­Share com­pon­ent that the data sub­ject has vis­ited our web­site, provided that the data sub­ject is logged in at Slide­Share at the time of the call-up to our web­site. This occurs regard­less of wheth­er the per­son clicks on the embed­ded media data or not. If such a trans­mis­sion of inform­a­tion to Slide­Share is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Slide­Share account before a call-up to our web­site is made.

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

39. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Tumblr

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Tumblr. Tumblr is a plat­form that allows users to cre­ate and run a blog. A blog is a web-based, gen­er­ally pub­licly-access­ible portal on which one or more people called blog­gers or web blog­gers may post art­icles or write down thoughts in so-called blo­g­posts. For example, in a Tumblr blog the user can pub­lish text, images, links, and videos, and spread them in the digit­al space. Fur­ther­more, Tumblr users may import con­tent from oth­er web­sites into their own blog.

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

Through each call to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a Tumblr com­pon­ent (Tumblr but­ton) has been integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject causes auto­mat­ic­ally the down­load of a dis­play of the cor­res­pond­ing Tumblr com­pon­ent of Tumblr. Learn more about the Tumblr-but­tons that are avail­able under https://www.tumblr.com/buttons. Dur­ing the course of this tech­nic­al pro­ced­ure, Tumblr becomes aware of what con­crete sub-page of our web­site was vis­ited by the data sub­ject. The pur­pose of the integ­ra­tion of the Tumblr com­pon­ent 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 digit­al world and to increase our vis­it­or numbers.

If the data sub­ject is logged in at Tumblr, Tumblr detects with every call-up to our web­site by the data subject—and for the entire dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Tumblr com­pon­ent and asso­ci­ated with the respect­ive Tumblr account of the data sub­ject. If the data sub­ject clicks on one of the Tumblr but­tons, integ­rated on our web­site, then Tumblr assigns this inform­a­tion to the per­son­al Tumblr user account of the data sub­ject and stores the per­son­al data.

Tumblr receives inform­a­tion via the Tumblr com­pon­ent that the data sub­ject has vis­ited our web­site, provided that the data sub­ject is logged in at Tumblr at the time of the call-up to our web­site. This occurs regard­less of wheth­er the per­son clicks on the Tumblr com­pon­ent or not. If such a trans­fer of inform­a­tion to Tumblr is not desir­able for the data sub­ject, then he or she may pre­vent this by log­ging off from their Tumblr account before a call-up to our web­site is made.

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

40. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Twitter

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Twit­ter. Twit­ter is a mul­ti­lin­gual, pub­licly-access­ible microb­log­ging ser­vice on which users may pub­lish and spread so-called ‘tweets,’ e.g. short mes­sages, which are lim­ited to 140 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 respect­ive 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 hasht­ags, links or retweets.

The oper­at­ing com­pany of Twit­ter is Twit­ter, Inc., 1355 Mar­ket Street, Suite 900, San Fran­cisco, CA 94103, UNITED STATES.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a Twit­ter com­pon­ent (Twit­ter but­ton) was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to down­load a dis­play of the cor­res­pond­ing Twit­ter com­pon­ent of Twit­ter. Fur­ther inform­a­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­nic­al pro­ced­ure, Twit­ter gains know­ledge of what spe­cif­ic sub-page of our web­site was vis­ited by the data sub­ject. The pur­pose of the integ­ra­tion of the Twit­ter com­pon­ent 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 digit­al world and increase our vis­it­or 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 dur­a­tion of their stay on our Inter­net site which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Twit­ter com­pon­ent and asso­ci­ated with the respect­ive Twit­ter account of the data sub­ject. If the data sub­ject clicks on one of the Twit­ter but­tons integ­rated on our web­site, then Twit­ter assigns this inform­a­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 inform­a­tion via the Twit­ter com­pon­ent that the data sub­ject has vis­ited our web­site, provided 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 wheth­er the per­son clicks on the Twit­ter com­pon­ent or not. If such a trans­mis­sion of inform­a­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­able data pro­tec­tion pro­vi­sions of Twit­ter may be accessed under https://twitter.com/privacy?lang=en.

41. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Webtrekk

On this web­site, the con­trol­ler has integ­rated com­pon­ents by Webtrekk. Webtrekk is a com­bin­a­tion of ana­lys­is and mar­ket­ing solu­tions in one sys­tem. Webtrekk allows the site oper­at­or to col­lect data on the use of the web­site, as well as indi­vidu­al­ize mar­ket­ing activities.

The oper­at­ing com­pany of Webtrekk is Webtrekk GmbH, Robert-Koch-Platz 4, 10115 Ber­lin, Germany.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler, Webtrekk col­lects data for mar­ket­ing and optim­isa­tion pur­poses and stores them. The pseud­onym­ized user pro­files are used for the pur­pose of ana­lyz­ing vis­it­or beha­vi­or and enabling an improve­ment of our Inter­net offer. The data col­lec­ted via the Webtrekk com­pon­ent are not used to identi­fy the data sub­ject without first obtain­ing a sep­ar­ate and expli­cit con­sent from the data sub­ject. These data will not be merged with per­son­al data or with oth­er data which con­tains the same pseudonym.

Webtrekk sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. Webtrekk uses the data col­lec­ted from our web­site and inform­a­tion on behalf of the con­trol­ler to ana­lyze user beha­viour of the data sub­ject, who has vis­ited our web­site. In addi­tion, Webtrekk uses the data to cre­ate reports on user activ­it­ies on our behalf and provide oth­er ser­vices for our enter­prise, which are in rela­tion to the usage of our web­site. The IP address of the data sub­ject is not merged by Webtrekk with oth­er per­son­al information.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the used Inter­net browser would also pre­vent Webtrekk from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Webtrekk may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data that are gen­er­ated by the Webtrekk cook­ie, relat­ing to a use of this Inter­net site, as well as the pro­cessing of these data by Webtrekk and the chance to pre­clude any such. To do this, the data sub­ject must click a link under https://www.webtrekk.com/en/legal/opt-out-webtrekk/, which is an opt-out cook­ie. The opt-out cook­ie is placed onto the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the data sub­ject deletes the cook­ies on 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of Webtrekk may be accessed under https://www.webtrekk.com/en/why-webtrekk/data-protection/.

42. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of WiredMinds

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Wired­Minds. The Wired­Minds com­pon­ents auto­mat­ic­ally recog­nize and qual­i­fy com­pan­ies who vis­it a web­site. The Wired­Minds com­pon­ent allows the oper­at­or of a web­site that uses the com­pon­ent to gen­er­ate leads, thus qual­i­fy­ing poten­tial new customers.

The oper­at­ing com­pany of Wired­Minds is Wired­Minds GmbH, Linden­spür­straße 32, 70176 Stut­tgart, Germany.

We use a Wired­Minds track­ing pixel. A track­ing pixel is a mini­ature graph­ic embed­ded in a web page to enable log file record­ing and log file ana­lys­is to sub­sequently per­form a stat­ist­ic­al analysis.

Wired­Minds also sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The set­ting of the cook­ie enables us to ana­lyze the usage of our website.

Using the data obtained, pseud­onym­ized usage pro­files are cre­ated. The pseud­onym­ized usage pro­files are used for the pur­pose of ana­lyz­ing vis­it­or beha­vi­or and enabling an improve­ment of our Inter­net offer. Data col­lec­ted through the Wired­Minds com­pon­ent are not used to identi­fy the data sub­ject without first obtain­ing a sep­ar­ate and expli­cit con­sent from the data sub­ject. These data will not be merged with per­son­al data or with oth­er data which con­tains the same pseudonym.

With each call-up to one of the indi­vidu­al pages of this web­site, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to sub­mit data for the pur­pose of online ana­lys­is the Wired­Minds com­pon­ent. Dur­ing the course of this tech­nic­al pro­ced­ure, Wired­Minds gains know­ledge of per­son­al inform­a­tion, such as the IP address, which inter alia, serves to under­stand the ori­gin of vis­it­ors and clicks.

The cook­ie is used to store per­son­al inform­a­tion, such as the access time, the loc­a­tion from which access was made, and the fre­quency of vis­its to our web­site. With each vis­it of our Inter­net pages, these per­son­al data, includ­ing the IP address of the Inter­net access used by the data sub­ject, are trans­ferred to the Wired­Minds serv­er. These per­son­al data are stored by Wired­Minds, but are not for­war­ded to third parties.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Wired­Minds from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Wired­Minds may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to the col­lec­tion of data relat­ing to a use of this site that are gen­er­ated by Wired­Minds and the chance to pre­clude any such. For this pur­pose, the data sub­ject must click the ‘don’t‑track-my-visits’ but­ton under the link https://wm.wiredminds.de/track/cookie_mgr.php?mode=dont_track_ask&websitesel. If the inform­a­tion tech­no­logy sys­tem of the data sub­ject is later deleted, format­ted or rein­stalled, then the data sub­ject must again set an opt-out cookie.

Fur­ther inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Wired­Minds may be retrieved under https://www.wiredminds.de/1/data-protection-report/.

43. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Xing

On this web­site, the con­trol­ler has integ­rated com­pon­ents 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­vidu­al users can cre­ate a per­son­al pro­file of them­selves at XING. Com­pan­ies may, e.g. cre­ate com­pany pro­files or pub­lish jobs on XING.

The oper­at­ing com­pany of XING is XING SE, Dam­mt­or­straße 30, 20354 Ham­burg, Germany.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a XING com­pon­ent (XING plug-in) was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to down­load a dis­play of the cor­res­pond­ing XING com­pon­ent of XING. Fur­ther inform­a­tion about the XING plug-in the may be accessed under https://dev.xing.com/plugins. Dur­ing the course of this tech­nic­al pro­ced­ure, XING gains know­ledge of what spe­cif­ic sub-page of our web­site was vis­ited 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 dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the XING com­pon­ent and asso­ci­ated with the respect­ive XING account of the data sub­ject. If the data sub­ject clicks on the XING but­ton integ­rated on our Inter­net site, e.g. the “Share”-button, then XING assigns this inform­a­tion to the per­son­al XING user account of the data sub­ject and stores the per­son­al data.

XING receives inform­a­tion via the XING com­pon­ent that the data sub­ject has vis­ited our web­site, provided 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 wheth­er the per­son clicks on the XING com­pon­ent or not. If such a trans­mis­sion of inform­a­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, provide inform­a­tion on the col­lec­tion, pro­cessing and use of per­son­al data by XING. In addi­tion, XING has pub­lished pri­vacy notices for the XING share but­ton under https://www.xing.com/app/share?op=data_protection.

44. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of YouTube

On this web­site, the con­trol­ler has integ­rated com­pon­ents of You­Tube. You­Tube is an Inter­net video portal that enables video pub­lish­ers to set video clips and oth­er users free of charge, which also provides free view­ing, review and com­ment­ing on them. You­Tube 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­pany of You­Tube is You­Tube, LLC, 901 Cherry Ave., San Bruno, CA 94066, UNITED STATES. The You­Tube, LLC is a sub­si­di­ary of Google Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, UNITED STATES.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a You­Tube com­pon­ent (You­Tube video) was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to down­load a dis­play of the cor­res­pond­ing You­Tube com­pon­ent. Fur­ther inform­a­tion about You­Tube may be obtained under https://www.youtube.com/yt/about/en/. Dur­ing the course of this tech­nic­al pro­ced­ure, You­Tube and Google gain know­ledge of what spe­cif­ic sub-page of our web­site was vis­ited by the data subject.

If the data sub­ject is logged in on You­Tube, You­Tube recog­nizes with each call-up to a sub-page that con­tains a You­Tube video, which spe­cif­ic sub-page of our Inter­net site was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted by You­Tube and Google and assigned to the respect­ive You­Tube account of the data subject.

You­Tube and Google will receive inform­a­tion through the You­Tube com­pon­ent that the data sub­ject has vis­ited our web­site, if the data sub­ject at the time of the call to our web­site is logged in on You­Tube; this occurs regard­less of wheth­er the per­son clicks on a You­Tube video or not. If such a trans­mis­sion of this inform­a­tion to You­Tube and Google is not desir­able for the data sub­ject, the deliv­ery may be pre­ven­ted if the data sub­ject logs off from their own You­Tube account before a call-up to our web­site is made.

You­Tube’s data pro­tec­tion pro­vi­sions, avail­able at https://www.google.com/intl/en/policies/privacy/, provide inform­a­tion about the col­lec­tion, pro­cessing and use of per­son­al data by You­Tube and Google.

45. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of the scal­able and cent­ral meas­ur­ing sys­tem of the INFOn­line GmbH

On this web­site, the data con­trol­ler has integ­rated a track­ing pixel for real-time meas­ure­ment. A track­ing pixel is a mini­ature graph­ic embed­ded in Inter­net pages to enable log file record­ing and log file ana­lys­is to sub­sequently per­form a stat­ist­ic­al ana­lys­is. The integ­rated track­ing pixels are used for the Scal­able Cent­ral Meas­ure­ment Sys­tem (SZMS) of INFOn­line GmbH.

The Scal­able Cent­ral Meas­ure­ment Sys­tem is oper­ated by INFOn­line GmbH, For­um Bonn Nord, Brühler Str. 9, 53119 Bonn, Germany.

The Scal­able Cent­ral Meas­ure­ment Sys­tem is used to determ­ine stat­ist­ic­al ratios, that is, the realm range meas­ure­ment. The embed­ded track­ing pixel is used to determ­ine if, when and by how many users (includ­ing the dataa sub­ject) our web­site was opened and what con­tent was retrieved.

The data obtained by means of the Scal­able Cent­ral Meas­ure­ment Sys­tem are col­lec­ted anonym­ously. In order to detect the access num­bers, a so-called ses­sion cook­ie is set up for the pur­pose of the recog­ni­tion of the web­site users, e.g. a sig­na­ture is made which con­sists of vari­ous auto­mat­ic­ally-trans­mit­ted inform­a­tion, or uses altern­at­ive meth­ods. The IP address of the Inter­net used by the data sub­ject is col­lec­ted and pro­cessed in an anonym­ous form only. The data sub­ject is not iden­ti­fied at any time.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent INFOn­line from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by INFOn­line may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to the col­lec­tion of data relat­ing to a use of this site that are gen­er­ated by INFOn­line 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 http://optout.ioam.de which uses an opt-out cook­ie. If the cook­ies are deleted 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not fully usable any­more by the data sub­ject. The applic­able data pro­tec­tion pro­vi­sions of INFOn­line may be accessed at https://www.infonline.de/datenschutz/.

46. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of DoubleClick

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Double­Click by Google. Double­Click is a trade­mark of Google, under which pre­dom­in­antly spe­cial online mar­ket­ing solu­tions are mar­keted to advert­ising agen­cies and publishers.

The oper­at­ing com­pany of Double­Click by Google is Google Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, UNITED STATES.

Double­Click by Google trans­mits data to the Double­Click serv­er with each impres­sion, clicks, or oth­er activ­ity. Each of these data trans­fers trig­gers a cook­ie request to the data sub­ject’s browser. If the browser accepts this request, Double­Click uses a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The pur­pose of the cook­ie is the optim­iz­a­tion and dis­play of advert­ising. The cook­ie is used, inter alia, to dis­play and place user-rel­ev­ant advert­ising as well as to cre­ate or improve reports on advert­ising cam­paigns. Fur­ther­more, the cook­ie serves to avoid mul­tiple dis­play of the same advertisement.

Double­Click uses a cook­ie ID that is required to execute the tech­nic­al pro­cess. For example, the cook­ie ID is required to dis­play an advert­ise­ment in a browser. Double­Click may also use the Cook­ie ID to record which advert­ise­ments have already been dis­played in a browser in order to avoid duplic­a­tions. It is also pos­sible for Double­Click to track con­ver­sions through the cook­ie ID. For instance, con­ver­sions are cap­tured, when a user has pre­vi­ously been shown a Double­Click advert­ising ad, and he or she sub­sequently makes a pur­chase on the advert­iser­’s web­site using the same Inter­net browser.

A cook­ie from Double­Click does not con­tain any per­son­al data. How­ever, a Double­Click cook­ie may con­tain addi­tion­al cam­paign IDs. A cam­paign ID is used to identi­fy cam­paigns that the user has already been in con­tact with.

With each call-up to one of the indi­vidu­al pages of this web­site, which is oper­ated by the con­trol­ler and on which a Double­Click com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted by the respect­ive Double­Click com­pon­ent to send data for the pur­pose of online advert­ising and billing of com­mis­sions to Google. Dur­ing the course of this tech­nic­al pro­ced­ure, Google gains know­ledge 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 stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Google from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Google may be deleted at any time via a web browser or oth­er soft­ware programs.

Fur­ther inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Double­Click may be retrieved under Double­Click by Google https://www.google.com/intl/en/policies/.

47. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Zanox

On this web­site, the con­trol­ler has integ­rated com­pon­ents by Zan­ox. Zan­ox is a Ger­man affil­i­ate net­work that offers affil­i­ate mar­ket­ing. Affil­i­ate mar­ket­ing is an Inter­net-based sales form that enables com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to place advert­ising that is usu­ally paid via click or sale com­mis­sions on third-party web­sites, also called affil­i­ates or pub­lish­ers (e.g. sales part­ners). The mer­chant provides, through the affil­i­ate net­work, an advert­ising medi­um, e.g. an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on their own Inter­net pages or pro­moted via oth­er chan­nels, such as keyword advert­ising or e‑marketing.

The oper­at­ing com­pany of Zan­ox is ZAN­OX AG, Stralauer Allee 2, 10245 Ber­lin, Germany.

Zan­ox sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The track­ing cook­ie of Zan­ox does not store any per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of stor­ing this data is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed via the affil­i­ate net­work, that is Zanox.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Zan­ox from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Zan­ox may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of Zan­ox may be retrieved under http://www.zanox.com/us/about-zanox/privacy/.

48. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Adcell

On this web­site, the con­trol­ler has integ­rated com­pon­ents of AdCell. AdCell is a Ger­man affil­i­ate net­work, which offers affil­i­ate mar­ket­ing. Affil­i­ate mar­ket­ing is an Inter­net-based sales form that enables com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to place advert­ising that is usu­ally paid via click or sale com­mis­sions on third-party web­sites, e.g. sales part­ners, also called affil­i­ates or pub­lish­ers. The mer­chant provides, through the affil­i­ate net­work, an advert­ising medi­um, e.g. an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on their own Inter­net pages or pro­moted via oth­er chan­nels, such as keyword advert­ising or e‑marketing.

The oper­at­ing com­pany of AdCell is Firstlead GmbH, Rosen­feld­er Str. 15–16, 10315 Ber­lin, Germany.

AdCell sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The track­ing cook­ie of AdCell stores no per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of stor­ing this data is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed via the affil­i­ate net­work, that is AdCell.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser use and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent AdCell from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by AdCell may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of AdCell may be retrieved under https://www.adcell.de/agb.

49. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Belboon

On this web­site, the con­trol­ler has integ­rated com­pon­ents by Bel­boon. Bel­boon is a Ger­man affil­i­ate net­work, which offers affil­i­ate mar­ket­ing. Affil­i­ate mar­ket­ing is an Inter­net-based sales form that enables com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to place advert­ising that is usu­ally paid via click or sale com­mis­sions on third-party web­sites, e.g. sales part­ners, also called affil­i­ates or pub­lish­ers. The mer­chant provides, through the affil­i­ate net­work, an advert­ising medi­um, e.g. an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on their own Inter­net pages or pro­moted via oth­er chan­nels, such as keyword advert­ising or e‑marketing.

The oper­at­ing com­pany of AdCell is Bel­boon GmbH, Wein­meister­str. 12–14, 10178 Berlin.

Bel­boon sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The track­ing cook­ie by Bel­boon stores no per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of stor­ing this data is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed via the affil­i­ate net­work, that is Belboon

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Bel­boon from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Bel­boon may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of Bel­boon may be retrieved under https://www.belboon.com/en/about-us/privacy/.

50. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of TradeTracker

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Trade­Track­er. Trade­Track­er is an affil­i­ate net­work that offers affil­i­ate mar­ket­ing. Affil­i­ate mar­ket­ing is an Inter­net-based sales form that enables com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to place advert­ising that is usu­ally paid via click or sale com­mis­sions on third-party web­sites (e.g. sales part­ners, also called affil­i­ates or pub­lish­ers). The mer­chant provides, through the affil­i­ate net­work, an advert­ising medi­um, e.g. an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on their own Inter­net pages or pro­moted via oth­er chan­nels, such as keyword advert­ising or e‑marketing.

The oper­at­ing com­pany of Trade­Track­er is Trade­Track­er Ger­many GmbH, Eif­festraße 426, 20537 Ham­burg, Germany.

Trade­Track­er sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The track­ing cook­ie of Trade­Track­er stores no per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of stor­ing this data is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed via the affil­i­ate net­work, that is TradeTracker.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Trade­Track­er from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Trade­Track­er may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of Trade­Track­er may be retrieved under https://tradetracker.com/privacy-policy/.

51. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Adgoal

The con­trol­ler has integ­rated com­pon­ents of Adgoal on this web­site. Adgoal is a Ger­man affil­i­ate net­work, which offers affil­i­ate mar­ket­ing. Affil­i­ate mar­ket­ing is an Inter­net-based sales form that enables com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to place advert­ising that is usu­ally paid via click or sale com­mis­sions on third-party web­sites, e.g. sales part­ners, also called affil­i­ates or pub­lish­ers. The mer­chant provides, through the affil­i­ate net­work, an advert­ising medi­um, e.g. an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on their own Inter­net pages or pro­moted via oth­er chan­nels, such as keyword advert­ising or e‑marketing.

The oper­at­ing com­pany of Adgoal is Adgoal GmbH, Schel­len­gasse 2. 74072 Heil­bronn, Germany.

Adgoal sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The track­ing cook­ie of Adgoal stores no per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of stor­ing this data is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed via the affil­i­ate net­work, that is Adgoal.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Adogal from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Adgoal may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of Adgoal may be retrieved under https://www.adgoal.de/en/privacy.html.

52. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of YieldKit

On this web­site, the con­trol­ler has integ­rated com­pon­ents of YieldKit. YieldKit is a Ger­man affil­i­ate net­work, which offers affil­i­ate mar­ket­ing. Affil­i­ate mar­ket­ing is an Inter­net-based sales form that enables com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to place advert­ising that is usu­ally paid via click or sale com­mis­sions on third-party web­sites, e.g. sales part­ners, also called affil­i­ates or pub­lish­ers. The mer­chant provides, through the affil­i­ate net­work, an advert­ising medi­um, e.g. an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on their own Inter­net pages or pro­moted via oth­er chan­nels, such as keyword advert­ising or e‑marketing.

The oper­at­ing com­pany of YieldKit is YieldKit GmbH, Gän­se­markt 43, 20354 Hamburg.

YieldKit sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. The track­ing cook­ie of YieldKit stores no per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of stor­ing this data is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed via the affil­i­ate net­work, that is YieldKit.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent YieldKit from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by YieldKit may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of YieldKit may be retrieved under http://yieldkit.com/legal-notes/privacy-policy/.

53. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Tradedoubler

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Trade­Dou­bler. Trade­Dou­bler is a Ger­man affil­i­ate net­work, which offers affil­i­ate mar­ket­ing. Affil­i­ate mar­ket­ing is an Inter­net-based sales form that enables com­mer­cial oper­at­ors of Inter­net sites, the so-called mer­chants or advert­isers, to place advert­ising that is usu­ally paid via click or sale com­mis­sions on third-party web­sites, e.g. sales part­ners, also called affil­i­ates or pub­lish­ers. The mer­chant provides, through the affil­i­ate net­work, an advert­ising medi­um, e.g. an advert­ising ban­ner or oth­er suit­able means of Inter­net advert­ising, which is sub­sequently integ­rated by an affil­i­ate on their own Inter­net pages or pro­moted via oth­er chan­nels, such as keyword advert­ising or e‑marketing.

The oper­at­ing com­pany of Trade­Dou­bler is Trade­Dou­bler GmbH, Herzog-Wil­helm-Straße 26, 80331 München, Germany.

Trade­Dou­bler sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. Trade­Dou­bler­’s track­ing cook­ie stores no per­son­al data. Only the iden­ti­fic­a­tion num­ber of the affil­i­ate, that is, the part­ner medi­at­ing the poten­tial cus­tom­er, as well as the ordin­al num­ber of the vis­it­or of a web­site and the clicked advert­ising medi­um are stored. The pur­pose of stor­ing this data is the pro­cessing of com­mis­sion pay­ments between a mer­chant and affil­i­ate, which are pro­cessed via the affil­i­ate net­work, that is TradeDoubler.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Trade­Dou­bler from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Trade­Dou­bler may be deleted at any time via a web browser or oth­er soft­ware programs.

The applic­able data pro­tec­tion pro­vi­sions of Trade­Dou­bler may be retrieved under http://www.tradedoubler.com/en/privacy-policy/.

54. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Oracle Elo­qua / Oracle Mar­ket­ing Cloud

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Oracle Eloqua/Oracle Mar­ket­ing Cloud (here­in­after referred to as the “Elo­qua”). Elo­qua com­pares rel­ev­ant Inter­net con­tent to data from pro­spect­ive cus­tom­ers and their pro­files, to enable Inter­net site oper­at­ors to speak more effect­ively and spe­cific­ally to pro­spects and cus­tom­ers. The pur­pose of Elo­qua is to increase the con­ver­sion rate of pro­spect­ive cus­tom­ers and thus increase the turnover of an Inter­net site operator.

The oper­at­ing com­pany of Elo­qua is Oracle Cor­por­a­tion, 500 Oracle Park­way, Red­wood Shores, CA 94065, UNITED STATES.

Elo­qua sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. Elo­qua will use the data col­lec­ted from our web­site and inform­a­tion on behalf of the con­trol­ler to ana­lyze user beha­viour of the data sub­ject, who has used our Inter­net page. In addi­tion, Elo­qua will use the data to cre­ate reports on user activ­it­ies on our behalf, as well as to provide oth­er ser­vices for our enter­prise, which are in rela­tion to the use of our website.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Oracle from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Oracle may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by the Elo­qua cook­ie as well as the pro­cessing of these data by Elo­qua and the chance to pre­clude any such. For this, the data sub­ject must press the ‘click here’ but­ton under https://www.oracle.com/marketingcloud/opt-status.html, which sets an opt-out cook­ie. The opt-out cook­ie is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the data sub­ject deletes the cook­ies on 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not entirely usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of Oracle may be accessed under https://www.oracle.com/legal/privacy/index.html.

55. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Lotame

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Lot­ame. Lot­ame is a plat­form for data man­age­ment through which data is impor­ted from third-party sources across devices, in order to sub­sequently per­son­al­ize con­tent, advert­ising and offers. Lot­ame is there­fore also an ana­lys­is ser­vice. An ana­lys­is ser­vice per­forms a sur­vey, col­lec­tion and ana­lys­is of data. It is mainly used to optim­ize an Inter­net site, in order to plan costs and bene­fits of advert­ising activities.

The oper­at­ing com­pany of Lot­ame the Lot­ame Solu­tions, Inc. Suite 2000 8850 Stan­ford Blvd. Columbia, Mary­land, 21045, UNITED STATES.

The pur­pose of Lot­ame is a cross-device approach of our cus­tom­ers and pro­spect­ive cus­tom­ers. Device inter­cep­tion is a response by the cus­tom­er if it takes place on a nor­mal com­puter sys­tem as well as on mobile devices such as note­books, tab­lets or mobile phones. Lot­ame uses so-called Unique Iden­ti­fi­ers (UIDs) for this pur­pose. A unique iden­ti­fi­er is a tech­no­logy that can be used to determ­ine which dif­fer­ent tech­no­lo­gic­al sys­tems are used by a par­tic­u­lar person.

Lot­ame sets a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies is explained above. With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a Lot­ame com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to trans­mit data through the Lot­ame com­pon­ent for optim­iz­a­tion pur­poses to Lot­ame. Dur­ing the course of this tech­nic­al pro­ced­ure, Lot­ame receives data that is used to cre­ate user pro­files. The res­ult­ing usage pro­files are used to determ­ine which dif­fer­ent inform­a­tion tech­no­logy devices the respect­ive user uses to optim­ize our advert­ising activ­it­ies as a result.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the Inter­net browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the used Inter­net browser would also pre­vent Lot­ame from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Lot­ame may be deleted at any time via a web browser or oth­er soft­ware programs.

There is also the pos­sib­il­ity of object­ing to a col­lec­tion of data elat­ing to a use of this Inter­net site that are gen­er­ated by the Lot­ame cook­ie as well as the pro­cessing of these data by Lot­ame and the chance to pre­clude any such. For this pur­pose, the data sub­ject must press the ‘opt-out’ but­ton under https://www.lotame.com/opt-out-preference-manager/ through which an opt-out cook­ie is set. The opt-out cook­ie set for this pur­pose is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies are deleted on the sys­tem of the data sub­ject, then the data sub­ject must call the link again and set a new opt-out cookie.

With the set­ting of the opt-out cook­ie, how­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not entirely usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of Lot­ame may be accessed at https://www.lotame.com/legal/.

56. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Bloglovin

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Blo­glov­in’. Blo­glov­in’ is an online plat­form that allows users to organ­ize their favor­ite blogs. A blog is a web-based, gen­er­ally pub­licly-access­ible portal, in which one or more people called blog­gers or web blog­gers can post art­icles or write down thoughts in so-called blogposts.

The oper­at­ing com­pany of Blo­glov­in’ is Blo­glov­in’ Inc., 25 Broad­way, New York, NY 10004, UNITED STATES.

With each call-up to one of the indi­vidu­al pages of this Inter­net site, which is oper­ated by the con­trol­ler and on which a Blo­glov­in’ com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to down­load a dis­play of the cor­res­pond­ing Blo­glov­in’ com­pon­ent, through the Blo­glov­in’ com­pon­ent. Dur­ing the course of this tech­nic­al pro­ced­ure, Blo­glov­in’ gains know­ledge of what spe­cif­ic sub-page of our web­site was vis­ited by the data subject.

If the data sub­ject is logged in at the same time at Blo­glov­in’, Blo­glov­in’ recog­nizes with each call-up to our web­site by the data subject—and for the entire dur­a­tion of their stay on our Inter­net site—which spe­cif­ic sub-page of our Inter­net page was vis­ited by the data sub­ject. This inform­a­tion is col­lec­ted through the Blo­glov­in’ com­pon­ent and through Blo­glov­in’ assigned to the respect­ive Blo­glov­in’ account of the data sub­ject. If the data sub­ject clicks on the Blo­glov­in’ but­ton that is integ­rated on our web­site, then this inform­a­tion is delivered to Blo­glov­in’. The data sub­ject has already agreed to the trans­mis­sion of such inform­a­tion to Bloglovin’.

Fur­ther inform­a­tion and the applic­able data pro­tec­tion pro­vi­sions of Blo­glov­in’ may be retrieved under https://www.bloglovin.com/tos.

57. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of Amobee

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Amo­bee. Amo­bee is a tech­no­lo­gic­al advert­ising agency spe­cial­iz­ing in the deliv­ery of advert­ising to mobile devices.

The oper­at­ing com­pany of Amo­bee is Amo­bee Inc., 950 Tower Lane, Suite 2000, Foster City, CA 94404, UNITED STATES.

The pur­pose of Amo­bee is to deliv­er advert­ising. Amo­bee uses a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject The defin­i­tion of cook­ies is explained above. With each call-up to the indi­vidu­al pages of this web­site, which oper­ated by the con­trol­ler and on which an Amo­bee com­pon­ent is integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted by the respect­ive Amo­bee com­pon­ent to trans­mit data to Amo­bee. Dur­ing the course of this tech­nic­al pro­ced­ure, Amo­bee gains know­ledge of the data that are sub­sequently used to cre­ate usage pro­files. The res­ult­ing usage pro­files serve advert­ising activities.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent Amo­bee from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Amo­bee may be deleted at any time via a web browser or oth­er soft­ware programs.

There is also the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by the Amo­bee cook­ie as well as the pro­cessing of these data by Amo­bee and the chance to pre­clude any such. For this pur­pose, the data sub­ject must press the ‘click-here-to-opt-out’ but­ton under http://amobee.com/privacy/technology/ through which an opt-out cook­ie is set. The opt-out cook­ie set for this pur­pose is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies are deleted 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not entirely usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of Amo­bee may be accessed under http://amobee.com/privacy/.

58. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of ADITION

On this web­site, the con­trol­ler has integ­rated com­pon­ents of ADI­TION. ADI­TION is a pro­vider of data-based digit­al mar­ket­ing that provides an advert­ising plat­form tar­get­ing advert­isers and online mar­ket­ing agencies.

The oper­at­ing com­pany of ADI­TION is ADI­TION tech­no­lo­gies AG, Ost­straße 55, 40211 Düs­sel­dorf, Germany.

The pur­pose of ADI­TION is the inser­tion of digit­al advert­ising media. ADI­TION uses a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. The defin­i­tion of cook­ies has already been explained above. ADI­TION does not store per­son­al data in the cook­ie. All inform­a­tion stored in the cook­ie is of a tech­nic­al nature and enables con­trol­ler, inter alia, to under­stand how fre­quently cer­tain advert­ise­ments are displayed.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent ADI­TION from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by ADI­TION may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by the ADI­TION cook­ie as well as the pro­cessing of these data by ADI­TION and the chance to pre­clude any such. For this pur­pose, the data sub­ject must click a link under https://www.adition.com/kontakt/datenschutz/, which sets an opt-out cook­ie. The opt-out cook­ie is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the data sub­ject deletes the cook­ies on 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not entirely usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of ADI­TION may be accessed under https://www.adition.com/en/kontakt/datenschutz/.

59. Data pro­tec­tion pro­vi­sions about the applic­a­tion and use of AdJug

On this web­site, the con­trol­ler has integ­rated com­pon­ents of AdJug. AdJug is an advert­ising exchange plat­form that provides online advert­ising (ban­ner advertising).

The oper­at­ing com­pany of AdJug is AdJug GmbH, Bay­er­straße 69, 80335 München, Germany.

AdJug sets a cook­ie. Fur­ther­more, with each call-up to a single page of this Inter­net site, which is oper­ated by the con­trol­ler and on which an AdJug com­pon­ent was integ­rated, the Inter­net browser on the inform­a­tion tech­no­logy sys­tem of the data sub­ject is auto­mat­ic­ally promp­ted to sub­mit data through the cor­res­pond­ing AdJug com­pon­ent for the pur­pose of dis­play­ing advert­ise­ments delivered by AdJug. In this tech­nic­al pro­ced­ure, AdJug gains inform­a­tion that our web­site was accessed by the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. The data trans­mit­ted with­in the frame­work of the tech­nic­al pro­ced­ure of AdJug serve for billing pur­poses in rela­tion to the dis­played advertising.

The data sub­ject may, as stated above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­res­pond­ing adjust­ment of the web browser used and thus per­man­ently deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net browser used would also pre­vent AdJug from set­ting a cook­ie on the inform­a­tion tech­no­logy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by AdJug may be deleted at any time via a web browser or oth­er soft­ware programs.

In addi­tion, the data sub­ject has the pos­sib­il­ity of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­ated by the AdJug cook­ie as well as the pro­cessing of these data by AdJug and the chance to pre­clude any such. For this pur­pose, the data sub­ject must press the con­sumer cook­ie opt-out link under http://www.de.adjug.com/datenschutz.html, which sets an opt-out cook­ie. The opt-out cook­ie, set for this pur­pose, is placed on the inform­a­tion tech­no­logy sys­tem used by the data sub­ject. If the cook­ies on the sys­tem of the data sub­ject are deleted, 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­ever, the pos­sib­il­ity exists that the web­sites of the con­trol­ler are not entirely usable any­more by the data subject.

The applic­able data pro­tec­tion pro­vi­sions of AdJug may be accessed under http://www.adjug.com/info/privacy.asp.

60. Pay­ment Meth­od: Data pro­tec­tion pro­vi­sions about the use of Klarna as a pay­ment processor

On this web­site, the con­trol­ler has integ­rated Klarna com­pon­ents. Klarna is an online pay­ment ser­vice pro­vider, which allows pur­chases on an account or a flex­ible install­ment pay­ment. Klarna also offers oth­er ser­vices, such as buy­er pro­tec­tion and iden­tity or cred­it­wor­thi­ness checks.

The oper­at­ing com­pany of Klarna is Klarna 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 pro­cess in our online shop as a pay­ment option, the data of the data sub­ject is auto­mat­ic­ally trans­mit­ted to Klarna. 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­cessing of the invoice or install­ment pur­chase, or iden­tity and cred­it­wor­thi­ness checks.

The per­son­al data trans­mit­ted to Klarna is usu­ally 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 neces­sary for the pro­cessing of an invoice or install­ment pur­chase. The pro­cessing of the pur­chase con­tract also requires such per­son­al data, which are in con­nec­tion with the respect­ive order. In par­tic­u­lar, the exchange of pay­ment inform­a­tion such as bank details, card num­ber, date of valid­ity and CVC code, cumu­lat­ive num­ber, item num­ber, data on goods and ser­vices, prices and taxes, inform­a­tion on the pre­vi­ous pur­chase beha­vi­or or oth­er details of the fin­an­cial situ­ation of the data subject.

The pur­pose of the trans­mis­sion of the data is, in par­tic­u­lar, the iden­ti­fic­a­tion check, pay­ment admin­is­tra­tion, and­fraud pre­ven­tion. The con­trol­ler shall provide Klarna with per­son­al data, in par­tic­u­lar, if a legit­im­ate interest in the trans­mis­sion exists. The per­son­al data exchanged between Klarna and the data sub­ject for the data pro­cessing shall be trans­mit­ted by Klarna to eco­nom­ic agen­cies. This trans­mis­sion is inten­ded for iden­tity and cred­it­wor­thi­ness checks.

Klarna shall also pass on the per­son­al data to affil­i­ates (Klarna Group) and ser­vice pro­viders or sub­con­tract­ors as far as this is neces­sary to ful­fill con­trac­tu­al oblig­a­tions or to pro­cess the data in the order.

Klarna col­lects and uses data and inform­a­tion on the pre­vi­ous pay­ment beha­vi­or of the data sub­ject as well as prob­ab­il­ity val­ues for their beha­vi­or in the future (so-called scor­ing) in order to decide on the reas­on­ing, imple­ment­a­tion or ter­min­a­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­tific­ally-recog­nized math­em­at­ic­al-stat­ist­ic­al methods.

The data sub­ject is able to revoke the con­sent to the hand­ling of per­son­al data at any time from Klarna. A revoc­a­tion shall not have any effect on per­son­al data which must be pro­cessed, used or trans­mit­ted in accord­ance with (con­trac­tu­al) pay­ment processing.

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

61. Pay­ment Meth­od: Data pro­tec­tion pro­vi­sions about the use of PayP­al as a pay­ment processor

On this web­site, the con­trol­ler has integ­rated com­pon­ents of PayP­al. PayP­al is an online pay­ment ser­vice pro­vider. Pay­ments are pro­cessed via so-called PayP­al accounts, which rep­res­ent vir­tu­al private or busi­ness accounts. PayP­al is also able to pro­cess vir­tu­al pay­ments through cred­it cards when a user does not have a PayP­al account. A PayP­al account is man­aged via an e‑mail address, which is why there are no clas­sic account num­bers. PayP­al makes it pos­sible to trig­ger online pay­ments to third parties or to receive pay­ments. PayP­al also accepts trust­ee func­tions and offers buy­er pro­tec­tion services.

The European oper­at­ing com­pany of PayP­al is PayP­al (Europe) S.à.r.l. & Cie. S.C.A., 22–24 Boulevard Roy­al, 2449 Lux­em­bourg, Luxembourg.

If the data sub­ject chooses “PayP­al” as the pay­ment option in the online shop dur­ing the order­ing pro­cess, we auto­mat­ic­ally trans­mit the data of the data sub­ject to PayP­al. 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 PayP­al is usu­ally first name, last name, address, email address, IP address, tele­phone num­ber, mobile phone num­ber, or oth­er data neces­sary for pay­ment pro­cessing. The pro­cessing of the pur­chase con­tract also requires such per­son­al data, which are in con­nec­tion with the respect­ive order.

The trans­mis­sion of the data is aimed at pay­ment pro­cessing and fraud pre­ven­tion. The con­trol­ler will trans­fer per­son­al data to PayP­al, in par­tic­u­lar, if a legit­im­ate interest in the trans­mis­sion is giv­en. The per­son­al data exchanged between PayP­al and the con­trol­ler for the pro­cessing of the data will be trans­mit­ted by PayP­al to eco­nom­ic cred­it agen­cies. This trans­mis­sion is inten­ded for iden­tity and cred­it­wor­thi­ness checks.

PayP­al will, if neces­sary, pass on per­son­al data to affil­i­ates and ser­vice pro­viders or sub­con­tract­ors to the extent that this is neces­sary to ful­fill con­trac­tu­al oblig­a­tions or for data to be pro­cessed in the order.

The data sub­ject has the pos­sib­il­ity to revoke con­sent for the hand­ling of per­son­al data at any time from PayP­al. A revoc­a­tion shall not have any effect on per­son­al data which must be pro­cessed, used or trans­mit­ted in accord­ance with (con­trac­tu­al) pay­ment processing.

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

62. Pay­ment Meth­od: Data pro­tec­tion pro­vi­sions about the use of Skrill as a pay­ment processor

On this web­site, the con­trol­ler has integ­rated com­pon­ents by Skrill. Skrill is an online pay­ment ser­vice pro­vider. 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­sib­il­ity 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­sible to trig­ger online pay­ments to third parties or to receive payments.

The oper­at­ing com­pany of Skrill is Skrill Lim­ited, Floor 27, 25 Canada Square, Lon­don, E14 5LQ, United Kingdom.

If the data sub­ject chooses “Skrill” as the pay­ment option dur­ing the order­ing pro­cess in our online-shop, the data will be trans­mit­ted auto­mat­ic­ally 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 neces­sary for pay­ment pro­cessing. The trans­mis­sion of data is aimed at pay­ment pro­cessing and fraud pre­ven­tion. The con­trol­ler will also provide Skrill with oth­er per­son­al data in the case, if a legit­im­ate interest 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 inten­ded for iden­tity and cred­it­wor­thi­ness checks.

If neces­sary, Skrill will pass on per­son­al data to affil­i­ates and ser­vice pro­viders or sub­con­tract­ors to the extent neces­sary to ful­fill con­trac­tu­al oblig­a­tions or to pro­cess the data in the order.

The data sub­ject has the pos­sib­il­ity to revoke the con­sent to the hand­ling of per­son­al data at any time from Skrill. A revoc­a­tion shall not have any effect on per­son­al data which must be pro­cessed, used or trans­mit­ted in accord­ance with (con­trac­tu­al) pay­ment processing.

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

63. Pay­ment Meth­od: Data pro­tec­tion pro­vi­sions about the use of Sofortüber­weisung as a pay­ment processor

On this web­site, the con­trol­ler has integ­rated com­pon­ents of Sofortüber­weisung. Sofortüber­weisung is a pay­ment ser­vice that allows cash­less pay­ment of products and ser­vices on the Inter­net. Sofortüber­weisung is a tech­nic­al pro­ced­ure by which the online deal­er imme­di­ately receives a pay­ment con­firm­a­tion. This enables a trader to deliv­er goods, ser­vices or down­loads to the cus­tom­er imme­di­ately after ordering.

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

If the data sub­ject chooses “imme­di­ate trans­fer” as the pay­ment option in our online shop dur­ing the order­ing pro­cess, 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­cessing via dir­ect 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­nic­al veri­fic­a­tion of the account status and retriev­al of addi­tion­al data to check the account assign­ment. The online trader is then auto­mat­ic­ally informed of the exe­cu­tion of the fin­an­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 neces­sary for pay­ment pro­cessing. The trans­mis­sion of the data is aimed at pay­ment pro­cessing and fraud pre­ven­tion. The con­trol­ler shall imme­di­ately trans­fer oth­er per­son­al data, even if a legit­im­ate interest in the trans­mis­sion exists. The per­son­al data exchanged between Sofortüber­weisung and the con­trol­ler shall be trans­mit­ted by Sofortüber­weisung to eco­nom­ic cred­it agen­cies. This trans­mis­sion is inten­ded for iden­tity and cred­it­wor­thi­ness checks.

Sofortüber­weisung provides per­son­al data to affil­i­ated com­pan­ies and ser­vice pro­viders or sub­con­tract­ors as far as this is neces­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­sib­il­ity to revoke the con­sent to the hand­ling of per­son­al data at any time from Sofortüber­weisung. A revoc­a­tion shall not have any effect on per­son­al data which must be pro­cessed, used or trans­mit­ted in accord­ance with (con­trac­tu­al) pay­ment processing.

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

64. Leg­al basis for the processing

Art. 6(1) lit. a GDPR serves as the leg­al basis for pro­cessing oper­a­tions for which we obtain con­sent for a spe­cif­ic pro­cessing pur­pose. If the pro­cessing of per­son­al data is neces­sary for the per­form­ance of a con­tract to which the data sub­ject is party, as is the case, for example, when pro­cessing oper­a­tions are neces­sary for the sup­ply of goods or to provide any oth­er ser­vice, the pro­cessing is based on Art­icle 6(1) lit. b GDPR. The same applies to such pro­cessing oper­a­tions which are neces­sary for car­ry­ing out pre-con­trac­tu­al meas­ures, for example in the case of inquir­ies con­cern­ing our products or ser­vices. Is our com­pany sub­ject to a leg­al oblig­a­tion by which pro­cessing of per­son­al data is required, such as for the ful­fill­ment of tax oblig­a­tions, the pro­cessing is based on Art. 6(1) lit. c GDPR. In rare cases, the pro­cessing of per­son­al data may be neces­sary to pro­tect the vital interests of the data sub­ject or of anoth­er nat­ur­al per­son. This would be the case, for example, if a vis­it­or were injured in our com­pany and his name, age, health insur­ance data or oth­er vital inform­a­tion would have to be passed on to a doc­tor, hos­pit­al or oth­er third party. Then the pro­cessing would be based on Art. 6(1) lit. d GDPR. Finally, pro­cessing oper­a­tions could be based on Art­icle 6(1) lit. f GDPR. This leg­al basis is used for pro­cessing oper­a­tions which are not covered by any of the above­men­tioned leg­al grounds, if pro­cessing is neces­sary for the pur­poses of the legit­im­ate interests pur­sued by our com­pany or by a third party, except where such interests are over­rid­den by the interests or fun­da­ment­al rights and freedoms of the data sub­ject which require pro­tec­tion of per­son­al data. Such pro­cessing oper­a­tions are par­tic­u­larly per­miss­ible because they have been spe­cific­ally men­tioned by the European legis­lat­or. He con­sidered that a legit­im­ate interest could be assumed if the data sub­ject is a cli­ent of the con­trol­ler (Recit­al 47 Sen­tence 2 GDPR).

65. The legit­im­ate interests pur­sued by the con­trol­ler or by a third party

Where the pro­cessing of per­son­al data is based on Art­icle 6(1) lit. f GDPR our legit­im­ate interest is to carry out our busi­ness in favor of the well-being of all our employ­ees and the shareholders.

66. Peri­od for which the per­son­al data will be stored

The cri­ter­ia used to determ­ine the peri­od of stor­age of per­son­al data is the respect­ive stat­utory reten­tion peri­od. After expir­a­tion of that peri­od, the cor­res­pond­ing data is routinely deleted, as long as it is no longer neces­sary for the ful­fill­ment of the con­tract or the ini­ti­ation of a contract.

67. Pro­vi­sion of per­son­al data as stat­utory or con­trac­tu­al require­ment; Require­ment neces­sary to enter into a con­tract; Oblig­a­tion of the data sub­ject to provide the per­son­al data; pos­sible con­sequences of fail­ure to provide such data

We cla­ri­fy that the pro­vi­sion of per­son­al data is partly required by law (e.g. tax reg­u­la­tions) or can also res­ult from con­trac­tu­al pro­vi­sions (e.g. inform­a­tion on the con­trac­tu­al part­ner). Some­times it may be neces­sary to con­clude a con­tract that the data sub­ject provides us with per­son­al data, which must sub­sequently be pro­cessed by us. The data sub­ject is, for example, obliged to provide us with per­son­al data when our com­pany signs a con­tract with him or her. The non-pro­vi­sion of the per­son­al data would have the con­sequence that the con­tract with the data sub­ject could not be con­cluded. Before per­son­al data is provided by the data sub­ject, the data sub­ject must con­tact any employ­ee. The employ­ee cla­ri­fies to the data sub­ject wheth­er the pro­vi­sion of the per­son­al data is required by law or con­tract or is neces­sary for the con­clu­sion of the con­tract, wheth­er there is an oblig­a­tion to provide the per­son­al data and the con­sequences of non-pro­vi­sion of the per­son­al data.

68. Exist­ence of auto­mated decision-making

As a respons­ible com­pany, we do not use auto­mat­ic decision-mak­ing or profiling.