Data Protection Declaration according to the GDPR

General

Name and address of the responsible person

The respon­si­ble per­son with­in the mean­ing of the Gen­er­al Data Pro­tec­tion Reg­u­la­tion and oth­er nation­al data pro­tec­tion laws of the mem­ber states as well as oth­er data pro­tec­tion reg­u­la­tions is:

Thomas Nowot­ny
Wal­lauer Str. 37
65191 Wies­baden
Mobile: +4916099137571

Mail: expertise@thomasnowotny.de

Web: www.thomasnowotny.de

Ger­many

Domains: www.thomasnowotny.de

Name and address of the data protection officer

The data pro­tec­tion offi­cer of the respon­si­ble par­ty is:

Thomas Nowot­ny
Wal­lauer Str. 37
65191 Wies­baden
Mobile: +4916099137571

Mail: expertise@thomasnowotny.de

Web: www.thomasnowotny.de

Ger­many

Domains: www.thomasnowotny.de

Thomas Nowot­ny as oper­a­tor of the web­site www.thomasnowotny.de works accord­ing to the reg­u­la­tions of the Fed­er­al Data Pro­tec­tion Act (BDSG) and the Gen­er­al Data Pro­tec­tion Reg­u­la­tion (GSG­VO).

Declaration of consent

This doc­u­ment has been cre­at­ed to demon­strate efforts to com­ply with pri­va­cy laws. This doc­u­ment con­tains the Cook­ie Pol­i­cy and Cook­ie Con­sent Set­tings to demon­strate con­sent for the time and region indi­cat­ed below. For more infor­ma­tion about this doc­u­ment, find it at https://complianz.io/consent.

This Cook­ie Pol­i­cy was last updat­ed on Feb­ru­ary 11, 2021 and applies to cit­i­zens of the Euro­pean Eco­nom­ic Zone.

1. Introduction

My web­site, www.thomasnowotny.de (here­inafter: “The Web­site”) uses cook­ies and sim­i­lar tech­nolo­gies (for con­ve­nience, all of these are col­lec­tive­ly referred to as “Cook­ies”). Cook­ies are also placed by third par­ties con­tract­ed by us. In the doc­u­ment below we inform you about the use of cook­ies on our website.

2. What are cookies

A cook­ie is a sim­ple small file that can be sent along with the pages of an Inter­net address and stored by the web brows­er on the PC or oth­er device. The infor­ma­tion stored in it can be sent to our servers or the servers of rel­e­vant third par­ties dur­ing sub­se­quent visits.

2.1. What are scripts?

A script is a piece of pro­gram code that allows our web­site to func­tion prop­er­ly and inter­ac­tive­ly. This code is exe­cut­ed on our serv­er or on your device.

3. Analytics Germanized for Google Analytics (GDPR / DSGVO)

3.1. What is Anal­i­tics Ger­man­ized for Google Analytics?

We use on our web­site the plu­g­in Anal­i­tics Ger­man­ized for Google Ana­lyt­ics by Pas­cal Bajo­rat (Bajo­rat Media) — web design­er and Word­Press devel­op­er from Berlin. We have made the fol­low­ing settings:

  • IP anno­myn­ni­sa­tion enabled
  • Demo­graph­ic and inter­est reports not enabled
  • Out­bound link track­ing not enabled
  • Advanced link attri­bu­tion not enabled
  • Con­sid­er­a­tion of “Do Not Track” head­ers enabled

3.2 What are the fea­tures in general?

Google Ana­lyt­ics pre-con­fig­ured to com­ply with EU law (GDPR / DSG­VO) and with many advanced Ana­lyt­ics set­tings for exten­sive track­ing capabilities.

With this plu­g­in, you can inte­grate Google Ana­lyt­ics in com­pli­ance with EU law and data pro­tec­tion. For this, you only need to enter your Google Ana­lyt­ics ID in the gen­er­al set­tings. Oth­er set­tings (e.g. AnonymizeIP) are pre­con­fig­ured accord­ing­ly and only need to be changed if required or if you want to add extensions.

For a pri­va­cy-com­pli­ant inte­gra­tion, it is nec­es­sary that you clar­i­fy the use of Google Ana­lyt­ics in your pri­va­cy pol­i­cy. In addi­tion, a pos­si­bil­i­ty for an opt-out from Google Ana­lyt­ics must be cre­at­ed. For the opt-out, you can use the short­code described in the Gen­er­al tab, point 3.

In the advanced set­tings, func­tions of Google Ana­lyt­ics can be acti­vat­ed. Cor­re­spond­ing infor­ma­tion can be found in the settings.

  • FUNC­TIONS OF GOOGLE ANA­LYT­ICS GERMANIZED
  • Easy Google Ana­lyt­ics inte­gra­tion, only the UA ID is need­ed, every­thing else is preconfigured
  • Pre­con­fig­ured to com­ply with EU law
  • Cook­ie Con­sent inte­gra­tion for EU cook­ie law
  • Com­pat­i­ble with Google Site Tag and Uni­ver­sal Ana­lyt­ics code (you have a choice)
  • Google Ana­lyt­ics opt-out link short­code for your pri­va­cy policy
  • Google Ana­lyt­ics inte­gra­tion can be dis­abled and you can use opt-out as a stand­alone fea­ture (com­pat­i­ble with oth­er Google Ana­lyt­ics plugins)
  • Com­pat­i­ble with the opt-out links gen­er­at­ed by eRecht24
  • Anonymize IP is inte­grat­ed and enabled by default
  • Demo­graph­ic and inter­est reports
  • Out­bound link tracking
  • Improved link attribution
  • Inte­gra­tion of cus­tom code
  • Sup­port for “Do Not Track” headers
  • WPML sup­port

LICENSE
GNU Gen­er­al Pub­lic License v.3 — http://www.gnu.org/licenses/gpl‑3.0.html

4. Cookies

4.1 Tech­ni­cal or func­tion­al cookies

Some cook­ies ensure that parts of our web­site func­tion prop­er­ly and that your user pref­er­ences remain known. By plac­ing func­tion­al cook­ies, we make it eas­i­er for you to vis­it our web­site. This way, when you vis­it our site, you do not have to repeat­ed­ly enter the same infor­ma­tion, or your items remain in your shop­ping cart until you pay, for exam­ple. We may place these cook­ies with­out your consent.

4.2 Analy­sis cookies

Since sta­tis­tics are col­lect­ed anony­mous­ly, no per­mis­sion is required to place ana­lyt­ic cookies.

4.2.1 Google Ana­lyt­ics Pri­va­cy Pol­i­cy (cre­at­ed with AdSim­ple’s Pri­va­cy Gen­er­a­tor)

Google Ana­lyt­ics Pri­va­cy Pol­i­cy Sum­ma­ry
👥 Data sub­jects: Vis­i­tors to the web­site.
🤝 Pur­pose: Eval­u­a­tion of vis­i­tor infor­ma­tion to opti­mize the web offer.
📓 Data processed: Access sta­tis­tics, which include data such as loca­tions of access­es, device data, access dura­tion and time, nav­i­ga­tion behav­ior, click behav­ior, and IP address­es. More details can be found fur­ther down in this pri­va­cy pol­i­cy.
📅 Stor­age dura­tion: depend­ing on the prop­er­ties used.
Legal basis: Art. 6 para. 1 lit. a DSG­VO (Con­sent), Art. 6 para. 1 lit. f DSG­VO (Legit­i­mate Interests).

4.2.1.1 What is Google Analytics?

We use the analy­sis track­ing tool Google Ana­lyt­ics (GA) of the Amer­i­can com­pa­ny Google Inc. on 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. 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.

Google Ana­lyt­ics is a track­ing tool used to ana­lyze traf­fic to 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 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: through audi­ence reports, we 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 web­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.

4.2.1.2 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.

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 that is linked to 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 makes it pos­si­ble to eval­u­ate pseu­do­ny­mous user profiles.

In order 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 stan­dard. 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.

Labels such as cook­ies and app instance IDs are used to 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
Wert: 2.1326744211.152311284017 – 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
Wert: 2.1687193234.152311284017 – 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_<property-id>
Val­ue: 1
Intend­ed use: 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_ <prop­er­ty-id>.
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_<property-id> 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 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 is always chang­ing the choice of their cook­ies as well.

Here we show you an overview of the most impor­tant data col­lect­ed by 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.

4.2.1.4 How long and where is the data stored?

Google has dis­trib­uted its servers 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. You can find out exact­ly where Google’s data cen­ters are locat­ed here: https://www.google.com/about/datacenters/inside/locations/?hl=de.

Your data is dis­trib­uted on dif­fer­ent phys­i­cal disks. This has the advan­tage that the data can be accessed more quick­ly and is bet­ter pro­tect­ed against manip­u­la­tion. In each Google data cen­ter, there are cor­re­spond­ing emer­gency pro­grams for your data. If, for exam­ple, the hard­ware at Google fails or nat­ur­al dis­as­ters par­a­lyze servers, 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, 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 defaults to a 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. 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 an option for data to be delet­ed only when you no longer vis­it our web­site with­in the time peri­od we have select­ed. In this case, the reten­tion peri­od will be 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.

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

Accord­ing to 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­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 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.

4.2.1.6 Legal basis

The use of Google Ana­lyt­ics requires your con­sent, which we have obtained with our cook­ie pop­up. Accord­ing to Art. 6 Para. 1 lit. a DSG­VO (con­sent), this con­sent con­sti­tutes the legal basis for the pro­cess­ing 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­i­mate inter­est on our part to ana­lyze the behav­ior of web­site vis­i­tors and thus to improve our offer tech­ni­cal­ly and eco­nom­i­cal­ly. With the help of Google Ana­lyt­ics, we detect web­site errors, can iden­ti­fy attacks and improve the eco­nom­ic effi­cien­cy. The legal basis for this is Art. 6 para. 1 lit. f DSG­VO (Legit­i­mate Interests).

We hope we have been able to pro­vide you with the most impor­tant infor­ma­tion regard­ing the data pro­cess­ing of Google Ana­lyt­ics. 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.

4.2.1.7 Google Ana­lyt­ics IP anonymization

We have imple­ment­ed Google Ana­lyt­ics IP address anonymiza­tion on this web­site. This func­tion 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 if they pro­hib­it 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 on IP anonymiza­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­is­tics and interests.

We have enabled adver­tis­ing report­ing fea­tures in Google Ana­lyt­ics. The reports on demo­graph­ic char­ac­ter­is­tics and inter­ests 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. You can learn more about the adver­tis­ing func­tions on https://support.google.com/analytics/answer/3450482?hl=de_AT&utm_id=ad.

You can stop the use of the activ­i­ties and infor­ma­tion of your Google account under “Adver­tis­ing set­tings” on https://adssettings.google.com/authenticated via checkbox.

4.2.1.9 Google Ana­lyt­ics deac­ti­va­tion link

If you click on the fol­low­ing deac­ti­va­tion link, you can pre­vent Google from record­ing fur­ther vis­its to this web­site. Note: 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.

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

We have con­clud­ed 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

4.2.1.11 Google Ana­lyt­ics Google Sig­nals Pri­va­cy Policy

We have enabled Google sig­nals in Google Ana­lyt­ics. This updates exist­ing Google Ana­lyt­ics fea­tures (adver­tis­ing reports, remar­ket­ing, cross-device reports, and inter­est and demo­graph­ic reports) to obtain aggre­gat­ed and anonymized data from you, pro­vid­ed 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­lect­ed and linked to the Google account. Google can thus rec­og­nize, for exam­ple, if you view a prod­uct on our web­site via a smart­phone and only buy the prod­uct lat­er via a lap­top. Thanks to the acti­va­tion of Google sig­nals, we can launch cross-device remar­ket­ing cam­paigns that would oth­er­wise not be pos­si­ble in this form. Remar­ket­ing means that we can also show you our offer on oth­er websites.

In Google Ana­lyt­ics, Google sig­nals also col­lect oth­er vis­i­tor data such as loca­tion, search his­to­ry, YouTube his­to­ry and data about your actions on our web­site. This gives us bet­ter adver­tis­ing reports from Google and more use­ful infor­ma­tion about your inter­ests and demo­graph­ics. This includes your age, what lan­guage you speak, where you live, or what gen­der you are. Fur­ther­more, social cri­te­ria such as your pro­fes­sion, mar­i­tal sta­tus or income are also added. All these char­ac­ter­is­tics help Google Ana­lyt­ics to define groups of peo­ple or tar­get groups.

The reports also help us to bet­ter assess your behav­ior, your wish­es and inter­ests. This allows us to opti­mize and adapt our ser­vices and prod­ucts 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 adver­tis­ing in your Google account. This is always aggre­gat­ed and anony­mous data and nev­er indi­vid­ual per­son data. In your Google account, you can man­age this data or delete it.

4.2.2 IONOS Web­An­a­lyt­ics Pri­va­cy Pol­i­cy (cre­at­ed with the AdSim­ple Pri­va­cy Gen­er­a­tor)

IONOS Web­An­a­lyt­ics Pri­va­cy Pol­i­cy Sum­ma­ry
👥 Data sub­jects: Vis­i­tors to the web­site.
🤝 Pur­pose: Eval­u­a­tion of vis­i­tor infor­ma­tion to opti­mize the web offer.
📓 Data processed: Access sta­tis­tics con­tain­ing data such as access loca­tions, device data, access dura­tion and time, and IP address­es in anonymized form.
📅 Stor­age peri­od: depend­ing on the dura­tion of the con­tract with IONOS Web­An­a­lyt­ics.
⚖️ Legal basis: Art. 6 para. 1 lit. a DSG­VO (Con­sent), Art. 6 para. 1 lit. f DSG­VO (Legit­i­mate Interests).

4.2.2.1 What is IONOS WebAnalytics?

We use the analy­sis tool IONOS Web­An­a­lyt­ics of the Ger­man com­pa­ny 1&1 IONOS SE, Elgen­dor­fer Straße 57, 56410 Montabaur, Ger­many on our web­site. The tool helps us ana­lyze our web­site and data is also col­lect­ed and stored for this pur­pose. How­ev­er, this tool does not col­lect data that could iden­ti­fy you as a per­son. Nev­er­the­less, in this pri­va­cy state­ment we would like to inform you in more detail about the data pro­cess­ing and stor­age and also explain why we use IONOS WebAnalytics.

IONOS Web­An­a­lyt­ics is, as the name sug­gests, a tool that is used to ana­lyze our web­site. The soft­ware pro­gram col­lects data about how long you stay on our web­site, which but­tons you click or from which oth­er web­site you found us. This gives us a good overview of user behav­ior on our web­site. All this infor­ma­tion is anony­mous. This means that we do not iden­ti­fy you as a per­son through this data, but only receive gen­er­al usage infor­ma­tion and statistics.

4.2.2.2 Why do we use IONOS Web­An­a­lyt­ics on our website?

Our goal is to pro­vide you with the best pos­si­ble expe­ri­ence on our web­site. We are con­fi­dent in our offer­ings and want our web­site to be a help­ful and use­ful place for you. To do this, we need to tai­lor our web­site to your needs and con­cerns as much as pos­si­ble. With a web ana­lyt­ics tool like IONOS Web­An­a­lyt­ics and the result­ing data we can improve our web­site to that end. The data can also help us to design adver­tis­ing and mar­ket­ing mea­sures more indi­vid­u­al­ly. With all these web analy­ses, how­ev­er, we are still con­cerned about the pro­tec­tion of per­son­al data. Unlike oth­er analy­sis tools, IONOS Web­An­a­lyt­ics does not store and process any data that could iden­ti­fy you as a person.

4.2.2.3 What data is stored by IONOS WebAnalytics?

Data is col­lect­ed and stored through log files or through a so-called pix­el. A pix­el is a snip­pet of JavaScript code that loads a col­lec­tion of func­tions that can be used to track user behav­ior. Web­An­a­lyt­ics delib­er­ate­ly avoids the use of cookies.

IONOS does not store any per­son­al data about you. When you sub­mit a page request, your IP address is trans­mit­ted, but then imme­di­ate­ly anonymized and processed in such a way that you can­not be iden­ti­fied as a person.

The fol­low­ing data is stored by IONOS WebAnalytics:

  • Your brows­er type and brows­er version
  • which web­site you have vis­it­ed before (refer­rer)
  • which spe­cif­ic web­site you have visited
  • which oper­at­ing sys­tem you are using
  • which end device you are using (PC, tablet or smartphone)
  • when you came to our site
  • your IP address in anonymized form

The data is not passed on to any third-par­ty providers and is only used for sta­tis­ti­cal analysis.

4.2.2.3 How long and where is the data stored?

The data is stored until the con­tract between IONOS Web­An­a­lyt­ics and us expires. The data is stored in our log direc­to­ry in the case of a reg­u­lar web host­ing plan and graph­i­cal sta­tis­tics are gen­er­at­ed from it. These logs are delet­ed every 8 weeks. In the case of a MyWeb­site tar­iff, the data is deter­mined via a pix­el. Here, the data is only stored and processed with­in IONOS WebAnalytics.

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

In prin­ci­ple, you have the right to infor­ma­tion, cor­rec­tion or dele­tion and restric­tion of the pro­cess­ing of your per­son­al data at any time. You can also revoke your con­sent to the pro­cess­ing of data at any time. How­ev­er, since no per­son­al data is stored or processed via IONOS Web­An­a­lyt­ics and there­fore an assign­ment of you as a per­son is not pos­si­ble, there is also no pos­si­bil­i­ty to delete such data.

4.2.2.5 Legal basis

The use of IONOS Web­An­a­lyt­ics requires your con­sent, which we have obtained with our Cook­ie Pop­up. Accord­ing to Art. 6 Para. 1 lit. a DSG­VO (Con­sent), this con­sent con­sti­tutes the legal basis for the pro­cess­ing 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­i­mate inter­est on our part in ana­lyz­ing the behav­ior of web­site vis­i­tors and thus improv­ing our offer tech­ni­cal­ly and eco­nom­i­cal­ly. With the help of IONOS Web­An­a­lyt­ics, we detect web­site errors, can iden­ti­fy attacks and improve eco­nom­ic effi­cien­cy. The legal basis for this is Art. 6 para. 1 lit. f DSG­VO (Legit­i­mate Interests).

We hope we have been able to pro­vide you with the most impor­tant infor­ma­tion around the tru­ly eco­nom­i­cal data pro­cess­ing of IONOS Web­An­a­lyt­ics. If you want to learn more about the track­ing ser­vice, we rec­om­mend that you read the com­pa­ny’s pri­va­cy pol­i­cy at https://www.ionos.de/hilfe/datenschutz/datenverarbeitung-von-webseitenbesuchern-ihres-11-ionos-produktes/webanalytics/?tid=311284017.

4.3 Adver­tis­ing cookies

On this web­site, we use adver­tis­ing cook­ies that allow us to gain insights into cam­paign results. This is done on the basis of a profile we cre­ate based on your behav­ior on our web­site www.thomasnowotny.de. These cook­ies link you as a web­site vis­i­tor to a unique ID, but do not profile your behav­ior and inter­ests in order to serve per­son­al­ized ads. Because these cook­ies are marked as track­ing cook­ies, we require your con­sent to place them.

4.4 Social Media Buttons

On our web­site, we have includ­ed but­tons for Face­book and LinkedIn to sup­port web pages (e. g.

“Like”, “Pin”) or shar­ing (e.g. “Tweet”) on social net­works such as Face­book and LinkedIn. These but­tons use code that comes from Face­book and LinkedIn them­selves. This code places cook­ies. These social media but­tons may also store and process cer­tain infor­ma­tion so that per­son­al­ized adver­tis­ing can be dis­played to you.

Please read the pri­va­cy pol­i­cy of these social net­works (which may change reg­u­lar­ly) to learn how they han­dle your (per­son­al) data that they process using these cook­ies. The retrieved data is anonymized as much as pos­si­ble. Face­book and LinkedIn are locat­ed in the Unit­ed States.

4.4.1 LinkedIn pri­va­cy policy

(Source: Cre­at­ed with the pri­va­cy gen­er­a­tor of AdSim­ple)

LinkedIn pri­va­cy pol­i­cy sum­ma­ry
👥 Data sub­jects: vis­i­tors to the web­site
🤝 Pur­pose: Opti­miza­tion of our ser­vice per­for­mance.
📓 Data processed: Data such as user behav­ior data, infor­ma­tion about your device and your IP address.
More details can be found below in the pri­va­cy pol­i­cy.
📅 Stor­age peri­od: the data is gen­er­al­ly delet­ed with­in 30 days.
⚖️ Legal basis: Art. 6 para. 1 lit. a DSG­VO (Con­sent), Art. 6 para. 1 lit. f DSG­VO (Legit­i­mate Interests).

4.4.3.1 What is LinkedIn?

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, USA on our web­site. The social plug-ins may be feeds, shar­ing con­tent or link­ing 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.

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.

4.4.1.2 Why do we use LinkedIn on our website?

We know how busy you are. That’s why you can’t fol­low all social media chan­nels indi­vid­u­al­ly. Even if it would be worth it, as in our case. Because time and again we post inter­est­ing news or reports that are worth spread­ing. That’s why we’ve made it pos­si­ble on our web­site to share inter­est­ing con­tent direct­ly on LinkedIn or to link direct­ly to our LinkedIn page. 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.

4.4.1.4 What data is stored by LinkedIn?

LinkedIn does not store any per­son­al data mere­ly by inte­grat­ing the social plug-ins. 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 to share our con­tent, for exam­ple, 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 Linked­In’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 com­plete and only serves as an exam­ple. The fol­low­ing cook­ies were set with­out being logged into LinkedIn:

Name: bcook­ie
Wert: =2&34aab2aa-2ae1-4d2a-8baf-c2e2d7235c16311284017-
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=AQF6KNnJ0G311284017…
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:3112840172900777718326218137
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.

4.4.1.5 How long and where is the data stored?

In prin­ci­ple, LinkedIn retains your per­son­al data for as long as the com­pa­ny con­sid­ers it nec­es­sary to pro­vide its own 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­tion. 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.

4.4.1.6 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 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 will be able to 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 LinkedIn from pro­cess­ing your data. 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­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 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.

4.4.1.7. Legal basis

If you have con­sent­ed that data from you can be processed and stored by inte­grat­ed social media ele­ments, this con­sent is con­sid­ered the legal basis of the data pro­cess­ing (Art. 6 para. 1 lit. a DSG­VO). In prin­ci­ple, your data will also be stored and processed on the basis of our legit­i­mate inter­est (Art. 6 para. 1 lit. f DSG­VO) in fast and good com­mu­ni­ca­tion with you or oth­er cus­tomers and busi­ness part­ners. Most social media plat­forms also set cook­ies in your brows­er to store data. That is why we rec­om­mend that you read our pri­va­cy text about cook­ies care­ful­ly and view the pri­va­cy pol­i­cy or cook­ie pol­i­cy of the respec­tive 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.

4.4.7 Google Fonts Local Pri­va­cy Policy

(Source: Cre­at­ed with the pri­va­cy gen­er­a­tor from AdSim­ple)

On our web­site, we use Google Fonts from Google Inc. The com­pa­ny respon­si­ble for the Euro­pean region is Google Ire­land Lim­it­ed (Gor­don House, Bar­row Street Dublin 4, Ire­land). We have embed­ded the Google fonts local­ly, i.e. on our web serv­er — not on Google’s servers. This means that there is no con­nec­tion to Google servers and thus no data trans­fer or storage.

4.4.7.1 What are Google Fonts?

Google Fonts used to be called Google Web Fonts. This is an inter­ac­tive direc­to­ry of over 800 fonts that Google pro­vides free of charge. With Google Fonts, you could use fonts with­out upload­ing them to your own serv­er. How­ev­er, in order to pre­vent any infor­ma­tion trans­fer to Google servers in this regard, we have down­loaded the fonts to our serv­er. This way we act pri­va­cy com­pli­ant and do not send any data to Google Fonts.

5. Hosting privacy policy 1&1

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 avail­able for a max­i­mum of 9 weeks.

5.1 Page request 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 IP address of the proxy and not the address of the work­sta­tion orig­i­nal­ly request­ing the page is shown in the log file.

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 WebHosting.

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 abil­i­ty to gen­er­ate mean­ing­ful vis­i­tor statistics.

Please note:

Due to pri­va­cy poli­cies 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/.

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 WebHosting.

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.

6. Your rights regarding personal data

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

You have the right to know why your per­son­al data is need­ed, 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­fi­ca­tion: you have the right when­ev­er you wish to sup­ple­ment, cor­rect and have your per­son­al data delet­ed or blocked.

If you have giv­en us con­sent to process your data, you have the right to with­draw this con­sent and have your per­son­al data delet­ed. Right to trans­fer your data: you have the right to request all your per­son­al data from one con­troller and to trans­fer it in its entire­ty to anoth­er controller.

Right to object: you can object to the pro­cess­ing of your data. We

com­ply with this unless there are legit­i­mate 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 we han­dle your data, we would like to hear it, but you also have the right to address it to the super­vi­so­ry author­i­ty (the Data Pro­tec­tion Authority).

7. Activation / deactivation and deletion of cookies

You can use your Inter­net brows­er to delete cook­ies auto­mat­i­cal­ly or man­u­al­ly. You can also spec­i­fy that cer­tain cook­ies may not be placed. Anoth­er option is to change your Inter­net brows­er set­tings so that you receive a mes­sage each time a cook­ie is set. For more infor­ma­tion on these options, find the instruc­tions in your browser’s help section.

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

7.1. Com­pli­anz — GDPR/CCPA Cook­ie Con­sent Plugin

7.1.1 What is Complianz?

Com­pli­anz is a GDPR/CCPA Cook­ie Con­sent plu­g­in that sup­ports GDPR, DSG­VO, LGPD, POPIA, APA, CCPA and PIPE­DA with a con­di­tion­al cook­ie notice and a cus­tomized cook­ie pol­i­cy based on the results of the inte­grat­ed cook­ie scan. (Source: https://wordpress.org/plugins/complianz-gdpr/)

7.1.2 What cook­ies does Com­pli­anz set?

cmplz­For­m­Val­ues
cmplz­Dash­board­De­fault­s­Set
cmplz_policy_id
cmplz_functional
cmplz_s­ta­tis­tics-anony­mous
cmplz_statistics
cmplz_marketing
cmplz_consent_status
cookieconsent_status

The sta­tis­tics are anonymized.

7.1.3 What does Com­pli­anz do?

Con­fig­ure the cook­ie hint for the spe­cif­ic region: Euro­pean Union, Unit­ed King­dom, Unit­ed States, Aus­tralia, South Africa or Cana­da. Or use a cook­ie hint globally.

Con­fig­ure the spe­cif­ic cook­ie con­sent per sub­re­gion, for exam­ple: Euro­pean Union + GDPR/CNIL or Unit­ed States + CCPA.
Cook­ie con­sent and con­di­tion­al cook­ie notice with cus­tom CSS and cus­tomiz­able tem­plates.
Ban­ner tem­plates include: GDPR friend­ly cook­ie wall — Accept/Reject — Cat­e­go­ry based con­sent.
Ban­ner Tem­plates CA/US/AU also include: dis­miss on scroll, time on page or both.
Proof of Con­sent; user con­sent reg­is­tra­tion that respects GDPR data min­i­miza­tion policy.

Auto­mat­ic detec­tion if the web­site needs a cook­ie notice (also called cook­ie ban­ner or pop-up).

Reg­u­lar cook­ie scan for changes in cook­ies, plu­g­ins and 3rd par­ty ser­vices.
Detect­ed cook­ie data is pre-pop­u­lat­ed by cookiedatabase.org, with clear and trans­par­ent cook­ie descrip­tions that are con­stant­ly updated.

A cook­ie pol­i­cy; gen­er­at­ed by you with a sim­ple wiz­ard, cre­at­ed by an IT law firm.
Do not sell my per­son­al infor­ma­tion: DNSMPI page for CCPA — if required.
Terms and con­di­tions are avail­able in a sep­a­rate plu­g­in: Com­pli­anz — Terms and Con­di­tions.
Inte­grat­ed with Word­Press pri­va­cy fea­tures. Export and delete per­son­al infor­ma­tion from our dashboard.

Imple­men­ta­tion of Google Tag Man­ag­er, Google Ana­lyt­ics, Mato­mo etc.

Cat­e­go­rize your cook­ies with Tag Man­ag­er or our own Script Cen­ter if need­ed.
Auto­mat­i­cal­ly anonymize IP address­es for Google Ana­lyt­ics, if required.
Inte­gra­tion with WP Con­sent API
Blocks third-par­ty cook­ies like Google Maps, Face­book, Insta­gram, AdSense, Recaptcha, Twit­ter, Active­Cam­paign and more.
Blocks iFrames, such as YouTube, Vimeo, Dai­ly­mo­tion embed­ded videos and social iFrames.
Shows place­hold­ers for blocked iFrames. Stills videos and indi­vid­ual place­hold­ers per service.

Inte­grates seam­less­ly with Guten­berg, Ele­men­tor, Divi, Formi­na­tor, WPBak­ery, Mon­sterin­sights, GAD­WP, Bee­hive, WPForms, Grav­i­ty Forms, Hap­py­Forms, Con­tact Form 7 <5.4 (CF7), Woocom­merce, Easy Dig­i­tal Down­loads, WP Google Maps, Google Maps Wid­get, CAOS | Host Google Ana­lyt­ics Local­ly and oth­er pop­u­lar plugins.

Test­ed with pop­u­lar themes and page builders.
Guten­berg blocks enabled.
Cook­ie ban­ners and legal doc­u­ments com­ply with WCAG 2.1 AA acces­si­bil­i­ty guide­lines.
Ready for GDPR, AVG, DSG­VO, CNIL, PECR, UK DPA, UK GDPR, CCPA, COP­PA, PIPE­DA, CASL, POPIA, Pri­va­cy Act 1988 & Aus­tralian Pri­va­cy Prin­ci­ples.
We are close­ly fol­low­ing the lat­est devel­op­ments in the ePri­va­cy Reg­u­la­tion, the pro­posed Cook­ie Law for the Euro­pean Union and oth­er laws around the world.

8. Cookie consent settings

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

geoip => 1 checkbox_style => slid­er use_categories => vis­i­ble 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 pol­i­cy readmore_imprint => Imprint accept_informational => Accept

message_optout => We use cook­ies to opti­mize our web­site and service.

message_optin => We use cook­ies to opti­mize our web­site and service.

readmore_optout => Cook­ie Policy

readmore_optout_dnsmpi => Do Not Sell My Per­son­al Infor­ma­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 => #

9. Multilingual Plugin Polylang

9.1. What is Polylang?

This web­site uses Poly­lang for mul­ti­lin­gual func­tion­al­i­ty. Poly­lang allows you to cre­ate a bilin­gual or mul­ti­lin­gual Word­Press web­site. You write posts and pages, cre­ate cat­e­gories and post key­words as usu­al, and then define the lan­guage for each of them. Trans­lat­ing a post, whether it’s in the default lan­guage or not, is optional.

9.2. What cook­ie does Poly­lang use?

The plu­g­in uses the fol­low­ing func­tion­al cook­ie pll_language for:

URL cus­tomiza­tion in the select­ed lan­guages
detec­tion of the brows­er lan­guage
Assign­ment of the media to a language

All texts are pro­tect­ed by copyright.

Source: Cre­at­ed with the pri­va­cy gen­er­a­tor from AdSim­ple or fur­ther as indi­cat­ed by link and / or reference.