We are very deligh­ted that you have shown inte­rest in our enter­pri­se. Data pro­tec­tion is of a par­ti­cu­lar­ly high prio­ri­ty for Sebas­ti­an Neu­haus. The use of the Inter­net pages of Sebas­ti­an Neu­haus is pos­si­ble wit­hout any indi­ca­ti­on of per­so­nal data; howe­ver, if a data sub­ject wants to use spe­cial enter­pri­se ser­vices via our web­site, pro­ces­sing of per­so­nal data could beco­me neces­sa­ry. If the pro­ces­sing of per­so­nal data is neces­sa­ry and the­re is no sta­tu­to­ry basis for such pro­ces­sing, we gene­ral­ly obtain con­sent from the data subject.

The pro­ces­sing of per­so­nal data, such as the name, address, e‑mail address, or tele­pho­ne num­ber of a data sub­ject shall always be in line with the Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR), and in accordance with the coun­try-spe­ci­fic data pro­tec­tion regu­la­ti­ons appli­ca­ble to Sebas­ti­an Neu­haus. By means of this data pro­tec­tion decla­ra­ti­on, our enter­pri­se would like to inform the gene­ral public of the natu­re, scope, and pur­po­se of the per­so­nal data we coll­ect, use and pro­cess. Fur­ther­mo­re, data sub­jects are infor­med, by means of this data pro­tec­tion decla­ra­ti­on, of the rights to which they are entitled.

As the con­trol­ler, Sebas­ti­an Neu­haus has imple­men­ted num­e­rous tech­ni­cal and orga­niza­tio­nal mea­su­res to ensu­re the most com­ple­te pro­tec­tion of per­so­nal data pro­ces­sed through this web­site. Howe­ver, Inter­net-based data trans­mis­si­ons may in prin­ci­ple have secu­ri­ty gaps, so abso­lu­te pro­tec­tion may not be gua­ran­teed. For this reason, every data sub­ject is free to trans­fer per­so­nal data to us via alter­na­ti­ve means, e.g. by telephone.

1. Definitions

The data pro­tec­tion decla­ra­ti­on of Sebas­ti­an Neu­haus is based on the terms used by the Euro­pean legis­la­tor for the adop­ti­on of the Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR). Our data pro­tec­tion decla­ra­ti­on should be legi­ble and under­stan­da­ble for the gene­ral public, as well as our cus­to­mers and busi­ness part­ners. To ensu­re this, we would like to first explain the ter­mi­no­lo­gy used.

In this data pro­tec­tion decla­ra­ti­on, we use, inter alia, the fol­lo­wing terms:

• a) Personal data

  Per­so­nal data means any infor­ma­ti­on rela­ting to an iden­ti­fied or iden­ti­fia­ble natu­ral per­son (“data sub­ject”). An iden­ti­fia­ble natu­ral per­son is one who can be iden­ti­fied, direct­ly or indi­rect­ly, in par­ti­cu­lar by refe­rence to an iden­ti­fier such as a name, an iden­ti­fi­ca­ti­on num­ber, loca­ti­on data, an online iden­ti­fier or to one or more fac­tors spe­ci­fic to the phy­si­cal, phy­sio­lo­gi­cal, gene­tic, men­tal, eco­no­mic, cul­tu­ral or social iden­ti­ty of that natu­ral person.

• b) Data subject

  Data sub­ject is any iden­ti­fied or iden­ti­fia­ble natu­ral per­son, who­se per­so­nal data is pro­ces­sed by the con­trol­ler respon­si­ble for the processing.

• c) Processing

  Pro­ces­sing is any ope­ra­ti­on or set of ope­ra­ti­ons which is per­for­med on per­so­nal data or on sets of per­so­nal data, whe­ther or not by auto­ma­ted means, such as coll­ec­tion, recor­ding, orga­ni­sa­ti­on, struc­tu­ring, sto­rage, adapt­a­ti­on or altera­ti­on, retrie­val, con­sul­ta­ti­on, use, dis­clo­sure by trans­mis­si­on, dis­se­mi­na­ti­on or other­wi­se making available, ali­gnment or com­bi­na­ti­on, rest­ric­tion, era­su­re or destruction.

• d) Restriction of processing

  Rest­ric­tion of pro­ces­sing is the mar­king of stored per­so­nal data with the aim of limi­ting their pro­ces­sing in the future.

• e) Profiling

  Pro­fil­ing means any form of auto­ma­ted pro­ces­sing of per­so­nal data con­sis­ting of the use of per­so­nal data to eva­lua­te cer­tain per­so­nal aspects rela­ting to a natu­ral per­son, in par­ti­cu­lar to ana­ly­se or pre­dict aspects con­cer­ning that natu­ral person’s per­for­mance at work, eco­no­mic situa­ti­on, health, per­so­nal pre­fe­ren­ces, inte­rests, relia­bi­li­ty, beha­viour, loca­ti­on or movements.

• f) Pseudonymisation

  Pseud­ony­mi­sa­ti­on is the pro­ces­sing of per­so­nal data in such a man­ner that the per­so­nal data can no lon­ger be attri­bu­ted to a spe­ci­fic data sub­ject wit­hout the use of addi­tio­nal infor­ma­ti­on, pro­vi­ded that such addi­tio­nal infor­ma­ti­on is kept sepa­ra­te­ly and is sub­ject to tech­ni­cal and orga­ni­sa­tio­nal mea­su­res to ensu­re that the per­so­nal data are not attri­bu­ted to an iden­ti­fied or iden­ti­fia­ble natu­ral person.

• g) Controller or controller responsible for the processing

  Con­trol­ler or con­trol­ler respon­si­ble for the pro­ces­sing is the natu­ral or legal per­son, public aut­ho­ri­ty, agen­cy or other body which, alo­ne or joint­ly with others, deter­mi­nes the pur­po­ses and means of the pro­ces­sing of per­so­nal data; whe­re the pur­po­ses and means of such pro­ces­sing are deter­mi­ned by Uni­on or Mem­ber Sta­te law, the con­trol­ler or the spe­ci­fic cri­te­ria for its nomi­na­ti­on may be pro­vi­ded for by Uni­on or Mem­ber Sta­te law.

• h) Processor

  Pro­ces­sor is a natu­ral or legal per­son, public aut­ho­ri­ty, agen­cy or other body which pro­ces­ses per­so­nal data on behalf of the controller.

• i) Recipient

  Reci­pi­ent is a natu­ral or legal per­son, public aut­ho­ri­ty, agen­cy or ano­ther body, to which the per­so­nal data are dis­c­lo­sed, whe­ther a third par­ty or not. Howe­ver, public aut­ho­ri­ties which may recei­ve per­so­nal data in the frame­work of a par­ti­cu­lar inquiry in accordance with Uni­on or Mem­ber Sta­te law shall not be regard­ed as reci­pi­ents; the pro­ces­sing of tho­se data by tho­se public aut­ho­ri­ties shall be in com­pli­ance with the appli­ca­ble data pro­tec­tion rules accor­ding to the pur­po­ses of the processing.

• j) Third party

  Third par­ty is a natu­ral or legal per­son, public aut­ho­ri­ty, agen­cy or body other than the data sub­ject, con­trol­ler, pro­ces­sor and per­sons who, under the direct aut­ho­ri­ty of the con­trol­ler or pro­ces­sor, are aut­ho­ri­sed to pro­cess per­so­nal data.

• k) Consent

  Con­sent of the data sub­ject is any free­ly given, spe­ci­fic, infor­med and unam­bi­guous indi­ca­ti­on of the data subject’s wis­hes by which he or she, by a state­ment or by a clear affir­ma­ti­ve action, signi­fies agree­ment to the pro­ces­sing of per­so­nal data rela­ting to him or her.

2. Name and Address of the controller

Con­trol­ler for the pur­po­ses of the Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR), other data pro­tec­tion laws appli­ca­ble in Mem­ber sta­tes of the Euro­pean Uni­on and other pro­vi­si­ons rela­ted to data pro­tec­tion is:

Sebas­ti­an Neu­haus
Schuess­ler­stras­se 16
40474 Dues­sel­dorf
Ger­ma­ny
Pho­ne +49 211 5162 9644
Email: mail@braunaudio.de
Web­site: www.braunaudio.de

3. Cookies

The Inter­net pages of Sebas­ti­an Neu­haus use coo­kies. Coo­kies are text files that are stored in a com­pu­ter sys­tem via an Inter­net browser.

Many Inter­net sites and ser­vers use coo­kies. Many coo­kies con­tain a so-cal­led coo­kie ID. A coo­kie ID is a uni­que iden­ti­fier of the coo­kie. It con­sists of a cha­rac­ter string through which Inter­net pages and ser­vers can be assi­gned to the spe­ci­fic Inter­net brow­ser in which the coo­kie was stored. This allows visi­ted Inter­net sites and ser­vers to dif­fe­ren­tia­te the indi­vi­du­al brow­ser of the dats sub­ject from other Inter­net brow­sers that con­tain other coo­kies. A spe­ci­fic Inter­net brow­ser can be reco­gni­zed and iden­ti­fied using the uni­que coo­kie ID.

Through the use of coo­kies, Sebas­ti­an Neu­haus can pro­vi­de the users of this web­site with more user-fri­end­ly ser­vices that would not be pos­si­ble wit­hout the coo­kie setting.

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

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

4. Collection of general data and information

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

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

5. Subscription to our newsletters

On the web­site of Sebas­ti­an Neu­haus, users are given the oppor­tu­ni­ty to sub­scri­be to our enterprise’s news­let­ter. The input mask used for this pur­po­se deter­mi­nes what per­so­nal data are trans­mit­ted, as well as when the news­let­ter is orde­red from the controller.

Sebas­ti­an Neu­haus informs its cus­to­mers and busi­ness part­ners regu­lar­ly by means of a news­let­ter about enter­pri­se offers. The enterprise’s news­let­ter may only be recei­ved by the data sub­ject if (1) the data sub­ject has a valid e‑mail address and (2) the data sub­ject regis­ters for the news­let­ter ship­ping. A con­fir­ma­ti­on e‑mail will be sent to the e‑mail address regis­tered by a data sub­ject for the first time for news­let­ter ship­ping, for legal reasons, in the dou­ble opt-in pro­ce­du­re. This con­fir­ma­ti­on e‑mail is used to pro­ve whe­ther the owner of the e‑mail address as the data sub­ject is aut­ho­ri­zed to recei­ve the newsletter.

During the regis­tra­ti­on for the news­let­ter, we also store the IP address of the com­pu­ter sys­tem assi­gned by the Inter­net ser­vice pro­vi­der (ISP) and used by the data sub­ject at the time of the regis­tra­ti­on, as well as the date and time of the regis­tra­ti­on. The coll­ec­tion of this data is neces­sa­ry in order to under­stand the (pos­si­ble) misu­se of the e‑mail address of a data sub­ject at a later date, and it the­r­e­fo­re ser­ves the aim of the legal pro­tec­tion of the controller.

The per­so­nal data coll­ec­ted as part of a regis­tra­ti­on for the news­let­ter will only be used to send our news­let­ter. In addi­ti­on, sub­scri­bers to the news­let­ter may be infor­med by e‑mail, as long as this is neces­sa­ry for the ope­ra­ti­on of the news­let­ter ser­vice or a regis­tra­ti­on in ques­ti­on, as this could be the case in the event of modi­fi­ca­ti­ons to the news­let­ter offer, or in the event of a chan­ge in tech­ni­cal cir­cum­s­tances. The­re will be no trans­fer of per­so­nal data coll­ec­ted by the news­let­ter ser­vice to third par­ties. The sub­scrip­ti­on to our news­let­ter may be ter­mi­na­ted by the data sub­ject at any time. The con­sent to the sto­rage of per­so­nal data, which the data sub­ject has given for ship­ping the news­let­ter, may be revo­ked at any time. For the pur­po­se of revo­ca­ti­on of con­sent, a cor­re­spon­ding link is found in each news­let­ter. It is also pos­si­ble to unsub­scri­be from the news­let­ter at any time direct­ly on the web­site of the con­trol­ler, or to com­mu­ni­ca­te this to the con­trol­ler in a dif­fe­rent way.

6. Newsletter-Tracking

The news­let­ter of Sebas­ti­an Neu­haus con­ta­ins so-cal­led track­ing pixels. A track­ing pixel is a minia­tu­re gra­phic embedded in such e‑mails, which are sent in HTML for­mat to enable log file recor­ding and ana­ly­sis. This allows a sta­tis­ti­cal ana­ly­sis of the suc­cess or fail­ure of online mar­ke­ting cam­paigns. Based on the embedded track­ing pixel, Sebas­ti­an Neu­haus may see if and when an e‑mail was ope­ned by a data sub­ject, and which links in the e‑mail were cal­led up by data subjects.

Such per­so­nal data coll­ec­ted in the track­ing pixels con­tai­ned in the news­let­ters are stored and ana­ly­zed by the con­trol­ler in order to opti­mi­ze 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 inte­rests of the data sub­ject. The­se per­so­nal data will not be pas­sed on to third par­ties. Data sub­jects are at any time entit­led to revo­ke the respec­ti­ve sepa­ra­te decla­ra­ti­on of con­sent issued by means of the dou­ble-opt-in pro­ce­du­re. After a revo­ca­ti­on, the­se per­so­nal data will be dele­ted by the con­trol­ler. Sebas­ti­an Neu­haus auto­ma­ti­cal­ly regards a with­dra­wal from the receipt of the news­let­ter as a revocation.

7. Contact possibility via the website

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

8. Routine erasure and blocking of personal data

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

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

9. Rights of the data subject

• a) Right of confirmation

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

• b) Right of access

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

  • the pur­po­ses of the processing;
  • the cate­go­ries of per­so­nal data concerned;
  • the reci­pi­ents or cate­go­ries of reci­pi­ents to whom the per­so­nal data have been or will be dis­c­lo­sed, in par­ti­cu­lar reci­pi­ents in third count­ries or inter­na­tio­nal organisations;
  • whe­re pos­si­ble, the envi­sa­ged peri­od for which the per­so­nal data will be stored, or, if not pos­si­ble, the cri­te­ria used to deter­mi­ne that period;
  • the exis­tence of the right to request from the con­trol­ler rec­ti­fi­ca­ti­on or era­su­re of per­so­nal data, or rest­ric­tion of pro­ces­sing of per­so­nal data con­cer­ning the data sub­ject, or to object to such processing;
  • the exis­tence of the right to lodge a com­plaint with a super­vi­so­ry authority;
  • whe­re the per­so­nal data are not coll­ec­ted from the data sub­ject, any available infor­ma­ti­on as to their source;
  • the exis­tence of auto­ma­ted decis­i­on-making, inclu­ding pro­fil­ing, refer­red to in Artic­le 22(1) and (4) of the GDPR and, at least in tho­se cases, meaningful infor­ma­ti­on about the logic invol­ved, as well as the signi­fi­can­ce and envi­sa­ged con­se­quen­ces of such pro­ces­sing for the data subject.

  Fur­ther­mo­re, the data sub­ject shall have a right to obtain infor­ma­ti­on as to whe­ther per­so­nal data are trans­fer­red to a third coun­try or to an inter­na­tio­nal orga­ni­sa­ti­on. Whe­re this is the case, the data sub­ject shall have the right to be infor­med of the appro­pria­te safe­guards rela­ting to the transfer.

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

• c) Right to rectification

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

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

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

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

  • The per­so­nal data are no lon­ger neces­sa­ry in rela­ti­on to the pur­po­ses for which they were coll­ec­ted or other­wi­se processed.
  • The data sub­ject with­draws con­sent to which the pro­ces­sing is based accor­ding to point (a) of Artic­le 6(1) of the GDPR, or point (a) of Artic­le 9(2) of the GDPR, and whe­re the­re is no other legal ground for the processing.
  • The data sub­ject objects to the pro­ces­sing pur­su­ant to Artic­le 21(1) of the GDPR and the­re are no over­ri­ding legi­ti­ma­te grounds for the pro­ces­sing, or the data sub­ject objects to the pro­ces­sing pur­su­ant to Artic­le 21(2) of the GDPR.
  • The per­so­nal data have been unlawful­ly processed.
  • The per­so­nal data must be era­sed for com­pli­ance with a legal obli­ga­ti­on in Uni­on or Mem­ber Sta­te law to which the con­trol­ler is subject.
  • The per­so­nal data have been coll­ec­ted in rela­ti­on to the offer of infor­ma­ti­on socie­ty ser­vices refer­red to in Artic­le 8(1) of the GDPR.

  If one of the afo­re­men­tio­ned reasons appli­es, and a data sub­ject wis­hes to request the era­su­re of per­so­nal data stored by Sebas­ti­an Neu­haus, he or she may, at any time, cont­act any employee of the con­trol­ler. An employee of Sebas­ti­an Neu­haus shall prompt­ly ensu­re that the era­su­re request is com­pli­ed with immediately.

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

• e) Right of restriction of processing

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

  • The accu­ra­cy of the per­so­nal data is con­tes­ted by the data sub­ject, for a peri­od enab­ling the con­trol­ler to veri­fy the accu­ra­cy of the per­so­nal data.
  • The pro­ces­sing is unlawful and the data sub­ject oppo­ses the era­su­re of the per­so­nal data and requests ins­tead the rest­ric­tion of their use instead.
  • The con­trol­ler no lon­ger needs the per­so­nal data for the pur­po­ses of the pro­ces­sing, but they are requi­red by the data sub­ject for the estab­lish­ment, exer­cise or defence of legal claims.
  • The data sub­ject has objec­ted to pro­ces­sing pur­su­ant to Artic­le 21(1) of the GDPR pen­ding the veri­fi­ca­ti­on whe­ther the legi­ti­ma­te grounds of the con­trol­ler over­ri­de tho­se of the data subject.

  If one of the afo­re­men­tio­ned con­di­ti­ons is met, and a data sub­ject wis­hes to request the rest­ric­tion of the pro­ces­sing of per­so­nal data stored by Sebas­ti­an Neu­haus, he or she may at any time cont­act any employee of the con­trol­ler. The employee of Sebas­ti­an Neu­haus will arran­ge the rest­ric­tion of the processing.

• f) Right to data portability

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

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

  In order to assert the right to data por­ta­bi­li­ty, the data sub­ject may at any time cont­act any employee of Sebas­ti­an Neuhaus.

• g) Right to object

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

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

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

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

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

• h) Automated individual decision-making, including profiling

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

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

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

• i) Right to withdraw data protection consent

  Each data sub­ject shall have the right gran­ted by the Euro­pean legis­la­tor to with­draw his or her con­sent to pro­ces­sing of his or her per­so­nal data at any time.

  If the data sub­ject wis­hes to exer­cise the right to with­draw the con­sent, he or she may, at any time, cont­act any employee of Sebas­ti­an Neuhaus.

10. Data protection for applications and the application procedures

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

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

On this web­site, the con­trol­ler has inte­gra­ted com­pon­ents of the enter­pri­se Face­book. Face­book is a social network.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

On this web­site, the con­trol­ler has inte­gra­ted com­pon­ents of the ser­vice Insta­gram. Insta­gram is a ser­vice that may be qua­li­fied as an audio­vi­su­al plat­form, which allows users to share pho­tos and vide­os, as well as dis­se­mi­na­te such data in other social networks.

The ope­ra­ting com­pa­ny of the ser­vices offe­red by Insta­gram is Insta­gram LLC, 1 Hacker Way, Buil­ding 14 First Flo­or, Men­lo Park, CA, UNITED STATES.

With each call-up to one of the indi­vi­du­al pages of this Inter­net site, which is ope­ra­ted by the con­trol­ler and on which an Insta­gram com­po­nent (Ins­ta but­ton) was inte­gra­ted, the Inter­net brow­ser on the infor­ma­ti­on tech­no­lo­gy sys­tem of the data sub­ject is auto­ma­ti­cal­ly prompt­ed to the down­load of a dis­play of the cor­re­spon­ding Insta­gram com­po­nent of Insta­gram. During the cour­se of this tech­ni­cal pro­ce­du­re, Insta­gram beco­mes awa­re of what spe­ci­fic sub-page of our web­site was visi­ted by the data subject.

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

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

Fur­ther infor­ma­ti­on and the appli­ca­ble data pro­tec­tion pro­vi­si­ons of Insta­gram may be retrie­ved under https://help.instagram.com/155833707900388 and https://www.instagram.com/about/legal/privacy/.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

16. Legal basis for the processing

Art. 6(1) lit. a GDPR ser­ves as the legal basis for pro­ces­sing ope­ra­ti­ons for which we obtain con­sent for a spe­ci­fic pro­ces­sing pur­po­se. If the pro­ces­sing of per­so­nal data is neces­sa­ry for the per­for­mance of a con­tract to which the data sub­ject is par­ty, as is the case, for exam­p­le, when pro­ces­sing ope­ra­ti­ons are neces­sa­ry for the sup­p­ly of goods or to pro­vi­de any other ser­vice, the pro­ces­sing is based on Artic­le 6(1) lit. b GDPR. The same appli­es to such pro­ces­sing ope­ra­ti­ons which are neces­sa­ry for car­ry­ing out pre-con­trac­tu­al mea­su­res, for exam­p­le in the case of inqui­ries con­cer­ning our pro­ducts or ser­vices. Is our com­pa­ny sub­ject to a legal obli­ga­ti­on by which pro­ces­sing of per­so­nal data is requi­red, such as for the ful­fill­ment of tax obli­ga­ti­ons, the pro­ces­sing is based on Art. 6(1) lit. c GDPR.
In rare cases, the pro­ces­sing of per­so­nal data may be neces­sa­ry to pro­tect the vital inte­rests of the data sub­ject or of ano­ther natu­ral per­son. This would be the case, for exam­p­le, if a visi­tor were inju­red in our com­pa­ny and his name, age, health insu­rance data or other vital infor­ma­ti­on would have to be pas­sed on to a doc­tor, hos­pi­tal or other third par­ty. Then the pro­ces­sing would be based on Art. 6(1) lit. d GDPR.
Final­ly, pro­ces­sing ope­ra­ti­ons could be based on Artic­le 6(1) lit. f GDPR. This legal basis is used for pro­ces­sing ope­ra­ti­ons which are not cover­ed by any of the abo­ve­men­tio­ned legal grounds, if pro­ces­sing is neces­sa­ry for the pur­po­ses of the legi­ti­ma­te inte­rests pur­sued by our com­pa­ny or by a third par­ty, except whe­re such inte­rests are over­ridden by the inte­rests or fun­da­men­tal rights and free­doms of the data sub­ject which requi­re pro­tec­tion of per­so­nal data. Such pro­ces­sing ope­ra­ti­ons are par­ti­cu­lar­ly per­mis­si­ble becau­se they have been spe­ci­fi­cal­ly men­tio­ned by the Euro­pean legis­la­tor. He con­side­red that a legi­ti­ma­te inte­rest could be assu­med if the data sub­ject is a cli­ent of the con­trol­ler (Reci­tal 47 Sen­tence 2 GDPR).

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

Whe­re the pro­ces­sing of per­so­nal data is based on Artic­le 6(1) lit. f GDPR our legi­ti­ma­te inte­rest is to car­ry out our busi­ness in favor of the well-being of all our employees and the shareholders.

18. Period for which the personal data will be stored

The cri­te­ria used to deter­mi­ne the peri­od of sto­rage of per­so­nal data is the respec­ti­ve sta­tu­to­ry reten­ti­on peri­od. After expi­ra­ti­on of that peri­od, the cor­re­spon­ding data is rou­ti­ne­ly dele­ted, as long as it is no lon­ger neces­sa­ry for the ful­fill­ment of the con­tract or the initia­ti­on of a contract.

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

We cla­ri­fy that the pro­vi­si­on of per­so­nal data is part­ly requi­red by law (e.g. tax regu­la­ti­ons) or can also result from con­trac­tu­al pro­vi­si­ons (e.g. infor­ma­ti­on on the con­trac­tu­al partner).

Some­ti­mes it may be neces­sa­ry to con­clude a con­tract that the data sub­ject pro­vi­des us with per­so­nal data, which must sub­se­quent­ly be pro­ces­sed by us. The data sub­ject is, for exam­p­le, obli­ged to pro­vi­de us with per­so­nal data when our com­pa­ny signs a con­tract with him or her. The non-pro­vi­si­on of the per­so­nal data would have the con­se­quence that the con­tract with the data sub­ject could not be concluded.

Befo­re per­so­nal data is pro­vi­ded by the data sub­ject, the data sub­ject must cont­act any employee. The employee cla­ri­fies to the data sub­ject whe­ther the pro­vi­si­on of the per­so­nal data is requi­red by law or con­tract or is neces­sa­ry for the con­clu­si­on of the con­tract, whe­ther the­re is an obli­ga­ti­on to pro­vi­de the per­so­nal data and the con­se­quen­ces of non-pro­vi­si­on of the per­so­nal data.

20. Existence of automated decision-making

As a respon­si­ble com­pa­ny, we do not use auto­ma­tic decis­i­on-making or profiling.

This Pri­va­cy Poli­cy has been gene­ra­ted by the Pri­va­cy Poli­cy Gene­ra­tor of the DGD – Your Exter­nal DPO that was deve­lo­ped in coope­ra­ti­on with Ger­man Lawy­ers from WILDE BEUGER SOLMECKE, Cologne.

This web­site uses Mamo­to, a web ana­ly­tics open-source soft­ware. Mamo­to uses “coo­kies”, which are text files pla­ced on your com­pu­ter, to help the web­site ana­ly­ze how users use the site. The infor­ma­ti­on gene­ra­ted by the coo­kie about your use of the web­site (inclu­ding your IP address anony­mi­zed pri­or to its sto­rage) will be stored on the ser­ver of the ser­vice pro­vi­der in Ger­ma­ny. You may refu­se the use of coo­kies by sel­ec­ting the appro­pria­te set­tings on your brow­ser, howe­ver plea­se note that if you do this you may not be able to use the full func­tion­a­li­ty of this website.

Opt-Out-iFrame: