Pri­va­cy Pol­i­cy

We are very delight­ed that you have shown inter­est in our enter­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 Wat­ti­fy GmbH. The use of the Inter­net pages of the Wat­ti­fy GmbH is pos­si­ble with­out any indi­ca­tion of per­son­al data; how­ev­er, if a data sub­ject wants to use spe­cial enter­prise ser­vices via our web­site, pro­cess­ing of per­son­al data could become nec­es­sary. If the pro­cess­ing of per­son­al data is nec­es­sary and there is no statu­to­ry basis for such pro­cess­ing, we gen­er­al­ly obtain con­sent from the data sub­ject.

Our trans­paren­cy doc­u­ment in accor­dance with Art. 13 and 14 GDPR is avail­able HERE .

The pro­cess­ing of per­son­al data, such as the name, address, e‑mail address, or tele­phone num­ber of a data sub­ject shall always be in line with the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GDPR), and in accor­dance with the coun­try-spe­cif­ic data pro­tec­tion reg­u­la­tions applic­a­ble to the Wat­ti­fy GmbH. By means of this data pro­tec­tion dec­la­ra­tion, our enter­prise would like to inform the gen­er­al pub­lic of the nature, scope, and pur­pose of the per­son­al data we col­lect, use and process. Fur­ther­more, data sub­jects are informed, by means of this data pro­tec­tion dec­la­ra­tion, of the rights to which they are enti­tled.

As the con­troller, the Wat­ti­fy GmbH has imple­ment­ed numer­ous tech­ni­cal and orga­ni­za­tion­al mea­sures to ensure the most com­plete pro­tec­tion of per­son­al data processed through this web­site. How­ev­er, Inter­net-based data trans­mis­sions may in prin­ci­ple have secu­ri­ty gaps, so absolute 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 alter­na­tive means, e.g. by tele­phone.

1. Def­i­n­i­tions

The data pro­tec­tion dec­la­ra­tion of the Wat­ti­fy GmbH is based on the terms used by the Euro­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 dec­la­ra­tion should be leg­i­ble and under­stand­able for the gen­er­al pub­lic, as well as our cus­tomers and busi­ness part­ners. To ensure this, we would like to first explain the ter­mi­nol­o­gy used.

In this data pro­tec­tion dec­la­ra­tion, we use, inter alia, the fol­low­ing terms:

• a) Per­son­al data

Per­son­al data means any infor­ma­tion relat­ing to an iden­ti­fied or iden­ti­fi­able nat­ur­al per­son (“data sub­ject”). An iden­ti­fi­able nat­ur­al per­son is one who can be iden­ti­fied, direct­ly or indi­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, loca­tion data, an online 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, genet­ic, men­tal, eco­nom­ic, cul­tur­al or social iden­ti­ty of that nat­ur­al per­son.

• b) Data sub­ject

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 respon­si­ble for the pro­cess­ing.

• c) Pro­cess­ing

Pro­cess­ing is any oper­a­tion or set of oper­a­tions which is per­formed on per­son­al data or on sets of per­son­al data, whether or not by auto­mat­ed means, such as col­lec­tion, record­ing, organ­i­sa­tion, struc­tur­ing, stor­age, adap­ta­tion or alter­ation, retrieval, 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, restric­tion, era­sure or destruc­tion.

• d) Restric­tion of pro­cess­ing

Restric­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) Pro­fil­ing

Pro­fil­ing means any form of auto­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 aspects relat­ing to a nat­ur­al per­son, in par­tic­u­lar to analyse or pre­dict aspects con­cern­ing that nat­ur­al per­son­’s per­for­mance at work, eco­nom­ic sit­u­a­tion, health, per­son­al pref­er­ences, inter­ests, reli­a­bil­i­ty, behav­iour, loca­tion or move­ments.

• f) Pseu­do­nymi­sa­tion

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 attrib­uted to a spe­cif­ic data sub­ject with­out the use of addi­tion­al infor­ma­tion, pro­vid­ed that such addi­tion­al infor­ma­tion is kept sep­a­rate­ly and is sub­ject to tech­ni­cal and organ­i­sa­tion­al mea­sures to ensure that the per­son­al data are not attrib­uted to an iden­ti­fied or iden­ti­fi­able nat­ur­al per­son.

• g) Con­troller or con­troller respon­si­ble for the pro­cess­ing

Con­troller or con­troller respon­si­ble for the pro­cess­ing is the nat­ur­al or legal per­son, pub­lic author­i­ty, agency or oth­er body which, alone or joint­ly with oth­ers, deter­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 deter­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) Proces­sor

Proces­sor is a nat­ur­al or legal per­son, pub­lic author­i­ty, agency or oth­er body which process­es per­son­al data on behalf of the con­troller.

• i) Recip­i­ent

Recip­i­ent is a nat­ur­al or legal per­son, pub­lic author­i­ty, agency or anoth­er body, to which the per­son­al data are dis­closed, whether a third par­ty or not. How­ev­er, pub­lic author­i­ties which may receive per­son­al data in the frame­work of a par­tic­u­lar inquiry in accor­dance with Union or Mem­ber State law shall not be regard­ed as recip­i­ents; the pro­cess­ing of those data by those pub­lic author­i­ties shall be in com­pli­ance with the applic­a­ble data pro­tec­tion rules accord­ing to the pur­pos­es of the pro­cess­ing.

• j) Third par­ty

Third par­ty is a nat­ur­al or legal per­son, pub­lic author­i­ty, agency or body oth­er than the data sub­ject, con­troller, proces­sor and per­sons who, under the direct author­i­ty of the con­troller or proces­sor, are autho­rised to process per­son­al data.

• k) Con­sent

Con­sent of the data sub­ject is any freely giv­en, spe­cif­ic, informed and unam­bigu­ous indi­ca­tion of the data sub­jec­t’s wish­es by which he or she, by a state­ment or by a clear affir­ma­tive action, sig­ni­fies agree­ment to the pro­cess­ing of per­son­al data relat­ing to him or her.

2. Name and Address of the con­troller

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 applic­a­ble in Mem­ber states of the Euro­pean Union and oth­er pro­vi­sions relat­ed to data pro­tec­tion is:

Wat­ti­fy GmbH

Untere Nab­burg­er Str. 10

92224 Amberg

Deutsch­land

Phone: +49 (0) 9621 77 88 15 0

Email: hello@wattify.de

Web­site: https://wattify.app/

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

The Data Pro­tec­tion Offi­cer of the con­troller is:

Phone: +498131779870

Email: info@dg-datenschutz.de

Web­site: http://​www​.dg​-daten​schutz​.de/

Any data sub­ject may, at any time, con­tact our Data Pro­tec­tion Offi­cer direct­ly with all ques­tions and sug­ges­tions con­cern­ing data pro­tec­tion.

4. Cook­ies

The Inter­net pages of the Wat­ti­fy GmbH use cook­ies. Cook­ies are text files that are stored in a com­put­er sys­tem via an Inter­net brows­er.

Many Inter­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 Inter­net pages and servers can be assigned to the spe­cif­ic Inter­net brows­er in which the cook­ie was stored. This allows vis­it­ed Inter­net sites and servers to dif­fer­en­ti­ate the indi­vid­ual brows­er of the dats sub­ject from oth­er Inter­net browsers that con­tain oth­er cook­ies. A spe­cif­ic Inter­net brows­er can be rec­og­nized and iden­ti­fied using the unique cook­ie ID.

Through the use of cook­ies, the Wat­ti­fy 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 set­ting.

By means of a cook­ie, the infor­ma­tion and offers on our web­site can be opti­mized with the user in mind. Cook­ies allow 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 enter access data each time the web­site is accessed, because 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. Anoth­er exam­ple is the cook­ie of a shop­ping cart in an online shop. The online store remem­bers the arti­cles that a cus­tomer has placed in the vir­tu­al shop­ping cart via a cook­ie.

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 Inter­net brows­er used, and may thus per­ma­nent­ly deny the set­ting of cook­ies. Fur­ther­more, already set cook­ies may be delet­ed at any time via an Inter­net brows­er or oth­er soft­ware pro­grams. This is pos­si­ble in all pop­u­lar Inter­net browsers. If the data sub­ject deac­ti­vates the set­ting of cook­ies in the Inter­net brows­er used, not all func­tions of our web­site may be entire­ly usable.

We use the fol­low­ing cook­ies:

Cook­ie name: CRAFT_CSRF_TOKEN

Pur­pose: Ensures brows­ing secu­ri­ty for vis­i­tors by pre­vent­ing cross-site request forgery. This cook­ie is essen­tial for the secu­ri­ty of the web­site and the vis­i­tor.

Stor­age peri­od: Ses­sion

Cook­ie name: li_​gc

Pur­pose: Stores the user’s con­sent sta­tus for cook­ies on the cur­rent domain.

Stor­age peri­od: 2 Years

Cook­ie name: uc_​settings

Pur­pose: Stores the user’s con­sent sta­tus for cook­ies on the cur­rent domain.

Stor­age peri­od: Per­sis­tent

Cook­ie name: uc_​ui_​version

Pur­pose: Stores the ver­sion num­ber of the Con­sent Ban­ner UI used on the cur­rent domain.

Stor­age peri­od: Per­sis­tent

Cook­ie name: lang

Pur­pose: Saves the user-select­ed lan­guage ver­sion of a web page.

Stor­age peri­od: Ses­sion

Cook­ie name: bcook­ie

Pur­pose: Used by the social net­work­ing ser­vice LinkedIn for track­ing the use of embed­ded ser­vices.

Stor­age peri­od: 2 Years

Cook­ie name: fr

Pur­pose: Used by Face­book to dis­play a range of adver­tis­ing prod­ucts, for exam­ple real-time bids from third par­ty adver­tis­ers.

Stor­age peri­od: 3 Months

Cook­ie name: lang

Pur­pose: Set by LinkedIn when a web page con­tains an embed­ded ​“Fol­low us” win­dow.

Stor­age peri­od: Ses­sion

Cook­ie name: lidc

Pur­pose: Used by the social net­work­ing ser­vice LinkedIn for track­ing the use of embed­ded ser­vices.

Stor­age peri­od: 1 Day

Cook­ie name: tr

Pur­pose: Used by Face­book to dis­play a range of adver­tis­ing prod­ucts, for exam­ple real-time bids from third par­ty adver­tis­ers.

Stor­age peri­od: Ses­sion

Cook­ie name: User­Match­His­to­ry

Pur­pose: Ensures brows­ing secu­ri­ty for vis­i­tors by pre­vent­ing cross-page forgery of requests. This cook­ie is essen­tial for the secu­ri­ty of the web­site and the vis­i­tor.

Stor­age peri­od: Ses­sion

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

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

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

6. Reg­is­tra­tion on our web­site

The data sub­ject has the pos­si­bil­i­ty to reg­is­ter on the web­site of the con­troller with the indi­ca­tion of per­son­al data. Which per­son­al data are trans­mit­ted to the con­troller is deter­mined by the respec­tive input mask used for the reg­is­tra­tion. The per­son­al data entered by the data sub­ject are col­lect­ed and stored exclu­sive­ly for inter­nal use by the con­troller, and for his own pur­pos­es. The con­troller may request trans­fer to one or more proces­sors (e.g. a par­cel ser­vice) that also uses per­son­al data for an inter­nal pur­pose which is attrib­ut­able to the con­troller.

By reg­is­ter­ing on the web­site of the con­troller, the IP address — assigned by the Inter­net ser­vice provider (ISP) and used by the data sub­ject — date, and time of the reg­is­tra­tion are also stored. The stor­age of this data takes place against the back­ground that this is the only way to pre­vent the mis­use of our ser­vices, and, if nec­es­sary, to make it pos­si­ble to inves­ti­gate com­mit­ted offens­es. Inso­far, the stor­age of this data is nec­es­sary to secure the con­troller. This data is not passed on to third par­ties unless there is a statu­to­ry oblig­a­tion to pass on the data, or if the trans­fer serves the aim of crim­i­nal pros­e­cu­tion.

The reg­is­tra­tion of the data sub­ject, with the vol­un­tary indi­ca­tion of per­son­al data, is intend­ed to enable the con­troller to offer the data sub­ject con­tents or ser­vices that may only be offered to reg­is­tered users due to the nature of the mat­ter in ques­tion. Reg­is­tered per­sons are free to change the per­son­al data spec­i­fied dur­ing the reg­is­tra­tion at any time, or to have them com­plete­ly delet­ed from the data stock of the con­troller.

The data con­troller shall, at any time, pro­vide infor­ma­tion upon request to each data sub­ject as to what per­son­al data are stored about the data sub­ject. In addi­tion, the data con­troller shall cor­rect or erase per­son­al data at the request or indi­ca­tion of the data sub­ject, inso­far as there are no statu­to­ry stor­age oblig­a­tions. The entire­ty of the controller’s employ­ees are avail­able to the data sub­ject in this respect as con­tact per­sons.

7. Sub­scrip­tion to our newslet­ters

On the web­site of the Wat­ti­fy GmbH, users are giv­en the oppor­tu­ni­ty to sub­scribe to our enter­prise’s newslet­ter. The input mask used for this pur­pose deter­mines what per­son­al data are trans­mit­ted, as well as when the newslet­ter is ordered from the con­troller.

The Wat­ti­fy GmbH informs its cus­tomers and busi­ness part­ners reg­u­lar­ly by means of a newslet­ter about enter­prise offers. The enter­prise’s newslet­ter may only be received by the data sub­ject if (1) the data sub­ject has a valid e‑mail address and (2) the data sub­ject reg­is­ters for the newslet­ter ship­ping. A con­fir­ma­tion e‑mail will be sent to the e‑mail address reg­is­tered by a data sub­ject for the first time for newslet­ter ship­ping, for legal rea­sons, in the dou­ble opt-in pro­ce­dure. This con­fir­ma­tion e‑mail is used to prove whether the own­er of the e‑mail address as the data sub­ject is autho­rized to receive the newslet­ter.

Dur­ing the reg­is­tra­tion for the newslet­ter, we also store the IP address of the com­put­er sys­tem assigned by the Inter­net ser­vice provider (ISP) and used by the data sub­ject at the time of the reg­is­tra­tion, as well as the date and time of the reg­is­tra­tion. The col­lec­tion of this data is nec­es­sary in order to under­stand the (pos­si­ble) mis­use of the e‑mail address of a data sub­ject at a lat­er date, and it there­fore serves the aim of the legal pro­tec­tion of the con­troller.

The per­son­al data col­lect­ed as part of a reg­is­tra­tion for the newslet­ter will only be used to send our newslet­ter. In addi­tion, sub­scribers to the newslet­ter may be informed by e‑mail, as long as this is nec­es­sary for the oper­a­tion of the newslet­ter ser­vice or a reg­is­tra­tion in ques­tion, as this could be the case in the event of mod­i­fi­ca­tions to the newslet­ter offer, or in the event of a change in tech­ni­cal cir­cum­stances. There will be no trans­fer of per­son­al data col­lect­ed by the newslet­ter ser­vice to third par­ties. The sub­scrip­tion to our newslet­ter may be ter­mi­nat­ed by the data sub­ject at any time. The con­sent to the stor­age of per­son­al data, which the data sub­ject has giv­en for ship­ping the newslet­ter, may be revoked at any time. For the pur­pose of revo­ca­tion of con­sent, a cor­re­spond­ing link is found in each newslet­ter. It is also pos­si­ble to unsub­scribe from the newslet­ter at any time direct­ly on the web­site of the con­troller, or to com­mu­ni­cate this to the con­troller in a dif­fer­ent way.

8. Newslet­ter track­ing

The newslet­ter of the Wat­ti­fy GmbH con­tains so-called track­ing pix­els. A track­ing pix­el is a minia­ture graph­ic embed­ded in such e‑mails, which are sent in HTML for­mat to enable log file record­ing and analy­sis. This allows a sta­tis­ti­cal analy­sis of the suc­cess or fail­ure of online mar­ket­ing cam­paigns. Based on the embed­ded track­ing pix­el, the Wat­ti­fy GmbH may see if and when an e‑mail was opened by a data sub­ject, and which links in the e‑mail were called up by data sub­jects.

Such per­son­al data col­lect­ed in the track­ing pix­els con­tained in the newslet­ters are stored and ana­lyzed by the con­troller in order to opti­mize the ship­ping of the newslet­ter, as well as to adapt the con­tent of future newslet­ters even bet­ter to the inter­ests of the data sub­ject. These per­son­al data will not be passed on to third par­ties. Data sub­jects are at any time enti­tled to revoke the respec­tive sep­a­rate dec­la­ra­tion of con­sent issued by means of the dou­ble-opt-in pro­ce­dure. After a revo­ca­tion, these per­son­al data will be delet­ed by the con­troller. The Wat­ti­fy GmbH auto­mat­i­cal­ly regards a with­draw­al from the receipt of the newslet­ter as a revo­ca­tion.

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

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

10. Sub­scrip­tion to com­ments in the blog on the web­site

The com­ments made in the blog of the Wat­ti­fy GmbH may be sub­scribed to by third par­ties. In par­tic­u­lar, there is the pos­si­bil­i­ty that a com­menter sub­scribes to the com­ments fol­low­ing his com­ments on a par­tic­u­lar blog post.

If a data sub­ject decides to sub­scribe to the option, the con­troller will send an auto­mat­ic con­fir­ma­tion e‑mail to check the dou­ble opt-in pro­ce­dure as to whether the own­er of the spec­i­fied e‑mail address decid­ed in favor of this option. The option to sub­scribe to com­ments may be ter­mi­nat­ed at any time.

11. 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 peri­od nec­es­sary to achieve the pur­pose of stor­age, or as far as this is grant­ed by the Euro­pean leg­is­la­tor or oth­er leg­is­la­tors in laws or reg­u­la­tions to which the con­troller is sub­ject to.

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

12. Rights of the data sub­ject

• a) Right of con­fir­ma­tion

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

• b) Right of access

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

• • the pur­pos­es of the pro­cess­ing;
  • the cat­e­gories of per­son­al data con­cerned;
  • the recip­i­ents or cat­e­gories of recip­i­ents to whom the per­son­al data have been or will be dis­closed, in par­tic­u­lar recip­i­ents in third coun­tries or inter­na­tion­al organ­i­sa­tions;
  • where pos­si­ble, the envis­aged peri­od for which the per­son­al data will be stored, or, if not pos­si­ble, the cri­te­ria used to deter­mine that peri­od;
  • the exis­tence of the right to request from the con­troller rec­ti­fi­ca­tion or era­sure of per­son­al data, or restric­tion of pro­cess­ing of per­son­al data con­cern­ing the data sub­ject, or to object to such pro­cess­ing;
  • the exis­tence of the right to lodge a com­plaint with a super­vi­so­ry author­i­ty;
  • where the per­son­al data are not col­lect­ed from the data sub­ject, any avail­able infor­ma­tion as to their source;
  • the exis­tence of auto­mat­ed deci­sion-mak­ing, includ­ing pro­fil­ing, referred to in Arti­cle 22(1) and (4) of the GDPR and, at least in those cas­es, mean­ing­ful infor­ma­tion about the log­ic involved, as well as the sig­nif­i­cance and envis­aged con­se­quences of such pro­cess­ing for the data sub­ject.

Fur­ther­more, the data sub­ject shall have a right to obtain infor­ma­tion as to whether per­son­al data are trans­ferred to a third coun­try or to an inter­na­tion­al organ­i­sa­tion. Where this is the case, the data sub­ject shall have the right to be informed of the appro­pri­ate safe­guards relat­ing to the trans­fer.

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

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

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

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

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

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

• • The per­son­al data are no longer nec­es­sary in rela­tion to the pur­pos­es for which they were col­lect­ed or oth­er­wise processed.
  • The data sub­ject with­draws con­sent to which the pro­cess­ing is based accord­ing to point (a) of Arti­cle 6(1) of the GDPR, or point (a) of Arti­cle 9(2) of the GDPR, and where there is no oth­er legal ground for the pro­cess­ing.
  • The data sub­ject objects to the pro­cess­ing pur­suant to Arti­cle 21(1) of the GDPR and there are no over­rid­ing legit­i­mate grounds for the pro­cess­ing, or the data sub­ject objects to the pro­cess­ing pur­suant to Arti­cle 21(2) of the GDPR.
  • The per­son­al data have been unlaw­ful­ly processed.
  • The per­son­al data must be erased for com­pli­ance with a legal oblig­a­tion in Union or Mem­ber State law to which the con­troller is sub­ject.
  • The per­son­al data have been col­lect­ed in rela­tion to the offer of infor­ma­tion soci­ety ser­vices referred to in Arti­cle 8(1) of the GDPR.

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

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

• e) Right of restric­tion of pro­cess­ing

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

• • The accu­ra­cy of the per­son­al data is con­test­ed by the data sub­ject, for a peri­od enabling the con­troller to ver­i­fy the accu­ra­cy of the per­son­al data.
  • The pro­cess­ing is unlaw­ful and the data sub­ject oppos­es the era­sure of the per­son­al data and requests instead the restric­tion of their use instead.
  • The con­troller no longer needs the per­son­al data for the pur­pos­es of the pro­cess­ing, but they are required by the data sub­ject for the estab­lish­ment, exer­cise or defence of legal claims.
  • The data sub­ject has object­ed to pro­cess­ing pur­suant to Arti­cle 21(1) of the GDPR pend­ing the ver­i­fi­ca­tion whether the legit­i­mate grounds of the con­troller over­ride those of the data sub­ject.

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

• f) Right to data porta­bil­i­ty

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

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

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

• g) Right to object

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

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

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

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

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

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

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

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

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

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

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

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

13. Data pro­tec­tion for appli­ca­tions and the appli­ca­tion pro­ce­dures

The data con­troller shall col­lect and process the per­son­al data of appli­cants for the pur­pose of the pro­cess­ing of the appli­ca­tion pro­ce­dure. The pro­cess­ing may also be car­ried out elec­tron­i­cal­ly. This is the case, in par­tic­u­lar, if an appli­cant sub­mits cor­re­spond­ing appli­ca­tion doc­u­ments by e‑mail or by means of a web form on the web­site to the con­troller. If the data con­troller con­cludes an employ­ment con­tract with an appli­cant, the sub­mit­ted data will be stored for the pur­pose of pro­cess­ing the employ­ment rela­tion­ship in com­pli­ance with legal require­ments. If no employ­ment con­tract is con­clud­ed with the appli­cant by the con­troller, the appli­ca­tion doc­u­ments shall be auto­mat­i­cal­ly erased two months after noti­fi­ca­tion of the refusal deci­sion, pro­vid­ed that no oth­er legit­i­mate inter­ests of the con­troller are opposed to the era­sure. Oth­er legit­i­mate inter­est in this rela­tion is, e.g. a bur­den of proof in a pro­ce­dure under the Gen­er­al Equal Treat­ment Act (AGG).

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

On this web­site, the con­troller has inte­grat­ed com­po­nents of the enter­prise Face­book. Face­book is a social net­work.

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

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

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

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

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

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

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

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

The oper­at­ing com­pa­ny of the ser­vices offered by Insta­gram is Face­book Ire­land Ltd., 4 Grand Canal Square, Grand Canal Har­bour, Dublin 2 Ire­land.

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

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

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

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Insta­gram may be retrieved under https://​help​.insta​gram​.com/155… and https://​www​.insta​gram​.com/abou….

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

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

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

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

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

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

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

17. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of Twit­ter

On this web­site, the con­troller has inte­grat­ed com­po­nents of Twit­ter. Twit­ter is a mul­ti­lin­gual, pub­licly-acces­si­ble microblog­ging ser­vice on which users may pub­lish and spread so-called ​‘tweets,’ e.g. short mes­sages, which are lim­it­ed to 280 char­ac­ters. These short mes­sages are avail­able for every­one, includ­ing those who are not logged on to Twit­ter. The tweets are also dis­played to so-called fol­low­ers of the respec­tive user. Fol­low­ers are oth­er Twit­ter users who fol­low a user’s tweets. Fur­ther­more, Twit­ter allows you to address a wide audi­ence via hash­tags, links or retweets.

The oper­at­ing com­pa­ny of Twit­ter is Twit­ter Inter­na­tion­al Com­pa­ny, One Cum­ber­land Place, Fen­ian Street Dublin 2, D02 AX07, Ire­land.

With each call-up to one of the indi­vid­ual pages of this Inter­net site, which is oper­at­ed by the con­troller and on which a Twit­ter com­po­nent (Twit­ter but­ton) was inte­grat­ed, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly prompt­ed to down­load a dis­play of the cor­re­spond­ing Twit­ter com­po­nent of Twit­ter. Fur­ther infor­ma­tion about the Twit­ter but­tons is avail­able under https://​about​.twit​ter​.com/de/r…. Dur­ing the course of this tech­ni­cal pro­ce­dure, Twit­ter gains knowl­edge of what spe­cif­ic sub-page of our web­site was vis­it­ed by the data sub­ject. The pur­pose of the inte­gra­tion of the Twit­ter com­po­nent is a retrans­mis­sion of the con­tents of this web­site to allow our users to intro­duce this web page to the dig­i­tal world and increase our vis­i­tor num­bers.

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

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

The applic­a­ble data pro­tec­tion pro­vi­sions of Twit­ter may be accessed under https://​twit​ter​.com/​p​r​i​v​a​cy?la….

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

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

The oper­at­ing com­pa­ny of YouTube is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land.

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

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

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

YouTube’s data pro­tec­tion pro­vi­sions, avail­able at https://​www​.google​.com/​i​n​tl/en…, pro­vide infor­ma­tion about the col­lec­tion, pro­cess­ing and use of per­son­al data by YouTube and Google.

19. Legal basis for the pro­cess­ing

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

20. The legit­i­mate inter­ests pur­sued by the con­troller or by a third par­ty

Where the pro­cess­ing of per­son­al data is based on Arti­cle 6(1) lit. f GDPR our legit­i­mate inter­est is to car­ry out our busi­ness in favor of the well-being of all our employ­ees and the share­hold­ers.

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

The cri­te­ria used to deter­mine the peri­od of stor­age of per­son­al data is the respec­tive statu­to­ry reten­tion peri­od. After expi­ra­tion of that peri­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 con­tract.

22. Pro­vi­sion of per­son­al data as statu­to­ry or con­trac­tu­al require­ment; Require­ment nec­es­sary to enter 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 required by law (e.g. tax reg­u­la­tions) or can also result from con­trac­tu­al pro­vi­sions (e.g. infor­ma­tion on the con­trac­tu­al part­ner). 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 exam­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 con­clud­ed. Before per­son­al data is pro­vid­ed by the data sub­ject, the data sub­ject must con­tact any employ­ee. The employ­ee clar­i­fies to the data sub­ject whether the pro­vi­sion of the per­son­al data is required 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.

23. Exis­tence of auto­mat­ed deci­sion-mak­ing

As a respon­si­ble com­pa­ny, we do not use auto­mat­ic deci­sion-mak­ing or pro­fil­ing.

24. Gen­er­al Terms and Con­di­tions for Data Pro­tec­tion

Our Terms and Con­di­tions for Data Pro­tec­tion, which include, among oth­er things, all five ver­sions of the EU Stan­dard Con­trac­tu­al Claus­es, the UK Inter­na­tion­al Data Trans­fer Agree­ment, the UK Adden­dum to the EU Stan­dard Con­trac­tu­al Claus­es, a Data Pro­cess­ing Agree­ment gov­erned by UK law, and a Data Pro­tec­tion and Con­fi­den­tial­i­ty Agree­ment for sup­pli­ers, will auto­mat­i­cal­ly form part of all agree­ments entered into with us. By enter­ing into any oth­er agree­ment with us, you auto­mat­i­cal­ly agree to the respec­tive terms. In detail:

1. EU Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₅ between Con­troller and Proces­sor:

If you are an EU/EEA-based ven­dor of ours that process­es per­son­al data on our behalf, by con­duct­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of our pub­lished Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₅. If we are your proces­sor, the Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₅ pub­lished by us will also auto­mat­i­cal­ly apply between you and us.

2. EU Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ MOD­ULE ONE: Trans­fer Con­troller to Con­troller:

To the extent that you are a ven­dor of ours locat­ed in a third coun­try and receive per­son­al data (pro­tect­ed by the GDPR, Mem­ber State law or Euro­pean Eco­nom­ic Area law) from us as a Con­troller and act as a Con­troller, by con­duct­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of the pub­lished Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ Mod­ule One. The same applies if you act as a Con­troller and trans­fer per­son­al data to us as a Con­troller.

3. EU Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ MOD­ULE TWO: Trans­fer Con­troller to Proces­sor:

To the extent that you are a ven­dor of ours locat­ed in a third coun­try and receive per­son­al data (pro­tect­ed by the GDPR, Mem­ber State law or Euro­pean Eco­nom­ic Area law) from us as a Con­troller and act as a Proces­sor, by con­duct­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of the pub­lished Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ Mod­ule Two. The same applies if you act as a Con­troller and trans­fer per­son­al data to us as a Proces­sor.

4. EU Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ MOD­ULE THREE: Trans­fer Proces­sor to Proces­sor:

To the extent that you are a ven­dor of ours and we are act­ing as a Proces­sor (e.g., for a sub­sidiary or a third par­ty), you are locat­ed in a third coun­try and receive inter­na­tion­al data trans­fers of per­son­al data (pro­tect­ed by the GDPR, Mem­ber State law or Euro­pean Eco­nom­ic Area law), and you are there­fore a (Sub)Processor, by con­duct­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of the pub­lished Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ Mod­ule Three. The same applies if you act as a Proces­sor and trans­fer per­son­al data to us as a (Sub)Processor.

5. EU Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ MOD­ULE FOUR: Trans­fer Proces­sor to Con­troller:

To the extent that you are a ven­dor of ours and we are act­ing as a Proces­sor (e.g., for a sub­sidiary or a third par­ty), you are locat­ed in a third coun­try and receive inter­na­tion­al data trans­fers of per­son­al data (pro­tect­ed by the GDPR, Mem­ber State law or Euro­pean Eco­nom­ic Area law), and you are a Con­troller, by con­duct­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of the pub­lished Stan­dard Con­trac­tu­al Claus­es ²⁰²¹⁄₉₁₄ Mod­ule Four. The same applies if you act as a Proces­sor and trans­fer per­son­al data to us as a Con­troller.

6. Con­fi­den­tial­i­ty and Data Pro­tec­tion Agree­ment for Ven­dors:

If you are a ven­dor of ours that is not a proces­sor, or if you receive oth­er and non-per­son­al data from us, by con­duct­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of the pub­lished Con­fi­den­tial­i­ty and Data Pro­tec­tion Agree­ment for Ven­dors.

7. Con­fi­den­tial­i­ty and Data Pro­tec­tion Agree­ment for Cus­tomers:

If you are a cus­tomer of ours and data is exchanged between us, we may sep­a­rate­ly agree to the pub­lished Con­fi­den­tial­i­ty and Data Pro­tec­tion Agree­ment for Cus­tomers by a con­cur­ring state­ment. This Con­fi­den­tial­i­ty Agree­ment shall only become effec­tive upon a sep­a­rate­ly dec­la­ra­tion of intent by the par­ties.

8. Inter­na­tion­al Data Trans­fer Agree­ment (Unit­ed King­dom)

To the extent that you are a par­ty to an agree­ment with us, and per­son­al data trans­ferred by us to you belongs to indi­vid­u­als who are from the Unit­ed King­dom or we are based in the Unit­ed King­dom, and you your­self are based out­side the Unit­ed King­dom and receive per­son­al data (pro­tect­ed by the UK GDPR or UK law) from us, by con­duct­ing or trans­act­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of the pub­lished ​“Inter­na­tion­al Data Trans­fer Agree­ment”.

9. Inter­na­tion­al Data Trans­fer Adden­dum to the Euro­pean Com­mis­sion’s Stan­dard Con­trac­tu­al Claus­es for Inter­na­tion­al Data Trans­fers (Unit­ed King­dom)

To the extent that you are a par­ty to an agree­ment with us, and per­son­al data we trans­fer to you belongs to indi­vid­u­als who are based in the UK or where we are based in the UK and you your­self are based out­side the UK and receive per­son­al data (which is pro­tect­ed by the UK GDPR or UK law) from us, by car­ry­ing out or trans­act­ing busi­ness for or with us, you auto­mat­i­cal­ly con­sent to the applic­a­bil­i­ty of the pub­lished ” Inter­na­tion­al Data Trans­fer Adden­dum to the Euro­pean Com­mis­sion’s Stan­dard Con­trac­tu­al Claus­es for Inter­na­tion­al Data Trans­fers”.

10. Data Pro­cess­ing Agree­ment for the Unit­ed King­dom

To the extent that you are a par­ty to an agree­ment with us, and both we and you have our reg­is­tered office in the Unit­ed King­dom, and you process per­son­al data (which is pro­tect­ed by the UK GDPR or UK law) on our behalf, you auto­mat­i­cal­ly agree to the applic­a­bil­i­ty of the pub­lished ​“Data Pro­cess­ing Agree­ment for the Unit­ed King­dom” by exe­cut­ing or con­duct­ing busi­ness for or with us. The same applies if you act as a Con­troller and trans­fer per­son­al data to us as a Proces­sor.

A list of our sub-proces­sors must be request­ed sep­a­rate­ly from us.

25. Data pro­tec­tion pro­vi­sions about the use of User­centrics

We have inte­grat­ed User­centrics on our web­site.

The oper­at­ing com­pa­ny of the ser­vices is User­centrics GmbH, Sendlinger Straße 7, 80331 Munich, Ger­many.

User­centrics is a con­sent man­age­ment plat­form that pro­vides exten­sive capa­bil­i­ties for man­ag­ing site vis­i­tor con­sent and analy­sis. The pur­pose of the pro­cess­ing is to ensure the secu­ri­ty of web­sites. The legal basis is Art. 6 para. 1 lit. f GDPR.

Fur­ther infor­ma­tion and the applic­a­ble pri­va­cy pol­i­cy of User­centrics can be found at https://​user​centrics​.com/​d​e​/​d​a​t​e​n​s​c​h​u​t​z​e​r​k​l​a​e​rung/.

26. Data pro­tec­tion pro­vi­sions about the appli­ca­tion and use of Mato­mo

On this web­site, the con­troller has inte­grat­ed the Mato­mo com­po­nent. Mato­mo is an open-source soft­ware tool for web analy­sis. Web analy­sis is the col­lec­tion, gath­er­ing and eval­u­a­tion of data on the behav­ior of vis­i­tors from Inter­net sites. A web analy­sis tool col­lects, inter alia, data on the web­site from which a data sub­ject came to a web­site (so-called refer­rer), which pages of the web­site were accessed or how often and for which peri­od of time a sub-page was viewed. A web analy­sis is main­ly used for the opti­miza­tion of a web­site and the cost-ben­e­fit analy­sis of Inter­net adver­tis­ing.

The soft­ware is oper­at­ed on the serv­er of the con­troller, the data pro­tec­tion-sen­si­tive log files are stored exclu­sive­ly on this serv­er.

The pur­pose of the Mato­mo com­po­nent is the analy­sis of the vis­i­tor flows on our web­site. The con­troller uses the obtained data and infor­ma­tion, inter alia, to eval­u­ate the use of this web­site in order to com­pile online reports, which show the activ­i­ties on our Inter­net pages.

Mato­mo sets a cook­ie on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject. The def­i­n­i­tion of cook­ies is explained above. With the set­ting of the cook­ie, an analy­sis of the use of our web­site is enabled. With each call-up to one of the indi­vid­ual pages of this web­site, the Inter­net brows­er on the infor­ma­tion tech­nol­o­gy sys­tem of the data sub­ject is auto­mat­i­cal­ly through the Mato­mo com­po­nent prompt­ed to sub­mit data for the pur­pose of online analy­sis to our serv­er. Dur­ing the course of this tech­ni­cal pro­ce­dure, we obtain knowl­edge about per­son­al infor­ma­tion, such as the IP address of the data sub­ject, which serves to under­stand the ori­gin of vis­i­tors and clicks.

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

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

In addi­tion, the data sub­ject has the pos­si­bil­i­ty of object­ing to a col­lec­tion of data relat­ing to a use of this Inter­net site that are gen­er­at­ed by Mato­mo as well as the pro­cess­ing of these data by Mato­mo and the chance to pre­clude any such. For this, the data sub­ject must set a ​“Do Not Track” option in the brows­er.

With each set­ting of the opt-out cook­ie, how­ev­er, there is the pos­si­bil­i­ty that the web­sites of the con­troller are no longer ful­ly usable for the data sub­ject.

Fur­ther infor­ma­tion and the applic­a­ble data pro­tec­tion pro­vi­sions of Mato­mo may be retrieved under https://​mato​mo​.org/​p​r​i​vacy/.

27. Data pro­tec­tion pro­vi­sions on the use and appli­ca­tion of Face­book SDKs for JavaScript, Android and iOS

The Face­book SDKs for JavaScript, Android and iOS pro­vide exten­sive client-side func­tion­al­i­ty that allows us to use the ​“Like” but­ton and oth­er social plug-ins on our web­sites and in our apps.

Fur­ther, the Face­book SDKs allow us to facil­i­tate a Face­book login for login and calls to the Face­book Graph API. Our users can launch dialogs that enable var­i­ous actions, such as shar­ing sto­ries. The Face­book SDKs fur­ther enable eas­i­er com­mu­ni­ca­tion when cre­at­ing games or an app tab on Face­book.

Also, the Face­book SDKs, allow users to post to Face­book through apps. Peo­ple can share con­tent, send mes­sages, and share sto­ries. In addi­tion, we bet­ter under­stand the actions in our apps and mea­sure the effec­tive­ness of our mobile app ads through the Face­book SDKs. We also use the Face­book SDKs to increase app installs with Mobile App Install Ads, increase inter­ac­tions with our apps using Mobile App Engage­ment Ads, and find audi­ences with Cus­tom Audi­ences for mobile apps.

The oper­a­tor of the Ser­vices is Meta Plat­forms, Inc., 1601 Wil­low Road Men­lo Park, CA 94025 Unit­ed States, email: support@fb.com. The con­troller of per­son­al data, if a data sub­ject lives out­side the Unit­ed States or Cana­da, is Face­book Ire­land Ltd, 4 Grand Canal Square, Grand Canal Har­bour, Dublin 2, Ire­land.

The pur­pose of the pro­cess­ing is the analy­sis of our apps, mar­ket­ing and adver­tis­ing. The legal basis is Art. 6 (1) (f) GDPR. Our legit­i­mate inter­ests are the analy­sis of our apps, mar­ket­ing and adver­tis­ing. Fur­ther­more, anoth­er legal basis is your con­sent via the cook­ie ban­ner or the app, Art. 6 (1) (a) GDPR.

For more infor­ma­tion about Face­book SDKs, please vis­it Face­book’s web­sites. To search for this infor­ma­tion, please use any pri­va­cy-com­pli­ant search engine and an anony­mous brows­er.

28. Data pro­tec­tion pro­vi­sions about the use of Google Tag Man­ag­er

The con­troller has inte­grat­ed Google Tag Man­ag­er on this web­site. Google Tag Man­ag­er is a free ser­vice that allows us to man­age tags and con­fig­ure mobile appli­ca­tions our­selves through a user-friend­ly web inter­face. More infor­ma­tion about Google Tag Man­ag­er can be found here: https://​www​.google​.com/​i​n​t​l​/​e​n​/​t​a​g​m​a​n​a​g​e​r​/​f​e​a​t​u​r​e​s​.html.

The oper­a­tor of the ser­vices is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land.

The pur­pose of pro­cess­ing is to man­age tags and con­fig­ure mobile appli­ca­tions through a user-friend­ly web inter­face.

When­ev­er you vis­it our web­sites, per­son­al data, includ­ing the IP address of the Inter­net con­nec­tion used by the data sub­ject, may be trans­ferred to Google in the Unit­ed States of Amer­i­ca. This per­son­al data is stored by Google in the Unit­ed States of Amer­i­ca. Google may trans­fer this per­son­al data col­lect­ed through the tech­ni­cal process to third par­ties or use it for inter­est-based adver­tis­ing.

It is pos­si­ble to opt out of inter­est-based adver­tis­ing by Google. To do this, the data sub­ject must vis­it the link www​.google​.com/​s​e​t​t​i​n​g​s/ads from each of the inter­net browsers they use and make the desired set­tings there.

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

29. Data pro­tec­tion pro­vi­sions on the use and appli­ca­tion of Google Ana­lyt­ics for Fire­base.

Google Ana­lyt­ics for Fire­base is a Google Plat­form ana­lyt­ics ser­vice for app devel­op­ers. Through Google Ana­lyt­ics for Fire­base, Google Ana­lyt­ics app reports are con­nect­ed to Fire­base Con­sole and oth­er app-spe­cif­ic Google prod­ucts. This allows us to have all users in our orga­ni­za­tion, whether they use Google Ana­lyt­ics or Fire­base Con­sole, work­ing with the same data and reports.

The reports pro­vide com­pre­hen­sive analy­sis of user behav­ior in the apps, as well as mar­ket­ing ana­lyt­ics for mobile apps. This helps us learn more about how users are inter­act­ing with our apps and what mar­ket­ing suc­cess­es we are achiev­ing. We also have the abil­i­ty to cre­ate audi­ences and con­nect with third-par­ty net­works to lever­age the data imme­di­ate­ly.

To see app reports in Google Ana­lyt­ics or Fire­base Con­sole, we built the Google Ana­lyt­ics for Fire­base SDK into our apps. The Fire­base SDK auto­mat­i­cal­ly col­lects basic data on app usage. This gives us data on basic inter­ac­tions, such as how many times our apps were opened, how many in-app pur­chas­es were made, and how many users were active dur­ing a giv­en time peri­od. We also see the demo­graph­ic char­ac­ter­is­tics and inter­ests of our users.

The oper­a­tor of the ser­vices is Google Ire­land Lim­it­ed, Gor­don House, Bar­row Street, Dublin, D04 E5W5, Ire­land.

The pur­pose of the pro­cess­ing is the analy­sis of our apps, mar­ket­ing and adver­tis­ing. The legal basis is Art. 6 (1) (f) GDPR. Our legit­i­mate inter­ests are the analy­sis of our apps, mar­ket­ing and adver­tis­ing. Fur­ther­more, anoth­er legal basis is your con­sent via the cook­ie ban­ner or the app, Art. 6 (1) (a) GDPR.

For more infor­ma­tion about Google Ana­lyt­ics for Fire­base and the Ana­lyt­ics for Fire­base SDK, please vis­it Google’s web­sites. To search for this infor­ma­tion, please use any pri­va­cy-com­pli­ant search engine and an anony­mous brows­er.

30. Trans­fers to Third Coun­tries

We express­ly point out that your per­son­al data will be trans­ferred to third coun­tries if you give or have giv­en vol­un­tary con­sent for such a trans­fer in accor­dance with Art. 49 (1) (1) (a) GDPR via our cook­ie ban­ner.

In the case of trans­fers to third coun­tries for which there is no EU ade­qua­cy deci­sion, there are always sig­nif­i­cant risks and no appro­pri­ate safe­guards for the pro­tec­tion of your per­son­al data (e.g., because of Sec­tion 702 FISA, Exec­u­tive Order EO12333 and the CloudAct in the USA). In third coun­tries, there may not be an ade­quate lev­el of data pro­tec­tion and data sub­ject rights may not be enforce­able.

Not even encryp­tion of per­son­al data may pro­vide ade­quate pro­tec­tion for your per­son­al data in third coun­tries. Com­pa­nies in third coun­tries that have pos­ses­sion or cus­tody of per­son­al data may be sub­ject to a legal oblig­a­tion to pro­vide access to or release such data to author­i­ties or oth­er mar­ket par­tic­i­pants. Addi­tion­al­ly, com­pa­nies in third coun­tries may be required by a court order to sur­ren­der per­son­al data (e.g., by a pre-tri­al dis­cov­ery). This may also apply to a cryp­to­graph­ic key.

WE THERE­FORE EXPRESS­LY WARN YOU ABOUT RECK­LESS­LY CON­SENT­ING TO THE TRANS­FER TO THIRD COUN­TRIES.