• en
  • de
  • nl

Imprint and data pri­va­cy

Imprint and data pri­va­cy

Head­quar­ter

Pix­for­mance Sports GmbH Haupt­straße 19 – 20
14624 Dall­gow-Döberitz

Devel­op­ment Office

Helmholtzs­traße 2 – 9
GSG Hof/​Aufgang H 10587 Berlin
+49 (0)30 39 80 56 10
+49 (0)30 39 80 56 129 contact@pixformance.com

Gen­er­al

Man­ag­ing Direc­tor:
Valerie Bön­ström
Dis­trict Court:  Amts­gericht Pots­dam
Com­mer­cial Reg­is­ter: HRB 26981 P
VAT NR.: DE287614422

1. Pri­va­cy pol­i­cy


Thank you for your inter­est in using our plat­form. The pro­tec­tion of your per­son­al data is very impor­tant to us. In the fol­low­ing, you will find all impor­tant infor­ma­tion regard­ing the col­lec­tion, pro­cess­ing and use of per­son­al data that we only process in accor­dance with the pro­vi­sions of the data pro­tec­tion law. Per­son­al infor­ma­tion is infor­ma­tion relat­ing to an iden­ti­fied or iden­ti­fi­able nat­ur­al per­son; a nat­ur­al per­son is regard­ed as iden­ti­fi­able when they can be direct­ly or indi­rect­ly iden­ti­fied, in par­tic­u­lar by means of assign­ment to an iden­ti­fi­er such as a name, an iden­ti­fi­ca­tion num­ber, loca­tion data, an online ID, or by one or more spe­cial fea­tures which are the expres­sion of the phys­i­cal, phys­i­o­log­i­cal, genet­ic, men­tal, eco­nom­ic, cul­tur­al or social iden­ti­ty of that nat­ur­al per­son. The pro­vi­sion of your per­son­al data is vol­un­tary. How­ev­er, the func­tion­al­i­ty of our ser­vices may be restrict­ed as a result of a lack of data. The legal prin­ci­ples of data pro­tec­tion can be found among oth­ers in the EU Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR) and the Fed­er­al Data Pro­tec­tion Act (FDPA). Respon­si­ble body Respon­si­ble in the sense of GDPR, the nation­al data pro­tec­tion laws and oth­er data pro­tec­tion reg­u­la­tions is:

Pix­for­mance Sports GmbH, Haupt­str. 19 – 20, 14624 Berlin Ger­many

Man­ag­ing Director/​owner: Valerie-Bures Bön­ström [+49 (0)30 398 056 10]

[contact@pixformance.com] www​.pix​for​mance​.com

Data pro­tec­tion offi­cer Data pro­tec­tion offi­cer is: Chris­t­ian Büs­dorf c/​o colognet­worx cnx GmbH Weins­bergstr. 118a 50823 Cologne

1.Data sources and cat­e­gories of data:

We process per­son­al data that we receive from you dur­ing reg­is­tra­tion or in con­nec­tion with the use of fea­tures of our plat­form and the ser­vices pro­vid­ed by us. Depend­ing on the use, the rel­e­vant per­son­al data can be from the fol­low­ing cat­e­gories of data: — Name, first name — Con­tact details (address, email, phone) — Gen­der, lan­guage — Date of birth — Account infor­ma­tion, authen­ti­ca­tion data (e.g. QR code, user name, email) — Train­ing and usage data (fit­ness val­ues, train­ing plans and train­ing time, train­ing lev­el) — Weight, body mass, mus­cle, fat, body size, blood pres­sure, health-relat­ed fac­tors — Sys­tem data (IP address, serv­er data) If you gain access to our plat­form via the Pix­for­mance Sports GmbH spp, we also process — pro­vid­ed we have your approval — - loca­tion data, access data, trans­ac­tion data — device infor­ma­tion (device mod­el, oper­at­ing sys­tem, data on device events (e.g. crash­es by apps, sys­tem activ­i­ty and date and time of the request) for the pur­pose of improv­ing the app and our ser­vices

2.Purposes of pro­cess­ing

We process the per­son­al data for the pro­vi­sion and ful­fil­ment of the ser­vices offered to you in the con­text of the plat­form and to fur­ther devel­op and opti­mize our ser­vices

3.Legal bases:

If you have pro­vid­ed us with con­sent for the pro­cess­ing of your per­son­al data, this will serve as a legal basis in con­junc­tion with arti­cle 6 para­graph 1 (a) of the EU Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR). The con­tract in con­junc­tion with arti­cle 6 para­graph 1 (b) of the GDPR forms the legal basis for the pro­cess­ing of per­son­al data with a con­tract­ing par­ty which is nec­es­sary for the per­for­mance of a con­tract. This also applies to pro­cess­ing pro­ce­dures that are nec­es­sary for the imple­men­ta­tion of pre­con­trac­tu­al mea­sures. Where nec­es­sary, we process your data on the basis of arti­cle 6 para­graph 1 (f) GDPR beyond the actu­al ful­fil­ment of the con­tract to pro­tect our legit­i­mate inter­ests and those of a third par­ty. The legal or reg­u­la­to­ry oblig­a­tion in con­junc­tion with arti­cle 6 para­graph 1 © GDPR forms the legal basis as far as pro­cess­ing of per­son­al data for the per­for­mance of a legal oblig­a­tion is required. Data pro­cess­ing due to require­ments for the pro­tec­tion of vital inter­ests aris­es from the legal basis from arti­cle 6 para­graph 1 (d) GDPR. To pro­tect the legit­i­mate inter­ests of our com­pa­ny or a third par­ty, data can be processed beyond the actu­al per­for­mance of the con­tract on the basis of arti­cle 6 para­graph 1 (f) GDPR, inso­far as it is nec­es­sary and inter­ests, rights and fun­da­men­tal free­doms of the per­son con­tract do not pre­vail.

4.Disclosure to third par­ties:

Per­son­al data gen­er­at­ed by the use of the plat­form are not gen­er­al­ly dis­closed by us to third par­ties. The data shall par­tic­u­lar­ly not be trans­mit­ted to places out­side the EU. With­in our com­pa­ny, only offices and employ­ees who require your data for the pur­pose of pro­vid­ing our ser­vices, tech­ni­cal tasks and legal oblig­a­tions shall gain access to your data. More­over, ser­vice providers and proces­sors can obtain data for these pur­pos­es if they fol­low our pri­va­cy poli­cies and under­take to respect data con­fi­den­tial­i­ty. A trans­fer to third par­ties shall be car­ried out only in excep­tion­al cas­es and only if you have pro­vid­ed pri­or express con­sent. 5. Stor­age peri­od Data will be delet­ed when it is no longer nec­es­sary to meet the pur­pose of their col­lec­tion. If the pur­pose of the pro­cess­ing is omit­ted or a statu­to­ry stor­age peri­od should expire, the per­son­al data shall be blocked or delet­ed rou­tine­ly and in accor­dance with statu­to­ry pro­vi­sions. This is the case after no lat­er than sev­en days if data is saved in log files. Stor­age extend­ing beyond this is pos­si­ble. In this case, user iden­ti­fi­ca­tion (e.g. IP address­es) shall be delet­ed or anonymized, so to ensure that an attri­bu­tion of the retriev­ing client is no longer pos­si­ble. In the case of the col­lec­tion of data for the pro­vi­sion of online ser­vices, this is the case once that ses­sion has fin­ished.

Stor­age peri­od

Data will be delet­ed when it is no longer nec­es­sary to meet the pur­pose of their col­lec­tion. If the pur­pose of the pro­cess­ing is omit­ted or a statu­to­ry stor­age peri­od should expire, the per­son­al data shall be blocked or delet­ed rou­tine­ly and in accor­dance with statu­to­ry pro­vi­sions. This is the case after no lat­er than sev­en days if data is saved in log files. Stor­age extend­ing beyond this is pos­si­ble. In this case, user iden­ti­fi­ca­tion (e.g. IP address­es) shall be delet­ed or anonymized, so to ensure that attri­bu­tion of the retriev­ing client is no longer pos­si­ble. In the case of the col­lec­tion of data for the pro­vi­sion of online ser­vices, this is the case once that ses­sion has fin­ished.

5.Collection of gen­er­al data and infor­ma­tion

The web­site of the Blog col­lects a series of gen­er­al data and infor­ma­tion when a data sub­ject or auto­mat­ed sys­tem calls up the web­site. This gen­er­al data and infor­ma­tion are stored in the serv­er log files. Col­lect­ed may be (1) the brows­er types and ver­sions used, (2) the oper­at­ing sys­tem used by the access­ing sys­tem, (3) the web­site from which an access­ing sys­tem reach­es our web­site (so-called refer­rers), (4) the sub-web­sites, (5) the date and time of access to the Inter­net site, (6) an Inter­net pro­to­col address (IP address), (7) the Inter­net ser­vice provider of the access­ing sys­tem, and (8) any oth­er sim­i­lar data and infor­ma­tion that may be used in the event of attacks on our infor­ma­tion tech­nol­o­gy sys­tems.

When using these gen­er­al data and infor­ma­tion, the Blog does not draw any con­clu­sions about the data sub­ject. Rather, this infor­ma­tion is need­ed to (1) deliv­er the con­tent of our web­site cor­rect­ly, (2) opti­mize the con­tent of our web­site as well as its adver­tise­ment, (3) ensure the long-term via­bil­i­ty of our infor­ma­tion tech­nol­o­gy sys­tems and web­site tech­nol­o­gy, and (4) pro­vide law enforce­ment author­i­ties with the infor­ma­tion nec­es­sary for crim­i­nal pros­e­cu­tion in case of a cyber-attack. There­fore, the Blog ana­lyzes anony­mous­ly col­lect­ed data and infor­ma­tion sta­tis­ti­cal­ly, with the aim of increas­ing the data pro­tec­tion and data secu­ri­ty of our enter­prise and to ensure an opti­mal lev­el of pro­tec­tion for the per­son­al data we process. The anony­mous data of the serv­er log files are stored sep­a­rate­ly from all per­son­al data pro­vid­ed by a data sub­ject.

  1. 6.Routine era­sure and block­ing of per­son­al data

The data con­troller shall process and store the per­son­al data of the data sub­ject only for the peri­od nec­es­sary to achieve the pur­pose of stor­age, or as far as this is grant­ed by the Euro­pean leg­is­la­tor or oth­er leg­is­la­tors in laws or reg­u­la­tions to which the con­troller is sub­ject to.

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

7.Rights of the data sub­ject

  1. a) Right of con­fir­ma­tion

Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to obtain from the con­troller the con­fir­ma­tion as to whether or not per­son­al data con­cern­ing him or her are being processed. If a data sub­ject wish­es to avail him­self of this right of con­fir­ma­tion, he or she may, at any time, con­tact any employ­ee of the con­troller.

  1. b) Right of access

Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor to obtain from the con­troller-free infor­ma­tion about his or her per­son­al data stored at any time and a copy of this infor­ma­tion. Fur­ther­more, the Euro­pean direc­tives and reg­u­la­tions grant the data sub­ject access to the fol­low­ing infor­ma­tion:

the pur­pos­es of the pro­cess­ing;

the cat­e­gories of per­son­al data con­cerned;

the recip­i­ents or cat­e­gories of recip­i­ents to whom the per­son­al data have been or will be dis­closed, in par­tic­u­lar recip­i­ents in third coun­tries or inter­na­tion­al orga­ni­za­tions;

where pos­si­ble, the envis­aged peri­od for which the per­son­al data will be stored, or, if not pos­si­ble, the cri­te­ria used to deter­mine that peri­od;

the exis­tence of the right to request from the con­troller rec­ti­fi­ca­tion or era­sure of per­son­al data, or restric­tion of pro­cess­ing of per­son­al data con­cern­ing the data sub­ject, or to object to such pro­cess­ing;

the exis­tence of the right to lodge a com­plaint with a super­vi­so­ry author­i­ty;

where the per­son­al data are not col­lect­ed from the data sub­ject, any avail­able infor­ma­tion as to their source;

the exis­tence of auto­mat­ed deci­sion-mak­ing, includ­ing pro­fil­ing, referred to in Arti­cle 22(1) and (4) of the GDPR and, at least in those cas­es, mean­ing­ful infor­ma­tion about the log­ic involved, as well as the sig­nif­i­cance and envis­aged con­se­quences of such pro­cess­ing for the data sub­ject.

Fur­ther­more, the data sub­ject shall have a right to obtain infor­ma­tion as to whether per­son­al data are trans­ferred to a third coun­try or to an inter­na­tion­al orga­ni­za­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 trans­fer.

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

  1. c) Right to rec­ti­fi­ca­tion

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

If a data sub­ject wish­es to exer­cise this right to rec­ti­fi­ca­tion, he or she may, at any time, con­tact any employ­ee of the con­troller.

  1. d) Right to era­sure (Right to be for­got­ten)

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

The per­son­al data are no longer nec­es­sary in rela­tion to the pur­pos­es for which they were col­lect­ed or oth­er­wise processed.

The data sub­ject with­draws con­sent to which the pro­cess­ing is based accord­ing to the point (a) of Arti­cle 6(1) of the GDPR, or point (a) of Arti­cle 9(2) of the GDPR, and where there is no oth­er legal ground for the pro­cess­ing.

The data sub­ject objects to the pro­cess­ing pur­suant to Arti­cle 21(1) of the GDPR and there are no over­rid­ing legit­i­mate grounds for the pro­cess­ing or the data sub­ject objects to the pro­cess­ing pur­suant to Arti­cle 21(2) of the GDPR.

The per­son­al data have been unlaw­ful­ly processed.

The per­son­al data must be erased for com­pli­ance with a legal oblig­a­tion in Union or Mem­ber State law to which the con­troller is sub­ject.

The per­son­al data have been col­lect­ed in rela­tion to the offer of infor­ma­tion soci­ety ser­vices referred to in Arti­cle 8(1) of the GDPR.

If one of the afore­men­tioned rea­sons applies, and a data sub­ject wish­es to request the era­sure of per­son­al data stored by the Blog, he or she may, at any time, con­tact any employ­ee of the con­troller. An employ­ee of Blog shall prompt­ly ensure that the era­sure request is com­plied with imme­di­ate­ly.

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

  1. e) The right of restric­tion of pro­cess­ing

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

The accu­ra­cy of the per­son­al data is con­test­ed by the data sub­ject, for a peri­od enabling the con­troller to ver­i­fy the accu­ra­cy of the per­son­al data.

The pro­cess­ing is unlaw­ful and the data sub­ject oppos­es the era­sure of the per­son­al data and requests instead of the restric­tion of their use instead.

The con­troller no longer needs the per­son­al data for the pur­pos­es of the pro­cess­ing, but they are required by the data sub­ject for the estab­lish­ment, exer­cise or defense of legal claims.

The data sub­ject has object­ed to pro­cess­ing pur­suant to Arti­cle 21(1) of the GDPR pend­ing the ver­i­fi­ca­tion whether the legit­i­mate grounds of the con­troller over­ride those of the data sub­ject.

If one of the afore­men­tioned con­di­tions is met, and a data sub­ject wish­es to request the restric­tion of the pro­cess­ing of per­son­al data stored by the Blog, he or she may at any time con­tact any employ­ee of the con­troller. The employ­ee of the Blog will arrange the restric­tion of the pro­cess­ing.

  1. f) Right to data porta­bil­i­ty

Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor, to receive the per­son­al data con­cern­ing him or her, which was pro­vid­ed to a con­troller, in a struc­tured, com­mon­ly used and machine-read­able for­mat. He or she shall have the right to trans­mit those data to anoth­er con­troller with­out hin­drance from the con­troller to which the per­son­al data have been pro­vid­ed, as long as the pro­cess­ing is based on con­sent pur­suant to point (a) of Arti­cle 6(1) of the GDPR or point (a) of Arti­cle 9(2) of the GDPR, or on a con­tract pur­suant to point (b) of Arti­cle 6(1) of the GDPR, and the pro­cess­ing is car­ried out by auto­mat­ed means, as long as the pro­cess­ing is not nec­es­sary for the per­for­mance of a task car­ried out in the pub­lic inter­est or in the exer­cise of offi­cial author­i­ty vest­ed in the con­troller.

Fur­ther­more, in exer­cis­ing his or her right to data porta­bil­i­ty pur­suant to Arti­cle 20(1) of the GDPR, the data sub­ject shall have the right to have per­son­al data trans­mit­ted direct­ly from one con­troller to anoth­er, where tech­ni­cal­ly fea­si­ble and when doing so does not adverse­ly affect the rights and free­doms of oth­ers.

In order to assert the right to data porta­bil­i­ty, the data sub­ject may at any time con­tact any employ­ee of the Blog.

  1. g) Right to object

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

The Blog shall no longer process the per­son­al data in the event of the objec­tion unless we can demon­strate com­pelling legit­i­mate grounds for the pro­cess­ing which over­ride the inter­ests, rights, and free­doms of the data sub­ject, or for the estab­lish­ment, exer­cise or defense of legal claims.

If the Blog process­es per­son­al data for direct mar­ket­ing pur­pos­es, the data sub­ject shall have the right to object at any time to the pro­cess­ing of per­son­al data con­cern­ing him or her for such mar­ket­ing. This applies to pro­file to the extent that it is relat­ed to such direct mar­ket­ing. If the data sub­ject objects to the Blog to the pro­cess­ing for direct mar­ket­ing pur­pos­es, the Blog will no longer process the per­son­al data for these pur­pos­es.

In addi­tion, the data sub­ject has the right, on grounds relat­ing to his or her par­tic­u­lar sit­u­a­tion, to object to pro­cess­ing of per­son­al data con­cern­ing him or her by the Blog for sci­en­tif­ic or his­tor­i­cal research pur­pos­es, or for sta­tis­ti­cal pur­pos­es pur­suant to Arti­cle 89(1) of the GDPR, unless the pro­cess­ing is nec­es­sary for the per­for­mance of a task car­ried out for rea­sons of pub­lic inter­est.

In order to exer­cise the right to object, the data sub­ject may con­tact any employ­ee of the Blog. In addi­tion, the data sub­ject is free in the con­text of the use of infor­ma­tion soci­ety ser­vices, and notwith­stand­ing Direc­tive 2002/​58/​EC, to use his or her right to object by auto­mat­ed means using tech­ni­cal spec­i­fi­ca­tions.

  1. h) Auto­mat­ed indi­vid­ual deci­sion-mak­ing, includ­ing pro­fil­ing

Each data sub­ject shall have the right grant­ed by the Euro­pean leg­is­la­tor not to be sub­ject to a deci­sion based sole­ly on auto­mat­ed pro­cess­ing, includ­ing pro­fil­ing, which pro­duces legal effects con­cern­ing him or her, or sim­i­lar­ly sig­nif­i­cant­ly affects him or her, as long as the deci­sion (1) is not is nec­es­sary for enter­ing into, or the per­for­mance of, a con­tract between the data sub­ject and a data con­troller, or (2) is not autho­rised by Union or Mem­ber State law to which the con­troller is sub­ject and which also lays down suit­able mea­sures to safe­guard the data subject’s rights and free­doms and legit­i­mate inter­ests, or (3) is not based on the data subject’s explic­it con­sent.

If the deci­sion (1) is nec­es­sary for enter­ing into, or the per­for­mance of, a con­tract between the data sub­ject and a data con­troller, or (2) it is based on the data subject’s explic­it con­sent, the Blog shall imple­ment suit­able mea­sures to safe­guard the data subject’s rights and free­doms and legit­i­mate inter­ests, at least the right to obtain human inter­ven­tion on the part of the con­troller, to express his or her point of view and con­test the deci­sion.

If the data sub­ject wish­es to exer­cise the rights con­cern­ing auto­mat­ed indi­vid­ual deci­sion-mak­ing, he or she may, at any time, con­tact any employ­ee of the Blog.

  1. i) Right to with­draw data pro­tec­tion con­sent

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

If the data sub­ject wish­es to exer­cise the right to with­draw the con­sent, he or she may, at any time, con­tact any employ­ee of the Blog.

8.Cookies

Our online plat­form uses cook­ies to rec­og­nize mul­ti­ple uses of our web­site by the same users/​internet con­nec­tion own­ers. Cook­ies are small text files that are filed and stored by your inter­net brows­er on your com­put­er. They are used to facil­i­tate the use of online plat­forms for users and to improve our web­site and our ser­vices. Some fea­tures of our web­site are not offered with­out the use of cook­ies. For them to work it is nec­es­sary that the brows­er is rec­og­nized even after chang­ing the page. The recog­ni­tion is pos­si­ble because the IP address is stored in the cook­ies. The legal basis for the pro­cess­ing of per­son­al data by using tech­ni­cal­ly required cook­ies is in our legit­i­mate inter­est in accor­dance with arti­cle 6 para­graph 1 (f) of the GDPR. The legal basis for the pro­cess­ing of per­son­al data by using cook­ies for ana­lyt­i­cal pur­pos­es is the required con­sent of the user in con­junc­tion with arti­cle 6 para­graph 1 (a) of the GDPR.

9.Server data

For tech­ni­cal oper­a­tions, data that is trans­mit­ted through your inter­net brows­er is col­lect­ed (so-called serv­er log files). These include brows­er type and ver­sion — oper­at­ing sys­tem used – the web­site from which you vis­it us (refer­rer URL) – the web­site that you vis­it — date and time of access — your Inter­net Pro­to­col (IP) address. The data thus trans­mit­ted is stored anony­mous­ly and sep­a­rate from per­son­al data. It is stored in log files to ensure the func­tion­al­i­ty of the online plat­form. In addi­tion, the data serves to opti­mize the plat­form and ensure the secu­ri­ty of our infor­ma­tion tech­nol­o­gy sys­tems. This is also the basis for our legit­i­mate inter­est in data pro­cess­ing as a legal basis in accor­dance with arti­cle 6 para­graph 1 (f) of the GDPR.

  • 10.Newsletter

Sub­scrip­tion to our newslet­ter

If you would like to receive our newslet­ter, we require a valid email address as well as infor­ma­tion that allows us to ver­i­fy that you are the own­er of the spec­i­fied email address and that you agree to receive this newslet­ter. No addi­tion­al data is col­lect­ed or is only col­lect­ed on a vol­un­tary basis. We only use this data to send the request­ed infor­ma­tion and do not pass it on to third par­ties.

We will, there­fore, process any data you enter onto the con­tact form only with your con­sent per Art. 6 (1) (a) DSGVO. You can revoke con­sent to the stor­age of your data and email address as well as their use for send­ing the newslet­ter at any time, e.g. through the “unsub­scribe” link in the newslet­ter. The data processed before we receive your request may still be legal­ly processed.

The data pro­vid­ed when reg­is­ter­ing for the newslet­ter will be used to dis­trib­ute the newslet­ter until you can­cel your sub­scrip­tion when said data will be delet­ed. Data we have stored for oth­er pur­pos­es (e.g. email address­es for the mem­bers’ area) remain unaf­fect­ed.

11.MailChimp

This web­site uses the ser­vices of MailChimp for send­ing newslet­ters. The provider is the Rock­et Sci­ence Group LLC, 675 Ponce De Leon Ave. NE, Suite 5000, Atlanta, GA 30308, USA. MailChimp is a ser­vice that helps u.a. the dis­patch of newslet­ters can be orga­nized and ana­lyzed.

If you enter dates for the pur­pos­es of newslet­ter sub­scrip­tion (e.g., e-mail address), they will be stored on MailChimp’s servers in the Unit­ed States. MailChimp is cer­ti­fied under the EU-US Pri­va­cy Shield. The Pri­va­cy Shield is an agree­ment between the Euro­pean Union (EU) and the US to ensure com­pli­ance with Euro­pean pri­va­cy stan­dards in the Unit­ed States. With the help of MailChimp, we can ana­lyze our newslet­ter cam­paigns. When you open an e-mail sent by MailChimp, a file includ­ed in the e-mail (called web bea­con) con­nects to MailChimp’s servers in the Unit­ed States. This way you can deter­mine if a newslet­ter mes­sage has been opened and which links have been clicked on. In addi­tion, tech­ni­cal infor­ma­tion is col­lect­ed (e.g., time of retrieval, IP address, brows­er type, and oper­at­ing sys­tem). This infor­ma­tion can­not be assigned to the respec­tive newslet­ter recip­i­ent. They are used exclu­sive­ly for the sta­tis­ti­cal analy­sis of newslet­ter cam­paigns. The results of these ana­lyzes can be used to bet­ter tai­lor future newslet­ters to the inter­ests of the recip­i­ent.

If you do not want analy­sis by MailChimp, unsub­scribe from the newslet­ter. For this pur­pose, we pro­vide a link in every newslet­ter mes­sage. Fur­ther­more, you can unsub­scribe from the newslet­ter direct­ly on the web­site. Data pro­cess­ing is based on your con­sent (Arti­cle 6 (1) (a) GDPR). You can revoke this con­sent at any time by unsub­scrib­ing from the newslet­ter. The legal­i­ty of the already com­plet­ed data pro­cess­ing oper­a­tions remains unaf­fect­ed by the revo­ca­tion. The data deposit­ed with us for the pur­pose of obtain­ing the newslet­ter will be stored by us from the newslet­ter until it has been removed from the newslet­ter and, after unsub­scrib­ing from the newslet­ter, delet­ed both from our servers and from the servers of MailChimp.

Data stored for oth­er pur­pos­es with us remain unaf­fect­ed. For details, see the pri­va­cy pol­i­cy of MailChimp at: https://​mailchimp​.com/​l​e​g​a​l​/​t​e​r​ms/.

12​.Con​tact pos­si­bil­i­ty via the web­site

The web­site of the Pix­for­mance Sports GmbH con­tains infor­ma­tion that enables a quick elec­tron­ic con­tact to our enter­prise, as well as direct com­mu­ni­ca­tion with us, which also includes a gen­er­al address of the so-called elec­tron­ic mail (e-mail address). If a data sub­ject con­tacts the con­troller by e-mail or via a con­tact form, the per­son­al data trans­mit­ted by the data sub­ject are auto­mat­i­cal­ly stored. Such per­son­al data trans­mit­ted on a vol­un­tary basis by a data sub­ject to the data con­troller are stored for the pur­pose of pro­cess­ing or con­tact­ing the data sub­ject. There is no trans­fer of this per­son­al data to third par­ties.

13.Routine era­sure and block­ing of per­son­al data

The data con­troller shall process and store the per­son­al data of the data sub­ject only for the peri­od nec­es­sary to achieve the pur­pose of stor­age, or as far as this is grant­ed by the Euro­pean leg­is­la­tor or oth­er leg­is­la­tors in laws or reg­u­la­tions to which the con­troller is sub­ject to.

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

  • 14​.Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of Face­book

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

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

With each call-up to one of the indi­vid­ual pages of this Inter­net web­site, which is oper­at­ed by the con­troller and into which a Face­book com­po­nent (Face­book plug-ins) was inte­grat­ed, the web brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed to down­load dis­play of the cor­re­spond­ing Face­book com­po­nent from Face­book through the Face­book com­po­nent. An overview of all the Face­book Plug-ins may be accessed under https://​devel​op​ers​.face​book​.com/​d​o​c​s​/​p​l​u​g​i​ns/. Dur­ing the course of this tech­ni­cal pro­ce­dure, Face­book is made aware of what spe­cif­ic sub-site of our web­site was vis­it­ed by the data sub­ject.

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

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

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

  • 15. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of Google Ana­lyt­ics (with anonymiza­tion func­tion)

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

The oper­a­tor of the Google Ana­lyt­ics com­po­nent is Google Inc., 1600 Amphithe­atre Pkwy, Moun­tain View, CA 94043 – 1351, Unit­ed States.

For the web ana­lyt­ics through Google Ana­lyt­ics the con­troller uses the appli­ca­tion “_​gat. _​anonymizeIp”. By means of this appli­ca­tion the IP address of the Inter­net con­nec­tion of the data sub­ject is abridged by Google and anonymized when access­ing our web­sites from a Mem­ber State of the Euro­pean Union or anoth­er Con­tract­ing State to the Agree­ment on the Euro­pean Eco­nom­ic Area.

The pur­pose of the Google Ana­lyt­ics com­po­nent is to ana­lyze the traf­fic on our web­site. Google uses the col­lect­ed data and infor­ma­tion, inter alia, to eval­u­ate the use of our web­site and to pro­vide online reports, which show the activ­i­ties on our web­sites, and to pro­vide oth­er ser­vices con­cern­ing the use of our Inter­net site for us.

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

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

The data sub­ject may, as stat­ed above, pre­vent the set­ting of cook­ies through our web­site at any time by means of a cor­re­spond­ing adjust­ment of the web brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such an adjust­ment to the Inter­net brows­er used would also pre­vent Google Ana­lyt­ics from set­ting a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. In addi­tion, cook­ies already in use by Google Ana­lyt­ics may be delet­ed at any time via a web brows­er or oth­er soft­ware pro­grams.

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

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google may be retrieved under https://​www​.google​.com/​i​n​t​l​/​e​n​/​p​o​l​i​c​i​e​s​/​p​r​i​v​a​cy/ and under http://​www​.google​.com/​a​n​a​l​y​t​i​c​s​/​t​e​r​m​s​/​u​s​.​h​tml. Google Ana­lyt­ics is fur­ther explained under the fol­low­ing Link https://​www​.google​.com/​a​n​a​l​y​t​i​cs/.

  • 16. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of Google AdWords

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

The oper­at­ing com­pa­ny of Google AdWords is Google Inc., 1600 Amphithe­atre 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­e­vant adver­tis­ing on the web­sites of third par­ties and in the search engine results of the search engine Google and an inser­tion of third-par­ty adver­tis­ing on our web­site.

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

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

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

The data sub­ject may, at any time, pre­vent the set­ting of cook­ies by our web­site, as stat­ed above, by means of a cor­re­spond­ing set­ting of the Inter­net brows­er used and thus per­ma­nent­ly deny the set­ting of cook­ies. Such a set­ting of the Inter­net brows­er used would also pre­vent Google from plac­ing a con­ver­sion cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. In addi­tion, a cook­ie set by Google AdWords may be delet­ed at any time via the Inter­net brows­er or oth­er soft­ware pro­grams.

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

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Google may be retrieved under https://​www​.google​.com/​i​n​t​l​/​e​n​/​p​o​l​i​c​i​e​s​/​p​r​i​v​a​cy/.

  • 17. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of Insta­gram

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

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

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which an Insta­gram com­po­nent (Ins­ta but­ton) was inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed to the down­load of a dis­play of the cor­re­spond­ing Insta­gram com­po­nent of Insta­gram. Dur­ing the course of this tech­ni­cal pro­ce­dure, Insta­gram becomes aware of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data sub­ject.

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

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

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Insta­gram may be retrieved under https://​help​.insta​gram​.com/​1​5​5​8​3​3​7​0​7​9​0​0​388 and https://​www​.insta​gram​.com/​a​b​o​u​t​/​l​e​g​a​l​/​p​r​i​v​a​cy/.

  • 18. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of LinkedIn

The con­troller has inte­grat­ed com­po­nents of the LinkedIn Cor­po­ra­tion on this web­site. LinkedIn is a web-based social net­work that enables users with exist­ing busi­ness con­tacts to con­nect and to make new busi­ness con­tacts. Over 400 mil­lion reg­is­tered peo­ple in more than 200 coun­tries use LinkedIn. Thus, LinkedIn is cur­rent­ly the largest plat­form for busi­ness con­tacts and one of the most vis­it­ed web­sites in the world.

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

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a LinkedIn com­po­nent (LinkedIn plug-in) was inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed to the down­load of a dis­play of the cor­re­spond­ing LinkedIn com­po­nent of LinkedIn. Fur­ther infor­ma­tion about the LinkedIn plug-in may be accessed under https://​devel​op​er​.linkedin​.com/​p​l​u​g​ins. Dur­ing the course of this tech­ni­cal pro­ce­dure, LinkedIn gains knowl­edge of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data sub­ject.

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

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

LinkedIn pro­vides under https://​www​.linkedin​.com/​p​s​e​t​t​i​n​g​s​/​g​u​e​s​t​-​c​o​n​t​r​ols the pos­si­bil­i­ty to unsub­scribe from e-mail mes­sages, SMS mes­sages and tar­get­ed ads, as well as the abil­i­ty to man­age ad set­tings. LinkedIn also uses affil­i­ates such as Éire, Google Ana­lyt­ics, BlueKai, Dou­bleClick, Nielsen, Com­score, Elo­qua, and Lotame. The set­ting of such cook­ies may be denied under https://​www​.linkedin​.com/​l​e​g​a​l​/​c​o​o​k​i​e​-​p​o​l​icy. The applic­a­ble pri­va­cy pol­i­cy for LinkedIn is avail­able under https://​www​.linkedin​.com/​l​e​g​a​l​/​p​r​i​v​a​c​y​-​p​o​l​icy. The LinkedIn Cook­ie Pol­i­cy is avail­able under https://​www​.linkedin​.com/​l​e​g​a​l​/​c​o​o​k​i​e​-​p​o​l​icy.

  • 19. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of Xing

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

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

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

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

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

The data pro­tec­tion pro­vi­sions pub­lished by XING, which is avail­able under https://​www​.xing​.com/​p​r​i​v​acy, pro­vide infor­ma­tion on the col­lec­tion, pro­cess­ing and use of per­son­al data by XING. In addi­tion, XING has pub­lished pri­va­cy notices for the XING share but­ton under https://​www​.xing​.com/​a​p​p​/​s​h​a​r​e​?​o​p​=​d​a​t​a​_​p​r​o​t​e​c​t​ion.

  • 20. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of YouTube

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

The oper­at­ing com­pa­ny of YouTube is YouTube, LLC, 901 Cher­ry Ave., San Bruno, CA 94066, UNITED STATES. The YouTube, LLC is a sub­sidiary of Google Inc., 1600 Amphithe­atre Pkwy, Moun­tain View, CA 94043 – 1351, UNITED STATES.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a YouTube com­po­nent (YouTube video) was inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed to down­load a dis­play of the cor­re­spond­ing YouTube com­po­nent. Fur­ther infor­ma­tion about YouTube may be obtained under https://​www​.youtube​.com/​y​t​/​a​b​o​u​t​/​en/. Dur­ing the course of this tech­ni­cal pro­ce­dure, YouTube and Google gain knowl­edge of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data sub­ject.

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

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

YouTube’s data pro­tec­tion pro­vi­sions, avail­able at https://​www​.google​.com/​i​n​t​l​/​e​n​/​p​o​l​i​c​i​e​s​/​p​r​i​v​a​cy/, pro­vide infor­ma­tion about the col­lec­tion, pro­cess­ing and use of per­son­al data by YouTube and Google.

21. Legal basis for the pro­cess­ing

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

  • 22. Google Web Fonts

For uni­form rep­re­sen­ta­tion of fonts, this page uses web fonts pro­vid­ed by Google. When you open a page, your brows­er loads the required web fonts into your brows­er cache to dis­play texts and fonts cor­rect­ly.

For this pur­pose, your brows­er has to estab­lish a direct con­nec­tion to Google servers. Google thus becomes aware that our web page was accessed via your IP address. The use of Google Web fonts is done in the inter­est of a uni­form and attrac­tive pre­sen­ta­tion of our web­site. This con­sti­tutes a jus­ti­fied inter­est pur­suant to Art. 6 (1) (f) DSGVO.

If your brows­er does not sup­port web fonts, a stan­dard font is used by your com­put­er.

Fur­ther infor­ma­tion about han­dling user data, can be found at https://​devel​op​ers​.google​.com/​f​o​n​t​s​/​faq and in Google’s pri­va­cy pol­i­cy at https://​www​.google​.com/​p​o​l​i​c​i​e​s​/​p​r​i​v​a​cy/.

CHANGES TO THIS DATA PRIVACY STATEMENT

PIXFORMANCE Sports GmbH reserves the right to change this data pri­va­cy state­ment.

Sta­tus: Octo­ber 2018