Pri­vacy policy

Our data pro­tec­tion decla­ra­tion is based on the terms used by the Euro­pean legis­la­tor for the adop­tion of the Gene­ral Data Pro­tec­tion Regu­la­tion (GDPR). Our data pro­tec­tion decla­ra­tion should be legi­ble and under­stan­da­ble for the gene­ral public as well as for our cus­to­mers and business part­ners. To ensure this, we would like to explain the terms used in advance.

We use the fol­lo­wing terms, among others, in this data pro­tec­tion decla­ra­tion:

a) per­so­nal data

Per­so­nal data is any infor­ma­tion rela­ting to an iden­ti­fied or iden­ti­fia­ble natu­ral per­son (her­ein­af­ter “data sub­ject”). A natu­ral per­son is con­side­red to be iden­ti­fia­ble if, directly or indi­rectly, in par­ti­cu­lar by means of assign­ment to an iden­ti­fier such as a name, an iden­ti­fi­ca­tion num­ber, loca­tion data, an online iden­ti­fier or to one or more spe­cial fea­tures, the expres­sion of the phy­si­cal, phy­sio­lo­gi­cal, gene­tic, psy­cho­lo­gi­cal, eco­no­mic, cul­tu­ral or social iden­tity of this natu­ral per­son can be iden­ti­fied.

b) data sub­ject

Data sub­ject is any iden­ti­fied or iden­ti­fia­ble natu­ral per­son whose per­so­nal data is pro­ce­s­sed by the data con­trol­ler.

c) pro­ce­s­sing

Pro­ce­s­sing is any pro­cess car­ried out with or wit­hout the help of auto­ma­ted pro­ce­du­res or any such series of pro­ce­s­ses in con­nec­tion with per­so­nal data such as coll­ec­ting, recor­ding, orga­ni­zing, arran­ging, sto­ring, adap­ting or chan­ging, rea­ding out, query­ing, using, dis­clo­sure by trans­mis­sion, dis­tri­bu­tion or any other form of making available, matching or lin­king, rest­ric­tion, dele­tion or des­truc­tion.

d) Rest­ric­tion of pro­ce­s­sing

Rest­ric­tion of pro­ce­s­sing is the mar­king of stored per­so­nal data with the aim of rest­ric­ting their future pro­ce­s­sing.

e) pro­fil­ing

Pro­fil­ing is any type of auto­ma­ted pro­ce­s­sing of per­so­nal data, which con­sists in using this per­so­nal data to eva­luate cer­tain per­so­nal aspects rela­ting to a natu­ral per­son, in par­ti­cu­lar aspects rela­ting to work per­for­mance, eco­no­mic situa­tion, health, per­so­nal Ana­lyze or pre­dict that natu­ral person’s pre­fe­ren­ces, inte­rests, relia­bi­lity, beha­vior, whe­re­a­bouts or relo­ca­tion.

f) Pseud­ony­mization

Pseud­ony­mization is the pro­ce­s­sing of per­so­nal data in such a way that the per­so­nal data can no lon­ger be assi­gned to a spe­ci­fic data sub­ject wit­hout the use of addi­tio­nal infor­ma­tion, pro­vi­ded that this addi­tio­nal infor­ma­tion is kept sepa­ra­tely and is sub­ject to tech­ni­cal and orga­nizatio­nal mea­su­res that ensure that the per­so­nal data not assi­gned to an iden­ti­fied or iden­ti­fia­ble natu­ral per­son.

g) Con­trol­ler or data con­trol­ler

The per­son respon­si­ble or respon­si­ble for pro­ce­s­sing is the natu­ral or legal per­son, aut­ho­rity, insti­tu­tion or other body that alone or jointly with others deci­des on the pur­po­ses and means of pro­ce­s­sing per­so­nal data. If the pur­po­ses and means of this pro­ce­s­sing are spe­ci­fied by Union law or the law of the Mem­ber Sta­tes, the per­son respon­si­ble or the spe­ci­fic cri­te­ria for his naming can be pro­vi­ded for by Union law or the law of the Mem­ber Sta­tes.

h) pro­ces­sors

Pro­ces­sor is a natu­ral or legal per­son, public aut­ho­rity, insti­tu­tion or other body that pro­ce­s­ses per­so­nal data on behalf of the per­son respon­si­ble.

i) Reci­pi­ent

Reci­pi­ent is a natu­ral or legal per­son, public aut­ho­rity, insti­tu­tion or other body to which per­so­nal data is dis­c­lo­sed, regard­less of whe­ther it is a third party or not. Howe­ver, aut­ho­ri­ties that may receive per­so­nal data in the con­text of a spe­ci­fic inve­sti­ga­tion man­date under Union or Mem­ber State law are not con­side­red reci­pi­ents.

j) third party

Third party is a natu­ral or legal per­son, public aut­ho­rity, agency or body other than the data sub­ject, the con­trol­ler, the pro­ces­sor and the per­sons who, under the direct respon­si­bi­lity of the con­trol­ler or the pro­ces­sor, are aut­ho­ri­zed to pro­cess the per­so­nal data.

k) Con­sent

Con­sent is any expres­sion of will vol­un­t­a­rily given by the data sub­ject in an infor­med man­ner and unequi­vo­cally for the spe­ci­fic case in the form of a decla­ra­tion or other unequi­vo­cal con­fir­ma­tory action with which the data sub­ject indi­ca­tes, d

The per­son respon­si­ble within the mea­ning of the Gene­ral Data Pro­tec­tion Regu­la­tion, other data pro­tec­tion laws appli­ca­ble in the mem­ber sta­tes of the Euro­pean Union and other pro­vi­si­ons of a data pro­tec­tion nature is:

WALDIS Safes Ltd
Hof­wi­sen­stra­sse 20
CH-8153 Ruem­lang

Phone: +41 43 211 12 00
Fax: +41 43 211 12 12
Mail: info@tresore.ch

Our inter­net pages use coo­kies. Coo­kies are text files that are filed and saved on a com­pu­ter system via an Inter­net brow­ser.

Num­e­rous web­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 web­sites and ser­vers can be assi­gned to the spe­ci­fic inter­net brow­ser in which the coo­kie was stored. This enables the visi­ted web­sites and ser­vers to distin­gu­ish the indi­vi­dual brow­ser of the per­son con­cer­ned from other inter­net brow­sers that con­tain other coo­kies. A spe­ci­fic inter­net brow­ser can be reco­gnized and iden­ti­fied via the uni­que coo­kie ID.

Through the use of coo­kies, we can pro­vide the users of this web­site with more user-fri­endly ser­vices that would not be pos­si­ble wit­hout the coo­kie set­ting.

By means of a coo­kie, the infor­ma­tion and offers on our web­site can be opti­mi­zed for the user. As alre­ady men­tio­ned, coo­kies enable us to reco­gnize the users of our web­site. The pur­pose of this reco­gni­tion is to make it easier for users to use our web­site. For exam­ple, the user of a web­site that uses coo­kies does not have to re-enter their access data each time they visit the web­site because this is done by the web­site and the coo­kie stored on the user’s com­pu­ter system. Ano­ther exam­ple is the coo­kie of a shop­ping cart in the online shop. The online shop uses a coo­kie to remem­ber the items that a cus­to­mer has pla­ced in the vir­tual shop­ping cart.

The per­son con­cer­ned can pre­vent the set­ting of coo­kies by our web­site at any time by means of a cor­re­spon­ding set­ting in the Inter­net brow­ser used and thus per­ma­nently object to the set­ting of coo­kies. Fur­ther­more, coo­kies that have alre­ady been set can 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 com­mon Inter­net brow­sers. If the per­son con­cer­ned 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 fully usable.

Our web­site coll­ects a series of gene­ral data and infor­ma­tion each time it is acce­s­sed by an affec­ted per­son or an auto­ma­ted system. This gene­ral data and infor­ma­tion is stored in the log files of the ser­ver. The (1) brow­ser types and ver­si­ons used, (2) the ope­ra­ting system used by the acce­s­sing system, (3) the web­site from which an acce­s­sing system acce­s­ses our web­site (so-cal­­led refer­rer), (4) the sub-web­­si­tes, which are acce­s­sed via an acce­s­sing system on our web­site can be con­trol­led, (5) the date and time of access to the web­site, (6) an Inter­net pro­to­col address (IP address), (7) the Inter­net ser­vice pro­vi­der of the acce­s­sing system and (8) other simi­lar data and infor­ma­tion used to avert thre­ats in the event of attacks on our infor­ma­tion tech­no­logy systems.

When using these gene­ral data and infor­ma­tion, we do not draw any con­clu­si­ons about the data sub­ject. Rather, this infor­ma­tion is requi­red to (1) deli­ver the con­tent of our web­site cor­rectly, (2) opti­mize the con­tent of our web­site and the adver­ti­sing for it, (3) ensure the long-term func­tion­a­lity of our infor­ma­tion tech­no­logy systems and the tech­no­logy of our web­site and ( 4) to pro­vide law enforce­ment aut­ho­ri­ties with the infor­ma­tion neces­sary for law enforce­ment in the event of a cyber attack. We the­r­e­fore eva­luate this anony­mously coll­ec­ted data and infor­ma­tion sta­tis­ti­cally and with the aim of incre­a­sing data pro­tec­tion and data secu­rity in our com­pany in order to ulti­m­ately ensure 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­tely from all per­so­nal data pro­vi­ded by an affec­ted per­son.

Due to legal regu­la­ti­ons, our Inter­net pages con­tain infor­ma­tion that enables quick elec­tro­nic cont­act to our com­pany and direct com­mu­ni­ca­tion with us, which also inclu­des a gene­ral address for so-cal­­led elec­tro­nic mail (e‑mail address). If a per­son con­cer­ned cont­acts the per­son respon­si­ble for pro­ce­s­sing by e‑mail or via a cont­act form, the per­so­nal data trans­mit­ted by the per­son con­cer­ned will be auto­ma­ti­cally saved. Such per­so­nal data trans­mit­ted on a vol­un­t­ary basis by a data sub­ject to the data con­trol­ler are stored for the pur­pose of pro­ce­s­sing or cont­ac­ting the data sub­ject.

This per­so­nal data will not be pas­sed on to third par­ties.

The per­son respon­si­ble for pro­ce­s­sing pro­ce­s­ses and stores the per­so­nal data of the per­son con­cer­ned only for the period of time neces­sary to achieve the pur­pose of sto­rage or if this is requi­red by the Euro­pean direc­tive and regu­la­tion giver or ano­ther legis­la­tor in laws or regu­la­ti­ons which the per­son respon­si­ble for pro­ce­s­sing sub­ject, was pro­vi­ded.

If the pur­pose of sto­rage no lon­ger applies or if a sto­rage period pre­scri­bed by the Euro­pean direc­tive and regu­la­tion aut­ho­rity or ano­ther respon­si­ble legis­la­tor expi­res, the per­so­nal data will be blocked or dele­ted as a mat­ter of rou­tine and in accordance with the sta­tu­tory pro­vi­si­ons.

a) Right to Con­fir­ma­tion

Every data sub­ject has the right, gran­ted by the Euro­pean direc­tive and regu­la­tion giver, to request con­fir­ma­tion from the per­son respon­si­ble for pro­ce­s­sing as to whe­ther per­so­nal data rela­ting to them are being pro­ce­s­sed. If a data sub­ject wis­hes to exer­cise this right to con­fir­ma­tion, they can cont­act an employee of the data con­trol­ler at any time.

b) Right to infor­ma­tion

Every per­son affec­ted by the pro­ce­s­sing of per­so­nal data has the right, gran­ted by the Euro­pean direc­tive and regu­la­tion giver, to receive free infor­ma­tion about the per­so­nal data stored about him and a copy of this infor­ma­tion from the per­son respon­si­ble for pro­ce­s­sing at any time. Fur­ther­more, the Euro­pean legis­la­tor for direc­ti­ves and regu­la­ti­ons has gran­ted the data sub­ject access to the fol­lo­wing infor­ma­tion:
the pro­ce­s­sing pur­po­ses
the cate­go­ries of per­so­nal data being pro­ce­s­sed
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 orga­nizati­ons
if pos­si­ble, the plan­ned dura­tion for which the per­so­nal data will be stored or, if this is not pos­si­ble, the cri­te­ria used to deter­mine that dura­tion
the exi­stence of a right to cor­rec­tion or dele­tion of the per­so­nal data con­cer­ning you or to rest­ric­tion of pro­ce­s­sing by the per­son respon­si­ble or a right to object to this pro­ce­s­sing
the exi­stence of a right of appeal to a super­vi­sory aut­ho­rity
if the per­so­nal data is not coll­ec­ted from the data sub­ject: all available infor­ma­tion about the ori­gin of the data
the exi­stence of auto­ma­ted decis­­ion-making inclu­ding pro­fil­ing in accordance with Article 22 (1) and (4) GDPR and — at least in these cases — meaningful infor­ma­tion about the logic invol­ved and the scope and inten­ded effects of such pro­ce­s­sing for the data sub­ject

Fur­ther­more, the data sub­ject has a right to infor­ma­tion as to whe­ther per­so­nal data has been trans­mit­ted to a third coun­try or to an inter­na­tio­nal orga­nization. If this is the case, the per­son con­cer­ned has the right to receive infor­ma­tion about the appro­priate gua­ran­tees in con­nec­tion with the trans­mis­sion.

If a data sub­ject wis­hes to exer­cise this right to infor­ma­tion, they can cont­act an employee of the data con­trol­ler at any time.

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

Every per­son affec­ted by the pro­ce­s­sing of per­so­nal data has the right gran­ted by the Euro­pean direc­tive and regu­la­tion giver to demand the imme­diate cor­rec­tion of incor­rect per­so­nal data con­cer­ning them. Fur­ther­more, the data sub­ject has the right, taking into account the pur­po­ses of the pro­ce­s­sing, to request the com­ple­tion of incom­plete per­so­nal data — also by means of a sup­ple­men­tary decla­ra­tion.

If a data sub­ject wis­hes to exer­cise this right to rec­ti­fi­ca­tion, they can cont­act an employee of the data con­trol­ler at any time.

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

Every per­son affec­ted by the pro­ce­s­sing of per­so­nal data has the right gran­ted by the Euro­pean direc­tive and regu­la­tion giver to demand that the per­son respon­si­ble delete the per­so­nal data con­cer­ning them imme­dia­tely if one of the fol­lo­wing rea­sons applies and if the pro­ce­s­sing is not neces­sary:
The per­so­nal data were coll­ec­ted for such pur­po­ses or other­wise pro­ce­s­sed for which they are no lon­ger neces­sary.
The data sub­ject revo­kes their con­sent on which the pro­ce­s­sing was based pur­su­ant to Article 6(1)(a) GDPR or Article 9(2)(a) GDPR, and there is no other legal basis for the pro­ce­s­sing.
The data sub­ject objects to the pro­ce­s­sing pur­su­ant to Article 21 (1) GDPR and there are no over­ri­ding legi­ti­mate rea­sons for the pro­ce­s­sing, or the data sub­ject objects to the pro­ce­s­sing pur­su­ant to Article 21 (2) GDPR pro­ce­s­sing on.
The per­so­nal data have been unlawfully pro­ce­s­sed.
Era­sure of the per­so­nal data is neces­sary to ful­fill a legal obli­ga­tion in Union or Mem­ber State law to which the con­trol­ler is sub­ject.
The per­so­nal data was coll­ec­ted in rela­tion to infor­ma­tion society ser­vices offe­red in accordance with Art. 8 Para. 1 DS-GVO.

If one of the above rea­sons applies and a data sub­ject wis­hes to have per­so­nal data stored by us dele­ted, they can

The per­son respon­si­ble for pro­ce­s­sing has inte­gra­ted the Google Ana­ly­tics com­po­nent with an anony­mization func­tion on this web­site. Google Ana­ly­tics is a web ana­ly­tics ser­vice. Web ana­ly­sis is the coll­ec­tion, coll­ec­tion and eva­lua­tion of data on the beha­vior of visi­tors to web­sites. A web ana­ly­sis ser­vice coll­ects, among other things, data about the web­site from which a per­son con­cer­ned came to a web­site (so-cal­­led refer­rer), which sub­pages of the web­site were acce­s­sed or how often and for how long a sub­page was viewed. A web ana­ly­sis is mainly used to opti­mize a web­site and for the cost-bene­­fit ana­ly­sis of inter­net adver­ti­sing.

The ope­ra­ting com­pany of the Google Ana­ly­tics com­po­nent is Google Inc., 1600 Amphi­thea­ter Pkwy, Moun­tain View, CA 94043–1351, USA.

The per­son respon­si­ble for pro­ce­s­sing uses the addi­tion “_gat._anonymizeIp” for the web ana­ly­sis via Google Ana­ly­tics. With this addi­tion, the IP address of the Inter­net con­nec­tion of the per­son con­cer­ned is shor­tened and anony­mi­zed by Google if our web­site is acce­s­sed from a mem­ber state of the Euro­pean Union or from ano­ther state party to the Agree­ment on the Euro­pean Eco­no­mic Area.

The pur­pose of the Google Ana­ly­tics com­po­nent is to ana­lyze visi­tor flows on our web­site. Google uses the data and infor­ma­tion obtai­ned, among other things, to eva­luate the use of our web­site, to com­pile online reports for us that show the acti­vi­ties on our web­site, and to pro­vide other ser­vices rela­ted to the use of our web­site.

Google Ana­ly­tics places a coo­kie on the infor­ma­tion tech­no­logy system of the data sub­ject. What coo­kies are has alre­ady been explai­ned above. By set­ting the coo­kie, Google is able to ana­lyze the use of our web­site. Each time one of the indi­vi­dual pages of this web­site is cal­led up, which is ope­ra­ted by the per­son respon­si­ble for pro­ce­s­sing and on which a Google Ana­ly­tics com­po­nent has been inte­gra­ted, the Inter­net brow­ser on the infor­ma­tion tech­no­logy system of the per­son con­cer­ned is auto­ma­ti­cally acti­va­ted by the respec­tive Google Ana­ly­tics com­po­nent to trans­mit data to Google for online ana­ly­sis. As part of this tech­ni­cal pro­cess, Google gains know­ledge of per­so­nal data, such as the IP address of the per­son con­cer­ned, which Google uses, among other things, to trace the ori­gin of visi­tors and clicks and sub­se­quently to enable com­mis­sion state­ments.

The coo­kie is used to store per­so­nal infor­ma­tion, such as access time, the loca­tion from which access was made and the fre­quency of visits to our web­site by the per­son con­cer­ned. Each time you visit our web­site, this per­so­nal data, inclu­ding the IP address of the Inter­net con­nec­tion used by the per­son con­cer­ned, is trans­mit­ted to Google in the United Sta­tes of Ame­rica. This per­so­nal data is stored by Google in the United Sta­tes of Ame­rica. Google may pass on this per­so­nal data coll­ec­ted via the tech­ni­cal pro­cess to third par­ties.

The per­son con­cer­ned can pre­vent the set­ting of coo­kies by our web­site, as alre­ady descri­bed above, at any time by means of a cor­re­spon­ding set­ting in the Inter­net brow­ser used and thus per­ma­nently object to the set­ting of coo­kies. Such a set­ting of the Inter­net brow­ser used would also pre­vent Google from set­ting a coo­kie on the infor­ma­tion tech­no­logy system of the per­son con­cer­ned. In addi­tion, a coo­kie alre­ady set by Google Ana­ly­tics can be dele­ted at any time via the Inter­net brow­ser or other soft­ware pro­grams.

Fur­ther­more, the data sub­ject has the option of objec­ting to and pre­ven­ting the coll­ec­tion of data gene­ra­ted by Google Ana­ly­tics rela­ting to the use of this web­site and the pro­ce­s­sing of this data by Google. To do this, the data sub­ject must down­load and install a brow­ser add-on from the link https://tools.google.com/dlpage/gaoptout. This brow­ser add-on tells Google Ana­ly­tics via Java­Script that no data and infor­ma­tion about visits to web­sites may be trans­mit­ted to Google Ana­ly­tics. The instal­la­tion of the brow­ser add-on is eva­lua­ted by Google as a con­tra­dic­tion. If the infor­ma­tion tech­no­logy system of the data sub­ject is later dele­ted, for­mat­ted or reinstal­led, the data sub­ject must reinstall the brow­ser add-on in order to deac­ti­vate Google Ana­ly­tics. If the brow­ser add-on is used by the data sub­ject or ano­ther per­son within their sphere of influence

Der für die Ver­ar­bei­tung Ver­ant­wort­li­che hat auf die­ser Inter­net­seite Google AdWords inte­griert. Google AdWords ist ein Dienst zur Inter­net­wer­bung, der es Wer­be­trei­ben­den gestat­tet, sowohl Anzei­gen in den Such­ma­schi­nen­er­geb­nis­sen von Google als auch im Google-Wer­­be­­net­z­­werk zu schal­ten. Google AdWords ermög­licht es einem Wer­be­trei­ben­den, vorab bestimmte Schlüs­sel­wör­ter fest­zu­le­gen, mit­tels derer eine Anzeige in den Such­ma­schi­nen­er­geb­nis­sen von Google aus­schließ­lich dann ange­zeigt wird, wenn der Nut­zer mit der Such­ma­schine ein schlüs­sel­wort­re­le­van­tes Such­ergeb­nis abruft. Im Google-Wer­­be­­net­z­­werk wer­den die Anzei­gen mit­tels eines auto­ma­ti­schen Algo­rith­mus und unter Beach­tung der zuvor fest­ge­leg­ten Schlüs­sel­wör­ter auf the­men­re­le­van­ten Inter­net­sei­ten ver­teilt.

Betrei­ber­ge­sell­schaft der Dien­ste von Google AdWords ist die Google Inc., 1600 Amphi­theatre Pkwy, Moun­tain View, CA 94043–1351, USA.

Der Zweck von Google AdWords ist die Bewer­bung unse­rer Inter­net­seite durch die Ein­blen­dung von inter­es­sen­re­le­van­ter Wer­bung auf den Inter­net­sei­ten von Dritt­un­ter­neh­men und in den Such­ma­schi­nen­er­geb­nis­sen der Such­ma­schine Google und eine Ein­blen­dung von Fremd­wer­bung auf unse­rer Inter­net­seite.

Gelangt eine betrof­fene Per­son über eine Google-Anzeige auf unsere Inter­net­seite, wird auf dem infor­ma­ti­ons­tech­no­lo­gi­schen System der betrof­fe­nen Per­son durch Google ein soge­nann­ter Con­­ver­­­sion-Coo­kie abge­legt. Was Coo­kies sind, wurde oben bereits erläu­tert. Ein Con­­ver­­­sion-Coo­kie ver­liert nach drei­ßig Tagen seine Gül­tig­keit und dient nicht zur Iden­ti­fi­ka­tion der betrof­fe­nen Per­son. Über den Con­­ver­­­sion-Coo­kie wird, sofern das Coo­kie noch nicht abge­lau­fen ist, nach­voll­zo­gen, ob bestimmte Unter­sei­ten, bei­spiels­weise der Waren­korb von einem Online-Shop-System, auf unse­rer Inter­net­seite auf­ge­ru­fen wur­den. Durch den Con­­ver­­­sion-Coo­kie kön­nen sowohl wir als auch Google nach­voll­zie­hen, ob eine betrof­fene Per­son, die über eine AdWords-Anzeige auf unsere Inter­net­seite gelangt ist, einen Umsatz gene­rierte, also einen Waren­kauf voll­zo­gen oder abge­bro­chen hat.

Die durch die Nut­zung des Con­­ver­­­sion-Coo­kies erho­be­nen Daten und Infor­ma­tio­nen wer­den von Google ver­wen­det, um Besuchs­sta­ti­sti­ken für unsere Inter­net­seite zu erstel­len. Diese Besuchs­sta­ti­sti­ken wer­den durch uns wie­derum genutzt, um die Gesamt­an­zahl der Nut­zer zu ermit­teln, wel­che über AdWords-Anzei­­gen an uns ver­mit­telt wur­den, also um den Erfolg oder Miss­erfolg der jewei­li­gen AdWords-Anzeige zu ermit­teln und um unsere AdWords-Anzei­­gen für die Zukunft zu opti­mie­ren. Weder unser Unter­neh­men noch andere Wer­be­kun­den von Google-AdWords erhal­ten Infor­ma­tio­nen von Google, mit­tels derer die betrof­fene Per­son iden­ti­fi­ziert wer­den könnte.

Mit­tels des Con­­ver­­­sion-Coo­kies wer­den per­so­nen­be­zo­gene Infor­ma­tio­nen, bei­spiels­weise die durch die betrof­fene Per­son besuch­ten Inter­net­sei­ten, gespei­chert. Bei jedem Besuch unse­rer Inter­net­sei­ten wer­den dem­nach per­so­nen­be­zo­gene Daten, ein­schließ­lich der IP-Adresse des von der betrof­fe­nen Per­son genutz­ten Inter­net­an­schlus­ses, an Google in den Ver­ei­nig­ten Staa­ten von Ame­rika über­tra­gen. Diese per­so­nen­be­zo­ge­nen Daten wer­den durch Google in den Ver­ei­nig­ten Staa­ten von Ame­rika gespei­chert. Google gibt diese über das tech­ni­sche Ver­fah­ren erho­be­nen per­so­nen­be­zo­ge­nen Daten unter Umstän­den an Dritte wei­ter.

Die betrof­fene Per­son kann die Set­zung von Coo­kies durch unsere Inter­net­seite, wie oben bereits dar­ge­stellt, jeder­zeit mit­tels einer ent­spre­chen­den Ein­stel­lung des genutz­ten Inter­net­brow­sers ver­hin­dern und damit der Set­zung von Coo­kies dau­er­haft wider­spre­chen. Eine sol­che Ein­stel­lung des genutz­ten Inter­net­brow­sers würde auch ver­hin­dern, dass Google einen Con­­ver­­­sion-Coo­kie auf dem infor­ma­ti­ons­tech­no­lo­gi­schen System der betrof­fe­nen Per­son setzt. Zudem kann ein von Google AdWords bereits gesetz­ter Coo­kie jeder­zeit über den Inter­net­brow­ser oder andere Soft­ware­pro­gramme gelöscht wer­den.

Fer­ner besteht für die betrof­fene Per­son die Mög­lich­keit, der inter­es­sen­be­zo­ge­nen Wer­bung durch Google zu wider­spre­chen. Hierzu muss die betrof­fene Per­son von jedem der von ihr genutz­ten Inter­net­brow­ser aus den Link www.google.de/settings/ads auf­ru­fen und dort die gewünsch­ten Ein­stel­lun­gen vor­neh­men.

Wei­tere Infor­ma­tio­nen und die gel­ten­den Daten­schutz­be­stim­mun­gen von Google kön­nen unter https://www.google.de/intl/de/policies/privacy/ abge­ru­fen wer­den.

The per­son respon­si­ble for pro­ce­s­sing has inte­gra­ted the Google+ but­ton as a com­po­nent on this web­site. Google+ is a so-cal­­led social net­work. A social net­work is a social mee­ting place ope­ra­ted on the Inter­net, an online com­mu­nity that usually enables users to com­mu­ni­cate with one ano­ther and to inter­act in vir­tual space. A social net­work can serve as a plat­form for exchan­ging opi­ni­ons and expe­ri­en­ces, or it allows the Inter­net com­mu­nity to pro­vide per­so­nal or com­­pany-rela­ted infor­ma­tion. Among other things, Google+ enables users of the social net­work to create pri­vate pro­files, upload pho­tos and net­work via fri­end requests.

The ope­ra­ting com­pany of Google+ is Google Inc., 1600 Amphi­thea­ter Pkwy, Moun­tain View, CA 94043–1351, USA.

Each time one of the indi­vi­dual pages of this web­site is cal­led up, which is ope­ra­ted by the per­son respon­si­ble for pro­ce­s­sing and on which a Google+ but­ton has been inte­gra­ted, the Inter­net brow­ser on the infor­ma­tion tech­no­logy system of the per­son con­cer­ned is auto­ma­ti­cally prompted by the respec­tive Google+ but­ton to dis­play the cor­re­spon­ding Google+ Down­load but­ton from Google. As part of this tech­ni­cal pro­cess, Google is infor­med which spe­ci­fic sub­page of our web­site is visi­ted by the per­son con­cer­ned. More detailed infor­ma­tion about Google+ is available at https://developers.google.com/+/.

If the per­son con­cer­ned is log­ged in to Google+ at the same time, Google reco­gnizes which spe­ci­fic sub­page of our web­site the per­son con­cer­ned is visi­ting each time the per­son con­cer­ned calls up our web­site and for the entire dura­tion of their stay on our web­site. This infor­ma­tion is coll­ec­ted by the Google+ but­ton and assi­gned by Google to the respec­tive Google+ account of the per­son con­cer­ned.

If the per­son con­cer­ned clicks on one of the Google+ but­tons inte­gra­ted on our web­site and thus makes a Google+1 recom­men­da­tion, Google assigns this infor­ma­tion to the per­so­nal Google+ user account of the per­son con­cer­ned and stores this per­so­nal data. Google stores the Google+1 recom­men­da­tion of the per­son con­cer­ned and makes it publicly available in accordance with the terms accepted by the per­son con­cer­ned in this respect. A Google+1 recom­men­da­tion given by the per­son con­cer­ned on this web­site will then be used in other Google ser­vices tog­e­ther with other per­so­nal data, such as the name of the Google+1 account used by the per­son con­cer­ned and the photo stored in it. For exam­ple, the search engine results of the Google search engine, the Google account of the per­son con­cer­ned or in other places, for exam­ple on web­sites or in con­nec­tion with adver­ti­se­ments, are stored and pro­ce­s­sed. Fur­ther­more, Google is able to link the visit to this web­site with other per­so­nal data stored by Google. Google also records this per­so­nal infor­ma­tion for the pur­pose of impro­ving or opti­mi­zing the various Google ser­vices.

Google always recei­ves infor­ma­tion via the Google+ but­ton that the per­son con­cer­ned has visi­ted our web­site if the per­son con­cer­ned is log­ged in to Google+ at the same time as acce­s­sing our web­site; this takes place regard­less of whe­ther the per­son con­cer­ned clicks on the Google+ but­ton or not.

If the per­son con­cer­ned does not want per­so­nal data to be trans­mit­ted to Google, they can pre­vent such a trans­mis­sion by log­ging out of their Google+ account before acce­s­sing our web­site.

Fur­ther infor­ma­tion and Google’s appli­ca­ble data pro­tec­tion regu­la­ti­ons can be found at https://www.google.de/intl/de/policies/privacy/. Fur­ther infor­ma­tion from Google on the Google +1 but­ton can be found at https://developers.google.com/+/web/buttons-policy.

The per­son respon­si­ble for pro­ce­s­sing has inte­gra­ted com­pon­ents of the com­pany Face­book on this web­site. Face­book is a social net­work.

A social net­work is a social mee­ting place ope­ra­ted on the Inter­net, an online com­mu­nity that usually enables users to com­mu­ni­cate with one ano­ther and to inter­act in vir­tual space. A social net­work can serve as a plat­form for exchan­ging opi­ni­ons and expe­ri­en­ces, or it allows the Inter­net com­mu­nity to pro­vide per­so­nal or com­­pany-rela­ted infor­ma­tion. Among other things, Face­book enables users of the social net­work to create pri­vate pro­files, upload pho­tos and net­work via fri­end requests.

Facebook’s ope­ra­ting com­pany is Face­book, Inc., 1 Hacker Way, Menlo Park, CA 94025, USA. If a per­son con­cer­ned lives out­side the USA or Canada, the per­son respon­si­ble for pro­ce­s­sing per­so­nal data is Face­book Ire­land Ltd., 4 Grand Canal Square, Grand Canal Har­bour, Dub­lin 2, Ire­land.

Each time one of the indi­vi­dual pages of this web­site is cal­led up, which is ope­ra­ted by the per­son respon­si­ble for pro­ce­s­sing and on which a Face­book com­po­nent (Face­book plug-in) has been inte­gra­ted, the Inter­net brow­ser on the infor­ma­tion tech­no­logy system of the per­son con­cer­ned is auto­ma­ti­cally acti­va­ted by the respec­tive Face­book com­po­nent cau­ses a repre­sen­ta­tion of the cor­re­spon­ding Face­book com­po­nent to be down­loa­ded from Face­book. A com­plete over­view of all Face­book plug-ins can be found at https://developers.facebook.com/docs/plugins/?locale=de_DE. As part of this tech­ni­cal pro­cess, Face­book is infor­med which spe­ci­fic sub­page of our web­site is visi­ted by the per­son con­cer­ned.

If the per­son con­cer­ned is log­ged on to Face­book at the same time, Face­book reco­gnizes which spe­ci­fic sub­page of our web­site the per­son con­cer­ned is visi­ting each time the per­son con­cer­ned calls up our web­site and for the entire dura­tion of their stay on our web­site. This infor­ma­tion is coll­ec­ted by the Face­book com­po­nent and assi­gned to the respec­tive Face­book account of the per­son con­cer­ned by Face­book. If the per­son con­cer­ned clicks on one of the Face­book but­tons inte­gra­ted on our web­site, for exam­ple the “Like” but­ton, or if the per­son con­cer­ned makes a com­ment, Face­book assigns this infor­ma­tion to the per­so­nal Face­book user account of the per­son con­cer­ned and stores this per­so­nal data .

Face­book always recei­ves infor­ma­tion via the Face­book com­po­nent that the per­son con­cer­ned has visi­ted our web­site if the per­son con­cer­ned is log­ged in to Face­book at the same time as acce­s­sing our web­site; this takes place regard­less of whe­ther the per­son con­cer­ned clicks on the Face­book com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Face­book in this way, they can pre­vent the trans­mis­sion by log­ging out of their Face­book account before acce­s­sing our web­site.

The data policy published by Face­book, which can be acce­s­sed at https://de-de.facebook.com/about/privacy/, pro­vi­des infor­ma­tion about the coll­ec­tion, pro­ce­s­sing and use of per­so­nal data by Face­book. It is also explai­ned there which set­ting opti­ons Face­book offers to pro­tect the pri­vacy of the data sub­ject. In addi­tion, various appli­ca­ti­ons are available that make it pos­si­ble to sup­press data trans­mis­sion to Face­book. Such appli­ca­ti­ons can be used by the per­son con­cer­ned to sup­press data trans­mis­sion to Face­book.

The per­son respon­si­ble for pro­ce­s­sing has inte­gra­ted com­pon­ents from Xing on this web­site. Xing is an Inter­­net-based social net­work that enables users to con­nect with exi­sting business cont­acts and estab­lish new business cont­acts. Indi­vi­dual users can create a per­so­nal pro­file for them­sel­ves on Xing. For exam­ple, com­pa­nies can create com­pany pro­files or publish job offers on Xing.

The ope­ra­ting com­pany of Xing is XING SE, Damm­tor­straße 30, 20354 Ham­burg, Ger­many.

Each time one of the indi­vi­dual pages of this web­site is cal­led up, which is ope­ra­ted by the per­son respon­si­ble for pro­ce­s­sing and on which a Xing com­po­nent (Xing plug-in) has been inte­gra­ted, the Inter­net brow­ser on the infor­ma­tion tech­no­logy system of the per­son con­cer­ned is auto­ma­ti­cally acti­va­ted by the respec­tive Xing com­po­nent cau­ses Xing to down­load a repre­sen­ta­tion of the cor­re­spon­ding Xing com­po­nent. Fur­ther infor­ma­tion on the Xing plug-ins can be found at https://dev.xing.com/plugins. As part of this tech­ni­cal pro­cess, Xing is infor­med which spe­ci­fic sub­page of our web­site is visi­ted by the per­son con­cer­ned.

If the per­son con­cer­ned is log­ged in to Xing at the same time, Xing reco­gnizes which spe­ci­fic sub­page of our web­site the per­son con­cer­ned is visi­ting each time the per­son con­cer­ned calls up our web­site and for the entire dura­tion of their stay on our web­site. This infor­ma­tion is coll­ec­ted by the Xing com­po­nent and assi­gned to the respec­tive Xing account of the data sub­ject by Xing. If the per­son con­cer­ned clicks on one of the Xing but­tons inte­gra­ted on our web­site, for exam­ple the “Share” but­ton, Xing assigns this infor­ma­tion to the per­so­nal Xing user account of the per­son con­cer­ned and stores this per­so­nal data.

Xing always recei­ves infor­ma­tion via the Xing com­po­nent that the per­son con­cer­ned has visi­ted our web­site if the per­son con­cer­ned is log­ged in to Xing at the same time as acce­s­sing our web­site; this takes place regard­less of whe­ther the data sub­ject clicks on the Xing com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Xing, they can pre­vent the trans­mis­sion by log­ging out of their Xing account before acce­s­sing our web­site.

The data pro­tec­tion regu­la­ti­ons published by Xing, which can be acce­s­sed at https://www.xing.com/privacy, pro­vide infor­ma­tion about the coll­ec­tion, pro­ce­s­sing and use of per­so­nal data by Xing. Xing has also published data pro­tec­tion noti­ces for the XING share but­ton at https://www.xing.com/app/share?op=data_protection.

The per­son respon­si­ble for pro­ce­s­sing has inte­gra­ted com­pon­ents from Twit­ter on this web­site. Twit­ter is a mul­ti­l­in­gual, publicly acce­s­si­ble micro­blog­ging ser­vice on which users can publish and dis­tri­bute so-cal­­led tweets, i.e. short mes­sa­ges limi­ted to 140 cha­rac­ters. These short mes­sa­ges can be acce­s­sed by anyone, inclu­ding peo­ple who are not regi­stered on Twit­ter. The tweets are also dis­played to the so-cal­­led fol­lo­wers of the respec­tive user. Fol­lo­wers are other Twit­ter users who fol­low a user’s tweets. Fur­ther­more, Twit­ter makes it pos­si­ble to address a broad audi­ence via hash­tags, links or ret­weets.

The ope­ra­ting com­pany of Twit­ter is Twit­ter, Inc., 1355 Mar­ket Street, Suite 900, San Fran­cisco, CA 94103, USA.

Each time one of the indi­vi­dual pages of this web­site is cal­led up, which is ope­ra­ted by the per­son respon­si­ble for pro­ce­s­sing and on which a Twit­ter com­po­nent (Twit­ter but­ton) has been inte­gra­ted, the Inter­net brow­ser on the infor­ma­tion tech­no­logy system of the per­son con­cer­ned is auto­ma­ti­cally acti­va­ted by the respec­tive Twit­ter com­po­nent cau­ses a repre­sen­ta­tion of the rele­vant Twit­ter com­po­nent to be down­loa­ded from Twit­ter. Fur­ther infor­ma­tion on the Twit­ter but­tons is available at https://about.twitter.com/de/resources/buttons. As part of this tech­ni­cal pro­cess, Twit­ter is infor­med which spe­ci­fic sub­page of our web­site is visi­ted by the per­son con­cer­ned. The pur­pose of inte­gra­ting the Twit­ter com­po­nent is to enable our users to redis­tri­bute the con­tent of this web­site, to make this web­site known in the digi­tal world and to increase our visi­tor num­bers.

If the per­son con­cer­ned is log­ged in to Twit­ter at the same time, Twit­ter reco­gnizes which spe­ci­fic sub­page of our web­site the per­son con­cer­ned is visi­ting each time the per­son con­cer­ned calls up our web­site and for the entire dura­tion of their stay on our web­site. This infor­ma­tion is coll­ec­ted by the Twit­ter com­po­nent and assi­gned by Twit­ter to the respec­tive Twit­ter account of the data sub­ject. If the per­son con­cer­ned clicks on one of the Twit­ter but­tons inte­gra­ted on our web­site, the data and infor­ma­tion thus trans­mit­ted are assi­gned to the per­so­nal Twit­ter user account of the per­son con­cer­ned and stored and pro­ce­s­sed by Twit­ter.

Twit­ter always recei­ves infor­ma­tion via the Twit­ter com­po­nent that the per­son con­cer­ned has visi­ted our web­site if the per­son con­cer­ned is log­ged in to Twit­ter at the same time as acce­s­sing our web­site; this takes place regard­less of whe­ther the data sub­ject clicks on the Twit­ter com­po­nent or not. If the data sub­ject does not want this infor­ma­tion to be trans­mit­ted to Twit­ter in this way, they can pre­vent the trans­mis­sion by log­ging out of their Twit­ter account before acce­s­sing our web­site.

Twitter’s appli­ca­ble data pro­tec­tion regu­la­ti­ons are available at https://twitter.com/privacy?lang=de.

Twit­ter is cer­ti­fied under the Pri­vacy Shield Agree­ment and thus offers a guarantee to com­ply with Euro­pean data pro­tec­tion law (https://www.privacyshield.gov/participant?id=a2zt0000000TORzAAO&status=Active). Pri­vacy Policy: https://twitter.com/de/privacy
Opt out: https://twitter.com/personalization

We main­tain online pre­sen­ces within social net­works and plat­forms in order to be able to com­mu­ni­cate with the cus­to­mers, inte­re­sted par­ties and users active there and to be able to inform them about our ser­vices there. When cal­ling up the respec­tive net­works and plat­forms, the terms and con­di­ti­ons and data pro­ce­s­sing gui­de­lines of their respec­tive ope­ra­tors apply.

Unless other­wise sta­ted in our data pro­tec­tion decla­ra­tion, we pro­cess user data if they com­mu­ni­cate with us within social net­works and plat­forms, e.g. write posts on our online pre­sence or send us mes­sa­ges.

We use con­tent or ser­vice offers from third-party pro­vi­ders within our online offer on the basis of our legi­ti­mate inte­rests (i.e. inte­rest in the ana­ly­sis, opti­mization and eco­no­mic ope­ra­tion of our online offer within the mea­ning of Art. 6 Para. 1 lit. f. DSGVO) in order to improve their con­tent and Inte­grate ser­vices such as videos or fonts (her­ein­af­ter uni­formly refer­red to as “con­tent”).

This always pre­sup­po­ses that the third-party pro­vi­ders of this con­tent per­ceive the IP address of the user, since wit­hout the IP address they could not send the con­tent to their brow­ser. The IP address is the­r­e­fore requi­red for the dis­play of this con­tent. We endea­vor to only use con­tent whose respec­tive pro­vi­ders only use the IP address to deli­ver the con­tent. Third-party pro­vi­ders can also use so-cal­­led pixel tags (invi­si­ble gra­phics, also known as “web bea­cons”) for sta­tis­ti­cal or mar­ke­ting pur­po­ses. The “pixel tags” can be used to eva­luate infor­ma­tion such as visi­tor traf­fic on the pages of this web­site. The pseud­ony­mous infor­ma­tion can also be stored in coo­kies on the user’s device and con­tain, among other things, tech­ni­cal infor­ma­tion about the brow­ser and ope­ra­ting system, refer­ring web­sites, visi­ting times and other infor­ma­tion on the use of our online offer, as well as being lin­ked to such infor­ma­tion from other sources.

This site uses so-cal­­led web fonts pro­vi­ded by Google for the uni­form dis­play of fonts. When you call up a page, your brow­ser loads the requi­red web fonts into your brow­ser cache in order to dis­play text and fonts cor­rectly. For this pur­pose, the brow­ser you are using must con­nect to the Google ser­vers. This gives Google know­ledge that our web­site was acce­s­sed via your IP address. Google Web Fonts are used in the inte­rest of a uni­form and appe­al­ing pre­sen­ta­tion of our online offe­ring. This repres­ents a legi­ti­mate inte­rest within the mea­ning of Article 6 (1) (f) GDPR.

If your brow­ser does not sup­port web fonts, a stan­dard font will be used by your com­pu­ter.

We inte­grate the fonts (“Google Fonts”) from the pro­vi­der Google LLC, 1600 Amphi­thea­ter Park­way, Moun­tain View, CA 94043, USA.
Pri­vacy Policy: https://www.google.com/policies/privacy/
Opt-Out: https://adssettings.google.com/authenticated.

We inte­grate the maps of the “Google Maps” ser­vice pro­vi­ded by Google LLC, 1600 Amphi­thea­ter Park­way, Moun­tain View, CA 94043, USA. The pro­ce­s­sed data may include, in par­ti­cu­lar, IP addres­ses and loca­tion data of the users, which, howe­ver, are not coll­ec­ted wit­hout their con­sent (usually as part of the set­tings on their mobile devices). The data can be pro­ce­s­sed in the USA. Pri­vacy Policy: https://www.google.com/policies/privacy/
Opt-Out: https://adssettings.google.com/authenticated

We embed the videos from the “You­Tube” plat­form pro­vi­ded by Google LLC, 1600 Amphi­thea­ter Park­way, Moun­tain View, CA 94043, USA.
Pri­vacy Policy: https://www.google.com/policies/privacy/
Opt-Out: https://adssettings.google.com/authenticated.

Func­tions and con­tent of the Insta­gram ser­vice offe­red by Insta­gram Inc., 1601 Wil­low Road, Menlo Park, CA, 94025, USA, can be inte­gra­ted within our online offer. This can include, for exam­ple, con­tent such as images, videos or text and but­tons with which users can express their liking for the con­tent, the aut­hors of the con­tent or sub­scribe to our posts. If the users are mem­bers of the Insta­gram plat­form, Insta­gram can assign the above-men­tio­­ned con­tent and func­tions to the user pro­files there. Insta­gram pri­vacy policy: http://instagram.com/about/legal/privacy/

Art. 6 I lit. a DS-GVO ser­ves our com­pany as the legal basis for pro­ce­s­sing ope­ra­ti­ons for which we obtain con­sent for a spe­ci­fic pro­ce­s­sing pur­pose. If the pro­ce­s­sing of per­so­nal data is neces­sary to ful­fill a con­tract to which the data sub­ject is party, as is the case, for exam­ple, with pro­ce­s­sing ope­ra­ti­ons that are neces­sary for the deli­very of goods or the pro­vi­sion of ano­ther ser­vice or con­side­ra­tion, the pro­ce­s­sing is based on Art. 6 I lit. b GDPR. The same applies to such pro­ce­s­sing ope­ra­ti­ons that are neces­sary to carry out pre-con­trac­tual mea­su­res, for exam­ple in the case of inqui­ries about our pro­ducts or ser­vices. If our com­pany is sub­ject to a legal obli­ga­tion which requi­res the pro­ce­s­sing of per­so­nal data, such as the ful­fill­ment of tax obli­ga­ti­ons, the pro­ce­s­sing is based on Art. 6 I lit. c GDPR. In rare cases, the pro­ce­s­sing of per­so­nal data could become neces­sary to pro­tect the vital inte­rests of the data sub­ject or ano­ther natu­ral per­son. This would be the case, for exam­ple, if a visi­tor were inju­red in our com­pany and his name, age, health insu­rance data or other vital infor­ma­tion would have to be pas­sed on to a doc­tor, hos­pi­tal or other third party. Then the pro­ce­s­sing would be based on Art. 6 I lit. d GDPR.
Ulti­m­ately, pro­ce­s­sing ope­ra­ti­ons could be based on Art. 6 I lit. f GDPR. Pro­ce­s­sing ope­ra­ti­ons that are not covered by any of the afo­re­men­tio­ned legal bases are based on this legal basis if the pro­ce­s­sing is neces­sary to pro­tect a legi­ti­mate inte­rest of our com­pany or a third party, pro­vi­ded that the inte­rests, fun­da­men­tal rights and fun­da­men­tal free­doms of the per­son con­cer­ned do not pre­vail. Such pro­ce­s­sing ope­ra­ti­ons are per­mit­ted to us in par­ti­cu­lar because they have been spe­ci­fi­cally men­tio­ned by the Euro­pean legis­la­tor. In this respect, he took the view that a legi­ti­mate inte­rest could be assu­med if the data sub­ject is a cus­to­mer of the per­son respon­si­ble (reci­tal 47 sen­tence 2 DS-GVO).

If the pro­ce­s­sing of per­so­nal data is based on Article 6 I lit. f GDPR, our legi­ti­mate inte­rest is con­duc­ting our business for the bene­fit of all our employees and our share­hol­ders.

As a respon­si­ble com­pany, we do not use auto­ma­tic decis­­ion-making or pro­fil­ing.

The cri­ter­ion for the dura­tion of the sto­rage of per­so­nal data is the respec­tive sta­tu­tory reten­tion period. After the dead­line has expi­red, the cor­re­spon­ding data will be rou­ti­nely dele­ted, pro­vi­ded that they are no lon­ger requi­red to ful­fill the con­tract or to initiate a con­tract.

Sta­tu­tory or con­trac­tual requi­re­ments for pro­vi­ding the per­so­nal data; Neces­sity for the con­clu­sion of the con­tract; obli­ga­tion of the data sub­ject to pro­vide the per­so­nal data; pos­si­ble con­se­quen­ces of non-pro­­vi­­sion

We cla­rify that the pro­vi­sion of per­so­nal data is partly requi­red by law (e.g. tax regu­la­ti­ons) or can also result from con­trac­tual regu­la­ti­ons (e.g. infor­ma­tion on the con­trac­tual part­ner).
Some­ti­mes it may be neces­sary for a con­tract to be con­clu­ded that a per­son con­cer­ned makes per­so­nal data available to us, which must then be pro­ce­s­sed by us. For exam­ple, the data sub­ject is obli­ged to pro­vide us with per­so­nal data if our com­pany con­clu­des a con­tract with them. Fail­ure to pro­vide the per­so­nal data would mean that the con­tract with the data sub­ject could not be con­clu­ded.
Before per­so­nal data is pro­vi­ded by the data sub­ject, the data sub­ject must cont­act one of our employees. Our employee cla­ri­fies to the data sub­ject on a case-by-case basis whe­ther the pro­vi­sion of the per­so­nal data is requi­red by law or con­tract or is neces­sary for the con­clu­sion of the con­tract, whe­ther there is an obli­ga­tion to pro­vide the per­so­nal data and what the con­se­quen­ces would be if the per­so­nal data were not pro­vi­ded.