Imprint

Imprint

Infor­ma­ti­on in accordance with §5 of the E‑Commerce Act, §14 of the Unter­neh­mens­ge­setz­buch, §63 of the Com­mer­cial Code and dis­clo­sure requi­re­ments under §25 of the Media Act.

Dani­el Gat­tin­ger MSc

Tech­ni­ker­stra­ße 25,
6020 Inns­bruck,
Öster­reich

Email: blog@alpineresistancemap.com

Source: Crea­ted with the Impres­sum Gene­ra­tor by AdSimp­le® Online Mar­ke­ting in coope­ra­ti­on with schoenheitsmagazin.at

Copyright notice

Con­tents and com­pi­la­ti­ons published on the­se web­sites by the pro­vi­ders are sub­ject to Euro­pean copy­right laws. Repro­duc­tion, editing, dis­tri­bu­ti­on as well as the use of any kind out­side the scope of the copy­right law requi­re a writ­ten per­mis­si­on of the aut­hor or ori­gi­na­tor. Down­loads and copies of the­se web­sites are per­mit­ted for pri­va­te use only.
The com­mer­cial use of our con­tents wit­hout per­mis­si­on of the ori­gi­na­tor is prohibited.

Copy­right laws of third par­ties are respec­ted as long as the con­tents on the­se web­sites do not ori­gi­na­te from the pro­vi­der. Con­tri­bu­ti­ons of third par­ties on this site are indi­ca­ted as such. Howe­ver, if you noti­ce any vio­la­ti­ons of copy­right law, plea­se inform us. Such con­tents will be remo­ved immediately.

Picture credits

Pic­tures, Illus­tra­ti­ons and dra­wings on this web­site are sub­ject to the Euro­pean copy­right laws. 

Pic­tu­re cre­dits belong to the fol­lo­wing persons:

  • Dani­el Gat­tin­ger MSc
  • Cayla Sil­ber­mann

Privacy policy

Privacy Policy

We crea­ted this Pri­va­cy Poli­cy (ver­si­on 01.01.1970–121400181), to decla­re which infor­ma­ti­on we coll­ect, how we use data and which opti­ons the users of our web­site have, accor­ding to the gui­de­lines of the Gene­ral Data Pro­tec­tion Regu­la­ti­on (EU) 2016/679

Unfort­u­na­te­ly, the­se sub­jects sound rather tech­ni­cal due to their natu­re, but we have put much effort into describ­ing the most important things as sim­ply and cle­ar­ly as possible.

Automatic Data Retention

Every time you visit a web­site nowa­days, cer­tain infor­ma­ti­on is auto­ma­ti­cal­ly crea­ted and saved, just as it hap­pens on this website.

When­ever you visit our web­site such as you are doing right now, our web­ser­ver (com­pu­ter on which this web­site is saved/stored) auto­ma­ti­cal­ly saves data such as

  • the address (URL) of the acces­sed website
  • brow­ser and brow­ser version
  • the used ope­ra­ting system
  • the address (URL) of the pre­vious­ly visi­ted site (refer­rer URL)
  • the host name and the IP-address of the device the web­site is acces­sed from
  • date and time

in files (web­ser­ver-log­files).

Gene­ral­ly, web­ser­ver-log­files stay saved for two weeks and then get dele­ted auto­ma­ti­cal­ly. We do not pass this infor­ma­ti­on to others, but we can­not exclude the pos­si­bi­li­ty that this data will be loo­ked at in case of ille­gal conduct.

Cookies

Our web­site uses HTTP-coo­kies to store user-spe­ci­fic data.
For your bet­ter under­stan­ding of the fol­lo­wing Pri­va­cy Poli­cy state­ment, we will explain to you below what coo­kies are and why they are in use.

What exactly are cookies?

Every time you surf the inter­net, you use a brow­ser. Com­mon brow­sers are for exam­p­le Chro­me, Safa­ri, Fire­fox, Inter­net Explo­rer and Micro­soft Edge. Most web­sites store small text-files in your brow­ser. The­se files are cal­led cookies.

What should not be dis­missed, is that coo­kies are very useful litt­le hel­pers. Near­ly all web­sites use coo­kies. More accu­ra­te­ly spea­king the­se are HTTP-coo­kies, sin­ce the­re are also dif­fe­rent coo­kies for other uses. http-coo­kies are small files which our web­site stores on your com­pu­ter. The­se coo­kie files are auto­ma­ti­cal­ly put into the coo­kie-fol­der, which is like the “brain” of your brow­ser. A coo­kie con­sists of a name and a value. Moreo­ver, to defi­ne a coo­kie, one or mul­ti­ple attri­bu­tes must be specified.

Coo­kies save cer­tain parts of your user data, such as e.g. lan­guage or per­so­nal page set­tings. When you re-open our web­site, your brow­ser sub­mits the­se “user spe­ci­fic” infor­ma­ti­on back to our site. Thanks to coo­kies, our web­site knows who you are and offers you the set­tings you are fami­li­ar to. In some brow­sers every coo­kie has its own file, in others such as Fire­fox, all coo­kies are stored in one sin­gle file.

The­re are both first-par­ty coo­kies and third-par­ty cooo­kies. First-par­ty coo­kies are crea­ted direct­ly by our site, while third-par­ty coo­kies are crea­ted by part­ner-web­sites (e.g. Goog­le Ana­ly­tics). Every coo­kie is indi­vi­du­al, sin­ce every coo­kie stores dif­fe­rent data. The expi­ra­ti­on time of a coo­kie also varies – it can be a few minu­tes, or up to a few years. Coo­kies are no soft­ware-pro­grams and con­tain no com­pu­ter viru­s­es, tro­jans or any other mal­wa­re. Coo­kies also can­not access your PC’s information.

This is an exam­p­le of how coo­kie-files can look:

name: _ga
value: GA1.2.1326744211.152121400181–9
pur­po­se: dif­fe­ren­tia­ti­on bet­ween web­site visi­tors
expi­ra­ti­on date: after 2 years

A brow­ser should sup­port the­se mini­mum sizes:

  • at least 4096 bytes per cookie
  • at least 50 coo­kies per domain
  • at least 3000 coo­kies in total

Which types of cookies are there?

What exact coo­kies we use, depends on the used ser­vices. We will explain this in the fol­lo­wing sec­tions of the Pri­va­cy Poli­cy state­ment. First­ly, we will brief­ly focus on the dif­fe­rent types of HTTP-cookies.

The­re are 4 dif­fe­rent types of cookies:

Essen­ti­al Coo­kies
The­se coo­kies are neces­sa­ry to ensu­re the basic func­tion of a web­site. They are nee­ded when a user for exam­p­le puts a pro­duct into their shop­ping cart, then con­ti­nues sur­fing on dif­fe­rent web­sites and comes back later in order to pro­ceed to the check­out. Even when the user clo­sed their win­dow prio­r­ly, the­se coo­kies ensu­re that the shop­ping cart does not get deleted.

Pur­po­si­ve Coo­kies
The­se coo­kies coll­ect info about the user beha­viour and record if the user poten­ti­al­ly recei­ves any error mes­sa­ges. Fur­ther­mo­re, the­se coo­kies record the website’s loa­ding time as well as its beha­viour within dif­fe­rent browsers.

Tar­get-ori­en­ta­ted Coo­kies
The­se coo­kies care for an impro­ved user-fri­end­li­ne­ss. Thus, infor­ma­ti­on such as pre­vious­ly ente­red loca­ti­ons, fonts or data in forms stay saved.

Adver­ti­sing Coo­kies
The­se coo­kies are also known as tar­ge­ting-Coo­kies. They ser­ve the pur­po­se of deli­ve­ring indi­vi­du­al­ly adapt­ed adver­ti­se­ments to the user. This can be very prac­ti­cal, but also rather annoying.

Upon your first visit to a web­site you are usual­ly asked which of the­se coo­kie-types you want to accept. Fur­ther­mo­re, this decis­i­on will of cour­se also be saved in a cookie.

How can I delete cookies?

You yours­elf take the decis­i­on if and how you want to use coo­kies. Thus, no mat­ter what ser­vice or web­site coo­kies are from, you always have the opti­on to dele­te, deac­ti­va­te or only par­ti­al­ly allow them. The­r­e­fo­re, you can for exam­p­le block coo­kies of third par­ties but allow any other cookies.

If you want chan­ge or dele­te coo­kie-set­tings and would like to deter­mi­ne which coo­kies have been saved to your brow­ser, you can find this info in your browser-settings:

Chro­me: Clear, enable and mana­ge coo­kies in Chrome 

Safa­ri: Mana­ge coo­kies and web­site data in Safari 

Fire­fox: Clear coo­kies and site data in Firefox 

Inter­net Explo­rer: Dele­te and mana­ge cookies 

Micro­soft Edge: Dele­te coo­kies in Micro­soft Edge 

If you gene­ral­ly do not want to allow any coo­kies at all, you can set up your brow­ser in a way, to noti­fy you when­ever a poten­ti­al coo­kie is about to be set. This gives you the oppor­tu­ni­ty to manu­al­ly deci­de to eit­her per­mit or deny the pla­ce­ment of every sin­gle coo­kie. The set­tings for this dif­fer from brow­ser to brow­ser. The­r­e­fo­re, it might be best for you to search for the ins­truc­tions in Goog­le. If you are using Chro­me, you could for exam­p­le put the search phra­se “dele­te coo­kies Chro­me” or “deac­ti­va­te coo­kies Chro­me” into Google.

How is my data protected?

The­re is a “coo­kie poli­cy” that has been in place sin­ce 2009. It sta­tes that the sto­rage of coo­kies requi­res the user’s con­sent. Howe­ver, among the count­ries of the EU, the­se gui­de­lines are often met with mixed reac­tions. In Aus­tria the gui­de­lines have been imple­men­ted in § 96 sec­tion 3 of the Tele­com­mu­ni­ca­ti­ons Act (TKG).

If you want to learn more about coo­kies and do not mind tech­ni­cal docu­men­ta­ti­on, we recom­mend https://tools.ietf.org/html/rfc6265, the Request for Comm­ents of the Inter­net Engi­nee­ring Task Force (IETF) cal­led “HTTP Sta­te Manage­ment Mechanism”.

Storage of Personal Data

Any per­so­nal data you elec­tro­ni­cal­ly sub­mit to us on this web­site, such as your name, email address, home address or other per­so­nal infor­ma­ti­on you pro­vi­de via the trans­mis­si­on of a form or via any comm­ents to the blog, are sole­ly used for the spe­ci­fied pur­po­se and get stored secu­re­ly along with the respec­ti­ve sub­mis­si­on times and IP-address. The­se data do not get pas­sed on to third parties.

The­r­e­fo­re, we use per­so­nal data for the com­mu­ni­ca­ti­on with only tho­se users, who have expli­cit­ly reques­ted being cont­ac­ted, as well as for the exe­cu­ti­on of the ser­vices and pro­ducts offe­red on this web­site. We do not pass your per­so­nal data to others wit­hout your appr­oval, but we can­not exclude the pos­si­bi­li­ty this data will be loo­ked at in case of ille­gal conduct.

If you send us per­so­nal data via email – and thus not via this web­site – we can­not gua­ran­tee any safe trans­mis­si­on or pro­tec­tion of your data. We recom­mend you, to never send con­fi­den­ti­al data via email.

Rights in accordance with the General Data Protection Regulation

You are gran­ted the fol­lo­wing rights in accordance with the pro­vi­si­ons of the GDPR (Gene­ral Data Pro­tec­tion Regu­la­ti­on) and the Aus­tri­an Data Pro­tec­tion Act (DSG):

  • right to rec­ti­fi­ca­ti­on (artic­le 16 GDPR)
  • right to era­su­re (“right to be for­got­ten“) (artic­le 17 GDPR)
  • right to rest­rict pro­ces­sing (artic­le 18 GDPR)
  • righ to noti­fi­ca­ti­on – noti­fi­ca­ti­on obli­ga­ti­on regar­ding rec­ti­fi­ca­ti­on or era­su­re of per­so­nal data or rest­ric­tion of pro­ces­sing (artic­le 19 GDPR)
  • right to data por­ta­bi­li­ty (artic­le 20 GDPR)
  • Right to object (artic­le 21 GDPR)
  • right not to be sub­ject to a decis­i­on based sole­ly on auto­ma­ted pro­ces­sing – inclu­ding pro­fil­ing – (artic­le 22 GDPR)

If you think that the pro­ces­sing of your data vio­la­tes the data pro­tec­tion law, or that your data pro­tec­tion rights have been inf­rin­ged in any other way, you can lodge a com­plaint with your respec­ti­ve regu­la­to­ry aut­ho­ri­ty. For Aus­tria this is the data pro­tec­tion aut­ho­ri­ty, who­se web­site you can access at https://www.data-protection-authority.gv.at/.

Evaluation of Visitor Behaviour

In the fol­lo­wing Pri­va­cy Poli­cy, we will inform you on if and how we eva­lua­te the data of your visit to this web­site. The eva­lua­ti­on is gene­ral­ly made anony­mously, and we can­not link to you per­so­nal­ly based on your beha­viour on this website.

You can find out more about how to dis­agree with the eva­lua­ti­on of visi­tor data, in the Pri­va­cy Poli­cy below.

TLS encryption with https

We use https to trans­fer infor­ma­ti­on on the inter­net in a tap-pro­of man­ner (data pro­tec­tion through tech­no­lo­gy design Artic­le 25 Sec­tion 1 GDPR). With the use of TLS (Trans­port Lay­er Secu­ri­ty), which is an encryp­ti­on pro­to­col for safe data trans­fer on the inter­net, we can ensu­re the pro­tec­tion of con­fi­den­ti­al infor­ma­ti­on. You can reco­g­ni­se the use of this safe­guar­ding tool by the litt­le lock-sym­bol, which is situa­ted in your browser’s top left cor­ner, as well as by the use of the let­ters https (ins­tead of http) as a part of our web address.

Google Fonts Privacy Policy

On our web­site we use Goog­le Fonts, from the com­pa­ny Goog­le Inc. (1600 Amphi­theat­re Park­way Moun­tain View, CA 94043, USA).

To use Goog­le Fonts, you must log in and set up a pass­word. Fur­ther­mo­re, no coo­kies will be saved in your brow­ser. The data (CSS, Fonts) will be reques­ted via the Goog­le domains fonts.googleapis.com and fonts.gstatic.com. Accor­ding to Goog­le, all requests for CSS and fonts are ful­ly sepa­ra­ted from any other Goog­le ser­vices. If you have a Goog­le account, you do not need to worry that your Goog­le account details are trans­mit­ted to Goog­le while you use Goog­le Fonts. Goog­le records the use of CSS (Cas­ca­ding Style Sheets) as well as the uti­li­sed fonts and stores the­se data secu­re­ly. We will have a detail­ed look at how exact­ly the data sto­rage works.

What are Google Fonts?

Goog­le Fonts (pre­vious­ly Goog­le Web Fonts) is a list of over 800 fonts which href=”https://en.wikipedia.org/wiki/Google?tid=121400181”>Google LLC pro­vi­des its users for free.

Many of the­se fonts have been published under the SIL Open Font Licen­se licen­se, while others have been published under the Apa­che licen­se. Both are free soft­ware licenses.

Why do we use Google Fonts on our website?

With Goog­le Fonts we can use dif­fe­rent fonts on our web­site and do not have to upload them to our own ser­ver. Goog­le Fonts is an important ele­ment which helps to keep the qua­li­ty of our web­site high. All Goog­le fonts are auto­ma­ti­cal­ly opti­mi­sed for the web, which saves data volu­me and is an advan­ta­ge espe­ci­al­ly for the use of mobi­le ter­mi­nal devices. When you use our web­site, the low data size pro­vi­des fast loa­ding times. Moreo­ver, Goog­le Fonts are secu­re Web Fonts. Various image syn­the­sis sys­tems (ren­de­ring) can lead to errors in dif­fe­rent brow­sers, ope­ra­ting sys­tems and mobi­le ter­mi­nal devices. The­se errors could opti­cal­ly distort parts of texts or enti­re web­sites. Due to the fast Con­tent Deli­very Net­work (CDN) the­re are no cross-plat­form issues with Goog­le Fonts. All com­mon brow­sers (Goog­le Chro­me, Mozil­la Fire­fox, Apple Safa­ri, Ope­ra) are sup­port­ed by Goog­le Fonts, and it relia­bly ope­ra­tes on most modern mobi­le ope­ra­ting sys­tems, inclu­ding Android 2.2+ and iOS 4.2+ (iPho­ne, iPad, iPod). We also use Goog­le Fonts for pre­sen­ting our enti­re online ser­vice as plea­sant­ly and as uni­form­ly as possible.

Which data is saved by Google?

When­ever you visit our web­site, the fonts are rel­oa­ded by a Goog­le ser­ver. Through this exter­nal cue, data gets trans­fer­red to Google’s ser­vers. The­r­e­fo­re, this makes Goog­le reco­g­ni­se that you (or your IP-address) is visi­ting our web­site. The Goog­le Fonts API was deve­lo­ped to redu­ce the usa­ge, sto­rage and gathe­ring of end user data to the mini­mum nee­ded for the pro­per depic­tion of fonts. What is more, API stands for „Appli­ca­ti­on Pro­gramming Inter­face“ and works as a soft­ware data intermediary.

Goog­le Fonts stores CSS and font requests safe­ly with Goog­le, and the­r­e­fo­re it is pro­tec­ted. Using its coll­ec­ted usa­ge figu­res, Goog­le can deter­mi­ne how popu­lar the indi­vi­du­al fonts are. Goog­le publishes the results on inter­nal ana­ly­sis pages, such as Goog­le Ana­ly­tics. Moreo­ver, Goog­le also uti­li­ses data of ist own web craw­ler, in order to deter­mi­ne which web­sites are using Goog­le fonts. This data is published in Goog­le Fonts’ Big­Query data­ba­se. Enter­pre­neurs and deve­lo­pers use Google’s web­ser­vice Big­Query to be able to inspect and move big volu­mes of data.

One more thing that should be con­side­red, is that every request for Goog­le Fonts auto­ma­ti­cal­ly trans­mits infor­ma­ti­on such as lan­guage pre­fe­ren­ces, IP address, brow­ser ver­si­on, as well as the browser’s screen reso­lu­ti­on and name to Google’s ser­vers. It can­not be cle­ar­ly iden­ti­fied if this data is saved, as Goog­le has not direct­ly declared it.

How long and where is the data stored?

Goog­le saves requests for CSS assets for one day in a tag on their ser­vers, which are pri­ma­ri­ly loca­ted out­side of the EU. This makes it pos­si­ble for us to use the fonts by means of a Goog­le style­sheet. With the help of a style­sheet, e.g. designs or fonts of a web­site can get chan­ged swift­ly and easily.

Any font rela­ted data is stored with Goog­le for one year. This is becau­se Google’s aim is to fun­da­men­tal­ly boost web­sites’ loa­ding times. With mil­li­ons of web­sites refer­ring to the same fonts, they are buf­fe­r­ed after the first visit and instant­ly reap­pear on any other web­sites that are visi­ted the­re­af­ter. Some­ti­mes Goog­le updates font files to eit­her redu­ce the data sizes, increase the lan­guage covera­ge or to impro­ve the design.

How can I delete my data or prevent it being stored?

The data Goog­le stores for eit­her a day or a year can­not be dele­ted easi­ly. Upon ope­ning the page this data is auto­ma­ti­cal­ly trans­mit­ted to Goog­le. In order to clear the data ahead of time, you have to cont­act Google’s sup­port at https://support.google.com/?hl=en-GB&tid=121400181. The only way for you to pre­vent the reten­ti­on of your data is by not visi­ting our website.

Unli­ke other web fonts, Goog­le offers us unrest­ric­ted access to all its fonts. Thus, we have a vast sea of font types at our dis­po­sal, which helps us to get the most out of our web­site. You can find out more ans­wers and infor­ma­ti­on on Goog­le Fonts at https://developers.google.com/fonts/faq?tid=121400181. While Goog­le does address rele­vant ele­ments on data pro­tec­tion at this link, it does not con­tain any detail­ed infor­ma­ti­on on data reten­ti­on.
It pro­ofs rather dif­fi­cult to recei­ve any pre­cise infor­ma­ti­on on stored data by Google.

On https://policies.google.com/privacy?hl=en-GB you can read more about what data is gene­ral­ly coll­ec­ted by Goog­le and what this data is used for.

Google Fonts Local Privacy Policy

On our web­site we use Goog­le Fonts, from the com­pa­ny Goog­le Inc. (1600 Amphi­theat­re Park­way Moun­tain View, CA 94043, USA).
We inte­gra­ted Goog­le Fonts local­ly, so on our own web­ser­ver and not on Google’s ser­vers. Hence, the­re is no con­nec­tion to Google’s ser­vers and con­se­quent­ly no data trans­fer or retention.

What are Google Fonts?

Goog­le Fonts was pre­vious­ly cal­led Goog­le Web Fonts. It is an inter­ac­ti­ve list with over 800 fonts which Goog­le LLC offer for free use. With the use of Goog­le Fonts, it is pos­si­ble to uti­li­se fonts wit­hout uploa­ding them to your own ser­ver. For that mat­ter, in order to pre­vent any trans­fer of infor­ma­ti­on to Google’s ser­vers, we down­loa­ded the fonts to our own ser­ver. This way we com­ply with the data pri­va­cy and do not trans­mit any data to Goog­le Fonts.

Unli­ke other web fonts, Goog­le offers us unrest­ric­ted access to all its fonts. Thus, we have a vast sea of font types at our dis­po­sal, which helps us to get the most out of our web­site. You can find out more ans­wers and infor­ma­ti­on on Goog­le Fonts at https://developers.google.com/fonts/faq?tid=121400181.

Google Analytics Privacy Policy

We use the track­ing and ana­ly­sis tool Goog­le Ana­ly­tics (GA) of the US-Ame­ri­can com­pa­ny Goog­le LLC (1600 Amphi­theat­re Park­way Moun­tain View, CA 94043, USA). Goog­le Ana­ly­tics coll­ects data on your actions on our web­site. When­ever you click a link for exam­p­le, this action is saved in a coo­kie and trans­fer­red to Goog­le Ana­ly­tics. With the help of reports which we recei­ve from Goog­le Ana­ly­tics, we can adapt our web­site and our ser­vices bet­ter to your wis­hes. In the fol­lo­wing, we will explain the track­ing tool in more detail, and most of all, we will inform you what data is saved and how you can pre­vent this.

What is Google Analytics?

Goog­le Ana­ly­tics is a track­ing tool with the pur­po­se of con­duc­ting data traf­fic ana­ly­sis of our web­site. For Goog­le Ana­ly­tics to work, the­re is a track­ing code inte­gra­ted to our web­site. Upon your visit to our web­site, this code records various actions you per­form on your web­site. As soon as you lea­ve our web­site, this data is sent to the Goog­le Ana­ly­tics ser­ver, whe­re it is stored.

Goog­le pro­ces­ses this data and we then recei­ve reports on your user beha­viour. The­se reports can be one of the following:

  • Tar­get audi­ence reports: With the help of tar­get audi­ence reports we can get to know our users bet­ter and can the­r­e­fo­re bet­ter under­stand who is inte­res­ted in our service.
  • Adver­ti­sing reports: Through adver­ti­sing reports we can ana­ly­se our online adver­ti­sing bet­ter and hence impro­ve it.
  • Acqui­si­ti­on reports: Acqui­si­ti­on reports pro­vi­de us hel­pful infor­ma­ti­on on how we can get more peo­p­le enthu­si­a­stic about our service.
  • Beha­viour reports: With the­se reports, we can find out how you inter­act with our web­site. By the means of beha­viour reports, we can under­stand what path you go on our web­site and what links you click.
  • Con­ver­si­on reports: A con­ver­si­on is the pro­cess of lea­ding you to car­ry out a desi­red action due to a mar­ke­ting mes­sa­ge. An exam­p­le of this would be trans­forming you from a mere web­site visi­tor into a buy­er or a news­let­ter sub­scri­ber. Hence, with the help of the­se reports we can see in more detail, if our mar­ke­ting mea­su­res are suc­cessful with you. Our aim is to increase our con­ver­si­on rate.
  • Real time reports: With the help of the­se reports we can see in real time, what hap­pens on our web­site. It makes us for exam­p­le see, we can see how many users are rea­ding this text right now.

Why do we use Google Analytics on our website?

The objec­ti­ve of our web­site is clear: We want to offer you the best pos­si­ble ser­vice. Goog­le Ana­ly­tics’ sta­tis­tics and data help us with rea­ching this goal.

Sta­tis­ti­cal­ly eva­lua­ted data give us a clear pic­tu­re of the strengths and weak­ne­s­ses of our web­site. On the one hand, we can opti­mi­se our page in a way, that makes it easier to be found by inte­res­ted peo­p­le on Goog­le. On the other hand, the data helps us to get a bet­ter under­stan­ding of you as our visi­tor. The­r­e­fo­re, we can very accu­ra­te­ly find out what we must impro­ve on our web­site, in order to offer you the best pos­si­ble ser­vice. The ana­ly­sis of that data also enables us to car­ry out our adver­ti­sing and mar­ke­ting mea­su­res in a more indi­vi­du­al and more cost-effec­ti­ve way. After all, it only makes sen­se to show our pro­ducts and ser­vices exclu­si­ve­ly to peo­p­le who are inte­res­ted in them.

What data gets stored by Google Analytics?

With the aid of a track­ing code, Goog­le Ana­ly­tics crea­tes a ran­dom, uni­que ID which is con­nec­ted to your brow­ser coo­kie. That way, Goog­le Ana­ly­tics reco­g­ni­s­es you as a new user. The next time you visit our site, you will be reco­g­nis­ed as a “recur­ring” user. All data that is coll­ec­ted gets saved tog­e­ther with this very user ID. Only this is how it is made pos­si­ble for us to eva­lua­te and ana­ly­se pseud­ony­mous user profiles.

Your inter­ac­tions on our web­site are mea­su­res by tags such as coo­kies and app ins­tance IDs. Inter­ac­tions are all kinds of actions that you per­form on our web­site. If you are also using other Goog­le sys­tems (such as a Goog­le Account), data gene­ra­ted by Goog­le Ana­ly­tics can be lin­ked with third-par­ty coo­kies. Goog­le does not pass on any Goog­le Ana­ly­tics data, unless we as the web­site owners aut­ho­ri­se it. In case it is requi­red by law, excep­ti­ons can occur.

The fol­lo­wing coo­kies are used by Goog­le Analytics:

Name: _ga
Value:2.1326744211.152121400181–5
Pur­po­se: By deafault, analytics.js uses the coo­kie _ga, to save the user ID. It gene­ral­ly ser­ves the pur­po­se of dif­fe­ren­cia­ting bet­ween web­site visi­tors.
Expi­ra­ti­on date: After 2 years

Name: _gid
Value:2.1687193234.152121400181–1
Pur­po­se: This coo­kie also ser­ves the pur­po­se of dif­fe­ren­tia­ting bet­ween web­site users
Expi­ra­ti­on date: After 24 hours

Name: _gat_gtag_UA_
Value: 1
Ver­wen­dungs­zweck: It is used for decre­asing the demand rate. If Goog­le Ana­ly­tics is pro­vi­ded via Goog­le Tag Mana­ger, this coo­kie gets the name _dc_gtm_ .
Expi­ra­ti­on date: After 1 minute

Name: AMP_TOKEN
Value: No infor­ma­ti­on
Pur­po­se: This coo­kie has a token which is used to retrie­ve the user ID by the AMP Cli­ent ID Ser­vice. Other pos­si­ble values sug­gest a log­off, a request or an error.
Expi­ra­ti­on date: After 30 seconds up to one year

Name: __utma
Value:1564498958.1564498958.1564498958.1
Pur­po­se: With this coo­kie your beha­viour on the web­site can be tra­cked and the site per­for­mance can be mea­su­red. The coo­kie is updated every time the infor­ma­ti­on is sent to Goog­le Ana­ly­tics.
Expi­ra­ti­on date: After 2 years

Name: __utmt
Value: 1
Pur­po­se: Just like _gat_gtag_UA_ this coo­kie is used for kee­ping the requi­re­ment rate in check.
Expi­ra­ti­on date: Afer 10 minutes

Name: __utmb
Value:3.10.1564498958
Pur­po­se: This coo­kie is used to deter­mi­ne new ses­si­ons. It is updated every time new data or infor­ma­ti­on gets sent to Goog­le Ana­ly­tics.
Expi­ra­ti­on date: After 30 minutes

Name: __utmc
Value: 167421564
Pur­po­se: This coo­kie is used to deter­mi­ne new ses­si­ons for recur­ring visi­tors. It is the­r­e­fo­re a ses­si­on coo­kie, and only stays saved until you clo­se the brow­ser again.
Expi­ra­ti­on date: After clo­sing the browser

Name: __utmz
Value: m|utmccn=(referral)|utmcmd=referral|utmcct=/
Pur­po­se: This coo­kie is used to iden­ti­fy the source of our website’s visi­tor num­ber. This means, that the coo­kie saves infor­ma­ti­on on whe­re you came to our web­site from. This could be ano­ther site or an adver­ti­se­ment.
Expi­ra­ti­on date: After 6 months

Name: __utmv
Value: No infor­ma­ti­on
Pur­po­se: The coo­kie is used to store cus­tom user data. It gets updated when­ever infor­ma­ti­on is sent to Goog­le Ana­ly­tics.
Expi­ra­ti­on date: After 2 years

Note: This list is by no means exhaus­ti­ve, sin­ce Goog­le are repea­ted­ly chan­ging the use of their cookies.

Below we will give you an over­view of the most important data that can be eva­lua­ted by Goog­le Analytics:

Heat­maps: Goog­le crea­tes so-cal­led Heat­maps an. The­se Heat­maps make it pos­si­ble to see the exact are­as you click on, so we can get infor­ma­ti­on on what rou­tes you make on our website.

Ses­si­on dura­ti­on: Goog­le calls the time you spend on our web­site wit­hout lea­ving it ses­si­on dura­ti­on. When­ever you are inac­ti­ve for 20 minu­tes, the ses­si­on ends automatically.

Boun­ce rate If you only look at one page of our web­site and then lea­ve our web­site again, it is cal­led a bounce.

Account crea­ti­on: If you crea­te an account or make an order on our web­site, Goog­le Ana­ly­tics coll­ects this data.

IP-Address: The IP address is only shown in a shor­ten­ed form, to make it impos­si­ble to cle­ar­ly allo­ca­te it.

Loca­ti­on: Your appro­xi­ma­te loca­ti­on and the coun­try you are in can be defi­ned by the IP address. This pro­cess is cal­led IP loca­ti­on determination.

Tech­ni­cal infor­ma­ti­on: Infor­ma­ti­on about your brow­ser type, your inter­net pro­vi­der and your screen reso­lu­ti­on are cal­led tech­ni­cal information.

Source: Both, Goog­le Ana­ly­tics as well as our­sel­ves, are inte­res­ted what web­site or what adver­ti­se­ment led you to our site.

Fur­ther pos­si­bly stored data includes cont­act data, poten­ti­al reviews, play­ing media (e.g. when you play a video on our site), sha­ring of con­tents via social media or adding our site to your favou­ri­tes. This list is not exhaus­ti­ve and only ser­ves as gene­ral gui­dance on Goog­le Ana­ly­tics’ data retention.

How long and where is the data saved?

Goog­le has ser­vers across the glo­be. Most of them are in Ame­ri­ca and the­r­e­fo­re your data is main­ly saved on Ame­ri­can ser­vers. Here you can read detail­ed infor­ma­ti­on on whe­re Google’s data cen­tres are loca­ted: https://www.google.com/about/datacenters/inside/locations/?hl=en

Your data is allo­ca­ted to various phy­si­cal data medi­ums. This has the advan­ta­ge of allo­wing to retrie­ve the data fas­ter, and of pro­tec­ting it bet­ter from mani­pu­la­ti­on. Every Goog­le data cent­re has respec­ti­ve emer­gen­cy pro­grams for your data. Hence, in case of a hard­ware fail­ure at Goog­le or a ser­ver error due to natu­ral dis­as­ters, the risk for a ser­vice inter­rup­ti­on stays rela­tively low.

Goog­le Ana­ly­tics has a 26 months stan­dar­di­sed peri­od of retai­ning your user data. After this time, your user data is dele­ted. Howe­ver, we have the pos­si­bi­li­ty to choo­se the reten­ti­on peri­od of user data our­sel­ves. The­re are the fol­lo­wing five options:

  • Dele­ti­on after 14 months
  • Dele­ti­on after 26 months
  • Dele­ti­on after 38 months
  • Dele­ti­on after 50 months
  • No auto­ma­ti­cal deletion

As soon as the cho­sen peri­od is expi­red, the data is dele­ted once a month. This reten­ti­on peri­od appli­es to any of your data which is lin­ked to coo­kies, user iden­ti­fi­ca­ti­on and adver­ti­se­ment IDs (e.g. coo­kies of the Dou­ble­Click domain). Any report results are based on aggre­ga­ted infor­ma­ti­on and are stored inde­pendent­ly of any user data. Aggre­ga­ted infor­ma­ti­on is a mer­ge of indi­vi­du­al data into a sin­gle and big­ger unit.

How can I delete my data or prevent data retention?

Under the pro­vi­si­ons of the Euro­pean Union’s data pro­tec­tion law, you have the right to obtain infor­ma­ti­on on your data and to update, dele­te or rest­rict it. With the help of a brow­ser add on that can deac­ti­va­te Goog­le Ana­ly­tics’ Java­Script (ga.js, analytics.js, dc.js), you can pre­vent Goog­le Ana­ly­tics from using your data. You can down­load this add on at https://tools.google.com/dlpage/gaoptout?hl=en-GB. Plea­se con­sider that this add on can only deac­ti­va­te any data coll­ec­tion by Goog­le Analytics.

Should you gene­ral­ly want to deac­ti­va­te, dele­te or mana­ge all coo­kies (inde­pendent­ly of Goog­le Ana­ly­tics), you can use one of the gui­des that are available for any browser:

Chro­me: Clear, enable and mana­ge coo­kies in Chrome 

Safa­ri: Mana­ge coo­kies and web­site data in Safari 

Fire­fox: Clear coo­kies and site data in Firefox 

Inter­net Explo­rer: Dele­te and mana­ge cookies 

Micro­soft Edge: Dele­te coo­kies in Micro­soft Edge 

Goog­le Ana­ly­tics is an acti­ve par­ti­ci­pant of the EU‑U.S. Pri­va­cy Shield Frame­work, which regu­la­tes cor­rect and save trans­fer of per­so­nal data.
You can find more infor­ma­ti­on on this at https://www.privacyshield.gov/participant?id=a2zt000000001L5AAI&tid=121400181. We hope we were able to make you more fami­li­ar with the most important infor­ma­ti­on on Goog­le Ana­ly­tics’ data pro­ces­sing. If you want to learn more about the track­ing ser­vice, we recom­mend both of the fol­lo­wing links: https://marketingplatform.google.com/about/analytics/terms/gb/ and https://support.google.com/analytics/answer/6004245?hl=en.

Google Analytics IP Anonymisation

We imple­men­ted Goog­le Ana­ly­tics’ IP address anony­mi­sa­ti­on to this web­site. Goog­le deve­lo­ped this func­tion, so this web­site can com­ply with the appli­ca­ble pri­va­cy laws and the local data pro­tec­tion aut­ho­ri­ties’ recom­men­da­ti­ons, should they pro­hi­bit the reten­ti­on of any full IP addres­ses.
The anony­mi­sa­ti­on or mas­king of IP addres­ses takes place, as soon as they reach Goog­le Ana­ly­tics’ data coll­ec­tion net­work, but befo­re the data would be saved or processed.

You can find more infor­ma­ti­on on IP anony­mi­sa­ti­on at https://support.google.com/analytics/answer/2763052?hl=en.

Newsletter Privacy Policy

When you sub­scri­be to our News­let­ter you sub­mit your per­so­nal data and give us the right to cont­act you via email. We use the data that is stored for the regis­tra­ti­on for the News­let­ter exclu­si­ve­ly for our News­let­ter and do not pass them on.

If you unsub­scri­be from the news­let­ter – for which you can find a link in the bot­tom of every news­let­ter – we will dele­te all data that was saved when you regis­tered for the newsletter.

MailChimp Privacy Policy

Like many other web­sites, we use the ser­vices of the news­let­ter com­pa­ny MailChimp on our web­site. The ope­ra­tor of MailChimp is the com­pa­ny The Rocket Sci­ence Group, LLC, 675 Pon­ce de Leon Ave NE, Suite 5000, Atlan­ta, GA 30308 USA. With the aid of MailChimp we can easi­ly send you inte­res­t­ing news via news­let­ter. For the use of the ser­vice we do not have to install any­thing but can still access a pool of very effi­ci­ent fea­tures. In the fol­lo­wing we will give more details on this email mar­ke­ting ser­vice and will inform you about the most important data pro­tec­tion aspects.

What is MailChimp?

MailChimp is a cloud-based news­let­ter manage­ment ser­vice. “Cloud-based“ means that we do not need to install MailChimp on our own com­pu­ter or ser­ver. Ins­tead, we use the ser­vice on an exter­nal ser­ver, or more spe­ci­fi­cal­ly via an IT infra­struc­tu­re, which is available via the inter­net. Using a soft­ware this way is also cal­led SaaS (soft­ware as a service).

MailChimp allows us to cho­se from a wide ran­ge of dif­fe­rent email types. Depen­ding on what goal we want to reach with our news­let­ter, we can run indi­vi­du­al cam­paigns, regu­lar cam­paigns, auto respon­ders (auto­ma­ted emails), A/B tests, RSS cam­paigns (mai­lings at pre-set times and fre­quen­ci­es) and fol­low-up campaigns.

Why do we use MailChimp on our website?

The reason we would use any news­let­ter ser­vice is so we can stay in cont­act with you. We want to keep you on the loop what news or attrac­ti­ve offers we have for you at the time. As we con­stant­ly seek out the easie­st and best solu­ti­ons for our mar­ke­ting mea­su­res, we have deci­ded on MailChimp as our news­let­ter manage­ment ser­vice. While the soft­ware is very easy to use, it offers many hel­pful fea­tures. For exam­p­le, it allows us to crea­te inte­res­t­ing and attrac­ti­ve news­let­ters in only a short time. With inte­gra­ted design tem­pla­tes we can crea­te every news­let­ter in an indi­vi­du­al way. Due to the “respon­si­ve design” fea­ture, our con­tents are also pre­sen­ted in a rea­da­ble and plea­sant way on your smart­phone (or any other mobi­le device).

With tools such as A/B test­ing or the exten­si­ve ana­ly­sis opti­ons, we can swift­ly tell how you like our news­let­ters. This means that we can react if neces­sa­ry and impro­ve our offer or our services.

Ano­ther advan­ta­ge is MailChimp’s “cloud sys­tem”. The data is not stored and pro­ces­sed direct­ly on our ser­ver. We can retrie­ve the datafrom exter­nal ser­vers and the­r­e­fo­re save our memo­ry space and also decrease main­ten­an­ce effort.

What data is saved by MailChimp?

Rocket Sci­ence Group LLC (MailChimp) ope­ra­te online plat­forms which enable us to get in cont­act with you, pro­vi­ded you sub­scri­bed to our news­let­ter. If you beco­me a sub­scri­ber of our news­let­ter via our web­site, by email you agree to beco­me a mem­ber of a MailChimp email list. Then, MailChimp saves your sub­scrip­ti­on data and your IP address, so it can veri­fy your ent­ry into the list pro­vi­der. Moreo­ver, MailChimp stores your email address, your name, your phy­si­cal address and demo­gra­phic infor­ma­ti­on, such as lan­guage or location.

This infor­ma­ti­on is used to send emails to you and to allow cer­tain other MailChimp func­tions (e.g. the eva­lua­ti­on of newsletters).

MailChimp also shares infor­ma­ti­on with third par­ties to impro­ve its ser­vices. Moreo­ver, MailChimp shares cer­tain data with adver­ti­sing part­ners of third par­ties to get a bet­ter under­stan­ding of its cli­ents’ inte­rests, in order to pro­vi­de rele­vant con­tents and tar­get-ori­en­ted advertising.

With so-cal­led “web bea­cons” (small gra­phics in HTML emails), MailChimp can deter­mi­ne if an email has arri­ved, has been ope­ned or if links have been cli­cked. This infor­ma­ti­on is then stored on MailChimp’s ser­vers. That way we recei­ve sta­tis­ti­cal eva­lua­tions and can see how you lik­ed our news­let­ter. The­r­e­fo­re, we can tail­or our offer bet­ter to your wis­hes and impro­ve our service.

Moreo­ver, MailChimp are allo­wed to use this data for impro­ving their own ser­vice. Thus, they can for exam­p­le tech­ni­cal­ly opti­mi­se the dis­tri­bu­ti­on or deter­mi­ne the loca­ti­on (or the coun­try) of the recipient.

The fol­lo­wing coo­kies can be set by MailChimp. The list is not exhaus­ti­ve and is mere­ly an exem­pla­ry selection:

Name: AVESTA_ENVIRONMENT
Value: Prod
Pur­po­se: This coo­kie is neces­sa­ry to pro­vi­de the ser­vices of Mailchimp. It is always set when a user regis­ters for a news­let­ter mai­ling list.
Expiry date: at the end of the session

Name: ak_bmsc
Value: F1766FA98C9BB9DE4A39F70A9E5EEAB55F6517348A7000001121400181‑3
Pur­po­se: The coo­kie is used to dif­fe­ren­tia­te a human from a bot. That way secu­re reports on the use of a web­site can be crea­ted.
Expiry date: after 2 hours

Name: bm_sv
Value: A5A322305B4401C2451FC22FFF547486~FEsKGvX8eovCwTeFTzb8//I3ak2Au…
Pur­po­se: This coo­kie comes from Mas­ter­Pass Digi­tal Wal­let (a Mas­ter­Card ser­vice) and is used to offer a secu­re and easy vir­tu­al pay­ment pro­cess to visi­tors. For this pur­po­se, the user is anony­mously iden­ti­fied on the web­site.
Expiry date: after 2 hours

Name: _abck
Value: 8D545C8CCA4C3A50579014C449B045121400181‑9
Pur­po­se: We could not find any fur­ther infor­ma­ti­on about the pur­po­se of this coo­kie.
Expiry date: after one year

For bet­ter dis­play it could be that you would some­ti­mes open our news­let­ter via a spe­ci­fied link. This can be the case if your email pro­gram does not work or if the news­let­ter is not dis­play­ed pro­per­ly. The news­let­ter will then be shown via a MailChimp web­site. MailChimp also uses coo­kies on its web­sites (small text files which save data on your brow­ser).
Per­so­nal data can be pro­ces­sed by MailChimp and their part­ners (e.g. Goog­le Ana­ly­tics). MailChimp is respon­si­ble for the coll­ec­tion of this data and we have no influence on it. MailChimp’s “Coo­kie State­ment” (at: https://mailchimp.com/legal/cookies/) tells you exact­ly how and why the com­pa­ny uses cookies.

How long and where is the data saved?

Sin­ce MailChimp is an Ame­ri­can com­pa­ny, all retai­ned data is stored on Ame­ri­can servers.

Gene­ral­ly, the data stays per­ma­nent­ly saved on MailChimp’s ser­vers and is dele­ted only when you request it. You can have your cont­act infor­ma­ti­on with us dele­ted. This per­ma­nent­ly remo­ves all your per­so­nal data for us and anony­mi­ses you in MailChimp’s reports. Howe­ver, you can also request the dele­ti­on of your data per­ma­nent­ly at MailChimp. Then all your data are remo­ved from the­re and we recei­ve a noti­fi­ca­ti­on from MailChimp. After we recei­ve the email we have 30 days to dele­te your cont­act from all integrations.

How can I delete my data or prevent data retention?

You can with­draw your appr­oval for the receipt of our news­let­ters any­ti­me, by cli­cking the link in the lower area of the recei­ved news­let­ter email. When you click on the unsub­scri­be link, your data with MailChimp gets deleted.

When you land on a MailChimp web­site via a link in our news­let­ter and coo­kies are con­se­quent­ly set in your brow­ser, you can dele­te or deac­ti­va­te the­se coo­kies anytime.

Depen­ding on the brow­ser, the deac­ti­va­ti­on or dele­ti­on dif­fers slight­ly. The fol­lo­wing ins­truc­tions show how to mana­ge coo­kies in your browser:

Chro­me: Clear, enable and mana­ge coo­kies in Chrome 

Safa­ri: Mana­ge coo­kies and web­site data in Safari 

Fire­fox: Clear coo­kies and site data in Firefox 

Inter­net Explo­rer: Dele­te and mana­ge cookies 

Micro­soft Edge: Dele­te coo­kies in Micro­soft Edge 

If you gene­ral­ly do not want to allow any coo­kies, you can set up your brow­ser in a way so it would noti­fy you when­ever a poten­ti­al coo­kie is about to be set. This lets you deci­de upon the pla­ce­ment of every sin­gle cookie.

MailChimp is an acti­ve par­ti­ci­pant in the EU‑U.S. Pri­va­cy Shield Frame­work, which regu­la­tes the cor­rect and secu­re trans­fer of per­so­nal data. You can find more infor­ma­ti­on on this at https://www.privacyshield.gov/participant?id=a2zt0000000TO6hAAG&tid=121400181. You can find more infor­ma­ti­on on MailChimp’s use of coo­kies at https://mailchimp.com/legal/cookies/, and you can learn more about data pro­tec­tion at MailChimp (Pri­va­cy) at https://mailchimp.com/legal/privacy/.

MailChimp Data Processing Addendum

We ente­red a con­tract with MailChimp on the Data Pro­ces­sing Adden­dum. This con­tract ser­ves as a pro­tec­tion of your per­so­nal data and ensu­res that MailChimp fol­lows the appli­ca­ble data pro­tec­tion regu­la­ti­ons and dis­c­lo­se your per­so­nal data to third parties.

You can find more infor­ma­ti­on on this con­tract at https://mailchimp.com/legal/data-processing-addendum/.

Embedded Social Media elements Privacy Policy

We have embedded ele­ments from social media ser­vices on our web­site, to dis­play pic­tures, vide­os and texts. By visi­ting pages that pre­sent such ele­ments, data is trans­fer­red from your brow­ser to the respec­ti­ve social media ser­vice, whe­re it is stored. We do not have access to this data.
The fol­lo­wing links lead to the respec­ti­ve social media ser­vices’ sites, whe­re you can find a decla­ra­ti­on on how they hand­le your data:

Facebook Data Policy

We use sel­ec­ted Face­book tools on our web­site. Face­book is a social media net­work of the com­pa­ny Face­book Ire­land Ltd., 4 Grand Canal Squa­re, Grand Canal Har­bour, Dub­lin 2 Ire­land. With the aid of this tool we can pro­vi­de the best pos­si­ble offers to you and anyo­ne inte­res­ted in our pro­ducts and ser­vices. In the fol­lo­wing we will give you an over­view on the dif­fe­rent Face­book tools, as well as on what data is sent to Face­book and how you can dele­te the­se data.

What are Facebook tools?

Along with many other pro­ducts, Face­book also offers so cal­led “Face­book Busi­ness Tools”. This is Facebook’s offi­ci­al name for the tools, but it is not very com­mon. The­r­e­fo­re, we deci­ded to mere­ly call them “Face­book tools”. They include the following:

  • Face­book-Pixel
  • social plug­ins (e.g. the “Like” or “Share“ button)
  • Face­book Login
  • Account Kit
  • APIs (appli­ca­ti­on pro­gramming interface)
  • SDKs (Soft­wart deve­lo­p­mept kits)
  • Platt­form-inte­gra­ti­ons
  • Plug­ins
  • Codes
  • Spe­ci­fi­ca­ti­ons
  • Docu­men­ta­ti­ons
  • Tech­no­lo­gies and Services

With the­se tools Face­book can extend its ser­vices and is able to recei­ve infor­ma­ti­on on user acti­vi­ties out­side of Facebook.

Why do we use Facebook tools on our website?

We only want to show our ser­vices and pro­ducts to peo­p­le who are genui­ne­ly inte­res­ted in them. With the help of adver­ti­se­ments (Face­book Ads) we can reach exact­ly the­se peo­p­le. Howe­ver, to be able to show sui­ta­ble adverts to users, Face­book requi­res addi­tio­nal infor­ma­ti­on on people’s needs and wis­hes. The­r­e­fo­re, infor­ma­ti­on on the user beha­viour (and cont­act details) on our web­site, are pro­vi­ded to Face­book. Con­se­quent­ly, Face­book can coll­ect bet­ter user data and is able to dis­play sui­ta­ble adverts for our pro­ducts or ser­vices. Thanks to the tools it is pos­si­ble to crea­te tar­ge­ted, cus­to­mi­sed ad cam­paigns of Facebook.

Face­book calls data about your beha­viour on our web­site “event data” and uses them for ana­ly­tics ser­vices. That way, Face­book can crea­te “cam­paign reports” about our ad cam­paigns’ effec­ti­ve­ness on our behalf. Moreo­ver, by ana­ly­ses we can get a bet­ter insight in how you use our ser­vices, our web­site or our pro­ducts. The­r­e­fo­re, some of the­se tools help us opti­mi­se your user expe­ri­ence on our web­site. With the social plug­ins for ins­tance, you can share our site’s con­tents direct­ly on Facebook.

What data is saved by the Facebook tools?

With the use of the Face­book tools, per­so­nal data (cus­to­mer data) may be sent to Face­book. Depen­ding on the tools used, cus­to­mer data such as name, address, tele­pho­ne num­ber and IP address may be transmitted.

Face­book uses this infor­ma­ti­on to match the data with the data it has on you (if you are a Face­book mem­ber). Howe­ver, befo­re the cus­to­mer data is trans­fer­red to Face­book, a so cal­led “Hash­ing” takes place. This means, that a data record of any size is trans­for­med into a string of cha­rac­ters, which also has the pur­po­se of encryp­ting data.

Moreo­ver, not only cont­act data, but also “event data“ is trans­fer­red. The­se data are the infor­ma­ti­on we recei­ve about you on our web­site. To give an exam­p­le, it allows us to see what sub­pages you visit or what pro­ducts you buy from us. Face­book does not dis­c­lo­se the obtai­ned infor­ma­ti­on to third par­ties (such as adver­ti­sers), unless the com­pa­ny has an expli­cit per­mis­si­on or is legal­ly obli­ged to do so. Also, “event data“ can be lin­ked to cont­act infor­ma­ti­on, which helps Face­book to offer impro­ved, cus­to­mi­sed adverts. Final­ly, after the pre­vious­ly men­tio­ned matching pro­cess, Face­book dele­tes the cont­act data.

To deli­ver opti­mi­sed adver­ti­se­ments, Face­book only uses event data, if they have been com­bi­ned with other data (that have been coll­ec­ted by Face­book in other ways). Face­book also uses event data for the pur­po­ses of secu­ri­ty, pro­tec­tion, deve­lo­p­ment and rese­arch. Many of the­se data are trans­mit­ted to Face­book via coo­kies. Coo­kies are litt­le text files, that are used for sto­ring data or infor­ma­ti­on in brow­sers. Depen­ding on the tools used, and on whe­ther you are a Face­book mem­ber, a dif­fe­rent num­ber of coo­kies are pla­ced in your brow­ser. In the descrip­ti­ons of the indi­vi­du­al Face­book tools we will go into more detail on Face­book coo­kies. You can also find gene­ral infor­ma­ti­on about the use of Face­book coo­kies at https://www.facebook.com/policies/cookies.

How long and where are the data saved?

Face­book fun­da­men­tal­ly stores data, until they are no lon­ger of use for their own ser­vices and pro­ducts. Face­book has ser­vers for sto­ring their data all around the world. Howe­ver, cus­to­mer data is cle­ared within 48 hours after they have been matched with their own user data.

How can I delete my data or prevent data retention?

In accordance with the Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR) you have the right of infor­ma­ti­on, rec­ti­fi­ca­ti­on, trans­fer and dele­ti­on of your data.

The coll­ec­ted data is only ful­ly dele­ted, when you dele­te your enti­re Face­book account. Dele­ting your Face­book account works as follows:

1) Click on set­tings in the top right side in Facebook.

2) Then, click “Your Face­book infor­ma­ti­on“ in the left column.

3) Now click on “Deac­ti­va­ti­on and deletion”.

4) Choo­se “Per­ma­nent­ly dele­te account“ and then click on “Con­ti­nue to account deletion“.

5) Enter your pass­word, click on “con­ti­nue“ and then on “Dele­te account“.

The reten­ti­on of data Face­book recei­ves via our site is done via coo­kies (e.g. with social plug­ins), among others. You can deac­ti­va­te, clear or mana­ge both all and indi­vi­du­al coo­kies in your brow­ser. How this can be done dif­fers depen­ding on the brow­ser you use. The fol­lo­wing ins­truc­tions show, how to mana­ge coo­kies in your browser:

Chro­me: Clear, enable and mana­ge coo­kies in Chrome 

Safa­ri: Mana­ge coo­kies and web­site data in Safari 

Fire­fox: Clear coo­kies and site data in Firefox 

Inter­net Explo­rer: Dele­te and mana­ge cookies 

Micro­soft Edge: Dele­te coo­kies in Micro­soft Edge 

If you gene­ral­ly do not want to allow any coo­kies at all, you can set up your brow­ser to noti­fy you when­ever a coo­kie is about to be set. This gives you the oppor­tu­ni­ty to deci­de upon the per­mis­si­on or dele­ti­on of every sin­gle cookie.

Face­book is an acti­ve par­ti­ci­pant in the EU‑U.S. Pri­va­cy Shield Frame­work, which regu­la­tes cor­rect and secu­re trans­fer of per­so­nal data. You can find more infor­ma­ti­on at https://www.privacyshield.gov/participant?id=a2zt0000000GnywAAC. We hope we could give you an under­stan­ding of the most important infor­ma­ti­on about the use of Face­book tools and data pro­ces­sing. If you want to find out more on how Face­book use your data, we recom­mend rea­ding the data poli­ci­es at https://www.facebook.com/about/privacy/update.

Facebook Social Plugins Privacy Policy

We instal­led so-cal­led social plug­ins from Face­book Inc. to our web­site. You can reco­g­ni­se the­se but­tons by the clas­sic Face­book logo, the “Like” but­ton (hand with rai­sed thumb) or by a “Face­book plug­in” label. A social plug­in is a small part of Face­book that is inte­gra­ted into our page. Each plug­in has its own func­tion. The most used func­tions are the well-known “Like” and “Share” buttons.

Face­book offers the fol­lo­wing social plugins:

  • “Save” but­ton
  • “Like” but­ton, Share, Send and Quote
  • Page plug­in
  • Comm­ents
  • Mes­sen­ger plugin
  • Embedded posts and video player
  • Group Plug­in

At https://developers.facebook.com/docs/plugins you will find more infor­ma­ti­on on how the indi­vi­du­al plug­ins are used. On the one hand, we use the social plug-ins to offer you a bet­ter user expe­ri­ence on our site, and on the other hand becau­se Face­book can opti­mi­se our adver­ti­se­ments with it.

If you have a Face­book account or have alre­a­dy visi­ted facebook.com, Face­book has alre­a­dy pla­ced at least one coo­kie in your brow­ser. In this case, your brow­ser sends infor­ma­ti­on to Face­book via this coo­kie as soon as you visit our web­site or inter­act with social plug­ins (e.g. the “Like” button).

The recei­ved infor­ma­ti­on will be dele­ted or anony­mi­sed within 90 days. Accor­ding to Face­book, this data includes your IP address, the web­sites you have visi­ted, the date, time and other infor­ma­ti­on rela­ting to your browser.

In order to pre­vent Face­book from coll­ec­ting much data and matching it with your Face­book data during your visit to our web­site, you must log out of Face­book while you visit our website.

If you are not log­ged in to Face­book or do not have a Face­book account, your brow­ser sends less infor­ma­ti­on to Face­book becau­se you have fewer Face­book coo­kies. Nevert­hel­ess, data such as your IP address or which web­site you are visi­ting can be trans­mit­ted to Face­book. We would like to expli­cit­ly point out that we do not know what exact data is coll­ec­ted. Howe­ver, based on our cur­rent know­ledge, we want to try informing you as best we can about data pro­ces­sing. You can also read about how Face­book uses the data in the company’s data poli­cy at https://www.facebook.com/about/privacy/update.

At least the fol­lo­wing coo­kies are set in your brow­ser when you visit a web­site with social plug­ins from Facebook:

Name: dpr
Value: no infor­ma­ti­on
Pur­po­se:This coo­kie is used to make the social plug­ins work on our web­site.
Expiry date: after end of session

Name: fr
Value: 0jieyh4121400181c2GnlufEJ9..Bde09j…1.0.Bde09j
Pur­po­se:The coo­kie is also neces­sa­ry for the plug­ins to func­tion pro­per­ly
Expiry date: after 3 months

Note: The­se coo­kies were set after our test and may be pla­ced even if you are not a Face­book member.

If you are regis­tered with Face­book, you can chan­ge your set­tings for adver­ti­se­ments yours­elf at https://www.facebook.com/ads/preferences/?entry_product=ad_settings_screen. If you are not a Face­book user, you can go to https://www.youronlinechoices.com/uk/your-ad-choices/ and mana­ge your usa­ge-based online adver­ti­sing. The­re you have the opti­on to deac­ti­va­te or acti­va­te providers.

If you want to learn more about Facebook’s data pro­tec­tion, we recom­mend the company’s own data poli­ci­es at https://www.facebook.com/policy.php.

Instagram Privacy Policy

We have inte­gra­ted func­tions of Insta­gram to our web­site. Insta­gram is a social media plat­form of the com­pa­ny Insta­gram LLC, 1601 Wil­low Rd, Men­lo Park CA 94025, USA. Sin­ce 2012, Insta­gram is a sub­si­dia­ry com­pa­ny of Face­book Inc. and is a part of Facebook’s pro­ducts. The inclu­si­on of Instagram’s con­tents on our web­site is cal­led embed­ding. With this, we can show you Insta­gram con­tents such as but­tons, pho­tos or vide­os direct­ly on our web­site. If you open web­sites of our online pre­sence, that have an inte­gra­ted Insta­gram func­tion, data gets trans­mit­ted to, as well as stored and pro­ces­sed by Insta­gram. Insta­gram uses the same sys­tems and tech­no­lo­gies as Face­book. The­r­e­fo­re, your data will be pro­ces­sed across all Face­book firms.

In the fol­lo­wing, we want to give you a more detail­ed insight on why Insta­gram coll­ects data, what data the­se are and how you can con­trol data pro­ces­sing. As Insta­gram belongs to Face­book Inc., we have, on the one hand recei­ved this infor­ma­ti­on from the Insta­gram gui­de­lines, and on the other hand from Facebook’s Data Policy.

What is Instagram?

Insta­gram is one of the most famous social media net­works world­wi­de. Insta­gram com­bi­nes the bene­fits of a blog with the bene­fits of audio-visu­al plat­forms such as You­Tube or Vimeo. To “Ins­ta“ (how the plat­form is casual­ly cal­led by many users) you can upload pho­tos and short vide­os, edit them with dif­fe­rent fil­ters and also share them to other social net­works. Also, if you do not want to be acti­ve on Insta­gram yours­elf, you can just fol­low other inte­res­t­ing users.

Why do we use Instagram on our website?

Insta­gram is a social media plat­form who­se suc­cess has sky­ro­cke­ted within recent years. Natu­ral­ly, we have also reac­ted to this boom. We want you to feel as com­for­ta­ble as pos­si­ble on our web­site. The­r­e­fo­re, we attach gre­at importance to diver­si­fied con­tents. With the embedded Insta­gram fea­tures we can enrich our con­tent with hel­pful, fun­ny or exci­ting Insta­gram con­tents. Sin­ce Insta­gram is a sub­si­dia­ry com­pa­ny of Face­book, the coll­ec­ted data can also ser­ve us for cus­to­mi­sed adver­ti­sing on Face­book. Hence, only per­sons who are genui­ne­ly inte­res­ted in our pro­ducts or ser­vices can see our ads.

Insta­gram also uses the coll­ec­ted data for track­ing and ana­ly­sis pur­po­ses. We recei­ve sum­ma­ri­sed sta­tis­tics and the­r­e­fo­re more insight to your wis­hes and inte­rests. It is important to men­ti­on that the­se reports do not iden­ti­fy you personally.

What data is saved by Instagram?

When­ever you land on one of our sites, which have Insta­gram func­tions (i.e. Insta­gram pho­tos or plug­ins) inte­gra­ted to them, your brow­ser auto­ma­ti­cal­ly con­nects with Instagram’s ser­vers. Ther­eby, data is sent to, as well as saved and pro­ces­sed by Insta­gram. This always hap­pens, whe­ther you have an Insta­gram account or not. Moreo­ver, it includes infor­ma­ti­on on our web­site, your com­pu­ter, your purcha­ses, the adver­ti­se­ments you see and on how you use our offer. The date and time of your inter­ac­tion is also stored. If you have an Insta­gram account or are log­ged in, Insta­gram saves signi­fi­cant­ly more data on you.

Face­book distin­gu­is­hes bet­ween cus­to­mer data and event data. We assu­me this is also the case for Insta­gram. Cus­to­mer data are for exam­p­le names, addres­ses, pho­ne num­bers and IP addres­ses. The­se data are only trans­mit­ted to Insta­gram, if they have been “hash­ed” first. Ther­eby, a set of data is trans­for­med into a string of cha­rac­ters, which encrypts any cont­act data. Moreo­ver, the afo­re­men­tio­ned “event data“ (data on your user beha­viour) is trans­mit­ted as well. It is also pos­si­ble, that cont­act data may get com­bi­ned with event data. The coll­ec­ted data data is matched with any data Insta­gram alre­a­dy has on you.

Fur­ther­mo­re, the gathe­red data are trans­fer­red to Face­book via litt­le text files (coo­kies) which usual­ly get set in your brow­ser. Depen­ding on the Insta­gram func­tion used, and whe­ther you have an Insta­gram account yours­elf, the amount of data that gets stored varies.

We assu­me data pro­ces­sing on Insta­gram works the same way as on Face­book. The­r­e­fo­re, if you have an account on Insta­gram or have visi­ted www.instagram.com, Insta­gram has set at least one coo­kie. If this is the case, your brow­ser uses the coo­kie to send infor­ma­ti­on to Insta­gram, as soon as you come across an Insta­gram func­tion. No later than 90 days (after matching) the data is dele­ted or anony­mi­sed. Even though we have stu­di­ed Instagram’s data pro­ces­sing in-depth, we can­not tell for sure what exact data Insta­gram coll­ects and retains.

In the fol­lo­wing we will show you a list of the least coo­kies pla­ced in your brow­ser when click on an Insta­gram func­tion (e.g. but­ton or an Ins­ta pic­tu­re). In our test we assu­me you do not have an Insta­gram account, sin­ce if you would be log­ged in to your Insta­gram account, your brow­ser would place signi­fi­cant­ly more coo­kies.
The fol­lo­wing coo­kies were used in our test:

Name: csrf­to­ken
Value: “”
Pur­po­se: This coo­kie is most likely set for secu­ri­ty reasons to pre­vent fal­si­fi­ca­ti­ons of requests. We could not find out more infor­ma­ti­on on it.
Expiry date: after one year

Name: mid
Value: “”
Pur­po­se: Insta­gram places this coo­kie to opti­mi­se its own offers and ser­vices in- and out­side of Insta­gram. The coo­kie allo­ca­tes a uni­que user ID.
Expiry date: after end of session

Name: fbsr_121400181124024
Value: no infor­ma­ti­on
Pur­po­se: This coo­kie stores the log­in request of Insta­gram app users.

 

Expiry date: after end of session

Name: rur
Value: ATN
Pur­po­se: This is an Insta­gram coo­kie which gua­ran­tees func­tion­a­li­ty on Insta­gram.
Expiry date: after end of session

Name: url­gen
Value: “{”194.96.75.33”: 1901}:1iEtYv:Y833k2_UjKvXgYe121400181”
Pur­po­se: This coo­kie ser­ves Instagram’s mar­ke­ting pur­po­ses.
Expiry date: after end of session

Note: We do not cla­im this list to be exhaus­ti­ve. The coo­kies that are pla­ced in each indi­vi­du­al case, depend on the func­tions embedded as well as on your use of Instagram.

How long and where are these data stored?

Insta­gram shares the infor­ma­ti­on obtai­ned within the Face­book busi­nesses with exter­nal part­ners and per­sons you are glo­bal­ly con­nec­ted with. Data pro­ces­sing is done accor­ding to Facebook’s inter­nal data poli­cy. Your data is dis­tri­bu­ted to Facebook’s ser­vers across the world, par­ti­al­ly for secu­ri­ty reasons. Most of the­se ser­vers are in the USA.

How can I delete my data or prevent data retention?

Thanks to the Gene­ral Data Pro­tec­tion Regu­la­ti­on (GDPR), you have the right of infor­ma­ti­on, rec­ti­fi­ca­ti­on, trans­fer and dele­ti­on of your data. Fur­ther­mo­re, you can mana­ge your data in Instagram’s set­tings. If you want to dele­te your data on Insta­gram com­ple­te­ly, you will have to dele­te your Insta­gram account permanently.

And this is how an Insta­gram account can be deleted:

First, open the Insta­gram app. Then, navi­ga­te to your pro­fi­le page, sel­ect the three bars in the top right, choo­se “Set­tings” and then click “Help”. Now, you will be redi­rec­ted to the company’s web­site, whe­re you must click on “Mana­ging Your Account” and then “Dele­te Your Account”.

When you dele­te your account com­ple­te­ly, Insta­gram dele­tes posts such as your pho­tos and sta­tus updates. Any infor­ma­ti­on other peo­p­le shared about you are not a part of your account and do the­r­e­fo­re not get deleted.

As men­tio­ned befo­re, Insta­gram pri­ma­ri­ly stores your data via coo­kies. You can mana­ge, deac­ti­va­te or dele­te the­se coo­kies in your brow­ser. Depen­ding on your brow­ser, mana­ging them varies a bit. We will show you the ins­truc­tions of the most rele­vant brow­sers here.

Chro­me: Clear, enable and mana­ge coo­kies in Chrome 

Safa­ri: Mana­ge coo­kies and web­site data in Safari 

Fire­fox: Clear coo­kies and site data in Firefox 

Inter­net Explo­rer: Dele­te and mana­ge cookies 

Micro­soft Edge: Dele­te coo­kies in Micro­soft Edge 

Gene­ral­ly, you can set your brow­ser to noti­fy you when­ever a coo­kie is about to be set. Then you can indi­vi­du­al­ly deci­de upon the per­mis­si­on of every cookie.

Insta­gram is a sub­si­dia­ry com­pa­ny of Face­book Inc. and Face­book is an acti­ve par­ti­ci­pant in the EU‑U.S. Pri­va­cy Shield Frame­work. This frame­work regu­la­tes cor­rect trans­fer bet­ween the USA and the Euro­pean Uni­on. At https://www.privacyshield.gov/participant?id=a2zt0000000GnywAAC you can find out more about this. We gave our best to make you fami­li­ar with the most important infor­ma­ti­on on data pro­ces­sing by Insta­gram. At https://help.instagram.com/519522125107875 you can find out more on Instagram’s data policies.

Twitter Privacy Policy

We have incor­po­ra­ted Twit­ter func­tions on our web­site. The­se are, for exam­p­le, embedded tweets, time­lines, but­tons or hash­tags. Twit­ter is a short mes­sa­ge ser­vice and social media plat­form from the firm Twit­ter Inc., One Cum­ber­land Place, Feni­an Street, Dub­lin 2 D02 AX07, Ireland.

To our know­ledge, in the Euro­pean Eco­no­mic Area and Switz­er­land, a mere inte­gra­ti­on of the Twit­ter func­tion does not trans­fer any per­so­nal data or data about your web acti­vi­ties to Twit­ter. Only when you inter­act with the Twit­ter func­tions, such as by cli­cking a but­ton, data could be sent to Twit­ter and get saved as well as pro­ces­sed the­re. We have no influence on this pro­ces­sing of data and do not bare any respon­si­bi­li­ty for it. Within this pri­va­cy state­ment, we want to give you an over­view of what data Twit­ter stores, what Twit­ter does with this data and how you can lar­ge­ly pro­tect yours­elf from data transmission.

What is Twitter?

For some, Twit­ter is a news ser­vice, for others, a social media plat­form, and for others still it is a micro­blog­ging ser­vice. All the­se terms are jus­ti­fied and mean pret­ty much the same.

Both indi­vi­du­als as well as com­pa­nies use Twit­ter for com­mu­ni­ca­ting with inte­res­ted peo­p­le via short mes­sa­ges. Twit­ter only allows 280 cha­rac­ters per mes­sa­ge. The­se mes­sa­ges are cal­led “tweets”. In con­trast to Face­book, for exam­p­le, the ser­vice does not focus on the expan­si­on of a net­work of “fri­ends”, but stri­ves to be regard­ed as an open, world­wi­de news plat­form. On Twit­ter you can also have an anony­mous account and tweets can be dele­ted by both, eit­her the com­pa­ny or the users themselves.

Why do we use Twitter on our website?

Like many other web­sites and com­pa­nies, we try to use dif­fe­rent chan­nels for offe­ring our ser­vices and com­mu­ni­ca­ting with our cus­to­mers. Twit­ter is a tru­ly useful “small” news ser­vice, which is why it has grown dear to us. We regu­lar­ly tweet or ret­weet exci­ting, fun­ny or inte­res­t­ing con­tent. We under­stand that you do not have the time to fol­low every chan­nel after chan­nel, as you sure­ly have enough other things to do. That is why we also have inte­gra­ted Twit­ter func­tions to our web­site. That way, you can expe­ri­ence our Twit­ter acti­vi­ties “on site” or come to our Twit­ter page via a direct link. With the inte­gra­ti­on, we want to streng­then the ser­vice and user-fri­end­li­ne­ss on our website.

What data is stored by Twitter?

You will find inte­gra­ted Twit­ter func­tions on some of our sub­pages. If you inter­act with Twit­ter con­tent, such as by cli­cking a but­ton, Twit­ter may coll­ect and save data. This can hap­pen even if you don’t have a Twit­ter account yours­elf. Twit­ter calls this data “log data”. It includes demo­gra­phic data, brow­ser coo­kie IDs, your smartphone’s ID, hash­ed email addres­ses, and infor­ma­ti­on on which pages you have visi­ted on Twit­ter and what actions you have taken the­re. Of cour­se, Twit­ter stores more data if you have a Twit­ter account and are log­ged in. This reten­ti­on is usual­ly done via coo­kies. Coo­kies are small text files that are usual­ly set in your brow­ser and trans­mit various infor­ma­ti­on to Twitter.

We will now show you which coo­kies are pla­ced if you are not log­ged in to Twit­ter but visit a web­site with built-in Twit­ter func­tions. Plea­se con­sider this list as an exam­p­le. We do not cla­im for this list to be exten­si­ve, sin­ce the array of coo­kies always chan­ges and depends on your indi­vi­du­al actions with Twit­ter con­tent.
The fol­lo­wing coo­kies have been used in our test:

Name: personalization_id
Value: “v1_cSJIsogU51SeE121400181”
Pur­po­se: This coo­kie stores infor­ma­ti­on on how you use the web­site and what ad may have led you to Twitter.

Expiry date: after 2 years

Name: lang
Value: en
Pur­po­se: This coo­kie stores your deafault or pre­fer­red lan­guage.
Expiry date: after end of session

Name: guest_id
Value: 121400181v1%3A157132626
Pur­po­se: This coo­kie is set to iden­ti­fy you as a guest.
Expiry date: after 2 years

Name: fm
Value: 0
Pur­po­se: Unfort­u­na­te­ly, we could not find out the pur­po­se of this coo­kie.
Expiry date: after end of session

Name: external_referer
Value: 1214001812beTA0sf5lkMrlGt
Pur­po­se: This coo­kie coll­ects anony­mous data, such as how often you visit Twit­ter and how long you visit Twit­ter.
Expiry date: after 6 days

Name: eu_cn
Value: 1
Pur­po­se: This coo­kie stores user acti­vi­ty and is used for Twitter’s various adver­ti­sing pur­po­ses.
Expiry date: after one year

Name: ct0
Value: c1179f07163a365d2ed7aad84c99d966
Pur­po­se: Unfort­u­na­te­ly we could not find any infor­ma­ti­on on this coo­kie.
Expiry date: after 6 hours

Name: _twitter_sess
Value: 53D%253D–dd0248121400181-
Pur­po­se: With this coo­kie you can use func­tions within Twitter’s web­site.
Expiry date: after end of session

Note: Twit­ter also works with third par­ties. The­r­e­fo­re, we have reco­gni­zed the three Goog­le Ana­ly­tics coo­kies _ga, _gat, _gid in our test.

On the one hand, Twit­ter uses the coll­ec­ted data for gai­ning bet­ter under­stand on user beha­viour, and thus to impro­ve their own ser­vices and adver­ti­sing offers. On the other hand, the data are also used for inter­nal secu­ri­ty measures.

How long and where are the data stored?

When Twit­ter coll­ects data from other web­sites, after a maxi­mum of 30 days, they will be dele­ted, sum­ma­ri­zed or other­wi­se con­cea­led. Twitter’s ser­vers are in various ser­ver cen­tres in the United Sta­tes. Accor­din­gly, it can be assu­med that the gathe­red data will be coll­ec­ted and stored in Ame­ri­ca. In our rese­arch we could not cle­ar­ly deter­mi­ne whe­ther Twit­ter also owns ser­vers in Euro­pe. Gene­ral­ly, Twit­ter may keep coll­ec­ted data stored until eit­her the data are no lon­ger useful to the com­pa­ny, until you dele­te the data or until a poten­ti­al legal dele­ti­on peri­od has been reached.

How can I delete my data or prevent data retention?

In their Pri­va­cy Poli­cy, Twit­ter repea­ted­ly empha­si­ze that they do not save data from exter­nal web­site visits, pro­vi­ded you or your brow­ser are in the Euro­pean Eco­no­mic Area or Switz­er­land. Howe­ver, if you inter­act direct­ly with Twit­ter, the com­pa­ny will of cour­se store your data.

If you have a Twit­ter account, you can mana­ge your data by cli­cking on “More” under the “Pro­fi­le” but­ton. Then click on “Set­tings and pri­va­cy”. Here you can mana­ge data pro­ces­sing individually.

If you do not have a Twit­ter account, you can go to twitter.com and click “Set­tings”. At “Per­so­na­liza­ti­on and data” you can mana­ge data that is coll­ec­ted on you.

As men­tio­ned abo­ve, most data are stored via coo­kies, which you can mana­ge, deac­ti­va­te or dele­te in your brow­ser. Plea­se note that when chan­ging coo­kie set­tings in your brow­ser, the edits will only affect that very brow­ser. This means that if you use ano­ther brow­ser in the future, you will have to mana­ge your coo­kie set­tings the­re again. In the fol­lo­wing you will find ins­truc­tions for mana­ging coo­kies in the most popu­lar browsers.

Chro­me: Clear, enable and mana­ge coo­kies in Chrome 

Safa­ri: Mana­ge coo­kies and web­site data in Safari 

Fire­fox: Clear coo­kies and site data in Firefox 

Inter­net Explo­rer: Dele­te and mana­ge cookies 

Micro­soft Edge: Dele­te coo­kies in Micro­soft Edge 

You can also set your brow­ser to noti­fy you about each indi­vi­du­al coo­kie. This lets you deci­de indi­vi­du­al­ly whe­ther you want to allow or deny a cookie.

Twit­ter also uses the data for per­so­na­li­sed adver­ti­sing in-and out­side of Twit­ter. You can switch off per­so­na­li­sed adver­ti­sing in the set­tings under “Per­so­na­liza­ti­on and data”. If you use Twit­ter on a brow­ser, you can deac­ti­va­te per­so­na­li­sed adver­ti­sing at http://optout.aboutads.info/?c=2&lang=EN.

Twit­ter is an acti­ve par­ti­ci­pant in the EU‑U.S. Pri­va­cy Shield Frame­work. This frame­work ensu­res cor­rect data trans­mis­si­on bet­ween the USA and the Euro­pean Uni­on. You can learn more about it at https://www.privacyshield.gov/participant?id=a2zt0000000TORzAAO.

We hope we could give you a basic over­view of Twitter’s data pro­ces­sing. We do not recei­ve any data from Twit­ter and are not respon­si­ble for what Twit­ter does with your data. If you have any fur­ther ques­ti­ons on this topic, we recom­mend rea­ding Twitter’s pri­va­cy state­ment at https://twitter.com/en/privacy.

LinkedIn Privacy Policy

On our web­site we use social plug­ins from the social media net­work Lin­ke­dIn, of the Lin­ke­dIn Cor­po­ra­ti­on, 2029 Stier­lin Court, Moun­tain View, CA 94043, USA. Social plug­ins can be feeds, con­tent sha­ring or a link to our Lin­ke­dIn page. Social plug­ins are cle­ar­ly mark­ed with the well-known Lin­ke­dIn logo and for exam­p­le allow sha­ring inte­res­t­ing con­tent direct­ly via our web­site. Moreo­ver, Lin­ke­dIn Ire­land Unli­mi­t­ed Com­pa­ny Wil­ton Place in Dub­lin is respon­si­ble for data pro­ces­sing in the Euro­pean Eco­no­mic Area and Switzerland.

By embed­ding the­se plug­ins, data can be sent to, as well as stored and pro­ces­sed by Lin­ke­dIn. In this pri­va­cy poli­cy we want to inform you what data this is, how the net­work uses this data and how you can mana­ge or pre­vent data retention.

What is LinkedIn?

Lin­ke­dIn is the lar­gest social net­work for busi­ness cont­acts. In con­trast to e.g. Face­book, Lin­ke­dIn focu­ses exclu­si­ve­ly on estab­li­shing busi­ness con­nec­tions. The­r­e­fo­re, com­pa­nies can pre­sent ser­vices and pro­ducts on the plat­form and estab­lish busi­ness rela­ti­onships. Many peo­p­le also use Lin­ke­dIn to find a job or to find sui­ta­ble employees for their own com­pa­ny. In Ger­ma­ny alo­ne, the net­work has over 11 mil­li­on mem­bers. In Aus­tria the­re are about 1.3 million.

Why do we use LinkedIn on our website?

We know how busy you are. You just can­not keep up with fol­lo­wing every sin­gle social media chan­nel. Even if it would real­ly be worth it, as it is with our chan­nels, sin­ce we keep pos­ting inte­res­t­ing news and artic­les worth spre­a­ding. The­r­e­fo­re, on our web­site we have crea­ted the oppor­tu­ni­ty to share inte­res­t­ing con­tent direct­ly on Lin­ke­dIn, or to refer direct­ly to our Lin­ke­dIn page. We con­sider built-in social plug­ins as an exten­ded ser­vice on our web­site. The data Lin­ke­dIn coll­ects also help us to dis­play poten­ti­al adver­ti­sing mea­su­res only to peo­p­le who are inte­res­ted in our offer.

What data are stored by LinkedIn?

Lin­ke­dIn stores no per­so­nal data due to the mere inte­gra­ti­on of social plug­ins. Lin­ke­dIn calls the data gene­ra­ted by plug­ins pas­si­ve impres­si­ons. Howe­ver, if you click on a social plug­in to e.g. share our con­tent, the plat­form stores per­so­nal data as so-cal­led “acti­ve impres­si­ons”. This hap­pens regard­less of whe­ther you have a Lin­ke­dIn account or not. If you are log­ged in, the coll­ec­ted data will be assi­gned to your account.

When you inter­act with our plug­ins, your brow­ser estab­lishes a direct con­nec­tion to LinkedIn’s ser­vers. Through that, the com­pa­ny logs various usa­ge data. The­se may include your IP address, log­in data, device infor­ma­ti­on or infor­ma­ti­on about your inter­net or cel­lu­lar pro­vi­der. If you use Lin­ke­dIn ser­vices via your smart­phone, your loca­ti­on may also be iden­ti­fied (after you have given per­mis­si­on). Moreo­ver, Lin­ke­dIn can share the­se data with third-par­ty adver­ti­sers in “hash­ed” form. Hash­ing means that a data set is trans­for­med into a cha­rac­ter string. This allows data to be encrypt­ed, which pre­vents per­sons from get­ting identified.

Most data on of your user beha­viour is stored in coo­kies. The­se are small text files that usual­ly get pla­ced in your brow­ser. Fur­ther­mo­re, Lin­ke­dIn can also use web bea­cons, pixel tags, dis­play tags and other device recognitions.

Various tests also show which coo­kies are set when a user inter­acts with a social plug-in. We do not cla­im for the infor­ma­ti­on we found to be exhaus­ti­ve, as it only ser­ves as an exam­p­le. The fol­lo­wing coo­kies were set wit­hout being log­ged in to LinkedIn:

Name: bcoo­kie
Value: =2&34aab2aa-2ae1-4d2a-8baf-c2e2d7235c16121400181-
Pur­po­se: This coo­kie is a so-cal­led “brow­ser ID coo­kie” and stores your iden­ti­fi­ca­ti­on num­ber (ID).
Expiry date: after 2 years

Name: lang
Value: v=2&lang=en-gb
Pur­po­se:This coo­kie saves your default or pre­fer­red lan­guage.
Expiry date: after end of session

Name: lidc
Value: 1818367:t=1571904767:s=AQF6KNnJ0G121400181…
Pur­po­se:This coo­kie is used for rou­ting. Rou­ting records how you found your way to Lin­ke­dIn and how you navi­ga­te through the web­site.
Expiry date: after 24 hours

Name: rtc
Value: kt0lrv3NF3x3t6xvDgGrZGDKkX
Pur­po­se:No fur­ther infor­ma­ti­on could be found about this coo­kie.
Expiry date: after 2 minutes

Name: JSESSIONID
Value: ajax:1214001812900777718326218137
Pur­po­se: This is a ses­si­on coo­kie that Lin­ke­dIn uses to main­tain anony­mous user ses­si­ons through the ser­ver.
Expiry date: after end of session

Name: bscoo­kie
Value: “v=1&201910230812…
Pur­po­se: This coo­kie is a secu­ri­ty coo­kie. Lin­ke­dIn descri­bes it as a secu­re brow­ser ID coo­kie.
Expiry date: after 2 years

Name: fid
Value: AQHj7Ii23ZBcqAAAA…
Pur­po­se: We could not find any fur­ther infor­ma­ti­on about this coo­kie.
Expiry date: after 7 days

Note: Lin­ke­dIn also works with third par­ties. That is why we iden­ti­fied the Goog­le Ana­ly­tics coo­kies _ga and _gat in our test.

How long and where are the data stored?

In gene­ral, Lin­ke­dIn reta­ins your per­so­nal data for as long as the com­pa­ny con­siders it neces­sa­ry for pro­vi­ding its ser­vices. Howe­ver, Lin­ke­dIn dele­tes your per­so­nal data when you dele­te your account. In some excep­tio­nal cases, Lin­ke­dIn keeps some sum­ma­ri­sed and anony­mi­sed data, even account dele­ti­ons. As soon as you dele­te your account, it may take up to a day until other peo­p­le can no lon­ger see your data. Lin­ke­dIn gene­ral­ly dele­tes the data within 30 days. Howe­ver, Lin­ke­dIn reta­ins data if it is neces­sa­ry for legal reasons. Also, data that can no lon­ger be assi­gned to any per­son remains stored even after the account is clo­sed. The data are stored on various ser­vers in Ame­ri­ca and pre­su­ma­b­ly also in Europe.

How can I delete my data or prevent data retention?

You have the right to access and dele­te your per­so­nal data at any time. In your Lin­ke­dIn account you can mana­ge, chan­ge and dele­te your data. Moreo­ver, you can request a copy of your per­so­nal data from LinkedIn.

How to access account data in your Lin­ke­dIn profile:

In Lin­ke­dIn, click on your pro­fi­le icon and sel­ect the “Set­tings & Pri­va­cy” sec­tion. Now click on “Pri­va­cy” and then on the sec­tion “How Lin­ke­dIn uses your data on”. Then, click “Chan­ge” in the row with “Mana­ge your data and acti­vi­ty”. The­re you can instant­ly view sel­ec­ted data on your web acti­vi­ty and your account history.

In your brow­ser you also have the opti­on of pre­ven­ting data pro­ces­sing by Lin­ke­dIn. As men­tio­ned abo­ve, Lin­ke­dIn stores most data via coo­kies that are pla­ced in your brow­ser. You can mana­ge, deac­ti­va­te or dele­te the­se coo­kies. Depen­ding on which brow­ser you have, the­se set­tings work a litt­le dif­fe­rent. You can find the ins­truc­tions for the most com­mon brow­sers here:

Chro­me: Clear, enable and mana­ge coo­kies in Chrome 

Safa­ri: Mana­ge coo­kies and web­site data in Safari 

Fire­fox: Clear coo­kies and site data in Firefox 

Inter­net Explo­rer: Dele­te and mana­ge cookies 

Micro­soft Edge: Dele­te coo­kies in Micro­soft Edge 

You can gene­ral­ly set your brow­ser to always noti­fy you when a coo­kie is about to be set. Then you can always deci­de indi­vi­du­al­ly whe­ther you want to allow the coo­kie or not.

Lin­ke­dIn is an acti­ve par­ti­ci­pant in the EU‑U.S. Pri­va­cy Shield Frame­works. This frame­work ensu­res cor­rect data trans­mis­si­on bet­ween the USA and the Euro­pean Uni­on. You can find out more about it at https://www.privacyshield.gov/participant?id=a2zt0000000L0UZAA0. We gave our best to pro­vi­de you the most essen­ti­al infor­ma­ti­on about LinkedIn’s data pro­ces­sing. At https://www.linkedin.com/legal/privacy-policy you can find out more about data pro­ces­sing of the social media net­work LinkedIn.

Pinterest Privacy Policy

On our web­site we use but­tons and wid­gets of the social media net­work Pin­te­rest, by the com­pa­ny Pin­te­rest Inc., 808 Brannan Street, San Fran­cis­co, CA 94103, USA.

By ope­ning pages that use the­se func­tions, data (IP address, brow­ser data, date and time, coo­kies) are trans­mit­ted to, and stored and eva­lua­ted by Pinterest.

The pri­va­cy gui­de­lines on what infor­ma­ti­on Pin­te­rest coll­ects and how they use it, can be found at https://policy.pinterest.com/en-gb/privacy-policy.

 

Source: Crea­ted with the Daten­schutz Gene­ra­tor by AdSimp­le® Link­buil­ding in coope­ra­ti­on with bauguide.at