Pri­va­cy policy

The fol­low­ing data pro­tec­tion dec­la­ra­tion applies to the use of our online offer [fld-technologies.com/](hereinafter “web­site”). We attach great impor­tance to data pro­tec­tion. The col­lec­tion and pro­cess­ing of your per­son­al data is car­ried out in com­pli­ance with the applic­a­ble data pro­tec­tion reg­u­la­tions, in par­tic­u­lar the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (DSG­VO). We col­lect and process your per­son­al data in order to offer you the above-men­tioned por­tal. This state­ment describes how and for what pur­pose your data is col­lect­ed and used and what choic­es you have in con­nec­tion with per­son­al data. By using this web­site, you con­sent to the col­lec­tion, use, and trans­fer of your data in accor­dance with this pri­va­cy policy.

Respon­si­ble

The per­son respon­si­ble for the col­lec­tion, pro­cess­ing, and use of your per­son­al data with­in the mean­ing of Art. 4 No. 7 DSG­VO is

Dr. Marek Fulde
Man­ag­ing Director/​CEO
FLD Tech­nolo­gies GmbH
Tam­bour­weg 5 | 63071 Offen­bach am Main
T: +49 1520 341 84 64 | F: +49 69 98 53 53 21 | E: marek.fulde@hyregio.com

USt.ID.Nr DE311474218

If you wish to object to the col­lec­tion, pro­cess­ing, or use of your data by us in accor­dance with these data pro­tec­tion pro­vi­sions as a whole or for indi­vid­ual mea­sures, you can address your objec­tion to the per­son respon­si­ble. You can save and print this pri­va­cy pol­i­cy at any time.

Data pro­tec­tion

We have writ­ten this pri­va­cy state­ment (ver­sion 03÷19÷2021−111682284) to explain to you, in accor­dance with the require­ments of the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (EU) 2016/679, what infor­ma­tion we col­lect, how we use data, and what deci­sion-mak­ing options you have as a vis­i­tor to this website.

Pri­va­cy state­ments usu­al­ly sound very tech­ni­cal. This ver­sion, on the oth­er hand, is intend­ed to describe the most impor­tant things to you as sim­ply and clear­ly as pos­si­ble. As far as pos­si­ble, tech­ni­cal terms are explained in a read­er-friend­ly way. We also want to con­vey that we only col­lect and use infor­ma­tion with this web­site if there is a cor­re­spond­ing legal basis. This is cer­tain­ly not pos­si­ble by pro­vid­ing the most con­cise, tech­ni­cal expla­na­tions pos­si­ble, as is often stan­dard prac­tice on the Inter­net when it comes to data pro­tec­tion. I hope you find the fol­low­ing expla­na­tions inter­est­ing and infor­ma­tive, and per­haps there are one or two pieces of infor­ma­tion that you did not yet know.
If you still have ques­tions, we would like to ask you to fol­low the exist­ing links and look at fur­ther infor­ma­tion on third-par­ty sites, or sim­ply write us an e‑mail. You can find our con­tact details in the imprint.

HOST­ING

Pri­va­cy 1&1 Ionos

The logs for the cur­rent day are updat­ed almost in real-time. Due to the large amount of data, log data is kept ready for a max­i­mum of 9 weeks.

PAGE CALL VIA A PROXY SERVER

The proxy serv­er func­tions more or less as a proxy that requests the pages and for­wards them to the user. Con­se­quent­ly, the log file con­tains the IP address of the proxy and not the address of the work­sta­tion that orig­i­nal­ly request­ed the page.

Some prox­ies send a head­er field called X‑For­ward­ed-For, in which the orig­i­nal IP is entered so that it is pos­si­ble to trace where a request orig­i­nal­ly came from when it is accessed via prox­ies. This X‑For­ward­ed-For head­er is append­ed to the end of each entry in the log file at 1&1 web hosting.

When using the 1&1 SSL proxy as well as proxy calls that trans­mit the cor­re­spond­ing infor­ma­tion, the IP address of the actu­al request­ing com­put­er is in the last col­umn of each log­line. This improves the pos­si­bil­i­ty of cre­at­ing mean­ing­ful vis­i­tor statistics.

Please note:

Due to data pro­tec­tion guide­lines on per­son­al data, the IP address­es of the callers in the log files are anonymized with an ‘x’ after 7 days. For more info, see 1und1’s data pro­tec­tion agree­ment at https://hosting.1und1.de/terms-gtc/terms-privacy/.

Auto­mat­ic data storage

Nowa­days, when you vis­it web­sites, cer­tain infor­ma­tion is auto­mat­i­cal­ly cre­at­ed and stored, includ­ing on this web­site. This col­lect­ed data should be col­lect­ed as spar­ing­ly as pos­si­ble and only with jus­ti­fi­ca­tion. By the way, by web­site, we mean the entire­ty of all web pages on your domain, i.e. every­thing from the home page (home­page) to the very last sub­page (like this one). By domain we mean, for exam­ple, example.de or example.com.

Even while you are vis­it­ing our web­site right now, our web serv­er — that is the com­put­er on which this web­site is stored — usu­al­ly auto­mat­i­cal­ly stores data for rea­sons of oper­a­tional secu­ri­ty, to com­pile access sta­tis­tics, etc., such as

  • the com­plete Inter­net address (URL) of the accessed web­site (e.g. https://www.beispielwebsite.de/beispielunterseite.html/)
    brows­er and brows­er ver­sion (e.g. Chrome 87)
    the oper­at­ing sys­tem used (e.g. Win­dows 10)
    the address (URL) of the pre­vi­ous­ly vis­it­ed page (refer­rer URL) (e.g. https://www.beispielquellsite.de/vondabinichgekommen.html/)
    the host­name and IP address of the device from which access is made (e.g. COM­PUT­ER­NAME and 194.23.43.121)
    date and time
    in files called web serv­er log files.

For illus­tra­tion:

As a rule, these files are stored for two weeks and then auto­mat­i­cal­ly delet­ed. We do not share this data, but we can­not exclude the pos­si­bil­i­ty that this data may be viewed by author­i­ties in the event of ille­gal behavior.

In short, your vis­it is logged by our provider (the com­pa­ny that runs our web­site on spe­cial com­put­ers (servers)), but we do not share your data!

Cook­ies

Our web­site uses HTTP cook­ies to store user-spe­cif­ic data.
Below, we explain what cook­ies are and why they are used so that you can bet­ter under­stand the fol­low­ing pri­va­cy policy.

What are the types of cookies?

We can dis­tin­guish 4 types of cookies:

Indis­pens­able cook­ies.
These cook­ies are nec­es­sary to ensure the basic func­tions of the web­site. For exam­ple, these cook­ies are need­ed when a user adds a prod­uct to the shop­ping cart, then con­tin­ues brows­ing on oth­er pages, and lat­er goes to the check­out. Through these cook­ies, the shop­ping cart is not delet­ed even if the user clos­es his brows­er window.

Pur­pose cook­ies
These cook­ies col­lect infor­ma­tion about user behav­ior and whether the user receives any error mes­sages. In addi­tion, these cook­ies are also used to mea­sure the load­ing time and behav­ior of the web­site with dif­fer­ent browsers.

Tar­get-ori­ent­ed cook­ies
These cook­ies pro­vide a bet­ter user expe­ri­ence. For exam­ple, entered loca­tions, font sizes, or form data are stored.

Adver­tis­ing cook­ies
These cook­ies are also called tar­get­ing cook­ies. They are used to deliv­er cus­tomized adver­tis­ing to the user. This can be very con­ve­nient, but also very annoying.

Usu­al­ly, when you vis­it a web­site for the first time, you are asked which of these cook­ie types you want to allow. And of course, this deci­sion is also stored in a cookie.

How can I delete cookies?

How and whether you want to use cook­ies, you decide. Regard­less of which ser­vice or web­site the cook­ies come from, you always have the option to delete, dis­able or only par­tial­ly allow cook­ies. For exam­ple, you can block third-par­ty cook­ies but allow all oth­er cookies.

If you want to deter­mine which cook­ies have been stored in your brows­er, if you want to change or delete cook­ie set­tings, you can find this in your brows­er settings:

Chrome: Delete, enable and man­age cook­ies in Chrome

Safari: Man­ag­ing cook­ies and web­site data with Safari

Fire­fox: Delete cook­ies to remove data that web­sites have placed on your computer

Inter­net Explor­er: Delete and man­age cookies

Microsoft Edge: Delete and man­age cookies

If you do not want to have cook­ies in prin­ci­ple, you can set up your brows­er so that it always informs you when a cook­ie is to be set. In this way, you can decide for each indi­vid­ual cook­ie whether you allow the cook­ie or not. The pro­ce­dure varies depend­ing on the brows­er. It is best to search for the instruc­tions in Google using the search term “delete cook­ies Chrome” or “dis­able cook­ies Chrome” in the case of a Chrome browser.

What about my privacy?

The so-called “Cook­ie Guide­lines” have been in place since 2009. These state that the stor­age of cook­ies requires your con­sent. With­in the EU coun­tries, how­ev­er, there are still very dif­fer­ent reac­tions to these direc­tives. In Aus­tria, how­ev­er, this direc­tive was imple­ment­ed in Sec­tion 96 (3) of the Telecom­mu­ni­ca­tions Act (TKG). In Ger­many, the Cook­ie Direc­tives were not imple­ment­ed as nation­al law. Instead, the imple­men­ta­tion of this direc­tive took place large­ly in § 15 para.3 of the Tele­me­dia Act (TMG).

If you would like to know more about cook­ies and are not afraid of tech­ni­cal doc­u­men­ta­tion, we rec­om­mend https://tools.ietf.org/html/rfc6265, the Request for Com­ments der Inter­net Engi­neer­ing Task Force (IETF) named “HTTP State Man­age­ment Mechanism”.

Stor­age of per­son­al data

Per­son­al data that you trans­mit to us elec­tron­i­cal­ly on this web­site, such as name, e‑mail address, address, or oth­er per­son­al infor­ma­tion in the con­text of sub­mit­ting a form or com­ments on the blog, will be used by us togeth­er with the time and IP address only for the pur­pose stat­ed in each case, kept secure and not dis­closed to third parties.

We thus use your per­son­al data only for com­mu­ni­ca­tion with those vis­i­tors who express­ly request con­tact and for the pro­cess­ing of the ser­vices and prod­ucts offered on this web­site. We do not dis­close your per­son­al data with­out your con­sent, but we can­not exclude the pos­si­bil­i­ty that this data may be accessed in the event of unlaw­ful conduct.

If you send us per­son­al data by e‑mail — thus away from this web­site — we can­not guar­an­tee secure trans­mis­sion and pro­tec­tion of your data. We rec­om­mend that you nev­er send con­fi­den­tial data by e‑mail with­out encryption.

Rights under the Gen­er­al Data Pro­tec­tion Regulation

Accord­ing to the pro­vi­sions of the GDPR, you are gen­er­al­ly enti­tled to the fol­low­ing rights:

  • Right to rec­ti­fi­ca­tion (Arti­cle 16 GDPR)
  • Right to era­sure (“right to be for­got­ten”) (Arti­cle 17 GDPR)
  • Right to restric­tion of pro­cess­ing (Arti­cle 18 GDPR)
  • Right to noti­fi­ca­tion — oblig­a­tion to noti­fy in con­nec­tion with the rec­ti­fi­ca­tion or era­sure of per­son­al data or the restric­tion of pro­cess­ing (Arti­cle 19 GDPR)
  • Right to data porta­bil­i­ty (Arti­cle 20 GDPR)
  • Right to object (Arti­cle 21 GDPR)
  • Right not to be sub­ject to a deci­sion based sole­ly on auto­mat­ed pro­cess­ing, includ­ing pro­fil­ing (Arti­cle 22 GDPR)

If you believe that the pro­cess­ing of your data vio­lates data pro­tec­tion law or that your data pro­tec­tion rights have been vio­lat­ed in any oth­er way, you can com­plain to the super­vi­so­ry author­i­ty. For Aus­tria, this is the data pro­tec­tion author­i­ty, whose web­site you can find at https://www.dsb.gv.at/ and for Ger­many, you can con­tact the Bun­des­beauf­tragte für den Daten­schutz und die Infor­ma­tions­frei­heit (BfDI).

Eval­u­a­tion of vis­i­tor behavior

In the fol­low­ing pri­va­cy pol­i­cy, we inform you whether and how we eval­u­ate data from your vis­it to this web­site. The eval­u­a­tion of the col­lect­ed data is usu­al­ly anony­mous and we can not con­clude from your behav­ior on this web­site to your person.

You can find out more about how to object to this analy­sis of vis­it data in the fol­low­ing pri­va­cy statement.

TLS encryp­tion with https

TLS, encryp­tion, and https sound very tech­ni­cal and they are. We use HTTPS (Hyper­text Trans­fer Pro­to­col Secure stands for “secure hyper­text trans­fer pro­to­col”) to trans­fer data over the inter­net in a tap-proof way.
This means that the com­plete trans­mis­sion of all data from your brows­er to our web serv­er is secured — no one can “lis­ten in”.

In this way, we have intro­duced an addi­tion­al lay­er of secu­ri­ty and ful­fill data pro­tec­tion through tech­nol­o­gy design Arti­cle 25(1) GDPR).

By using TLS (Trans­port Lay­er Secu­ri­ty), an encryp­tion pro­to­col for secure data trans­mis­sion on the Inter­net, we can ensure the pro­tec­tion of con­fi­den­tial data.
You can rec­og­nize the use of this pro­tec­tion of data trans­mis­sion by the small lock sym­bol at the top left of the brows­er to the left of the Inter­net address (e.g., beispielseite.de) and the use of the scheme https (instead of http) as part of our Inter­net address.
If you want to know more about encryp­tion, we rec­om­mend the Google search for “Hyper­text Trans­fer Pro­to­col Secure wiki” to get good links to fur­ther information.

Google Fonts Pri­va­cy Policy

On our web­site, we use the Google Font Montser­rat as a self-host­ed font. This web­site does not obtain or load Google Fonts via Google CDN.

Google Ana­lyt­ics Pri­va­cy Policy

We use on our web­site the analy­sis track­ing tool Google Ana­lyt­ics (GA) of the Amer­i­can com­pa­ny Google Inc. For the Euro­pean area, the com­pa­ny Google Ire­land Lim­it­ed (Gor­don House, Bar­row Street Dublin 4, Ire­land) is respon­si­ble for all Google ser­vices. Google Ana­lyt­ics col­lects data about your actions on our web­site. For exam­ple, when you click on a link, this action is stored in a cook­ie and sent to Google Ana­lyt­ics. Using the reports we receive from Google Ana­lyt­ics, we can bet­ter tai­lor our web­site and ser­vice to your pref­er­ences. In the fol­low­ing, we will go into more detail about the track­ing tool and, in par­tic­u­lar, inform you about what data is stored and how you can pre­vent this.

What is Google Analytics?

Google Ana­lyt­ics is a track­ing tool used for traf­fic analy­sis of our web­site. In order for Google Ana­lyt­ics to work, a track­ing code is built into the code of our web­site. When you vis­it our web­site, this code records var­i­ous actions you take on our web­site. Once you leave our web­site, this data is sent to the Google Ana­lyt­ics servers and stored there.

Google process­es the data and we receive reports about your user behav­ior. These reports may include, but are not lim­it­ed to, the following:

  • Audi­ence reports: Audi­ence reports help us get to know our users bet­ter and know more pre­cise­ly who is inter­est­ed in our service.
  • Ad reports: Ad reports help us ana­lyze and improve our online advertising.
  • Acqui­si­tion reports: Acqui­si­tion reports give us help­ful infor­ma­tion on how to attract more peo­ple to our service.
  • Behav­ior reports: This is where we learn how you inter­act with our site. We can track the path you take on our site and which links you click.
  • Con­ver­sion reports: Con­ver­sion is when you take the desired action based on a mar­ket­ing mes­sage. For exam­ple, you go from being a mere web­site vis­i­tor to a buy­er or newslet­ter sub­scriber. These reports help us learn more about how our mar­ket­ing efforts are work­ing for you. This is how we aim to increase our con­ver­sion rate.
  • Real-time reports: Here we always know imme­di­ate­ly what is hap­pen­ing on our web­site. For exam­ple, we can see how many users are read­ing this text.

Why do we use Google Ana­lyt­ics on our website?

Our goal with this web­site is clear: we want to pro­vide you with the best pos­si­ble ser­vice. The sta­tis­tics and data from Google Ana­lyt­ics help us achieve this goal.

The sta­tis­ti­cal­ly eval­u­at­ed data shows us a clear pic­ture of the strengths and weak­ness­es of our web­site. On the one hand, we can opti­mize our site so that it can be found more eas­i­ly by inter­est­ed peo­ple on Google. On the oth­er hand, the data helps us to bet­ter under­stand you as a vis­i­tor. Thus, we know very well what we need to improve on our web­site in order to pro­vide you with the best pos­si­ble ser­vice. The data also helps us to car­ry out our adver­tis­ing and mar­ket­ing mea­sures in a more indi­vid­ual and cost-effec­tive way. After all, it only makes sense to show our prod­ucts and ser­vices to peo­ple who are inter­est­ed in them.

What data is stored by Google Analytics?

Google Ana­lyt­ics uses a track­ing code to cre­ate a ran­dom, unique ID asso­ci­at­ed with your brows­er cook­ie. This is how Google Ana­lyt­ics rec­og­nizes you as a new user. The next time you vis­it our site, you will be rec­og­nized as a “return­ing” user. All col­lect­ed data is stored togeth­er with this user ID. This is how it is pos­si­ble to eval­u­ate pseu­do­ny­mous user pro­files in the first place.

To be able to ana­lyze our web­site with Google Ana­lyt­ics, a prop­er­ty ID must be insert­ed into the track­ing code. The data is then stored in the cor­re­spond­ing prop­er­ty. For each new­ly cre­at­ed prop­er­ty, the Google Ana­lyt­ics 4 prop­er­ty is the default. Alter­na­tive­ly, you can also cre­ate the Uni­ver­sal Ana­lyt­ics prop­er­ty. Depend­ing on the prop­er­ty used, data is stored for dif­fer­ent lengths of time.

Iden­ti­fiers such as cook­ies and app instance IDs mea­sure your inter­ac­tions on our web­site. Inter­ac­tions are all types of actions you take on our web­site. If you also use oth­er Google sys­tems (such as a Google account), data gen­er­at­ed through Google Ana­lyt­ics may be linked to third-par­ty cook­ies. Google does not share Google Ana­lyt­ics data unless we, as the web­site oper­a­tor, autho­rize it. Excep­tions may occur if required by law.

The fol­low­ing cook­ies are used by Google Analytics:

Name: _​ga
Val­ue: 2.1326744211.152111682284 – 5
Pur­pose: By default, analytics.js uses the _​ga cook­ie to store the user ID. Basi­cal­ly, it is used to dis­tin­guish web­site vis­i­tors.
Expi­ra­tion date: after 2 years

Name: _​gid
Val­ue: 2.1687193234.152111682284 – 1
Pur­pose: The cook­ie is also used to dis­tin­guish the web­site vis­i­tors.
Expi­ra­tion date: after 24 hours

Name: _​gat_​gtag_​UA_​Value: 1
Pur­pose: Used to low­er the request rate. If Google Ana­lyt­ics is deployed via Google Tag Man­ag­er, this cook­ie will be named _​dc_​gtm_​.
Expi­ra­tion date: after 1 minute

Name: AMP_TOKEN
Val­ue: not spec­i­fied
Pur­pose: The cook­ie has a token that can be used to retrieve a user ID from the AMP client ID ser­vice. Oth­er pos­si­ble val­ues indi­cate a logout, a request, or an error.
Expi­ra­tion date: after 30 sec­onds up to one year.

Name: _​_​utma
Wert: 1564498958.1564498958.1564498958.1
Pur­pose: This cook­ie is used to track your behav­ior on the web­site and mea­sure per­for­mance. The cook­ie is updat­ed every time infor­ma­tion is sent to Google Ana­lyt­ics.
Expi­ra­tion date: after 2 years

Name: _​_​utmt
Val­ue: 1
Pur­pose: The cook­ie is used like _​gat_​gtag_​UA_​to throt­tle the request rate.
Expi­ra­tion date: after 10 minutes

Name: _​_​utmb
Val­ue: 3.10.1564498958
Pur­pose: This cook­ie is used to deter­mine new ses­sions. It is updat­ed every time new data or info is sent to Google Ana­lyt­ics.
Expi­ra­tion date: after 30 minutes

Name: _​_​utmc
Val­ue: 167421564
Pur­pose: This cook­ie is used to set new ses­sions for return­ing vis­i­tors. This is a ses­sion cook­ie and is only stored until you close the brows­er again.
Expi­ra­tion date: After you close the browser.

Name: _​_​utmz
Val­ue: m|utmccn=(referral)|utmcmd=referral|utmcct=/
Pur­pose: The cook­ie is used to iden­ti­fy the source of the traf­fic to our web­site. That is, the cook­ie stores from where you came to our web­site. This may have been anoth­er page or an adver­tise­ment.
Expi­ra­tion date: after 6 months

Name: _​_​utmv
Val­ue: not spec­i­fied
Pur­pose: The cook­ie is used to store cus­tom user data. It is updat­ed when­ev­er infor­ma­tion is sent to Google Ana­lyt­ics.
Expi­ra­tion date: after 2 years

Note: This enu­mer­a­tion can­not claim to be com­plete, as Google also changes the choice of their cook­ies every now and then.

Here we show you an overview of the most impor­tant data col­lect­ed with Google Analytics:

Heatmaps: Google cre­ates so-called heatmaps. Heatmaps allow you to see exact­ly those areas that you click on. This gives us infor­ma­tion about where you are “on the move” on our site.

Ses­sion dura­tion: Google defines ses­sion dura­tion as the time you spend on our site with­out leav­ing. If you have been inac­tive for 20 min­utes, the ses­sion ends automatically.

Bounce rate: A bounce is when you view only one page on our site and then leave our site.

Account cre­ation: when you cre­ate an account or make an order on our web­site, Google Ana­lyt­ics col­lects this data.

IP address: The IP address is only shown in a short­ened form so that no clear assign­ment is possible.

Loca­tion: The IP address can be used to deter­mine the coun­try and your approx­i­mate loca­tion. This process is also referred to as IP- loca­tion determination.

Tech­ni­cal infor­ma­tion: Tech­ni­cal infor­ma­tion includes, but is not lim­it­ed to, your brows­er type, inter­net ser­vice provider, or screen resolution.

Source of ori­gin: Google Ana­lyt­ics or we are of course also inter­est­ed in which web­site or which adver­tise­ment you came to our site from.

Oth­er data include con­tact details, any rat­ings, play­ing media (for exam­ple, if you play a video via our site), shar­ing con­tent via social media or adding to your favorites. The enu­mer­a­tion does not claim to be com­plete and only serves as a gen­er­al ori­en­ta­tion of the data stor­age by Google Analytics.

How long and where is the data stored?

Google has your servers spread all over the world. Most servers are locat­ed in Amer­i­ca and con­se­quent­ly, your data is most­ly stored on Amer­i­can servers. Here you can read exact­ly where Google’s data cen­ters are locat­ed: https://www.google.com/about/datacenters/inside/locations/?hl=de

Ihre Dat­en sind auf ver­schiedene physikalis­che Daten­träger verteilt. Dies hat den Vorteil, dass die Dat­en schneller abgerufen wer­den kön­nen und bess­er vor Manip­u­la­tio­nen geschützt sind. In jedem Google-Rechen­zen­trum gibt es entsprechende Not­fall­pro­gramme für Ihre Dat­en. Wenn z. B. die Hard­ware bei Google aus­fällt oder Naturkatas­tro­phen die Serv­er lahm­le­gen, bleibt das Risiko ein­er Ser­vice­un­ter­brechung bei Google den­noch gering..

The data reten­tion peri­od depends on the prop­er­ties used. When using the new­er Google Ana­lyt­ics 4 prop­er­ties, the reten­tion peri­od of your user data is set to 14 months. For oth­er so-called event data, we have the option to choose a reten­tion peri­od of 2 months or 14 months.

For Uni­ver­sal Ana­lyt­ics prop­er­ties, Google Ana­lyt­ics has a default reten­tion peri­od of 26 months for your user data. Then your user data is delet­ed. How­ev­er, we have the option to choose the reten­tion peri­od of user data our­selves. There are five vari­ants avail­able to us for this:

  • Dele­tion after 14 months
  • Dele­tion after 26 months
  • Dele­tion after 38 months
  • Dele­tion after 50 months
  • No auto­mat­ic deletion

In addi­tion, there is also the option that data will only be delet­ed if you no longer vis­it our web­site with­in the peri­od we have select­ed. In this case, the reten­tion peri­od is reset each time you vis­it our web­site again with­in the spec­i­fied period.

Once the spec­i­fied peri­od has expired, the data is delet­ed once a month. This reten­tion peri­od applies to your data asso­ci­at­ed with cook­ies, user recog­ni­tion, and adver­tis­ing IDs (e.g. Dou­bleClick domain cook­ies). Report­ing results are based on aggre­gat­ed data and are stored sep­a­rate­ly from user data. Aggre­gat­ed data is a merg­ing of indi­vid­ual data into a larg­er unit.

How can I delete my data or pre­vent data storage?

Under Euro­pean Union data pro­tec­tion law, you have the right to obtain infor­ma­tion about your data, update it, delete it, or restrict it. Using the brows­er add-on to dis­able Google Ana­lyt­ics JavaScript (ga.js, analytics.js, dc.js), you can pre­vent Google Ana­lyt­ics from using your data. You can down­load and install the brows­er add-on at https://tools.google.com/dlpage/gaoptout?hl=de. Please note that this add-on only dis­ables data col­lec­tion by Google Analytics.

If you gen­er­al­ly want to dis­able, delete or man­age cook­ies (inde­pen­dent­ly of Google Ana­lyt­ics), there are sep­a­rate instruc­tions for each browser:

Chrome: Delete, enable and man­age cook­ies in Chrome

Safari: Man­ag­ing cook­ies and web­site data with Safari

Fire­fox: Delete cook­ies to remove data that web­sites have placed on your computer

Inter­net Explor­er: Delete and man­age cookies

Microsoft Edge: Delete and man­age cookies

Please note that when using this tool, data from you may also be stored and processed out­side the EU. Most third coun­tries (includ­ing the USA) are not con­sid­ered secure under cur­rent Euro­pean data pro­tec­tion law. Data to inse­cure third coun­tries may there­fore not sim­ply be trans­ferred, stored, and processed there unless there are suit­able safe­guards (such as EU stan­dard con­trac­tu­al claus­es) between us and the non-Euro­pean ser­vice provider.

We hope we have been able to pro­vide you with the most impor­tant infor­ma­tion about Google Ana­lyt­ics data pro­cess­ing. If you want to learn more about the track­ing ser­vice, we rec­om­mend these two links: http://www.google.com/analytics/terms/de.html and https://support.google.com/analytics/answer/6004245?hl=de.

Google Ana­lyt­ics IP anonymization

We have imple­ment­ed Google Ana­lyt­ics IP address anonymiza­tion on this web­site. This fea­ture was devel­oped by Google to enable this web­site to com­ply with applic­a­ble data pro­tec­tion reg­u­la­tions and rec­om­men­da­tions of local data pro­tec­tion author­i­ties when they pro­hib­it the stor­age of the full IP address. The anonymiza­tion or mask­ing of the IP takes place as soon as the IP address­es arrive in the Google Ana­lyt­ics data col­lec­tion net­work and before any stor­age or pro­cess­ing of the data takes place.

You can find more infor­ma­tion about IP anonymiza­tion on https://support.google.com/analytics/answer/2763052?hl=de.

Google Ana­lyt­ics reports on demo­graph­ic char­ac­ter­is­tics and interests

We have turned on the adver­tis­ing report fea­tures in Google Ana­lyt­ics. The demo­graph­ic and inter­est reports con­tain infor­ma­tion on age, gen­der, and inter­ests. This allows us — with­out being able to assign this data to indi­vid­ual per­sons — to get a bet­ter pic­ture of our users. Learn more about the adver­tis­ing func­tions at https://support.google.com/analytics/answer/3450482?hl=de_AT&utm_id=ad.

You can con­trol the use of your Google Account activ­i­ties and infor­ma­tion under “Adver­tis­ing Set­tings” on https://adssettings.google.com/authenticated.End via a checkbox.

If you click on the fol­low­ing deac­ti­va­tion link, you can pre­vent Google from col­lect­ing fur­ther vis­its to this web­site. Atten­tion: Delet­ing cook­ies, using the incognito/​private mode of your brows­er, or using a dif­fer­ent brows­er will result in data being col­lect­ed again.

Deac­ti­vate Google Analytics

Google Ana­lyt­ics Data Pro­cess­ing Addendum

We have entered into a direct cus­tomer agree­ment with Google for the use of Google Ana­lyt­ics by accept­ing the “Data Pro­cess­ing Adden­dum” in Google Analytics.

You can find out more about the data pro­cess­ing adden­dum for Google Ana­lyt­ics here: https://support.google.com/analytics/answer/3379636?hl=de&utm_id=ad

Google Tag Man­ag­er Pri­va­cy Policy

For our web­site, we use the Google Tag Man­ag­er of the com­pa­ny Google Inc. For the Euro­pean area, the com­pa­ny Google Ire­land Lim­it­ed (Gor­don House, Bar­row Street Dublin 4, Ire­land) is respon­si­ble for all Google ser­vices. This Tag Man­ag­er is one of many help­ful mar­ket­ing prod­ucts from Google. Through the Google Tag Man­ag­er, we can cen­tral­ly incor­po­rate and man­age code sec­tions from var­i­ous track­ing tools that we use on our website.

In this pri­va­cy pol­i­cy, we want to explain in more detail what Google Tag Man­ag­er does, why we use it, and in what form data is processed.

What is Google Tag Manager?

As the say­ing goes: orga­ni­za­tion is half the bat­tle! And that of course also applies to the main­te­nance of our web­site. In order to make our web­site as good as pos­si­ble for you and all the peo­ple who are inter­est­ed in our prod­ucts and ser­vices, we need var­i­ous track­ing tools such as Google Ana­lyt­ics. The col­lect­ed data from these tools show us what you are most inter­est­ed in, where we can improve our ser­vices, and which peo­ple we should still show our offers to. And for this track­ing to work, we need to embed appro­pri­ate JavaScript codes into our web­site. In prin­ci­ple, we could include each code sec­tion of each track­ing tool sep­a­rate­ly in our source code. How­ev­er, this requires quite a lot of time and it’s easy to lose track. That’s why we use Google Tag Man­ag­er. We can eas­i­ly incor­po­rate the nec­es­sary scripts and man­age them from one place. More­over, Google Tag Man­ag­er offers an easy-to-use inter­face and you don’t need any pro­gram­ming skills. This is how we man­age to keep order in our tag jungle.

What data is stored by Google Tag Manager?

The Tag Man­ag­er itself is a domain that does not set any cook­ies or store any data. It acts as a mere “man­ag­er” of the imple­ment­ed tags. The data is col­lect­ed by the indi­vid­ual tags of the dif­fer­ent web ana­lyt­ics tools. The data is vir­tu­al­ly passed through to the indi­vid­ual track­ing tools in the Google Tag Man­ag­er and is not stored.

How­ev­er, the sit­u­a­tion is quite dif­fer­ent with the embed­ded tags of the var­i­ous web analy­sis tools, such as Google Ana­lyt­ics. Depend­ing on the analy­sis tool, var­i­ous data about your web behav­ior is usu­al­ly col­lect­ed, stored, and processed with the help of cook­ies. For this, please read our pri­va­cy texts on the indi­vid­ual analy­sis and track­ing tools that we use on our website.

In the Tag Man­ag­er account set­tings, we have allowed Google to receive anonymized data from us. How­ev­er, this is only the use and usage of our Tag Man­ag­er and not your data stored via the code sec­tions. We allow Google and oth­ers to receive select­ed data in anonymized form. We thus con­sent to the anony­mous shar­ing of our web­site data. Which sum­ma­rized and anony­mous data is for­ward­ed exact­ly, we could not find out — despite long research. In any case, Google deletes all infor­ma­tion that could iden­ti­fy our web­site. Google com­bines the data with hun­dreds of oth­er anony­mous web­site data and cre­ates user trends as part of bench­mark­ing mea­sures. Bench­mark­ing com­pares our own results with those of our com­peti­tors. Process­es can be opti­mized on the basis of the infor­ma­tion collected.

How long and where the data is stored?

When Google stores data, this data is stored on Google’s own servers. The servers are dis­trib­uted all over the world. Most of them are locat­ed in Amer­i­ca. At https://www.google.com/about/datacenters/inside/locations/?hl=de you can read exact­ly where the Google servers are located.

How long the indi­vid­ual track­ing tools store data from you can be found in our indi­vid­ual pri­va­cy texts for the indi­vid­ual tools.

How to delete my data or pre­vent data storage?

The Google Tag Man­ag­er itself does not set cook­ies but man­ages tags from var­i­ous track­ing web­sites. In our pri­va­cy texts for the indi­vid­ual track­ing tools, you will find detailed infor­ma­tion on how to delete or man­age your data.

Please note that when using this tool, data from you may also be stored and processed out­side the EU. Most third coun­tries (includ­ing the USA) are not con­sid­ered secure under cur­rent Euro­pean data pro­tec­tion law. Data to inse­cure third coun­tries may there­fore not sim­ply be trans­ferred, stored and processed there unless there are suit­able safe­guards (such as EU stan­dard con­trac­tu­al claus­es) between us and the non-Euro­pean ser­vice provider.

If you want to learn more about the Google Tag Man­ag­er, we rec­om­mend the FAQs at https://www.google.com/intl/de/tagmanager/faq.html.

Google Site Kit Pri­va­cy Policy

We have inte­grat­ed the Word­Press plu­g­in Google Site Kit of the Amer­i­can com­pa­ny Google Inc. into our web­site. For the Euro­pean area, the com­pa­ny Google Ire­land Lim­it­ed (Gor­don House, Bar­row Street Dublin 4, Ire­land) is respon­si­ble for all Google ser­vices. With Google Site Kit, we can quick­ly and eas­i­ly view sta­tis­tics that come from var­i­ous Google prod­ucts such as Google Ana­lyt­ics direct­ly in our Word­Press dash­board. The tool or the tools includ­ed in Google Site Kit also col­lect, among oth­er things, per­son­al data from you. In this pri­va­cy pol­i­cy, we explain why we use Google Site Kit, how long and where data is stored, and which oth­er pri­va­cy texts are rel­e­vant for you in this context.

What is Google Site Kit?

Google Site Kit is a plu­g­in for the Word­Press con­tent man­age­ment sys­tem. With this plu­g­in, we can view impor­tant web­site ana­lyt­ics sta­tis­tics direct­ly in our dash­board. These are sta­tis­tics that are col­lect­ed by oth­er Google prod­ucts. First and fore­most, from Google Ana­lyt­ics. Besides Google Ana­lyt­ics, Google Search Con­sole, Page Speed Insight, Google AdSense, Google Opti­mize, and Google Tag Man­ag­er ser­vices can also be linked to Google Site Kit.

Why we use Google Site Kit on our website?

As a ser­vice provider, it is our job to offer you the best pos­si­ble expe­ri­ence on our web­site. You should feel com­fort­able on our web­site and find exact­ly what you are look­ing for quick­ly and eas­i­ly. Sta­tis­ti­cal eval­u­a­tions help us to get to know you bet­ter and to adapt our offer to your wish­es and inter­ests. We use var­i­ous Google tools for these eval­u­a­tions. Site Kit makes our work much eas­i­er in this regard because we can view and ana­lyze the sta­tis­tics of Google prod­ucts right in the dash­board. So we don’t have to log in sep­a­rate­ly for each tool. Site Kit thus always pro­vides a good overview of the most impor­tant analy­sis data.

What data is stored by Google Site Kit?

If you have active­ly agreed to track­ing tools in the cook­ie notice (also called script or ban­ner), Google prod­ucts such as Google Ana­lyt­ics will set cook­ies and send data from you, for exam­ple about your user behav­ior, to Google, where it will be stored and processed. This also includes per­son­al data such as your IP address.

For more detailed infor­ma­tion on the indi­vid­ual ser­vices, we have sep­a­rate text sec­tions in this pri­va­cy state­ment. For exam­ple, take a look at our pri­va­cy pol­i­cy on Google Ana­lyt­ics. Here we go into great detail about the data col­lect­ed. You will learn how long Google Ana­lyt­ics stores, man­ages and process­es data, which cook­ies may be used, and how you can pre­vent data stor­age. Like­wise, we also have our own pri­va­cy state­ments with com­pre­hen­sive infor­ma­tion for oth­er Google ser­vices such as Google Tag Man­ag­er or Google AdSense.

In the fol­low­ing, we show you exem­plary Google Ana­lyt­ics cook­ies that can be set in your brows­er, pro­vid­ed that you have agreed in prin­ci­ple to data pro­cess­ing by Google. Please note that these cook­ies are only a selection:

Name: _​ga
Value:2.1326744211.152111682284 – 2
Pur­pose: By default, analytics.js uses the _​ga cook­ie to store the user ID. Basi­cal­ly, it is used to dis­tin­guish web­site vis­i­tors.
Expi­ra­tion date: after 2 years

Name: _​gid
Value:2.1687193234.152111682284 – 7
Pur­pose: This cook­ie is also used to dis­tin­guish web­site vis­i­tors.
Expi­ra­tion date: after 24 hours

Name: _​gat_​gtag_​UA_​Value: 1
Pur­pose: This cook­ie is used to low­er the request rate.
Expi­ra­tion date: after 1 minute

How long and where the data is stored?

Google stores col­lect­ed data on its own Google servers, which are dis­trib­uted world­wide. Most servers are locat­ed in the Unit­ed States and there­fore it is eas­i­ly pos­si­ble that your data is also stored there. At https://www.google.com/about/datacenters/inside/locations/?hl=de you can see exact­ly where the com­pa­ny pro­vides servers.

Data col­lect­ed by Google Ana­lyt­ics is retained for a stan­dard peri­od of 26 months. After that, your user data is delet­ed. The reten­tion peri­od applies to all data linked to cook­ies, user recog­ni­tion, and adver­tis­ing IDs.

How to delete my data or pre­vent data storage?

You always have the right to obtain infor­ma­tion about your data, to have your data delet­ed, cor­rect­ed, or restrict­ed. In addi­tion, you can also dis­able, delete or man­age cook­ies in your brows­er at any time. Here we show you the cor­re­spond­ing instruc­tions of the most pop­u­lar browsers:

Chrome: Delete, enable and man­age cook­ies in Chrome

Safari: Man­ag­ing cook­ies and web­site data with Safari

Fire­fox: Delete cook­ies to remove data that web­sites have placed on your computer

Inter­net Explor­er: Delete and man­age cookies

Microsoft Edge: Delete and man­age cookies

Please note that when using this tool, data from you may also be stored and processed out­side the EU. Most third coun­tries (includ­ing the USA) are not con­sid­ered secure under cur­rent Euro­pean data pro­tec­tion law. Data to inse­cure third coun­tries may there­fore not sim­ply be trans­ferred, stored, and processed there unless there are suit­able safe­guards (such as EU stan­dard con­trac­tu­al claus­es) between us and the non-Euro­pean ser­vice provider.

To learn more about Google’s data pro­cess­ing, we rec­om­mend that you read Google’s com­pre­hen­sive pri­va­cy pol­i­cy at https://policies.google.com/privacy?hl=de.

Embed­ded Social Media Ele­ments Pri­va­cy Policy

We inte­grate ele­ments of social media ser­vices on our web­site to dis­play images, videos, and texts.
When you vis­it pages that dis­play these ele­ments, data is trans­ferred from your brows­er to the respec­tive social media ser­vice and stored there. We do not have access to this data.
The fol­low­ing links will take you to the pages of the respec­tive social media ser­vices where it is explained how they han­dle your data:

LinkedIn Pri­va­cy Policy

We use social plug-ins of the social media net­work LinkedIn, of the com­pa­ny LinkedIn Cor­po­ra­tion, 2029 Stier­lin Court, Moun­tain View, CA 94043, the USA on our web­site. The social plug-ins may be feeds, con­tent shar­ing, or links to our LinkedIn page. The social plug-ins are clear­ly marked with the famil­iar LinkedIn logo and allow, for exam­ple, inter­est­ing con­tent to be shared direct­ly via our web­site. For the Euro­pean Eco­nom­ic Area and Switzer­land, LinkedIn Ire­land Unlim­it­ed Com­pa­ny Wilton Place in Dublin is respon­si­ble for data processing.

By embed­ding such plug-ins, data can be sent to LinkedIn, stored, and processed there. In this pri­va­cy pol­i­cy, we want to inform you about what data is involved, how the net­work uses this data, and how you can man­age or pre­vent data storage.

What is LinkedIn?

LinkedIn is the largest social net­work for busi­ness con­tacts. Unlike Face­book, for exam­ple, the com­pa­ny focus­es exclu­sive­ly on build­ing busi­ness con­tacts. Com­pa­nies can present ser­vices and prod­ucts on the plat­form and estab­lish busi­ness rela­tion­ships. Many peo­ple also use LinkedIn to look for jobs or to find suit­able employ­ees for their own com­pa­ny. In Ger­many alone, the net­work has over 11 mil­lion mem­bers. In Aus­tria, there are around 1.3 million.

Why we use LinkedIn on our website?

We con­sid­er built-in social plug-ins as an extend­ed ser­vice on our web­site. The data that LinkedIn col­lects also helps us to show pos­si­ble adver­tis­ing mea­sures only to peo­ple who are inter­est­ed in our offer.

What data is stored by LinkedIn?

Only through the mere inte­gra­tion of the social plug-ins, LinkedIn does not store any per­son­al data. LinkedIn calls this data gen­er­at­ed by plug-ins pas­sive impres­sions. How­ev­er, when you click on a social plug-in, for exam­ple, to share our con­tent, the plat­form stores per­son­al data as so-called “active impres­sions”. And this is regard­less of whether you have a LinkedIn account or not. If you are logged in, the col­lect­ed data is assigned to your account.

Your brows­er estab­lish­es a direct con­nec­tion to LinkedIn’s servers when you inter­act with our plug-ins. In this way, the com­pa­ny logs var­i­ous usage data. In addi­tion to your IP address, this can be login data, device infor­ma­tion, or info about your inter­net or mobile provider, for exam­ple. If you access LinkedIn ser­vices via your smart­phone, your loca­tion (after you have allowed this) can also be deter­mined. LinkedIn may also share this data in “hashed” form with third-par­ty adver­tis­ers. Hash­ing means turn­ing a record into a string of char­ac­ters. This can be used to encrypt the data in such a way that indi­vid­u­als can no longer be identified.

Most data about your user behav­ior is stored in cook­ies. These are small text files that are usu­al­ly set in your brows­er. Fur­ther­more, LinkedIn can also use web bea­cons, pix­el tags, dis­play tags, and oth­er device identifiers.

Var­i­ous tests also show which cook­ies are set when a user inter­acts with a social plug-in. The data found can­not claim to be exhaus­tive and is pro­vid­ed as an exam­ple only. The fol­low­ing cook­ies were set with­out being logged into LinkedIn:

Name: bcook­ie
Wert: =2&34aab2aa-2ae1-4d2a-8baf-c2e2d7235c16111682284-
Pur­pose: The cook­ie is a so-called “brows­er ID cook­ie” and con­se­quent­ly stores your iden­ti­fi­ca­tion num­ber (ID).
Expi­ra­tion date: After 2 years

Name: lang
Val­ue: v=2&lang=en-en
Pur­pose: This cook­ie stores your default or pre­ferred lan­guage.
Expi­ra­tion date: After end of session

Name: lidc
Wert: 1818367:t=1571904767:s=AQF6KNnJ0G111682284…
Pur­pose: This cook­ie is used for rout­ing. Rout­ing records the ways you came to LinkedIn and how you nav­i­gate through the web­site there.
Expi­ra­tion date: after 24 hours

Name: rtc
Val­ue: kt0lrv3NF3x3t6xvDgGrZGDKkX
Pur­pose: No fur­ther infor­ma­tion could be obtained about this cook­ie.
Expi­ra­tion date: after 2 minutes

Name: JSES­SION­ID
Wert: ajax:1116822842900777718326218137
Pur­pose: This is a ses­sion cook­ie that LinkedIn uses to main­tain anony­mous user ses­sions through the serv­er.
Expi­ra­tion date: after the end of the session

Name: bscook­ie
Val­ue: “v=1&201910230812…
Pur­pose: This cook­ie is a secu­ri­ty cook­ie. LinkedIn describes it as a secure brows­er ID cook­ie.
Expi­ra­tion date: after 2 years

Name: fid
Val­ue: AQHj7Ii23ZBcqAAAA…
Pur­pose: No fur­ther infor­ma­tion could be found about this cook­ie.
Expi­ra­tion date: after 7 days

Note: LinkedIn also works with third-par­ty providers. That is why we also detect­ed the two Google Ana­lyt­ics cook­ies _​ga and _​gat dur­ing our test.

How long and where the data is stored?

Gen­er­al­ly, LinkedIn will retain your per­son­al data for as long as it deems it nec­es­sary to pro­vide its ser­vices. How­ev­er, LinkedIn deletes your per­son­al data when you delete your account. In some excep­tion­al cas­es, LinkedIn retains some data in aggre­gate and anonymized form even after you delete your account. Once you delete your account, oth­er peo­ple will not be able to see your data with­in one day. LinkedIn gen­er­al­ly deletes data with­in 30 days. How­ev­er, LinkedIn retains data if it is nec­es­sary due to legal oblig­a­tions. Data that can no longer be assigned to indi­vid­u­als remain stored even after the account is closed. The data is stored on var­i­ous servers in Amer­i­ca and pre­sum­ably also in Europe.

How to delete my data or pre­vent data storage?

You have the right to access and also delete your per­son­al data at any time. In your LinkedIn account, you can man­age, change and delete your data. In addi­tion, you can also request a copy of your per­son­al data from LinkedIn.

To access account data in your LinkedIn profile:

In LinkedIn, click on your pro­file icon and select the “Set­tings and Pri­va­cy” sec­tion. Now click on “Pri­va­cy” and then in the “How LinkedIn uses your data” sec­tion click on “Change”. In just a short time, you can down­load select­ed data about your web activ­i­ty and account history.

You also have the option in your brows­er to pre­vent data pro­cess­ing by LinkedIn. As men­tioned above, LinkedIn stores most data via cook­ies that are set in your brows­er. You can man­age, deac­ti­vate or delete these cook­ies. Depend­ing on which brows­er you have, the man­age­ment works slight­ly dif­fer­ent­ly. You can find the instruc­tions for the most com­mon browsers here:

Chrome: Delete, enable and man­age cook­ies in Chrome

Safari: Man­ag­ing cook­ies and web­site data with Safari

Fire­fox: Delete cook­ies to remove data that web­sites have placed on your computer

Inter­net Explor­er: Delete and man­age cookies

Microsoft Edge: Delete and man­age cookies

You can also basi­cal­ly set up your brows­er so that you are always informed when a cook­ie is to be set. Then you can always decide indi­vid­u­al­ly whether you want to allow the cook­ie or not.

Please note that when using this tool, data from you may also be stored and processed out­side the EU. Most third coun­tries (includ­ing the USA) are not con­sid­ered secure under cur­rent Euro­pean data pro­tec­tion law. Data to inse­cure third coun­tries may there­fore not sim­ply be trans­ferred, stored, and processed there unless there are suit­able safe­guards (such as EU stan­dard con­trac­tu­al claus­es) between us and the non-Euro­pean ser­vice provider.

We have tried to bring you clos­er to the most impor­tant infor­ma­tion about data pro­cess­ing by LinkedIn. At https://www.linkedin.com/legal/privacy-policy you can learn even more about the data pro­cess­ing of the social media net­work LinkedIn.

XING Pri­va­cy Policy

We use social plu­g­ins of the social media net­work Xing, of the com­pa­ny Xing SE, Damm­torstraße 30, 20354 Ham­burg, Ger­many, on our web­site. Through these func­tions, you can, for exam­ple, share con­tent on Xing direct­ly via our web­site, log in via Xing or fol­low inter­est­ing con­tent. You can rec­og­nize the plug-ins by the com­pa­ny name or the Xing logo. If you call up a web­site that uses a Xing plug-in, data may be trans­mit­ted to the “Xing servers”, stored and ana­lyzed. In this data pro­tec­tion dec­la­ra­tion, we want to inform you about what data is involved and how you can man­age or pre­vent this data storage.

What is Xing?

Xing is a social net­work with its head­quar­ters in Ham­burg. The com­pa­ny spe­cial­izes in man­ag­ing pro­fes­sion­al con­tacts. That is, unlike oth­er net­works, Xing is pri­mar­i­ly about pro­fes­sion­al net­work­ing. The plat­form is often used for job search­es or to find employ­ees for one’s own com­pa­ny. In addi­tion, Xing offers inter­est­ing con­tent on var­i­ous pro­fes­sion­al top­ics. The glob­al coun­ter­part is the Amer­i­can com­pa­ny LinkedIn.

Why we use Xing on our website?

There is now a flood of social media chan­nels and we are well aware that your time is very pre­cious. Not every company’s social media chan­nel can be scru­ti­nized close­ly. That’s why we want to make your life as easy as pos­si­ble, so you can share or fol­low inter­est­ing con­tent direct­ly from our web­site on Xing. With such “social plug-ins,” we expand our ser­vice on our web­site. In addi­tion, the data col­lect­ed by Xing helps us to car­ry out tar­get­ed adver­tis­ing mea­sures on the plat­form. This means that our ser­vice is only shown to peo­ple who are real­ly inter­est­ed in it.

What data is stored by Xing?

Xing offers the Share but­ton, the Fol­low but­ton, and the Log-in but­ton as plug-ins for web­sites. As soon as you open a page where a social plug-in from Xing is installed, your brows­er con­nects to servers in a data cen­ter used by Xing. In the case of the share but­ton, no data is to be stored — accord­ing to Xing — that could infer a direct ref­er­ence to a per­son. In par­tic­u­lar, Xing does not store your IP address. Fur­ther­more, no cook­ies are set in con­nec­tion with the share but­ton. Thus, no eval­u­a­tion of your user behav­ior takes place. You can obtain more infor­ma­tion about this via https://www.xing.com/app/share%3Fop%3Ddata_protection.

For the oth­er Xing plug-ins, cook­ies are only set in your brows­er when you inter­act with the plug-in or click on it. Here, per­son­al data such as your IP address, brows­er data, date, and time of your page view on Xing may be stored. If you have a XING account and are logged in, col­lect­ed data will be assigned to your per­son­al account and the data stored therein.

The fol­low­ing cook­ies are set in your brows­er when you click on the fol­low or log-in but­ton and are not yet logged in to Xing. Please keep in mind that this is an exem­plary list and we can­not claim to be complete.

Name: AMCVS_0894FF2554F733210A4C98C6%40AdobeOrg
Val­ue: 1
Pur­pose: This cook­ie is used to cre­ate and store web­site vis­i­tor iden­ti­fiers.
Expi­ra­tion date: after end of session

Name: c_​
Val­ue: 157c609dc9fe7d7ff56064c6de87b019111682284‑8
Pur­pose: We could not find out more infor­ma­tion about this cook­ie.
Expi­ra­tion date: after one day

Name: pre­vPage
Val­ue: wbm%2FWelcome%2Flogin
Pur­pose: This cook­ie stores the URL of the pre­vi­ous web page you vis­it­ed.
Expi­ra­tion date: after 30 minutes

Name: s_​cc
Val­ue: true
Pur­pose: This Adobe Site Cat­a­lyst cook­ie deter­mines whether cook­ies are gen­er­al­ly enabled in the brows­er.
Expi­ra­tion date: after end of session

Name: s_​fid
Wert: 6897CD­CD1013221C-39D­DAC­C982217CD1111682284‑2
Pur­pose: This cook­ie is used to iden­ti­fy a unique vis­i­tor.
Expi­ra­tion date: after 5 years

Name: visitor_​id
Wert: fe59f­be5-e9c6-4fca-8776 – 30d0c1a89c32
Pur­pose: The vis­i­tor cook­ie con­tains a unique vis­i­tor ID and the unique iden­ti­fi­er for your account.
Expi­ra­tion date: after 2 years

Name:_session_id
Wert: 533a0a6641df82b46383da06ea0e84e7111682284‑2
Pur­pose: This cook­ie cre­ates a tem­po­rary ses­sion ID that is used as an in-ses­sion user ID. The cook­ie is absolute­ly nec­es­sary to pro­vide Xing’s fea­tures.
Expi­ra­tion date: after the end of the session

As soon as you are logged in to Xing or become a mem­ber, fur­ther per­son­al data is def­i­nite­ly col­lect­ed, processed, and stored. Xing also dis­clos­es per­son­al data to third par­ties if this is nec­es­sary for the ful­fill­ment of its own busi­ness pur­pos­es, if you have giv­en your con­sent, or if there is a legal obligation.

How long and where the data is stored?

Xing stores the data on var­i­ous servers in var­i­ous data cen­ters. The com­pa­ny stores this data until you delete the data or until a user account is delet­ed. Of course, this only affects users who are already Xing members.

How to delete my data or pre­vent data storage?

You have the right to access and also delete your per­son­al data at any time. Even if you are not a Xing mem­ber, you can use your brows­er to pre­vent pos­si­ble data pro­cess­ing or man­age it accord­ing to your wish­es. Most data is stored via cook­ies. Depend­ing on which brows­er you have, the man­age­ment works slight­ly dif­fer­ent­ly. You can find the instruc­tions for the most com­mon browsers here:

Chrome: Delete, enable and man­age cook­ies in Chrome

Safari: Man­ag­ing cook­ies and web­site data with Safari

Fire­fox: Delete cook­ies to remove data that web­sites have placed on your computer

Inter­net Explor­er: Delete and man­age cookies

Microsoft Edge: Delete and man­age cookies

You can also basi­cal­ly set up your brows­er so that you are always informed when a cook­ie is to be set. Then you can always decide indi­vid­u­al­ly whether you want to allow the cook­ie or not.

We have tried to bring you clos­er to the most impor­tant infor­ma­tion about data pro­cess­ing by Xing. At https://privacy.xing.com/de/datenschutzerklaerung you can learn even more about the data pro­cess­ing of the social media net­work Xing.

All texts are pro­tect­ed by copyright.

Source: Cre­at­ed with the Daten­schutz Gen­er­a­tor by AdSimple