Pri­vacy policy accord­ing to the DSGVO

 

I am pleased about your vis­it to my web­site and your interest in my com­pany. The pro­tec­tion of your per­son­al data is import­ant to me. Per­son­al data is indi­vidu­al inform­a­tion about per­son­al or fac­tu­al cir­cum­stances of a spe­cif­ic or iden­ti­fi­able nat­ur­al per­son. This includes inform­a­tion such as civil name, address, tele­phone num­ber and date of birth. Since this data enjoys spe­cial pro­tec­tion, it is only col­lec­ted by me to the extent tech­nic­ally neces­sary. In the fol­low­ing, I explain what inform­a­tion I col­lect dur­ing your vis­it to my web­site and how it is used.
My data pro­tec­tion prac­tice is in accord­ance with the reg­u­la­tions of the Fed­er­al Data Pro­tec­tion Act (BDSG), the Tele­media Act (TMG) and the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (DSVGO). I will col­lect, pro­cess and store your per­son­al data exclus­ively for the pro­cessing of inquir­ies and, if neces­sary, for the pro­cessing of orders / con­tracts. Only if you have pre­vi­ously giv­en your con­sent sep­ar­ately, your data will also be used for fur­ther pur­poses that are pre­cisely defined in the con­sent, e.g. for inform­a­tion about offers via news­let­ter, etc.

 

Respons­ible body in the sense of § 13 para. 1 TMG / § 3 para. 7 BDSG

Respons­ible body in the sense of data pro­tec­tion law is:
Silke Rosen­baum Con­sult­ing
USP-Products Silke Rosen­baum-Tiben
Krüse­mannstr. 25
47803 Krefeld
Tel. +49 (0) 172 25 26155
Email: sr@usp-products.com

Domains: https://usp-products.com

Silke Rosen­baum Con­sult­ing as oper­at­or of the web­site https://usp-products.com (here­in­after referred to as “The Web­site”) oper­ates in accord­ance with the pro­vi­sions of the Ger­man Fed­er­al Data Pro­tec­tion Act (BDSG) and the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GSGVO).

Declar­a­tion of consent

This doc­u­ment has been cre­ated to demon­strate efforts to com­ply with data pro­tec­tion laws. This doc­u­ment con­tains the Cook­ie Policy and Cook­ie Con­sent Set­tings to demon­strate con­sent for the time and region indic­ated below. For more inform­a­tion about this doc­u­ment vis­it  https://complianz.io/consent.

Oth­er parts were cre­ated with the Datens­chutz Gen­er­at­or by AdSimple and are marked as such in sections.

  1. Introduction

The Web­site uses cook­ies and sim­il­ar tech­no­lo­gies (for con­veni­ence, all of these are col­lect­ively referred to as “cook­ies”). Cook­ies are also placed by third parties con­trac­ted by us. In the doc­u­ment below I inform you about the use of cook­ies on my website.

  1. What are cookies

A cook­ie is a simple small file that can be sent togeth­er with the pages of an Inter­net address and stored by the web browser on the PC or oth­er device. The inform­a­tion stored in it may be sent to my serv­ers or the serv­ers of rel­ev­ant third parties dur­ing sub­sequent visits.

  1. What are scripts?

A script is a piece of pro­gram code that allows my web­site to func­tion prop­erly and inter­act­ively. This code is executed on my serv­er or on your device.

  1. Cook­ies

4.1 Tech­nic­al or func­tion­al cookies

Some cook­ies ensure that parts of my web­site work prop­erly and that your user pref­er­ences remain known. By pla­cing func­tion­al cook­ies, I make it easi­er for you to vis­it my web­site. This way, when you vis­it my web­site, you do not have to repeatedly enter the same inform­a­tion, or your items remain in your shop­ping cart until you pay, for example. We may place these cook­ies without your consent.

4.2 Ana­lyt­ics cookies

Since stat­ist­ics are col­lec­ted anonym­ously, no per­mis­sion is required to place ana­lyt­ic­al cookies.

4.2.1. Google Ana­lyt­ics pri­vacy policy (cre­ated with the pri­vacy gen­er­at­or by AdSimple)

Google Ana­lyt­ics Pri­vacy Policy Sum­mary
👥 Data sub­jects: Vis­it­ors to the web­site
🤝 Pur­pose: Eval­u­ation of vis­it­or inform­a­tion to optim­ize the web offer..
📓 Pro­cessed data: Access stat­ist­ics, which include data such as loc­a­tions of accesses, device data, access dur­a­tion and time, nav­ig­a­tion beha­vi­or, click beha­vi­or and IP addresses. More details can be found below in this pri­vacy policy.
📅 Stor­age dur­a­tion: depend­ing on the prop­er­ties used
⚖️ Leg­al basis: Art. 6 para. 1 lit. a DSGVO (con­sent), Art. 6 para. 1 lit. f DSGVO (legit­im­ate interests)

4.2.1.1. What is Google Analytics?

We use on my web­site the ana­lys­is track­ing tool Google Ana­lyt­ics (GA) of the Amer­ic­an com­pany Google Inc. For the European area the com­pany Google Ire­land Lim­ited (Gor­don House, Bar­row Street Dub­lin 4, Ire­land) is respons­ible for all Google ser­vices. Google Ana­lyt­ics col­lects data about your actions on my web­site. For example, when you click on a link, this action is stored in a cook­ie and sent to Google Ana­lyt­ics. Using the reports I receive from Google Ana­lyt­ics, I can bet­ter tail­or my web­site and ser­vice to your pref­er­ences. In the fol­low­ing, I 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.

Google Ana­lyt­ics is a track­ing tool used to ana­lyze traffic to my web­site. In order for Google Ana­lyt­ics to work, a track­ing code is built into the code of my web­site. When you vis­it my web­site, this code records vari­ous actions you take on my web­site. Once you leave my web­site, this data is sent to Google Ana­lyt­ics serv­ers and stored there.

Google pro­cesses the data and I receive reports about your user beha­vi­or. These reports may include, but are not lim­ited to:

  • Audi­ence reports: Audi­ence reports help us get to know my users bet­ter and know more pre­cisely who is inter­ested in my service.
  • Ad reports: Ad reports help us ana­lyze and improve my online advertising.
  • Acquis­i­tion reports: Acquis­i­tion reports give us help­ful inform­a­tion on how to attract more people to my service.
  • Beha­vi­or reports: This is where I learn how you inter­act with my web­site. We can track the path you take on my site and which links you click.
  • Con­ver­sion reports: Con­ver­sion is when you take a desired action based on a mar­ket­ing mes­sage. For example, you go from being just a web­site vis­it­or to a buy­er or news­let­ter sub­scriber. These reports help us learn more about how my mar­ket­ing efforts are work­ing for you. This is how I aim to increase my con­ver­sion rate.
  • Real-time reports: Here I always know imme­di­ately what is hap­pen­ing on my web­site. For example, I can see how many users are read­ing this text.

4.2.1.2. Why do I use Google Ana­lyt­ics on my website?

My goal with this web­site is clear: I want to provide you with the best pos­sible ser­vice. The stat­ist­ics and data from Google Ana­lyt­ics help us achieve this goal.

The stat­ist­ic­ally eval­u­ated data shows us a clear pic­ture of the strengths and weak­nesses of my web­site. On the one hand, I can optim­ize my site so that it can be found more eas­ily by inter­ested people on Google. On the oth­er hand, the data helps us to bet­ter under­stand you as a vis­it­or. Thus, I know very well what I need to improve on my web­site in order to provide you with the best pos­sible ser­vice. The data also helps us to carry out my advert­ising and mar­ket­ing meas­ures in a more indi­vidu­al and cost-effect­ive way. After all, it only makes sense to show my products and ser­vices to people who are inter­ested in them.

4.2.1.3. 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­ated with your browser cook­ie. This is how Google Ana­lyt­ics recog­nizes you as a new user. The next time you vis­it my site, you will be recog­nized as a “return­ing” user. All col­lec­ted data is stored togeth­er with this user ID. This makes it pos­sible to eval­u­ate pseud­onym­ous user profiles.

In order to ana­lyze my web­site with Google Ana­lyt­ics, a prop­erty ID must be inser­ted into the track­ing code. The data is then stored in the cor­res­pond­ing prop­erty. For each newly cre­ated prop­erty, the Google Ana­lyt­ics 4 prop­erty is stand­ard. Altern­at­ively, you can also cre­ate the Uni­ver­sal Ana­lyt­ics prop­erty. Depend­ing on the prop­erty used, data is stored for dif­fer­ent lengths of time.

Labels such as cook­ies and app instance IDs are used to meas­ure your inter­ac­tions on my web­site. Inter­ac­tions are all types of actions you take on my web­site. If you also use oth­er Google sys­tems (such as a Google account), data gen­er­ated through Google Ana­lyt­ics may be linked to third-party cook­ies. Google does not share Google Ana­lyt­ics data unless I, as the web­site oper­at­or, author­ize it. Excep­tions may occur if required by law.

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

Name: _ga
Value: 2.1326744211.152311284017–5
Pur­pose: By default, analytics.js uses the _ga cook­ie to store the user ID. Basic­ally, it is used to dis­tin­guish web­site vis­it­ors.
Expir­a­tion date: after 2 years

Name: _gid
Value 2.1687193234.152311284017–1
Pur­pose: The cook­ie is also used to dis­tin­guish the web­site vis­it­ors.
Expir­a­tion date: after 24 hours

Name: _gat_gtag_UA_<property-id>
Value: 1
Inten­ded use: used to lower the request rate. If Google Ana­lyt­ics is deployed via Google Tag Man­ager, this cook­ie will be named _dc_gtm_ <prop­erty-id>.
Expir­a­tion date: after 1 minute

Name: AMP_TOKEN
Value: not spe­cified
Pur­pose: The cook­ie has a token that can be used to retrieve a user ID from the AMP cli­ent ID ser­vice. Oth­er pos­sible val­ues indic­ate a logout, a request, or an error.
Expir­a­tion date: after 30 seconds up to one year.

Name: __utma
Value: 1564498958.1564498958.1564498958.1
Pur­pose: This cook­ie is used to track your beha­vi­or on the web­site and meas­ure per­form­ance. The cook­ie is updated every time inform­a­tion is sent to Google Ana­lyt­ics.
Expir­a­tion date: after 2 years

Name: __utmt
Value: 1
Pur­pose: The cook­ie is used like _gat_gtag_UA_<property-id> to throttle the request rate.
Expir­a­tion date: after 10 minutes

Name: __utmb
Value: 3.10.1564498958
Pur­pose: This cook­ie is used to determ­ine new ses­sions. It is updated every time new data or info is sent to Google Ana­lyt­ics.
Expir­a­tion date: after 30 minutes

Name: __utmc
Value: 167421564
Pur­pose: This cook­ie is used to set new ses­sions for return­ing vis­it­ors. This is a ses­sion cook­ie and is only stored until you close the browser again.
Expir­a­tion date: After you close the browser.

Name: __utmz
Value: m|utmccn=(referral)|utmcmd=referral|utmcct=/
Pur­pose: The cook­ie is used to identi­fy the source of traffic to my web­site. That is, the cook­ie stores from where you came to my web­site. This may have been anoth­er page or an advert­ise­ment.
Expir­a­tion date: after 6 months

Name: __utmv
Value: not spe­cified
Pur­pose: The cook­ie is used to store cus­tom user data. It is updated whenev­er inform­a­tion is sent to Google Ana­lyt­ics.
Expir­a­tion date: after 2 years

Note: This list can­not claim to be com­plete, as Google also changes the choice of their cook­ies again and again.

Here I show you an over­view of the most import­ant data col­lec­ted by Google Analytics:

Heat­maps: Google cre­ates so-called heat­maps. Heat­maps allow you to see exactly those areas that you click on. This gives us inform­a­tion about where you are “on the move” on my site.

Ses­sion dur­a­tion: Google defines ses­sion dur­a­tion as the time you spend on my site without leav­ing. If you have been inact­ive for 20 minutes, the ses­sion ends automatically.

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

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

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

Loc­a­tion: The IP address can be used to determ­ine the coun­try and your approx­im­ate loc­a­tion. This pro­cess is also referred to as IP- loc­a­tion determination.

Tech­nic­al inform­a­tion: Tech­nic­al inform­a­tion includes, but is not lim­ited to, your browser type, inter­net ser­vice pro­vider, or screen resolution.

Source of ori­gin: Google Ana­lyt­ics or I are of course also inter­ested in which web­site or which advert­ise­ment you came to my site from.

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

4.2.1.4. How long and where is the data stored?

Google has your serv­ers spread all over the world. Most serv­ers are loc­ated in Amer­ica and con­sequently your data is mostly stored on Amer­ic­an serv­ers. Here you can read exactly where Google’s data cen­ters are loc­ated:: https://www.google.com/about/datacenters/inside/locations/?hl=de

Your data is dis­trib­uted on dif­fer­ent phys­ic­al data car­ri­ers. This has the advant­age that the data can be retrieved more quickly and is bet­ter pro­tec­ted against manip­u­la­tion. In every Google data cen­ter, there are cor­res­pond­ing emer­gency pro­grams for your data. If, for example, the hard­ware at Google fails or nat­ur­al dis­asters para­lyze serv­ers, the risk of a ser­vice inter­rup­tion at Google still remains low.

The reten­tion peri­od of the data 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 fixed at 14 months. For oth­er so-called event data, I 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 defaults to a reten­tion peri­od of 26 months for your user data. Then your user data is deleted. How­ever, I have the option to choose the reten­tion peri­od of user data ourselves. We have five vari­ants avail­able for this purpose:

  • 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 deleted if you no longer vis­it my web­site with­in the time peri­od I have selec­ted. In this case, the reten­tion peri­od is reset each time you vis­it my web­site again with­in the spe­cified period.

Once the spe­cified peri­od has expired, the data is deleted once a month. This reten­tion peri­od applies to your data asso­ci­ated with cook­ies, user recog­ni­tion and advert­ising IDs (e.g. Double­Click domain cook­ies). Report­ing res­ults are based on aggreg­ated data and are stored sep­ar­ately from user data. Aggreg­ated data is a mer­ging of indi­vidu­al data into a lar­ger unit.

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

Under European Uni­on data pro­tec­tion law, you have the right to obtain inform­a­tion about your data, update it, delete it, or restrict it. Using the browser add-on to dis­able Google Ana­lyt­ics JavaS­cript (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 browser 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­ally want to dis­able, delete or man­age cook­ies (inde­pend­ently of Google Ana­lyt­ics), there are sep­ar­ate instruc­tions for each browser:

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

Safari: Man­age 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 Explorer: 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 pro­cessed out­side the EU. Most third coun­tries (includ­ing the USA) are not con­sidered secure under cur­rent European data pro­tec­tion law. Data to insec­ure third coun­tries may there­fore not simply be trans­ferred, stored and pro­cessed there unless there are suit­able safe­guards (such as EU stand­ard con­trac­tu­al clauses) between us and the non-European ser­vice provider.

4.2.1.6. Leg­al basis

The use of Google Ana­lyt­ics requires your con­sent, which I have obtained with my cook­ie popup. Accord­ing to Art. 6 para. 1 lit. a DSGVO (con­sent), this con­sent con­sti­tutes the leg­al basis for the pro­cessing of per­son­al data as it may occur dur­ing the col­lec­tion by web ana­lyt­ics tools.

In addi­tion to con­sent, there is a legit­im­ate interest on my part to ana­lyze the beha­vi­or of web­site vis­it­ors and thus to improve my offer tech­nic­ally and eco­nom­ic­ally. With the help of Google Ana­lyt­ics, I detect web­site errors, can identi­fy attacks and improve the eco­nom­ic effi­ciency. The leg­al basis for this is Art. 6 para. 1 lit. f DSGVO (Legit­im­ate Interests).

We hope I have been able to provide you with the most import­ant inform­a­tion regard­ing the data pro­cessing of Google Ana­lyt­ics. If you want to learn more about the track­ing ser­vice, I recom­mend these two links: http://www.google.com/analytics/terms/de.html and https://support.google.com/analytics/answer/6004245?hl=de.

4.2.1.7. Google Ana­lyt­ics IP anonymization

We have imple­men­ted Google Ana­lyt­ics IP address anonym­iz­a­tion on this web­site. This fea­ture was developed by Google to enable this web­site to com­ply with applic­able data pro­tec­tion reg­u­la­tions and recom­mend­a­tions of loc­al data pro­tec­tion author­it­ies when they pro­hib­it stor­age of the full IP address. The anonym­iz­a­tion or mask­ing of the IP takes place as soon as the IP addresses arrive at the Google Ana­lyt­ics data col­lec­tion net­work and before any stor­age or pro­cessing of the data takes place.

You can find more inform­a­tion on IP anonym­iz­a­tion at  https://support.google.com/analytics/answer/2763052?hl=de.

4.2.1.8. Google Ana­lyt­ics reports on demo­graph­ic char­ac­ter­ist­ics and interests

We have turned on the advert­ising reports fea­tures in Google Ana­lyt­ics. The demo­graph­ic and interest reports con­tain inform­a­tion on age, gender and interests. This allows us – without being able to assign this data to indi­vidu­al per­sons – to get a bet­ter pic­ture of my users. You can learn more about the advert­ising func­tions at https://support.google.com/analytics/answer/3450482?hl=de_AT&utm_id=ad.

You can stop the use of the activ­it­ies and inform­a­tion of your Google account under “Advert­ising set­tings” on https://adssettings.google.com/authenticated via checkbox.

4.2.1.9. Google Ana­lyt­ics deac­tiv­a­tion link

If you click on the fol­low­ing deac­tiv­a­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 browser, or using anoth­er browser will res­ult in data being col­lec­ted again.

Google Deac­tiv­ate Google Analytics

4.2.1.10 Google Ana­lyt­ics Data Pro­cessing Addendum

We have entered into a dir­ect cus­tom­er agree­ment with Google for the use of Google Ana­lyt­ics by accept­ing the “Data Pro­cessing Addendum” in Google Analytics.

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

4.2.1.11 Google Ana­lyt­ics Google Sig­nals Pri­vacy Policy

We have enabled Google sig­nals in Google Ana­lyt­ics. This updates exist­ing Google Ana­lyt­ics fea­tures (ad reports, remarket­ing, cross-device reports, and interest and demo­graph­ic reports) to get aggreg­ated and anonym­ized data from you if you have allowed per­son­al­ized ads in your Google account.

What makes this spe­cial is that it is cross-device track­ing. That means your data can be ana­lyzed across devices. By enabling Google sig­nals, data is col­lec­ted and linked to the Google account. Google can thus recog­nize, for example, if you view a product on my web­site via a smart­phone and only buy the product later via a laptop. Thanks to the activ­a­tion of Google sig­nals, I can launch cross-device remarket­ing cam­paigns that would oth­er­wise not be pos­sible in this form. Remarket­ing means that I can also show you my offer on oth­er websites.

In Google Ana­lyt­ics, Google sig­nals also col­lect oth­er vis­it­or data such as loc­a­tion, search his­tory, You­Tube his­tory and data about your actions on my web­site. This gives us bet­ter advert­ising reports from Google and more use­ful inform­a­tion about your interests and demo­graph­ics. This includes your age, what lan­guage you speak, where you live, or what gender you are. Fur­ther­more, social cri­ter­ia such as your pro­fes­sion, mar­it­al status or income are also added. All these char­ac­ter­ist­ics help Google Ana­lyt­ics to define groups of people or tar­get groups.

The reports also help us to bet­ter assess your beha­vi­or, your wishes and interests. This allows us to optim­ize and adapt my ser­vices and products for you. By default, this data expires after 26 months. Please note that this data col­lec­tion only occurs if you have allowed per­son­al­ized advert­ising in your Google account. This is always aggreg­ated and anonym­ous data and nev­er indi­vidu­al per­son data. In your Google account, you can man­age this data or delete it.

.

4.2.2. Google Site Kit (cre­ated with the Datens­chutz Gen­er­at­or by AdSimple)

Google Site Kit Pri­vacy Declar­a­tion (Sum­mary)
👥 Data sub­jects: Vis­it­ors to the web­site
🤝 Pur­pose: Eval­u­ation of vis­it­or inform­a­tion to optim­ize the web offer..
📓 Pro­cessed data: Access stat­ist­ics, which include data such as loc­a­tions of accesses, device data, access dur­a­tion and time, nav­ig­a­tion beha­vi­or, click beha­vi­or and IP addresses. More details can be found below in this pri­vacy policy.
📅 Stor­age dur­a­tion: depend­ing on the prop­er­ties used
⚖️ Leg­al basis: Art. 6 para. 1 lit. a DSGVO (con­sent), Art. 6 para. 1 lit. f DSGVO (legit­im­ate interests)

4.2.2.1. What is Google Site Kit?

We have integ­rated the Word­Press plu­gin Google Site Kit of the Amer­ic­an com­pany Google Inc. into my web­site. For the European area, the com­pany Google Ire­land Lim­ited (Gor­don House, Bar­row Street Dub­lin 4, Ire­land) is respons­ible for all Google ser­vices. With Google Site Kit, I can quickly and eas­ily view stat­ist­ics that come from vari­ous Google products such as Google Ana­lyt­ics dir­ectly in my Word­Press dash­board. The tool or the tools included in Google Site Kit also col­lect, among oth­er things, per­son­al data from you. In this pri­vacy policy, I explain why I use Google Site Kit, how long and where data is stored and which oth­er pri­vacy texts are rel­ev­ant for you in this context.

Google Site Kit is a plu­gin for the Word­Press con­tent man­age­ment sys­tem. With this plu­gin, I can view import­ant stat­ist­ics for web­site ana­lys­is dir­ectly in my dash­board. These are stat­ist­ics that are col­lec­ted by oth­er Google products. First and fore­most, from Google Ana­lyt­ics. Besides Google Ana­lyt­ics, Google Search Con­sole, Page Speed Insight, Google AdSense, Google Optim­ize and Google Tag Man­ager ser­vices can also be linked to Google Site Kit.

4.2.2.2. Why I use Google Site Kit on my website?

As a ser­vice pro­vider, it is my job to offer you the best pos­sible exper­i­ence on my web­site. You should feel com­fort­able on my web­site and find exactly what you are look­ing for quickly and eas­ily. Stat­ist­ic­al eval­u­ations help us to get to know you bet­ter and to adapt my offer to your wishes and interests. We use vari­ous Google tools for these eval­u­ations. Site Kit makes my work much easi­er in this regard, because I can view and ana­lyze the stat­ist­ics of Google products right in the dash­board. So I don’t have to log in sep­ar­ately for each tool. Site Kit thus always provides a good over­view of the most import­ant ana­lys­is data.

4.2.2.3. What data is stored by Google Site Kit?

If you have act­ively agreed to track­ing tools in the cook­ie notice (also called script or ban­ner), Google products such as Google Ana­lyt­ics will set cook­ies and send data about you, such as your user beha­vi­or, to Google, where it will be stored and pro­cessed. This also includes per­son­al data such as your IP address.

For more detailed inform­a­tion on the indi­vidu­al ser­vices, I have sep­ar­ate text sec­tions in this pri­vacy policy. For example, take a look at my pri­vacy policy on Google Ana­lyt­ics. Here I go into great detail about the data col­lec­ted. You will learn how long Google Ana­lyt­ics stores, man­ages and pro­cesses data, which cook­ies may be used and how you can pre­vent data stor­age. Like­wise, I also have my own pri­vacy state­ments with com­pre­hens­ive inform­a­tion for oth­er Google ser­vices, such as Google Tag Man­ager or Google AdSense.

In the fol­low­ing, I show you exem­plary Google Ana­lyt­ics cook­ies that can be set in your browser, provided that you have agreed in prin­ciple to data pro­cessing by Google. Please note that these cook­ies are only a selection:

Name: _ga
Value:2.1326744211.152311284017–2
Pur­pose: By default, analytics.js uses the _ga cook­ie to store the user ID. Basic­ally, it is used to dis­tin­guish web­site vis­it­ors.
Expir­a­tion date: after 2 years

Name: _gid
Value:2.1687193234.152311284017–7
Pur­pose: This cook­ie is also used to dis­tin­guish web­site vis­it­ors.
Expir­a­tion date: after 24 hours

Name: _gat_gtag_UA_<property-id>
Value: 1
Pur­pose: This cook­ie is used to lower the request rate.
Expir­a­tion date: after 1 minute

4.2.2.4. How long and where is the data stored?

Google stores col­lec­ted data on its own Google serv­ers, which are dis­trib­uted world­wide. Most serv­ers are loc­ated in the United States and there­fore it is eas­ily pos­sible that your data is also stored there. At https://www.google.com/about/datacenters/inside/locations/?hl=de you can see exactly where the com­pany provides servers.

Data col­lec­ted by Google Ana­lyt­ics is kept for a stand­ard 26 months. After that, your user data is deleted. The reten­tion peri­od applies to all data linked to cook­ies, user recog­ni­tion and advert­ising IDs.

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

You always have the right to obtain inform­a­tion about your data, to have your data deleted, cor­rec­ted or restric­ted. In addi­tion, you can also dis­able, delete or man­age cook­ies in your browser at any time. Here I show you the cor­res­pond­ing instruc­tions for the most pop­u­lar browsers

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

Safari: Man­age 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 Explorer: 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 pro­cessed out­side the EU. Most third coun­tries (includ­ing the USA) are not con­sidered secure under cur­rent European data pro­tec­tion law. Data to insec­ure third coun­tries may there­fore not simply be trans­ferred, stored and pro­cessed there unless there are suit­able safe­guards (such as EU stand­ard con­trac­tu­al clauses) between us and the non-European ser­vice provider.

4.2.2.6. Leg­al basis

The use of Google Site Kit requires your con­sent, which I have obtained with my cook­ie popup. Accord­ing to Art. 6 para. 1 lit. a DSGVO (con­sent), this con­sent con­sti­tutes the leg­al basis for the pro­cessing of per­son­al data, as may occur dur­ing the col­lec­tion by web ana­lyt­ics tools.

In addi­tion to con­sent, there is a legit­im­ate interest on my part in ana­lyz­ing the beha­vi­or of web­site vis­it­ors and thus improv­ing my offer tech­nic­ally and eco­nom­ic­ally. With the help of Google Site Kit, I detect web­site errors, can identi­fy attacks and improve the eco­nom­ic effi­ciency. The leg­al basis for this is Art. 6 para. 1 lit. f DSGVO (Legit­im­ate Interests).

To learn more about Google’s data pro­cessing, I recom­mend that you read Google’s com­pre­hens­ive pri­vacy policy at. https://policies.google.com/privacy?hl=de.

4.3 Social Media

4.3.1. Linked­In Pri­vacy Declaration

(Cre­ated with the Datens­chutz Gen­er­at­or by AdSimple)

Linked­In Pri­vacy Declar­a­tion Sum­mary
👥 Data sub­jects: Vis­it­ors to the web­site
🤝 Pur­pose: Optim­iz­a­tion of my ser­vice per­form­ance
📓 Pro­cessed Data: Data such as user beha­vi­or data, inform­a­tion about your device and your IP address.
📅 Stor­age peri­od: the data is deleted with­in 30 days in prin­ciple
⚖️ Leg­al basis: Art. 6 para. 1 lit. a DSGVO (con­sent), Art. 6 para. 1 lit. f DSGVO (legit­im­ate interests)

4.3.1.1. What is LinkedIn?

We use social plug-ins of the social media net­work Linked­In, of the com­pany Linked­In Cor­por­a­tion, 2029 Sti­er­lin Court, Moun­tain View, CA 94043, USA on my web­site. The social plug-ins may be feeds, con­tent shar­ing or links to my Linked­In page. The social plug-ins are clearly marked with the famil­i­ar Linked­In logo and allow, for example, inter­est­ing con­tent to be shared dir­ectly via my web­site. For the European Eco­nom­ic Area and Switzer­land, Linked­In Ire­land Unlim­ited Com­pany Wilton Place in Dub­lin is respons­ible for data processing.

By embed­ding such plug-ins, data can be sent to Linked­In, stored and pro­cessed there. In this pri­vacy policy, I 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.

Linked­In is the largest social net­work for busi­ness con­tacts. Unlike Face­book, for example, the com­pany focuses exclus­ively on build­ing busi­ness con­tacts. Com­pan­ies can present ser­vices and products on the plat­form and estab­lish busi­ness rela­tion­ships. Many people also use Linked­In to look for jobs or to find suit­able employ­ees for their own com­pany. In Ger­many alone, the net­work has over 11 mil­lion mem­bers. In Aus­tria, there are about 1.3 million.

4.3.1.2 Why do I use Linked­In on my website?

We know how busy you are. That’s why I can­’t fol­low all social media chan­nels indi­vidu­ally. Even if it would be worth it, as in my case. Because time and again I post inter­est­ing news or reports that are worth spread­ing. That’s why I’ve made it pos­sible on my web­site to share inter­est­ing con­tent dir­ectly on Linked­In or to link dir­ectly to my Linked­In page. We con­sider built-in social plug-ins as an exten­ded ser­vice on my web­site. The data that Linked­In col­lects also helps us to show pos­sible advert­ising meas­ures only to people who are inter­ested in my offer.

4.3.1.3.. What data is stored by LinkedIn?

Linked­In does not store any per­son­al data merely by integ­rat­ing the social plug-ins. Linked­In calls this data gen­er­ated by plug-ins pass­ive impres­sions. How­ever, when you click on a social plug-in to share my con­tent, for example, the plat­form stores per­son­al data as so-called “act­ive impres­sions”. And this is regard­less of wheth­er you have a Linked­In account or not. If you are logged in, the col­lec­ted data is assigned to your account.

Your browser estab­lishes a dir­ect con­nec­tion to LinkedIn’s serv­ers when you inter­act with my plug-ins. In this way, the com­pany logs vari­ous usage data. In addi­tion to your IP address, this can be login data, device inform­a­tion or info about your inter­net or mobile pro­vider, for example. If you access Linked­In ser­vices via your smart­phone, your loc­a­tion (after you have allowed this) can also be determ­ined. Linked­In may also share this data in “hashed” form with third-party advert­isers. 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­vidu­als can no longer be identified.

Most data about your user beha­vi­or is stored in cook­ies. These are small text files that are usu­ally set in your browser. Fur­ther­more, Linked­In can also use web beacons, pixel tags, dis­play tags and oth­er device identifiers.

Vari­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 exhaust­ive and is provided as an example only. The fol­low­ing cook­ies were set without being logged in to LinkedIn:

Name: bcook­ie
Wert: =2&34aab2aa-2ae1-4d2a-8baf-c2e2d7235c16311284017-
Pur­pose: The cook­ie is a so-called “browser ID cook­ie” and con­sequently stores your iden­ti­fic­a­tion num­ber (ID).
Expir­a­tion date: After 2 years

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

Name: lidc
Value: 1818367:t=1571904767:s=AQF6KNnJ0G311284017…
Pur­pose: This cook­ie is used for rout­ing. Rout­ing records the ways you came to Linked­In and how you nav­ig­ate through the web­site there.
Expir­a­tion date: after 24 hours

Name: rtc
Value: kt0lrv3NF3x3t6xvDgGrZGDKkX
Pur­pose: No fur­ther inform­a­tion could be found about this cook­ie.
Expir­a­tion date: after 2 minutes

Name: JSESSIONID
Value: ajax:3112840172900777718326218137
Pur­pose: This is a ses­sion cook­ie that Linked­In uses to main­tain anonym­ous user ses­sions through the serv­er.
Expir­a­tion date: after the end of the session

Name: bscook­ie
Value: “v=1&201910230812…
Pur­pose: This cook­ie is a secur­ity cook­ie. Linked­In describes it as a secure browser ID cook­ie.
Expir­a­tion date: after 2 years

Name: fid
Value: AQHj7Ii23ZBcqAAAA…
Pur­pose: No fur­ther inform­a­tion could be found about this cook­ie.
Expir­a­tion date: after 7 days

4.3.1.4 How long and where is the data stored?

In prin­ciple, Linked­In retains your per­son­al data for as long as the com­pany con­siders it neces­sary to provide its own ser­vices. How­ever, Linked­In deletes your per­son­al data when you delete your account. In some excep­tion­al cases, Linked­In retains some data in aggreg­ate and anonym­ized form even after you delete your account. Once you delete your account, oth­er people will not be able to see your data with­in one day. Linked­In gen­er­ally deletes data with­in 30 days. How­ever, Linked­In retains data if it is neces­sary due to leg­al oblig­a­tion. Data that can no longer be assigned to indi­vidu­als remain stored even after the account is closed. The data is stored on vari­ous serv­ers in Amer­ica and pre­sum­ably also in Europe.

4.3.1.5 How can I 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 Linked­In 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 Linked­In profile:

In Linked­In, click on your pro­file icon and select the “Set­tings and Pri­vacy” sec­tion. Now click on “Pri­vacy” and then in the “How Linked­In uses your data” sec­tion click on “Change”. In just a short time, you will be able to down­load selec­ted data about your web activ­ity and account history.

You also have the option in your browser to pre­vent Linked­In from pro­cessing your data. As men­tioned above, Linked­In stores most data via cook­ies that are set in your browser. You can man­age, deac­tiv­ate or delete these cook­ies. Depend­ing on which browser you have, the man­age­ment works slightly dif­fer­ently. 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­age 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 Explorer: delete and man­age cookies

Microsoft Edge: delete and man­age cookies

You can also basic­ally set up your browser so that you are always informed when a cook­ie is to be set. Then you can always decide indi­vidu­ally wheth­er you want to allow the cook­ie or not.

Please note that when using this tool, data from you may also be stored and pro­cessed out­side the EU. Most third coun­tries (includ­ing the USA) are not con­sidered secure under cur­rent European data pro­tec­tion law. Data to insec­ure third coun­tries may there­fore not simply be trans­ferred, stored and pro­cessed there unless there are suit­able safe­guards (such as EU stand­ard con­trac­tu­al clauses) between us and the non-European ser­vice provider.

4.3.1.6.. Leg­al basis

If you have con­sen­ted that data from you can be pro­cessed and stored by integ­rated social media ele­ments, this con­sent is con­sidered the leg­al basis for data pro­cessing (Art. 6 para. 1 lit. a DSGVO). In prin­ciple, your data will also be stored and pro­cessed on the basis of my legit­im­ate interest (Art. 6 para. 1 lit. f DSGVO) in fast and good com­mu­nic­a­tion with you or oth­er cus­tom­ers and busi­ness part­ners. Most social media plat­forms also set cook­ies in your browser to store data. That is why I recom­mend that you read my pri­vacy text about cook­ies care­fully and view the pri­vacy policy or cook­ie policy of the respect­ive ser­vice provider.

We have tried to bring you closer to the most import­ant inform­a­tion about data pro­cessing by LinkedIn.

Learn more at https://www.linkedin.com/legal/privacy-policy about data pro­cessing by LinkedIn.

4.3.2. XING Pri­vacy Declaration

(Cre­ated with the Datens­chutz Gen­er­at­or by AdSimple)

Xing Pri­vacy Declar­a­tion Sum­mary
Linked­In Pri­vacy Declar­a­tion Sum­mary
👥 Data sub­jects: Vis­it­ors to the web­site
🤝 Pur­pose: Optim­iz­a­tion of my ser­vice per­form­ance
📓 Pro­cessed Data: Data such as user beha­vi­or data, inform­a­tion about your device and your IP address.
📅 Stor­age peri­od: the data is deleted with­in 30 days in prin­ciple
⚖️ Leg­al basis: Art. 6 para. 1 lit. a DSGVO (con­sent), Art. 6 para. 1 lit. f DSGVO (legit­im­ate interests)

4.3.2.1. What is Xing?

We use social plu­gins of the social media net­work Xing, of the com­pany Xing SE, Dam­mt­or­straße 30, 20354 Ham­burg, Ger­many, on my web­site. Through these func­tions, you can, for example, share con­tent on Xing dir­ectly via my web­site, log in via Xing or fol­low inter­est­ing con­tent. You can recog­nize the plug-ins by the com­pany 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 serv­ers”, stored and ana­lyzed. In this pri­vacy policy, I want to inform you about what data is involved and how you can man­age or pre­vent this data storage.

Xing is a social net­work with its headquar­ters in Ham­burg. The com­pany spe­cial­izes in man­aging pro­fes­sion­al con­tacts. That is, unlike oth­er net­works, Xing is primar­ily about pro­fes­sion­al net­work­ing. The plat­form is often used for job searches or to find employ­ees for one’s own com­pany. In addi­tion, Xing offers inter­est­ing con­tent on vari­ous pro­fes­sion­al top­ics. The glob­al coun­ter­part is the Amer­ic­an com­pany LinkedIn.

4.3.2.2.. Why do I use Xing on my website?

There is now a flood of social media chan­nels and I are well aware that your time is very pre­cious. Not every company’s social media chan­nel can be closely scru­tin­ized. That’s why I want to make your life as easy as pos­sible, so you can share or fol­low inter­est­ing con­tent dir­ectly from my web­site on Xing. With such “social plug-ins” I extend my ser­vice on my web­site. In addi­tion, the data col­lec­ted by Xing helps us to carry out tar­geted advert­ising meas­ures on the plat­form. This means that my ser­vice is only shown to people who are really inter­ested in it.

4.3.2.3 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 browser con­nects to serv­ers 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 dir­ect 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­ation of your user beha­vi­or takes place. You can obtain more inform­a­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 browser when you inter­act with the plug-in or click on it. Here, per­son­al data such as your IP address, browser data, date and time of your page view on Xing may be stored. If you have a XING account and are logged in, col­lec­ted 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 browser 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 I can­not claim completeness:

Name: AMCVS_0894FF2554F733210A4C98C6%40AdobeOrg
Value: 1
Pur­pose: This cook­ie is used to cre­ate and store web­site vis­it­or iden­ti­fi­ers.
Expir­a­tion date: after end of session

Name: c_
Value: 157c609dc9fe7d7ff56064c6de87b019311284017‑8
Pur­pose: We could not find out more inform­a­tion about this cook­ie.
Expir­a­tion date: after one day

Name: pre­vPage
Value: wbm%2FWelcome%2Flogin
Pur­pose: This cook­ie stores the URL of the pre­vi­ous web page you vis­ited.
Expir­a­tion date: after 30 minutes

Name: s_cc
Value: true
Pur­pose: This Adobe Site Cata­lyst cook­ie determ­ines wheth­er cook­ies are gen­er­ally enabled in the browser.
Expir­a­tion date: after end of session

Name: s_fid
Value: 6897CDCD1013221C-39DDACC982217CD1311284017‑2
Pur­pose: This cook­ie is used to identi­fy a unique vis­it­or.
Expir­a­tion date: after 5 years

Name: visitor_id
Value fe59fbe5-e9c6-4fca-8776–30d0c1a89c32
Pur­pose: The vis­it­or cook­ie con­tains a unique vis­it­or ID and the unique iden­ti­fi­er for your account.
Expir­a­tion date: after 2 years

Name:_session_id
Value: 533a0a6641df82b46383da06ea0e84e7311284017‑2
Pur­pose: This cook­ie cre­ates a tem­por­ary ses­sion ID that is used as an in-ses­sion user ID. The cook­ie is abso­lutely neces­sary to provide the fea­tures of Xing.
Expir­a­tion date: after the end of the session.

As soon as you are logged in or a mem­ber of Xing, fur­ther per­son­al data is def­in­itely col­lec­ted, pro­cessed and stored. Xing also dis­closes per­son­al data to third parties if this is neces­sary for the ful­fill­ment of its own busi­ness pur­poses, if you have giv­en your con­sent, or if there is a leg­al obligation.

4.3.2.4. Wie lange und wo wer­den die Daten gespeichert?

Xing stores the data on vari­ous serv­ers in vari­ous data cen­ters. The com­pany stores this data until you delete the data or until a user account is deleted. Of course, this only affects users who are already Xing members.

4.3.2.5 How can I 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 browser to pre­vent pos­sible data pro­cessing or man­age it accord­ing to your wishes. Most data is stored via cook­ies. Depend­ing on which browser you have, the man­age­ment works slightly dif­fer­ently. 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­age 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 Explorer: delete and man­age cookies

Microsoft Edge: delete and man­age cookies

You can also basic­ally set up your browser so that you are always informed when a cook­ie is to be set. Then you can always decide indi­vidu­ally wheth­er you want to allow the cook­ie or not.

4.3.2.6 Leg­al basis

If you have con­sen­ted that data from you can be pro­cessed and stored by integ­rated social media ele­ments, this con­sent is con­sidered the leg­al basis for data pro­cessing (Art. 6 para. 1 lit. a DSGVO). In prin­ciple, your data will also be stored and pro­cessed on the basis of my legit­im­ate interest (Art. 6 para. 1 lit. f DSGVO) in fast and good com­mu­nic­a­tion with you or oth­er cus­tom­ers and busi­ness part­ners. Most social media plat­forms also set cook­ies in your browser to store data. That is why I recom­mend that you read my pri­vacy text about cook­ies care­fully and view the pri­vacy policy or cook­ie policy of the respect­ive ser­vice provider.

We have tried to bring you closer to the most import­ant inform­a­tion about data pro­cessing by Xing.

Learn more at https://privacy.xing.com/de/datenschutzerklaerung about data pro­cessing by Xing.

4.4.7. Google Fonts Pri­vacy Declaration

(Cre­ated with the Datens­chutz Gen­er­at­or by AdSimple)

On my web­site I use Google Fonts of the com­pany Google Inc. For the European area the com­pany Google Ire­land Lim­ited (Gor­don House, Bar­row Street Dub­lin 4, Ire­land) is respons­ible. We have embed­ded the Google fonts loc­ally, i.e. on my web serv­er – not on Google’s serv­ers. As a res­ult, there is no con­nec­tion to Google serv­ers and thus no data trans­mis­sion or storage.

4.4.7.1 What are Google Fonts?

Google Fonts used to be called Google Web Fonts. This is an inter­act­ive dir­ect­ory of over 800 fonts that Google provides free of charge. With Google Fonts, you could use fonts without upload­ing them to your own serv­er. How­ever, in order to pre­vent any inform­a­tion trans­fer to Google serv­ers in this regard, I have down­loaded the fonts to my serv­er. This way I act pri­vacy com­pli­ant and do not send any data to Google Fonts.

  1. Host­ing United Domains

The web­site is hos­ted by United Domains AG.

Respons­ible for the col­lec­tion of data on united-domains.de is the

united-domains AG
Gautinger street 10
82319 Star­n­berg
Phone 08151 / 36867–0
Fax 08151 / 36867–77
support@united-domains.de

You can find inform­a­tion about data pro­tec­tion at https://www.united-domains.de/unternehmen/datenschutz/

You can find the imprint at:  https://www.united-domains.de/unternehmen/kontakt/

If you have any ques­tions, please send an email to support@united-domains.de or use the con­tact form to United Domains AG. The data will be pro­cessed in Ger­many on the serv­ers of my ser­vice pro­vider OTRS AG, Zim­mersmüh­len­weg 11, 61440 Oberursel

  1. Your rights in rela­tion to per­son­al data

They have the fol­low­ing rights in rela­tion to your per­son­al data:

They have the right to know why your per­son­al data is needed, what hap­pens to it and how long it is kept.

Right of access: You have the right to access your per­son­al data known to us. Right to rec­ti­fic­a­tion: you have the right whenev­er you wish to sup­ple­ment, cor­rect and have your per­son­al data deleted or blocked.

If you have giv­en us con­sent to pro­cess your data, you have the right to with­draw this con­sent and have your per­son­al data deleted. Right to trans­fer your data: you have the right to request all your per­son­al data from one con­trol­ler and to trans­fer it in its entirety to anoth­er controller.

Right to object: you can object to the pro­cessing of your data. We com­ply with this unless there are legit­im­ate grounds for the processing.

To exer­cise these rights please con­tact us. Please refer to the con­tact details at the end of this Cook­ie State­ment. If you have a com­plaint about how I handle your data, I would like to hear it, but you also have the right to address it to the super­vis­ory author­ity (the Data Pro­tec­tion Authority).

  1. Activation/deactivation and dele­tion of cookies

You can use your Inter­net browser to delete cook­ies auto­mat­ic­ally or manu­ally. You can also spe­cify that cer­tain cook­ies may not be placed. Anoth­er option is to change your Inter­net browser set­tings so that you receive a mes­sage each time a cook­ie is set. For more inform­a­tion on these options, find the instruc­tions in your browser’s help section.

Please note that my web­site may not func­tion prop­erly if all cook­ies are dis­abled.  If you delete the cook­ies in your browser, they will be re-placed when you vis­it my web­site again.

  1. Cook­ie con­sent settings

 

block_ajax_content => set_cookies_on_root => cookie_domain => do_not_track => con­sent­type => opt­in region => eu

geoip => 1 checkbox_style => slider use_categories => vis­ible use_categories_optinstats => hidden

accept => accept cookies

revoke => Man­age con­sent dis­miss => Func­tion­al cook­ies only dismiss_timeout => 10 readmore_optin => Cook­ie policy readmore_imprint => Imprint accept_informational => Accept

message_optout => We use cook­ies to optim­ize my web­site and service.

message_optin => We use cook­ies to optim­ize my web­site and service.

readmore_optout => Cook­ie Policy

readmore_optout_dnsmpi => Do Not Sell My Per­son­al Inform­a­tion soft_cookiewall =>

dismiss_on_scroll => dismiss_on_timeout => cookie_expiry => 365 tcf_active =>

view_preferences => view pref­er­ences save_preferences => save pref­er­ences accept_all => accept all

privacy_link_us => #

All texts are pro­tec­ted by copyright.

Source: Cre­ated with Datens­chutz Gen­er­at­or by AdSimple

Trans­lated with www.DeepL.com/Translator (free version)