Datenschutz EN -privacy-

Privacy police here in English.

Privacy police / Datenschutzerklärung


Data Used: We use GOOGOLE FONTS – without accept this you can not use this website. Please refer to the appropriate   for the specific type of data it collects.

Data protection and data acquisition
What is the importance of using the Google Fonts Web API to protect the data of my users?
The Google Fonts API is designed to restrict the collection, storage and use of end user data. The use of Google Fonts Web API is not authenticated and the Google Fonts API does not set cookies or do not log it. Inquiries to Google Fonts Web API are sent to resource -specific domains such as or Font inquiries are separated from registration data that are sent to during the use of other authenticated Google services.
What data receives Google from the visitors of my website when I embed Google Fonts via the Google Fonts Web API?
When end users visit a website on which Google Fonts are embedded, their browser send HTTP inquiries to the Google Fonts Web API. The Google Fonts Web API provides users the Google Fonts-CSS (Cascading Style Sheets) and then the font files specified in the CSS. These HTTP inquiries include (1) the IP address used by the respective user to access the Internet (2) the requested URL on the Google server and (3) The HTTP header that the user -Agent contains that contains the internet browser and the operating system versions of website visitors as well as the reference URL (i.e. the website on which the Google font should be displayed).

For clarification, it should be mentioned that Google does not use the information recorded by Google Fonts for the creation of end user profiles or for targeted advertising.

Why does Google get the IP addresses of visitors to my website when I embed Google Fonts via the Google Fonts Web API?
Google receives the IP address of the website seeker, which is processed to respond to the visitor’s request and for security purposes.

The Internet Protocol needs IP addresses to transmit data via the Internet between a specific client (i.e. browser) and a specific server. For this reason, every client request to any server contains the client’s IP address so that the server can respond to this IP address. Accordingly, the fact that Google’s servers are mandatory for the transfer of fonts is not unique for Google and is in harmony with the functioning of the Internet.

Can I embed Google Fonts into my website without sending end user data to the Google server?
Instead of calling on fonts from Google servers, developers can host web fonts locally on their website by downloading the fonts and uploading them to their server. If a font is loaded by the website of the website operator, Google does not receive any data on the website visits. However, the self -hosted Google Fonts also has some disadvantages (see below).

Further information on Google Fonts’s self -hosting can be found in the short guide thread for self -hosted web fonts.

What are the advantages of embedding Google Fonts into my website via the Google Fonts Web API?
Hosting web fonts on Google’s servers offers several advantages for both developers and end users. With Google Fonts you can give websites and other digital products personality and performance. A lot has happened of its original benefit: we want to make the web faster because your browser can save frequently used fonts on all websites that the API used in the cache. This is no longer the case, but the API continues to offer additional and important optimizations so that websites are invited quickly and the fonts work well.

Using the codes generated by Google Fonts, our servers automatically send the smallest possible file to every user. This is done with the technologies supported by the browser. For example, we use the WOFF 2.0 compression, if available. This can reduce the font size and makes the web faster for all users, especially in areas where bandwidth and connectivity pose problems. The symbols provided by Google Fonts benefit from the same infrastructure.

For sites running WooCommerce (also owned by Automattic) and this feature simultaneously and having all purchase tracking explicitly enabled, purchase events will send Google Analytics the following information: order number, product id and name, product category, total cost, and quantity of items purchased. Google Analytics does offer IP anonymization, which can be enabled by the site owner.


Data Used: We use the APP Google Tag Manager. Privacy of google you see here: