Pri­va­cy Policy

We are very de­light­ed that you have shown in­ter­est in our en­ter­prise. Data pro­tec­tion is of a par­tic­u­lar­ly high pri­or­i­ty for the man­age­ment of the CAVI Real Es­tate GmbH. The use of the In­ter­net pages of the CAVI Real Es­tate GmbH is pos­si­ble with­out any in­di­ca­tion of per­son­al data; how­ev­er, if a data sub­ject wants to use spe­cial en­ter­prise ser­vices via our web­site, pro­cess­ing of per­son­al data could be­come nec­es­sary. If the pro­cess­ing of per­son­al data is nec­es­sary and there is no statu­to­ry ba­sis for such pro­cess­ing, we gen­er­al­ly ob­tain con­sent from the data subject. 

 

The pro­cess­ing of per­son­al data, such as the name, ad­dress, e‑mail ad­dress, or tele­phone num­ber of a data sub­ject shall al­ways be in line with the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR), and in ac­cor­dance with the coun­try-spe­cif­ic data pro­tec­tion reg­u­la­tions ap­plic­a­ble to the CAVI Real Es­tate GmbH. By means of this data pro­tec­tion de­c­la­ra­tion, our en­ter­prise would like to in­form the gen­er­al pub­lic of the na­ture, scope, and pur­pose of the per­son­al data we col­lect, use and process. Fur­ther­more, data sub­jects are in­formed, by means of this data pro­tec­tion de­c­la­ra­tion, of the rights to which they are entitled. 

 

As the con­troller, the CAVI Real Es­tate GmbH has im­ple­ment­ed nu­mer­ous tech­ni­cal and or­ga­ni­za­tion­al mea­sures to en­sure the most com­plete pro­tec­tion of per­son­al data processed through this web­site. How­ev­er, In­ter­net-based data trans­mis­sions may in prin­ci­ple have se­cu­ri­ty gaps, so ab­solute pro­tec­tion may not be guar­an­teed. For this rea­son, every data sub­ject is free to trans­fer per­son­al data to us via al­ter­na­tive means, e.g. by telephone.

1. De­f­i­n­i­tions

The data pro­tec­tion de­c­la­ra­tion of the CA is based on the terms used by the Eu­ro­pean leg­is­la­tor for the adop­tion of the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR). Our data pro­tec­tion de­c­la­ra­tion should be leg­i­ble and un­der­stand­able for the gen­er­al pub­lic, as well as our cus­tomers and busi­ness part­ners. To en­sure this, we would like to first ex­plain the ter­mi­nol­o­gy used. Our data pro­tec­tion de­c­la­ra­tion should be leg­i­ble and un­der­stand­able for the gen­er­al pub­lic, as well as our cus­tomers and busi­ness part­ners. To en­sure this, we would like to first ex­plain the ter­mi­nol­o­gy used.

 

In this data pro­tec­tion de­c­la­ra­tion, we use, in­ter alia, the fol­low­ing terms: 

 

a) Per­son­al data 

 

Per­son­al data means any in­for­ma­tion re­lat­ing to an iden­ti­fied or iden­ti­fi­able nat­ur­al per­son (“data sub­ject”). An iden­ti­fi­able nat­ur­al per­son is one who can be iden­ti­fied, di­rect­ly or in­di­rect­ly, in par­tic­u­lar by ref­er­ence to an iden­ti­fi­er such as a name, an iden­ti­fi­ca­tion num­ber, lo­ca­tion data, an on­line iden­ti­fi­er or to one or more fac­tors spe­cif­ic to the phys­i­cal, phys­i­o­log­i­cal, ge­net­ic, men­tal, eco­nom­ic, cul­tur­al or so­cial iden­ti­ty of that nat­ur­al person 

 

b) Data subject 

 

Data sub­ject is any iden­ti­fied or iden­ti­fi­able nat­ur­al per­son, whose per­son­al data is processed by the con­troller re­spon­si­ble for the processing. 

 

c) Processing 

 

Pro­cess­ing is any op­er­a­tion or set of op­er­a­tions which is per­formed on per­son­al data or on sets of per­son­al data, whether or not by au­to­mat­ed means, such as col­lec­tion, record­ing, or­gan­i­sa­tion, struc­tur­ing, stor­age, adap­ta­tion or al­ter­ation, re­trieval, con­sul­ta­tion, use, dis­clo­sure by trans­mis­sion, dis­sem­i­na­tion or oth­er­wise mak­ing avail­able, align­ment or com­bi­na­tion, re­stric­tion, era­sure or destruction. 

 

d) Re­stric­tion of processing 

 

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

 

e) Profiling 

 

Pro­fil­ing means any form of au­to­mat­ed pro­cess­ing of per­son­al data con­sist­ing of the use of per­son­al data to eval­u­ate cer­tain per­son­al as­pects re­lat­ing to a nat­ur­al per­son, in par­tic­u­lar to analyse or pre­dict as­pects con­cern­ing that nat­ur­al person’s per­for­mance at work, eco­nom­ic sit­u­a­tion, health, per­son­al pref­er­ences, in­ter­ests, re­li­a­bil­i­ty, be­hav­iour, lo­ca­tion or movements. 

 

f) Pseudonymisation 

 

Pseu­do­nymi­sa­tion is the pro­cess­ing of per­son­al data in such a man­ner that the per­son­al data can no longer be at­trib­uted to a spe­cif­ic data sub­ject with­out the use of ad­di­tion­al in­for­ma­tion, pro­vid­ed that such ad­di­tion­al in­for­ma­tion is kept sep­a­rate­ly and is sub­ject to tech­ni­cal and or­gan­i­sa­tion­al mea­sures to en­sure that the per­son­al data are not at­trib­uted to an iden­ti­fied or iden­ti­fi­able nat­ur­al person. 

 

g) Con­troller or con­troller re­spon­si­ble for the processing 

 

Con­troller or con­troller re­spon­si­ble for the pro­cess­ing is the nat­ur­al or le­gal per­son, pub­lic au­thor­i­ty, agency or oth­er body which, alone or joint­ly with oth­ers, de­ter­mines the pur­pos­es and means of the pro­cess­ing of per­son­al data; where the pur­pos­es and means of such pro­cess­ing are de­ter­mined by Union or Mem­ber State law, the con­troller or the spe­cif­ic cri­te­ria for its nom­i­na­tion may be pro­vid­ed for by Union or Mem­ber State law. 

 

h) Processor 

 

Proces­sor is a nat­ur­al or le­gal per­son, pub­lic au­thor­i­ty, agency or oth­er body which process­es per­son­al data on be­half of the controller. 

 

i) Recipient 

 

Re­cip­i­ent is a nat­ur­al or le­gal per­son, pub­lic au­thor­i­ty, agency or an­oth­er body, to which the per­son­al data are dis­closed, whether a third par­ty or not. How­ev­er, pub­lic au­thor­i­ties which may re­ceive per­son­al data in the frame­work of a par­tic­u­lar in­quiry in ac­cor­dance with Union or Mem­ber State law shall not be re­gard­ed as re­cip­i­ents; the pro­cess­ing of those data by those pub­lic au­thor­i­ties shall be in com­pli­ance with the ap­plic­a­ble data pro­tec­tion rules ac­cord­ing to the pur­pos­es of the processing 

 

j) Third party 

 

Third par­ty is a nat­ur­al or le­gal per­son, pub­lic au­thor­i­ty, agency or body oth­er than the data sub­ject, con­troller, proces­sor and per­sons who, un­der the di­rect au­thor­i­ty of the con­troller or proces­sor, are au­tho­rised to process per­son­al data. 

 

k) Consen 

 

Con­sent of the data sub­ject is any freely giv­en, spe­cif­ic, in­formed and un­am­bigu­ous in­di­ca­tion of the data subject’s wish­es by which he or she, by a state­ment or by a clear af­fir­ma­tive ac­tion, sig­ni­fies agree­ment to the pro­cess­ing of per­son­al data re­lat­ing to him or her.

 

2. Name and Ad­dress of the controller

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

3. Cook­ies

The In­ter­net pages of the CAVI Real Es­tate GmbH use cook­ies. Cook­ies are text files that are stored in a com­put­er sys­tem via an In­ter­net browser. 

 

Many In­ter­net sites and servers use cook­ies. Many cook­ies con­tain a so-called cook­ie ID. A cook­ie ID is a unique iden­ti­fi­er of the cook­ie. It con­sists of a char­ac­ter string through which In­ter­net pages and servers can be as­signed to the spe­cif­ic In­ter­net brows­er in which the cook­ie was stored. This al­lows vis­it­ed In­ter­net sites and servers to dif­fer­en­ti­ate the in­di­vid­ual brows­er of the dats sub­ject from oth­er In­ter­net browsers that con­tain oth­er cook­ies. A spe­cif­ic In­ter­net brows­er can be rec­og­nized and iden­ti­fied us­ing the unique cook­ie ID. 

 

Through the use of cook­ies, the CAVI Real Es­tate GmbH can pro­vide the users of this web­site with more user-friend­ly ser­vices that would not be pos­si­ble with­out the cook­ie setting. 

 

By means of a cook­ie, the in­for­ma­tion and of­fers on our web­site can be op­ti­mized with the user in mind. Cook­ies al­low us, as pre­vi­ous­ly men­tioned, to rec­og­nize our web­site users. The pur­pose of this recog­ni­tion is to make it eas­i­er for users to uti­lize our web­site. The web­site user that uses cook­ies, e.g. does not have to en­ter ac­cess data each time the web­site is ac­cessed, be­cause this is tak­en over by the web­site, and the cook­ie is thus stored on the user’s com­put­er sys­tem. An­oth­er ex­am­ple is the cook­ie of a shop­ping cart in an on­line shop. The on­line store re­mem­bers the ar­ti­cles that a cus­tomer has placed in the vir­tu­al shop­ping cart via a cookie. 

 

The data sub­ject may, at any time, pre­vent the set­ting of cook­ies through our web­site by means of a cor­re­spond­ing set­ting of the In­ter­net brows­er used, and may thus per­ma­nent­ly deny the set­ting of cook­ies. Fur­ther­more, al­ready set cook­ies may be delet­ed at any time via an In­ter­net brows­er or oth­er soft­ware pro­grams. This is pos­si­ble in all pop­u­lar In­ter­net browsers. If the data sub­ject de­ac­ti­vates the set­ting of cook­ies in the In­ter­net brows­er used, not all func­tions of our web­site may be en­tire­ly usable.

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

The web­site of the CAVI Real Es­tate GmbH col­lects a se­ries of gen­er­al data and in­for­ma­tion when a data sub­ject or au­to­mat­ed sys­tem calls up the web­site. This gen­er­al data and in­for­ma­tion are stored in the serv­er log files. Col­lect­ed may be (1) the brows­er types and ver­sions used, (2) the op­er­at­ing sys­tem used by the ac­cess­ing sys­tem, (3) the web­site from which an ac­cess­ing sys­tem reach­es our web­site (so-called re­fer­rers), (4) the sub-web­sites, (5) the date and time of ac­cess to the In­ter­net site, (6) an In­ter­net pro­to­col ad­dress (IP ad­dress), (7) the In­ter­net ser­vice provider of the ac­cess­ing sys­tem, and (8) any oth­er sim­i­lar data and in­for­ma­tion that may be used in the event of at­tacks on our in­for­ma­tion tech­nol­o­gy systems. 

 

When us­ing these gen­er­al data and in­for­ma­tion, the CAVI Real Es­tate GmbH does not draw any con­clu­sions about the data sub­ject. Rather, this in­for­ma­tion is need­ed to (1) de­liv­er the con­tent of our web­site cor­rect­ly, (2) op­ti­mize the con­tent of our web­site as well as its ad­ver­tise­ment, (3) en­sure the long-term vi­a­bil­i­ty of our in­for­ma­tion tech­nol­o­gy sys­tems and web­site tech­nol­o­gy, and (4) pro­vide law en­force­ment au­thor­i­ties with the in­for­ma­tion nec­es­sary for crim­i­nal pros­e­cu­tion in case of a cy­ber-at­tack. There­fore, the CAVI Real Es­tate Gmb­HA an­a­lyzes anony­mous­ly col­lect­ed data and in­for­ma­tion sta­tis­ti­cal­ly, with the aim of in­creas­ing the data pro­tec­tion and data se­cu­ri­ty of our en­ter­prise, and to en­sure an op­ti­mal lev­el of pro­tec­tion for the per­son­al data we process. The anony­mous data of the serv­er log files are stored sep­a­rate­ly from all per­son­al data pro­vid­ed by a data subject.

5. Con­tact pos­si­bil­i­ty via the website

The web­site of the CAVI Real Es­tate GmbH con­tains in­for­ma­tion that en­ables a quick elec­tron­ic con­tact to our en­ter­prise, as well as di­rect com­mu­ni­ca­tion with us, which also in­cludes a gen­er­al ad­dress of the so-called elec­tron­ic mail (e‑mail ad­dress). If a data sub­ject con­tacts the con­troller by e‑mail or via a con­tact form, the per­son­al data trans­mit­ted by the data sub­ject are au­to­mat­i­cal­ly stored. Such per­son­al data trans­mit­ted on a vol­un­tary ba­sis by a data sub­ject to the data con­troller are stored for the pur­pose of pro­cess­ing or con­tact­ing the data sub­ject. There is no trans­fer of this per­son­al data to third parties

6. Rou­tine era­sure and block­ing of per­son­al data

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

 

If the stor­age pur­pose is not ap­plic­a­ble, or if a stor­age pe­ri­od pre­scribed by the Eu­ro­pean leg­is­la­tor or an­oth­er com­pe­tent leg­is­la­tor ex­pires, the per­son­al data are rou­tine­ly blocked or erased in ac­cor­dance with le­gal requirements.

7. Rights of the data subject
a) Right of confirmation

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

b) Right of access

Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor to ob­tain from the con­troller free in­for­ma­tion about his or her per­son­al data stored at any time and a copy of this in­for­ma­tion. Fur­ther­more, the Eu­ro­pean di­rec­tives and reg­u­la­tions grant the data sub­ject ac­cess to the fol­low­ing information:
    • the pur­pos­es of the processing
    • the cat­e­gories of per­son­al data concerned
    • the re­cip­i­ents or cat­e­gories of re­cip­i­ents to whom the per­son­al data have been or will be dis­closed, in par­tic­u­lar re­cip­i­ents in third coun­tries or in­ter­na­tion­al organisations
    • where pos­si­ble, the en­vis­aged pe­ri­od for which the per­son­al data will be stored, or, if not pos­si­ble, the cri­te­ria used to de­ter­mine that period
    • the ex­is­tence of the right to re­quest from the con­troller rec­ti­fi­ca­tion or era­sure of per­son­al data, or re­stric­tion of pro­cess­ing of per­son­al data con­cern­ing the data sub­ject, or to ob­ject to such processing
    • the ex­is­tence of the right to lodge a com­plaint with a su­per­vi­so­ry authority
    • where the per­son­al data are not col­lect­ed from the data sub­ject, any avail­able in­for­ma­tion as to their source
    • the ex­is­tence of au­to­mat­ed de­ci­sion-mak­ing, in­clud­ing pro­fil­ing, re­ferred to in Ar­ti­cle 22(1) and (4) of the GDPR and, at least in those cas­es, mean­ing­ful in­for­ma­tion about the log­ic in­volved, as well as the sig­nif­i­cance and en­vis­aged con­se­quences of such pro­cess­ing for the data subject.
Fur­ther­more, the data sub­ject shall have a right to ob­tain in­for­ma­tion as to whether per­son­al data are trans­ferred to a third coun­try or to an in­ter­na­tion­al or­gan­i­sa­tion. Where this is the case, the data sub­ject shall have the right to be in­formed of the ap­pro­pri­ate safe­guards re­lat­ing to the transfer.

If a data sub­ject wish­es to avail him­self of this right of ac­cess, he or she may, at any time, con­tact any em­ploy­ee of the controller.
c) Right to rectification

Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor to ob­tain from the con­troller with­out un­due de­lay the rec­ti­fi­ca­tion of in­ac­cu­rate per­son­al data con­cern­ing him or her. Tak­ing into ac­count the pur­pos­es of the pro­cess­ing, the data sub­ject shall have the right to have in­com­plete per­son­al data com­plet­ed, in­clud­ing by means of pro­vid­ing a sup­ple­men­tary statement.

If a data sub­ject wish­es to ex­er­cise this right to rec­ti­fi­ca­tion, he or she may, at any time, con­tact any em­ploy­ee of the controller.

d) Right to era­sure (Rightto be forgotten)
Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor to ob­tain from the con­troller the era­sure of per­son­al data con­cern­ing him or her with­out un­due de­lay, and the con­troller shall have the oblig­a­tion to erase per­son­al data with­out un­due de­lay where one of the fol­low­ing grounds ap­plies, as long as the pro­cess­ing is not necessary:
    • The per­son­al data are no longer nec­es­sary in re­la­tion to the pur­pos­es for which they were col­lect­ed or oth­er­wise processed
    • The data sub­ject with­draws con­sent to which the pro­cess­ing is based ac­cord­ing to point (a) of Ar­ti­cle 6 (1) of the GDPR or point (a) of Ar­ti­cle 9 (2) of the GDPR, and where there is no oth­er le­gal ground for the processing.
    • The data sub­ject ob­jects to the pro­cess­ing pur­suant to Ar­ti­cle 21 (1) of the GDPR and there are no over­rid­ing le­git­i­mate grounds for the pro­cess­ing, or the data sub­ject ob­jects to the pro­cess­ing pur­suant to Ar­ti­cle 21 (2) of the GDPR.
    • The per­son­al data have been un­law­ful­ly processed.
    • The per­son­al data must be erased for com­pli­ance with a le­gal oblig­a­tion in Union or Mem­ber State law to which the con­troller is subject
    • The per­son­al data have been col­lect­ed in re­la­tion to the of­fer of in­for­ma­tion so­ci­ety ser­vices re­ferred to in Ar­ti­cle 8 (1) of the GDPR.

If one of the afore­men­tioned rea­sons ap­plies, and a data sub­ject wish­es to re­quest the era­sure of per­son­al data stored by the CAVI Real Es­tate GmbH, he or she may, at any time, con­tact any em­ploy­ee of the con­troller. An em­ploy­ee of CAVI Real Es­tate GmbH shall prompt­ly en­sure that the era­sure re­quest is com­plied with immediately.

Where the con­troller has made per­son­al data pub­lic and is oblig­ed pur­suant to Ar­ti­cle 17 (1) to erase the per­son­al data, the con­troller, tak­ing ac­count of avail­able tech­nol­o­gy and the cost of im­ple­men­ta­tion, shall take rea­son­able steps, in­clud­ing tech­ni­cal mea­sures, to in­form oth­er con­trollers pro­cess­ing the per­son­al data that the data sub­ject has re­quest­ed era­sure by such con­trollers of any links to, or copy or repli­ca­tion of, those per­son­al data, as far as pro­cess­ing is not re­quired. An em­ploy­ees of the CAVI Real Es­tate GmbH will arrange the nec­es­sary mea­sures in in­di­vid­ual cases.

e) Right of re­stric­tion of processin
Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor to ob­tain from the con­troller re­stric­tion of pro­cess­ing where one of the fol­low­ing applies:
    • The ac­cu­ra­cy of the per­son­al data is con­test­ed by the data sub­ject, for a pe­ri­od en­abling the con­troller to ver­i­fy the ac­cu­ra­cy of the per­son­al data.
    • The pro­cess­ing is un­law­ful and the data sub­ject op­pos­es the era­sure of the per­son­al data and re­quests in­stead the re­stric­tion of their use instead.
    • The con­troller no longer needs the per­son­al data for the pur­pos­es of the pro­cess­ing, but they are re­quired by the data sub­ject for the es­tab­lish­ment, ex­er­cise or de­fence of le­gal claims.
    • The data sub­ject has ob­ject­ed to pro­cess­ing pur­suant to Ar­ti­cle 21 (1) of the GDPR pend­ing the ver­i­fi­ca­tion whether the le­git­i­mate grounds of the con­troller over­ride those of the data subject
If one of the afore­men­tioned con­di­tions is met, and a data sub­ject wish­es to re­quest the re­stric­tion of the pro­cess­ing of per­son­al data stored by the CAVI Real Es­tate GmbH, he or she may at any time con­tact any em­ploy­ee of the con­troller. The em­ploy­ee of the CAVI Real Es­tate GmbH will arrange the re­stric­tion of the processing.

f) Right to data portability
Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor, to re­ceive the per­son­al data con­cern­ing him or her, which was pro­vid­ed to a con­troller, in a struc­tured, com­mon­ly used and ma­chine-read­able for­mat. He or she shall have the right to trans­mit those data to an­oth­er con­troller with­out hin­drance from the con­troller to which the per­son­al data have been pro­vid­ed, as long as the pro­cess­ing is based on con­sent pur­suant to point (a) of Ar­ti­cle 6 (1) of the GDPR or point (a) of Ar­ti­cle 9 (2) of the GDPR, or on a con­tract pur­suant to point (b) of Ar­ti­cle 6 (1) of the GDPR, and the pro­cess­ing is car­ried out by au­to­mat­ed means, as long as the pro­cess­ing is not nec­es­sary for the per­for­mance of a task car­ried out in the pub­lic in­ter­est or in the ex­er­cise of of­fi­cial au­thor­i­ty vest­ed in the controller.


Fur­ther­more, in ex­er­cis­ing his or her right to data porta­bil­i­ty pur­suant to Ar­ti­cle 20 (1) of the GDPR, the data sub­ject shall have the right to have per­son­al data trans­mit­ted di­rect­ly from one con­troller to an­oth­er, where tech­ni­cal­ly fea­si­ble and when do­ing so does not ad­verse­ly af­fect the rights and free­doms of oth­ers.In or­der to as­sert the right to data porta­bil­i­ty, the data sub­ject may at any time con­tact any em­ploy­ee of the CAVI Real Es­tate GmbH.

g) Right to objec
Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor to ob­ject, on grounds re­lat­ing to his or her par­tic­u­lar sit­u­a­tion, at any time, to pro­cess­ing of per­son­al data con­cern­ing him or her, which is based on point (e) or (f) of Ar­ti­cle 6 (1) of the GDPR. This also ap­plies to pro­fil­ing based on these provisions.


The CAVI Real Es­tate GmbH shall no longer process the per­son­al data in the event of the ob­jec­tion, un­less we can demon­strate com­pelling le­git­i­mate grounds for the pro­cess­ing which over­ride the in­ter­ests, rights and free­doms of the data sub­ject, or for the es­tab­lish­ment, ex­er­cise or de­fence of le­gal claims.If the CAVI Real Es­tate GmbH process­es per­son­al data for di­rect mar­ket­ing pur­pos­es, the data sub­ject shall have the right to ob­ject at any time to pro­cess­ing of per­son­al data con­cern­ing him or her for such mar­ket­ing. This ap­plies to pro­fil­ing to the ex­tent that it is re­lat­ed to such di­rect mar­ket­ing. If the data sub­ject ob­jects to the CAVI Real Es­tate GmbH to the pro­cess­ing for di­rect mar­ket­ing pur­pos­es, the CAVI Real Es­tate GmbH will no longer process the per­son­al data for these purposes


In ad­di­tion, the data sub­ject has the right, on grounds re­lat­ing to his or her par­tic­u­lar sit­u­a­tion, to ob­ject to pro­cess­ing of per­son­al data con­cern­ing him or her by the CA for sci­en­tif­ic or his­tor­i­cal re­search pur­pos­es, or for sta­tis­ti­cal pur­pos­es pur­suant to Ar­ti­cle 89 (1) of the GDPR, un­less the pro­cess­ing is nec­es­sary for the per­for­mance of a task car­ried out for rea­sons of pub­lic interest

In or­der to ex­er­cise the right to ob­ject, the data sub­ject may con­tact any em­ploy­ee of the CAVI Real Es­tate GmbH. In ad­di­tion, the data sub­ject is free in the con­text of the use of in­for­ma­tion so­ci­ety ser­vices, and notwith­stand­ing Di­rec­tive 2002/58/EC, to use his or her right to ob­ject by au­to­mat­ed means us­ing tech­ni­cal specifications.

h) Au­to­mat­ed in­di­vid­ual de­ci­sion-mak­ing, in­clud­ing profiling

Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor not to be sub­ject to a de­ci­sion based sole­ly on au­to­mat­ed pro­cess­ing, in­clud­ing pro­fil­ing, which pro­duces le­gal ef­fects con­cern­ing him or her, or sim­i­lar­ly sig­nif­i­cant­ly af­fects him or her, as long as the de­ci­sion (1) is not is nec­es­sary for en­ter­ing into, or the per­for­mance of, a con­tract be­tween the data sub­ject and a data con­troller, or (2) is not au­tho­rised by Union or Mem­ber State law to which the con­troller is sub­ject and which also lays down suit­able mea­sures to safe­guard the data subject’s rights and free­doms and le­git­i­mate in­ter­ests, or (3) is not based on the data subject’s ex­plic­it consent

If the de­ci­sion (1) is nec­es­sary for en­ter­ing into, or the per­for­mance of, a con­tract be­tween the data sub­ject and a data con­troller, or (2) it is based on the data subject’s ex­plic­it con­sent, the CAVI Real Es­tate GmbH shall im­ple­ment suit­able mea­sures to safe­guard the data subject’s rights and free­doms and le­git­i­mate in­ter­ests, at least the right to ob­tain hu­man in­ter­ven­tion on the part of the con­troller, to ex­press his or her point of view and con­test the decision

If the data sub­ject wish­es to ex­er­cise the rights con­cern­ing au­to­mat­ed in­di­vid­ual de­ci­sion-mak­ing, he or she may, at any time, con­tact any em­ploy­ee of the CAVI Real Es­tate GmbH.

If the de­ci­sion (1) is nec­es­sary for en­ter­ing into, or the per­for­mance of, a con­tract be­tween the data sub­ject and a data con­troller, or (2) it is based on the data subject’s ex­plic­it con­sent, the CAVI Real Es­tate GmbH shall im­ple­ment suit­able mea­sures to safe­guard the data subject’s rights and free­doms and le­git­i­mate in­ter­ests, at least the right to ob­tain hu­man in­ter­ven­tion on the part of the con­troller, to ex­press his or her point of view and con­test the decision

If the data sub­ject wish­es to ex­er­cise the rights con­cern­ing au­to­mat­ed in­di­vid­ual de­ci­sion-mak­ing, he or she may, at any time, con­tact any em­ploy­ee of the CAVI Real Es­tate GmbH.


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

Each data sub­ject shall have the right grant­ed by the Eu­ro­pean leg­is­la­tor to with­draw his or her con­sent to pro­cess­ing of his or her per­son­al data at any time.
If the data sub­ject wish­es to ex­er­cise the right to with­draw the con­sent, he or she may, at any time, con­tact any em­ploy­ee of the CAVI Real Es­tate GmbH.
8. Web Fonts by Adobe Typekit

For the uni­form rep­re­sen­ta­tion of fonts, we use so-called web fonts, which are pro­vid­ed by Adobe. When you call up a page, your brows­er loads the re­quired web fonts into your brows­er cache to dis­play texts and fonts cor­rect­ly. For this pur­pose, the brows­er you are us­ing must con­nect to the Adobe servers. As a re­sult, Adobe is in­formed that our web­site has been ac­cessed via your IP ad­dress. Adobe Type­Kit fonts are used in the in­ter­est of a uni­form and at­trac­tive pre­sen­ta­tion of our on­line of­fers. The le­gal ba­sis is Art. 6 Para­graph. 1 lit. f DSGVO.

For more in­for­ma­tion about Adobe Type­Kit Fonts, please see the Adobe Pri­va­cy Pol­i­cy for Ger­many: https://www.adobe.com/de/privacy/policies/typekit.html

You can set your brows­er so that the fonts are not loaded from the Adobe servers (e. g. B. by in­stalling add-ons like No­Script or Ghostery). If your brows­er does not sup­port the Adobe fonts or if you pre­vent ac­cess to the Adobe servers, the text will be dis­played in the system’s de­fault font.

9. Google Maps

Diese Web­seite nutzt Google Maps zur Darstel­lung in­ter­ak­tiv­er Karten und zur Er­stel­lung von An­fahrts­beschrei­bun­gen. Google Maps ist ein Kar­ten­di­enst von Google Inc., 1600 Am­phithe­atre Park­way, Moun­tain View, Cal­i­for­nia 94043, USA. Durch die Nutzung von Google Maps kön­nen In­for­ma­tio­nen über die Be­nutzung dieser Web­site ein­schließlich Ihrer IP-Adresse und der im Rah­men der Routen­plan­er­funk­tion eingegebe­nen (Start-) Adresse an Google in den USA über­tra­gen wer­den. Wenn Sie eine Web­seite un­seres In­ter­ne­tauftritts aufrufen, die Google Maps en­thält, baut Ihr Brows­er eine di­rek­te Verbindung mit den Servern von Google auf. Der Karten­in­halt wird von Google di­rekt an Ihren Brows­er über­mit­telt und von diesem in die Web­seite einge­bun­den. Da­her haben wir keinen Ein­fluss auf den Um­fang der auf diese Weise von Google er­hobe­nen Dat­en. Entsprechend un­serem Ken­nt­nis­stand sind dies zu­min­d­est fol­gende Daten:

  • Da­tum und Uhrzeit des Be­suchs auf der be­tr­e­f­fend­en Webseite,

  • In­ter­ne­tadresse oder URL der aufgerufe­nen Webseite,

  • IP-Adresse, im Rah­men der Routen­pla­nung eingegebene (Start-)Anschrift.

Auf die weit­ere Ve­r­ar­beitung und Nutzung der Dat­en durch Google haben wir keinen Ein­fluss und kön­nen da­her hi­er­für keine Ve­r­ant­wor­tung übernehmen. Wenn Sie nicht möcht­en, dass Google über un­seren In­ter­ne­tauftritt Dat­en über Sie er­hebt, ve­r­ar­beit­et oder nutzt, kön­nen Sie in Ihrem Browsere­in­stel­lun­gen JavaScript deak­tivieren. In diesem Fall kön­nen Sie die Kar­te­nanzeige je­doch nicht nutzen.

Zweck und Um­fang der Daten­er­he­bung und die weit­ere Ve­r­ar­beitung und Nutzung der Dat­en durch Google sowie Ihre dies­bezüglichen Rechte und Ein­stel­lungsmöglichkeit­en zum Schutz Ihrer Pri­vat­sphäre ent­nehmen Sie bitte den Daten­schutzhin­weisen von Google (https://policies.google.com/privacy?hl=de).

Durch die Nutzung un­ser­er Web­seite erk­lären Sie sich mit der Bear­beitung der über Sie er­hobe­nen Dat­en durch Google Maps Routen­plan­er in der zu­vor beschriebe­nen Art und Weise und zu dem zu­vor be­nan­nten Zweck einverstanden.

10. SSL or TLS Encryption

For se­cu­ri­ty rea­sons and to pro­tect the trans­mis­sion of con­fi­den­tial con­tent, such as or­ders or in­quiries that you send to us as the site op­er­a­tor, this site uses SSL or TLS en­cryp­tion. TLS en­cryp­tion. You can recog­nise an en­crypt­ed con­nec­tion by the fact that the ad­dress line of the brows­er changes from “http://” to “https://” and by the lock sym­bol in your brows­er line.

If the SSL or TLS en­cryp­tion is ac­ti­vat­ed, the data you trans­mit to us can­not be read by third parties.

11. Le­gal ba­sis for the processing

Art. 6(1) lit. (1) lit. a GDPR serves as the le­gal ba­sis for pro­cess­ing op­er­a­tions for which we ob­tain con­sent for a spe­cif­ic pro­cess­ing pur­pose. If the pro­cess­ing of per­son­al data is nec­es­sary for the per­for­mance of a con­tract to which the data sub­ject is par­ty, as is the case, for ex­am­ple, when pro­cess­ing op­er­a­tions are nec­es­sary for the sup­ply of goods or to pro­vide any oth­er ser­vice, the pro­cess­ing is based on Ar­ti­cle 6(1) lit. b GDPR. The same ap­plies to such pro­cess­ing op­er­a­tions which are nec­es­sary for car­ry­ing out pre-con­trac­tu­al mea­sures, for ex­am­ple in the case of in­quiries con­cern­ing our prod­ucts or ser­vices. Is our com­pa­ny sub­ject to a le­gal oblig­a­tion by which pro­cess­ing of per­son­al data is re­quired, such as for the ful­fill­ment of tax oblig­a­tions, the pro­cess­ing is based on Art. 6(1) lit. c GDPR. In rare cas­es, the pro­cess­ing of per­son­al data may be nec­es­sary to pro­tect the vi­tal in­ter­ests of the data sub­ject or of an­oth­er nat­ur­al per­son. This would be the case, for ex­am­ple, if a vis­i­tor were in­jured in our com­pa­ny and his name, age, health in­sur­ance data or oth­er vi­tal in­for­ma­tion would have to be passed on to a doc­tor, hos­pi­tal or oth­er third par­ty. Then the pro­cess­ing would be based on Art. 6(1) lit. d GDPR.

Fi­nal­ly, pro­cess­ing op­er­a­tions could be based on Ar­ti­cle 6(1) lit. f GDPR. This le­gal ba­sis is used for pro­cess­ing op­er­a­tions which are not cov­ered by any of the above­men­tioned le­gal grounds, if pro­cess­ing is nec­es­sary for the pur­pos­es of the le­git­i­mate in­ter­ests pur­sued by our com­pa­ny or by a third par­ty, ex­cept where such in­ter­ests are over­rid­den by the in­ter­ests or fun­da­men­tal rights and free­doms of the data sub­ject which re­quire pro­tec­tion of per­son­al data Such pro­cess­ing op­er­a­tions are par­tic­u­lar­ly per­mis­si­ble be­cause they have been specif­i­cal­ly men­tioned by the Eu­ro­pean leg­is­la­tor. He con­sid­ered that a le­git­i­mate in­ter­est could be as­sumed if the data sub­ject is a client of the con­troller (Recital 47 Sen­tence 2 GDPR).

Fi­nal­ly, pro­cess­ing op­er­a­tions could be based on Ar­ti­cle 6(1) lit. f GDPR. This le­gal ba­sis is used for pro­cess­ing op­er­a­tions which are not cov­ered by any of the above­men­tioned le­gal grounds, if pro­cess­ing is nec­es­sary for the pur­pos­es of the le­git­i­mate in­ter­ests pur­sued by our com­pa­ny or by a third par­ty, ex­cept where such in­ter­ests are over­rid­den by the in­ter­ests or fun­da­men­tal rights and free­doms of the data sub­ject which re­quire pro­tec­tion of per­son­al data Such pro­cess­ing op­er­a­tions are par­tic­u­lar­ly per­mis­si­ble be­cause they have been specif­i­cal­ly men­tioned by the Eu­ro­pean leg­is­la­tor. He con­sid­ered that a le­git­i­mate in­ter­est could be as­sumed if the data sub­ject is a client of the con­troller (Recital 47 Sen­tence 2 GDPR).
12. The le­git­i­mate in­ter­ests pur­sued by the con­troller or by a third party

Where the pro­cess­ing of per­son­al data is based on Ar­ti­cle 6(1) lit. f GDPR our le­git­i­mate in­ter­est is to car­ry out our busi­ness in fa­vor of the well-be­ing of all our em­ploy­ees and the shareholders

13. Pe­ri­od for which the per­son­al data will be stored

The cri­te­ria used to de­ter­mine the pe­ri­od of stor­age of per­son­al data is the re­spec­tive statu­to­ry re­ten­tion pe­ri­od. Af­ter ex­pi­ra­tion of that pe­ri­od, the cor­re­spond­ing data is rou­tine­ly delet­ed, as long as it is no longer nec­es­sary for the ful­fill­ment of the con­tract or the ini­ti­a­tion of a contract.

14. Pro­vi­sion of per­son­al data as statu­to­ry or con­trac­tu­al re­quire­ment; Re­quire­ment nec­es­sary to en­ter into a con­tract; Oblig­a­tion of the data sub­ject to pro­vide the per­son­al data; pos­si­ble con­se­quences of fail­ure to pro­vide such data

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

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

Be­fore per­son­al data is pro­vid­ed by the data sub­ject, the data sub­ject must con­tact any em­ploy­ee. The em­ploy­ee clar­i­fies to the data sub­ject whether the pro­vi­sion of the per­son­al data is re­quired by law or con­tract or is nec­es­sary for the con­clu­sion of the con­tract, whether there is an oblig­a­tion to pro­vide the per­son­al data and the con­se­quences of non-pro­vi­sion of the per­son­al data.

15. Ex­is­tence of au­to­mat­ed decision-making

As a re­spon­si­ble com­pa­ny, we do not use au­to­mat­ic de­ci­sion-mak­ing or profiling.

16. Sta­tus and up­date of this data pro­tec­tion declaration

This data pro­tec­tion de­c­la­ra­tion has the sta­tus of Oc­to­ber 2021. We re­serve the right to up­date the data pro­tec­tion de­c­la­ra­tion in due course in or­der to im­prove data pro­tec­tion and/or to adapt it to changes in of­fi­cial prac­tice or jurisdiction.