Disclaimer

Pri­va­cy Poli­cy

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

The pro­ces­sing of per­so­nal data, such as the name, address, e‐mail address, or tele­pho­ne num­ber of a data sub­ject shall always be in line with the Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR), and in accordance with the country‐specific data pro­tec­tion regu­la­ti­ons app­li­ca­ble to the Text&Aktion GbR. By means of this data pro­tec­tion decla­ra­ti­on, our enter­pri­se would like to inform the gene­ral public of the natu­re, scope, and pur­po­se of the per­so­nal data we collect, use and pro­cess. Fur­ther­mo­re, data sub­jec­ts are infor­med, by means of this data pro­tec­tion decla­ra­ti­on, of the rights to which they are ent­it­led.

As the con­trol­ler, the Text&Aktion GbR has imple­men­ted nume­rous tech­ni­cal and orga­ni­za­tio­nal mea­su­res to ensu­re the most com­ple­te pro­tec­tion of per­so­nal data pro­ces­sed through this web­site. Howe­ver, Internet‐based data trans­mis­si­ons may in princip­le have secu­ri­ty gaps, so abso­lu­te pro­tec­tion may not be gua­ran­te­ed. For this rea­son, every data sub­ject is free to trans­fer per­so­nal data to us via alter­na­ti­ve means, e.g. by tele­pho­ne.

Defi­ni­ti­ons

The data pro­tec­tion decla­ra­ti­on of the Text&Aktion GbR is based on the terms used by the European legis­la­tor for the adop­ti­on of the Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR). Our data pro­tec­tion decla­ra­ti­on should be legi­ble and under­stand­a­ble for the gene­ral public, as well as our custo­mers and busi­ness part­ners. To ensu­re this, we would like to first exp­lain the ter­mi­no­lo­gy used.

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

a) Per­so­nal data

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

b) Data sub­ject

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

c) Pro­ces­sing

Pro­ces­sing is any ope­ra­ti­on or set of ope­ra­ti­ons which is per­for­med on per­so­nal data or on sets of per­so­nal data, whe­ther or not by auto­ma­ted means, such as collec­tion, record­ing, orga­ni­sa­ti­on, struc­tu­ring, sto­rage, adap­tati­on or alte­ra­ti­on, retrie­val, con­sul­ta­ti­on, use, dis­clo­sure by trans­mis­si­on, dis­se­mi­na­ti­on or other­wi­se making avail­ab­le, align­ment or com­bi­na­ti­on, restric­tion, era­su­re or dest­ruc­tion.

d) Restric­tion of pro­ces­sing

Restric­tion of pro­ces­sing is the mar­king of stored per­so­nal data with the aim of limi­t­ing their pro­ces­sing in the future.

e) Pro­filing

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

f) Pseud­ony­mi­sa­ti­on

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

g) Con­trol­ler or con­trol­ler respon­si­ble for the pro­ces­sing

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

h) Pro­ces­sor

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

i) Reci­pi­ent

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

j) Third par­ty

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

k) Con­sent

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

Name and Address of the con­trol­ler

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

The Inter­net pages of the Text&Aktion GbR use coo­kies. Coo­kies are text files that are stored in a com­pu­ter sys­tem via an Inter­net brow­ser.

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

Through the use of coo­kies, the Text&Aktion GbR can pro­vi­de the users of this web­site with more user‐friendly ser­vices that would not be pos­si­ble wit­hout the coo­kie set­ting.

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

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

Collec­tion of gene­ral data and infor­ma­ti­on

The web­site of the Text&Aktion GbR collec­ts a series of gene­ral data and infor­ma­ti­on when a data sub­ject or auto­ma­ted sys­tem calls up the web­site. This gene­ral data and infor­ma­ti­on are stored in the ser­ver log files. Collec­ted may be (1) the brow­ser types and ver­si­ons used, (2) the ope­ra­ting sys­tem used by the acces­sing sys­tem, (3) the web­site from which an acces­sing sys­tem reaches our web­site (so‐called refer­rers), (4) the sub‐websites, (5) the date and time of access to the Inter­net site, (6) an Inter­net pro­to­col address (IP address), (7) the Inter­net ser­vice pro­vi­der of the acces­sing sys­tem, and (8) any other simi­lar data and infor­ma­ti­on that may be used in the event of attacks on our infor­ma­ti­on tech­no­lo­gy sys­tems.

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

Rou­ti­ne era­su­re and blo­cking of per­so­nal data

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

If the sto­rage pur­po­se is not app­li­ca­ble, or if a sto­rage peri­od pre­scri­bed by the European legis­la­tor or ano­t­her com­pe­tent legis­la­tor expi­res, the per­so­nal data are rou­ti­ne­ly blo­cked or era­sed in accordance with legal requi­re­ments.

Rights of the data sub­ject

a) Right of con­fir­ma­ti­on

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

b) Right of access

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

the pur­po­ses of the pro­ces­sing;

the cate­go­ries of per­so­nal data con­cer­ned;

the reci­pi­ents or cate­go­ries of reci­pi­ents to whom the per­so­nal data have been or will be dis­c­lo­sed, in par­ti­cu­lar reci­pi­ents in third coun­tries or inter­na­tio­nal orga­ni­sa­ti­ons;

whe­re pos­si­ble, the envi­sa­ged peri­od for which the per­so­nal data will be stored, or, if not pos­si­ble, the cri­te­ria used to deter­mi­ne that peri­od;

the exis­tence of the right to request from the con­trol­ler rec­tifi­ca­ti­on or era­su­re of per­so­nal data, or restric­tion of pro­ces­sing of per­so­nal data con­cer­ning the data sub­ject, or to object to such pro­ces­sing;

the exis­tence of the right to lodge a com­p­laint with a super­vi­so­ry aut­ho­ri­ty;

whe­re the per­so­nal data are not collec­ted from the data sub­ject, any avail­ab­le infor­ma­ti­on as to their source;

the exis­tence of auto­ma­ted decision‐making, inclu­ding pro­filing, refer­red to in Arti­cle 22(1) and (4) of the GDPR and, at least in tho­se cases, mea­ning­ful infor­ma­ti­on about the logic invol­ved, as well as the signi­fi­can­ce and envi­sa­ged con­se­quen­ces of such pro­ces­sing for the data sub­ject.

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

If a data sub­ject wis­hes to avail him­s­elf of this right of access, he or she may, at any time, con­tact any employee of the con­trol­ler.

c) Right to rec­tifi­ca­ti­on

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

If a data sub­ject wis­hes to exer­ci­se this right to rec­tifi­ca­ti­on, he or she may, at any time, con­tact any employee of the con­trol­ler.

d) Right to era­su­re (Right to be for­got­ten)

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

The per­so­nal data are no lon­ger necessa­ry in rela­ti­on to the pur­po­ses for which they were collec­ted or other­wi­se pro­ces­sed.

The data sub­ject with­draws con­sent to which the pro­ces­sing 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 whe­re the­re is no other legal ground for the pro­ces­sing.

The data sub­ject objec­ts to the pro­ces­sing pur­suant to Arti­cle 21(1) of the GDPR and the­re are no over­ri­ding legi­ti­ma­te grounds for the pro­ces­sing, or the data sub­ject objec­ts to the pro­ces­sing pur­suant to Arti­cle 21(2) of the GDPR.

The per­so­nal data have been unlaw­ful­ly pro­ces­sed.

The per­so­nal data must be era­sed for com­pli­an­ce with a legal obli­ga­ti­on in Uni­on or Mem­ber Sta­te law to which the con­trol­ler is sub­ject.

The per­so­nal data have been collec­ted in rela­ti­on to the offer of infor­ma­ti­on socie­ty ser­vices refer­red to in Arti­cle 8(1) of the GDPR.

If one of the afo­re­men­tio­ned rea­sons app­lies, and a data sub­ject wis­hes to request the era­su­re of per­so­nal data stored by the Text&Aktion GbR, he or she may, at any time, con­tact any employee of the con­trol­ler. An employee of Text&Aktion GbR shall prompt­ly ensu­re that the era­su­re request is com­plied with imme­dia­te­ly.

Whe­re the con­trol­ler has made per­so­nal data public and is obli­ged pur­suant to Arti­cle 17(1) to era­se the per­so­nal data, the con­trol­ler, taking account of avail­ab­le tech­no­lo­gy and the cost of imple­men­ta­ti­on, shall take rea­son­ab­le steps, inclu­ding tech­ni­cal mea­su­res, to inform other con­trol­lers pro­ces­sing the per­so­nal data that the data sub­ject has requested era­su­re by such con­trol­lers of any links to, or copy or repli­ca­ti­on of, tho­se per­so­nal data, as far as pro­ces­sing is not requi­red. An employees of the Text&Aktion GbR will arran­ge the necessa­ry mea­su­res in indi­vi­du­al cases.

e) Right of restric­tion of pro­ces­sing

Each data sub­ject shall have the right gran­ted by the European legis­la­tor to obtain from the con­trol­ler restric­tion of pro­ces­sing whe­re one of the fol­lo­wing app­lies:

The accu­ra­cy of the per­so­nal data is con­tested by the data sub­ject, for a peri­od enab­ling the con­trol­ler to veri­fy the accu­ra­cy of the per­so­nal data.

The pro­ces­sing is unlaw­ful and the data sub­ject oppo­ses the era­su­re of the per­so­nal data and requests ins­tead the restric­tion of their use ins­tead.

The con­trol­ler no lon­ger needs the per­so­nal data for the pur­po­ses of the pro­ces­sing, but they are requi­red by the data sub­ject for the estab­lish­ment, exer­ci­se or defence of legal claims.

The data sub­ject has objec­ted to pro­ces­sing pur­suant to Arti­cle 21(1) of the GDPR pen­ding the veri­fi­ca­ti­on whe­ther the legi­ti­ma­te grounds of the con­trol­ler over­ri­de tho­se of the data sub­ject.

If one of the afo­re­men­tio­ned con­di­ti­ons is met, and a data sub­ject wis­hes to request the restric­tion of the pro­ces­sing of per­so­nal data stored by the Text&Aktion GbR, he or she may at any time con­tact any employee of the con­trol­ler. The employee of the Text&Aktion GbR will arran­ge the restric­tion of the pro­ces­sing.

f) Right to data por­ta­bi­li­ty

Each data sub­ject shall have the right gran­ted by the European legis­la­tor, to recei­ve the per­so­nal data con­cer­ning him or her, which was pro­vi­ded to a con­trol­ler, in a struc­tu­red, com­mon­ly used and machine‐readable for­mat. He or she shall have the right to trans­mit tho­se data to ano­t­her con­trol­ler wit­hout hin­dran­ce from the con­trol­ler to which the per­so­nal data have been pro­vi­ded, as long as the pro­ces­sing is based on con­sent pur­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­ces­sing is car­ri­ed out by auto­ma­ted means, as long as the pro­ces­sing is not necessa­ry for the per­for­mance of a task car­ri­ed out in the public inte­rest or in the exer­ci­se of offi­ci­al aut­ho­ri­ty vested in the con­trol­ler.

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

In order to assert the right to data por­ta­bi­li­ty, the data sub­ject may at any time con­tact any employee of the Text&Aktion GbR.

g) Right to object

Each data sub­ject shall have the right gran­ted by the European legis­la­tor to object, on grounds rela­ting to his or her par­ti­cu­lar situa­ti­on, at any time, to pro­ces­sing of per­so­nal data con­cer­ning him or her, which is based on point (e) or (f) of Arti­cle 6(1) of the GDPR. This also app­lies to pro­filing based on the­se pro­vi­si­ons.

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

If the Text&Aktion GbR pro­ces­ses per­so­nal data for direct mar­ke­ting pur­po­ses, the data sub­ject shall have the right to object at any time to pro­ces­sing of per­so­nal data con­cer­ning him or her for such mar­ke­ting. This app­lies to pro­filing to the extent that it is rela­ted to such direct mar­ke­ting. If the data sub­ject objec­ts to the Text&Aktion GbR to the pro­ces­sing for direct mar­ke­ting pur­po­ses, the Text&Aktion GbR will no lon­ger pro­cess the per­so­nal data for the­se pur­po­ses.

In addi­ti­on, the data sub­ject has the right, on grounds rela­ting to his or her par­ti­cu­lar situa­ti­on, to object to pro­ces­sing of per­so­nal data con­cer­ning him or her by the Text&Aktion GbR for sci­en­ti­fic or his­to­ri­cal rese­arch pur­po­ses, or for sta­tis­ti­cal pur­po­ses pur­suant to Arti­cle 89(1) of the GDPR, unless the pro­ces­sing is necessa­ry for the per­for­mance of a task car­ri­ed out for rea­sons of public inte­rest.

In order to exer­ci­se the right to object, the data sub­ject may con­tact any employee of the Text&Aktion GbR. In addi­ti­on, the data sub­ject is free in the con­text of the use of infor­ma­ti­on socie­ty ser­vices, and not­wi­th­stan­ding Direc­tive 2002/58/EC, to use his or her right to object by auto­ma­ted means using tech­ni­cal spe­ci­fi­ca­ti­ons.

h) Auto­ma­ted indi­vi­du­al decision‐making, inclu­ding pro­filing

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

If the decisi­on (1) is necessa­ry for ent­e­ring into, or the per­for­mance of, a con­tract bet­ween the data sub­ject and a data con­trol­ler, or (2) it is based on the data subject’s expli­cit con­sent, the Text&Aktion GbR shall imple­ment sui­ta­ble mea­su­res to safe­guard the data subject’s rights and free­doms and legi­ti­ma­te inte­rests, at least the right to obtain human inter­ven­ti­on on the part of the con­trol­ler, to express his or her point of view and con­test the decisi­on.

If the data sub­ject wis­hes to exer­ci­se the rights con­cer­ning auto­ma­ted indi­vi­du­al decision‐making, he or she may, at any time, con­tact any employee of the Text&Aktion GbR.

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

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

If the data sub­ject wis­hes to exer­ci­se the right to with­draw the con­sent, he or she may, at any time, con­tact any employee of the Text&Aktion GbR.

Data pro­tec­tion for app­li­ca­ti­ons and the app­li­ca­ti­on pro­ce­du­res

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

Data pro­tec­tion pro­vi­si­ons about the app­li­ca­ti­on and use of Face­book

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

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

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

If the data sub­ject is log­ged in at the same time on Face­book, Face­book detec­ts with every call‐up to our web­site by the data subject—and for the ent­i­re dura­ti­on of their stay on our Inter­net site—which spe­ci­fic sub‐site of our Inter­net page was visi­ted by the data sub­ject. This infor­ma­ti­on is collec­ted through the Face­book com­po­nent and asso­cia­ted 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­gra­ted into our web­site, e.g. the “Like” but­ton, or if the data sub­ject sub­mits a com­ment, then Face­book matches this infor­ma­ti­on with the per­so­nal Face­book user account of the data sub­ject and stores the per­so­nal data.

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

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

Data pro­tec­tion pro­vi­si­ons about the app­li­ca­ti­on and use of Twit­ter

On this web­site, the con­trol­ler has inte­gra­ted com­pon­ents of Twit­ter. Twit­ter is a mul­ti­lin­gu­al, publicly‐accessible micro­blog­ging ser­vice on which users may publish and spread so‐called ‘tweets,’ e.g. short messa­ges, which are limi­ted to 280 cha­rac­ters. The­se short messa­ges are avail­ab­le for ever­yo­ne, inclu­ding tho­se who are not log­ged on to Twit­ter. The tweets are also dis­play­ed to so‐called fol­lo­wers of the respec­tive user. Fol­lo­wers are other Twit­ter users who fol­low a user’s tweets. Fur­ther­mo­re, Twit­ter allows you to address a wide audi­ence via hash­tags, links or ret­weets.

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

If the data sub­ject is log­ged in at the same time on Twit­ter, Twit­ter detec­ts with every call‐up to our web­site by the data sub­ject and for the ent­i­re dura­ti­on of their stay on our Inter­net site which spe­ci­fic sub‐page of our Inter­net page was visi­ted by the data sub­ject. This infor­ma­ti­on is collec­ted through the Twit­ter com­po­nent and asso­cia­ted 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­gra­ted on our web­site, then Twit­ter assigns this infor­ma­ti­on to the per­so­nal Twit­ter user account of the data sub­ject and stores the per­so­nal data.

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

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

Legal basis for the pro­ces­sing

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

The legi­ti­ma­te inte­rests pur­sued by the con­trol­ler or by a third par­ty

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

Peri­od for which the per­so­nal data will be stored

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

Pro­vi­si­on of per­so­nal data as sta­tuto­ry or con­trac­tu­al requi­re­ment; Requi­re­ment necessa­ry to enter into a con­tract; Obli­ga­ti­on of the data sub­ject to pro­vi­de the per­so­nal data; pos­si­ble con­se­quen­ces of fail­u­re to pro­vi­de such data

We cla­ri­fy that the pro­vi­si­on of per­so­nal data is part­ly requi­red by law (e.g. tax regu­la­ti­ons) or can also result from con­trac­tu­al pro­vi­si­ons (e.g. infor­ma­ti­on on the con­trac­tu­al part­ner). Some­ti­mes it may be necessa­ry to con­clu­de a con­tract that the data sub­ject pro­vi­des us with per­so­nal data, which must sub­se­quent­ly be pro­ces­sed by us. The data sub­ject is, for examp­le, obli­ged to pro­vi­de us with per­so­nal data when our com­pa­ny signs a con­tract with him or her. The non‐provision of the per­so­nal data would have the con­se­quence that the con­tract with the data sub­ject could not be con­clu­ded. Befo­re per­so­nal data is pro­vi­ded by the data sub­ject, the data sub­ject must con­tact any employee. The employee cla­ri­fies to the data sub­ject whe­ther the pro­vi­si­on of the per­so­nal data is requi­red by law or con­tract or is necessa­ry for the con­clu­si­on of the con­tract, whe­ther the­re is an obli­ga­ti­on to pro­vi­de the per­so­nal data and the con­se­quen­ces of non‐provision of the per­so­nal data.

Exis­tence of auto­ma­ted decision‐making

Data pro­tec­tion pro­vi­si­ons about the app­li­ca­ti­on and use of You­Tube

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

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

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

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

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

As a respon­si­ble com­pa­ny, we do not use auto­ma­tic decision‐making or pro­filing.

Contact

Social Media

Our site uses cookies to optimize and properly display our website. By continuing to use this website, you agree to the use of cookies. In our privacy policy you can see which cookies are used on this website and instructions on how to refuse them.OKMore Information