top of page


dr med vet. Fabienne Ferrara (M.mel.)

Kaiserin-Augusta-Allee 87

10589 Berlin


I have written this data protection declaration (version 28.05.2020-311181089) in order to provide you with information in accordance with the requirements ofGeneral Data Protection Regulation (EU) 2016/679to explain which information ich collect, ich data use and what choices you have as a visitor to this website.

Unfortunately, it is in the nature of things that these explanations sound very technical, but I have tried to describe the most important things as simply and clearly as possible when creating them.

Automatic data storage

When you visit websites today, certain information is automatically created and stored, including on this website.

If you visit my website as you are right now, our web server (computer on which this website is stored) automatically saves data such as

  • the address (URL) of the accessed website

  • Browser and browser version

  • the operating system used

  • the address (URL) of the previously visited page (referrer URL)

  • the hostname and IP address of the device from which access is being made

  • Date and Time

in files (web server log files).

As a rule, web server log files are stored for two weeks and then automatically deleted. I do not pass on this data, but cannot rule out that this data will be viewed in the event of illegal behavior.


My website uses HTTP cookies to store user-specific data.
In the following, explain ich what cookies are and why they are used so that you can better understand the following data protection declaration.

What exactly are cookies?

Whenever you surf the Internet, you use a browser. Well-known browsers include Chrome, Safari, Firefox, Internet Explorer and Microsoft Edge. Most websites store small text files in your browser. These files are called cookies.

One thing cannot be denied: Cookies are really useful little helpers. Almost all websites use cookies. More specifically, they are HTTP cookies, because there are other cookies for other purposes. HTTP cookies are small files that our website stores on your computer. These cookie files are automatically stored in the cookie folder, which is basically the "brain" of your browser. A cookie consists of a name and a value. When defining a cookie, one or more attributes must also be specified.

Cookies store certain user data from you, such as language or personal page settings. When you visit our site again, your browser sends the "user-related" information back to my site. Thanks to the cookies, my website knows who you are and offers you your usual default setting. In einigen Browsern hat jedes Cookie eine eigene Datei, in anderen wie beispielsweise Firefox sind alle Cookies in einer einzigen Datei saved.

There are both first-party cookies and third-party cookies. First-party cookies are created directly by my site, third-party cookies are created by partner websites (e.g. Google Analytics). Each cookie must be evaluated individually, as each cookie stores different data. The expiry time of a cookie also varies from a few minutes to a few years. Cookies are not software programs and do not contain viruses, trojans or other "pests". Cookies also cannot access information on your PC.

For example, cookie data can look like this:

  • Name: _ga

  • Expiry time: 2 years

  • Use: Differentiation of website visitors

  • Sample value: GA1.2.1326744211.152311181089

A browser should support the following minimum sizes:

  • A cookie should contain at least 4096 bytes

  • At least 50 cookies should be stored per domain

  • A total of at least 3000 cookies should be able to be stored

What types of cookies are there?

The question of which cookies I use in particular depends on the services used and is clarified in the following sections of the data protection declaration. At this point I would like to briefly explain the different types of HTTP cookies.

There are 4 types of cookies:

Strictly Necessary Cookies
These cookies are necessary to ensure basic functions of the website. For example, these cookies are needed if a user puts a product in the shopping cart, then continues surfing on other pages and only goes to the checkout later. These cookies do not delete the shopping cart, even if the user closes their browser window.

Functional cookies
These cookies collect information about user behavior and whether the user receives any error messages. In addition, these cookies are also used to measure the loading time and behavior of the website in different browsers.

Targeting cookies
These cookies ensure a better user experience. For example, entered locations, font sizes or form data are saved.

advertising cookies
These cookies are also called targeting cookies. They are used to provide the user with individually tailored advertising. This can be very useful, but also very annoying.

Usually, when you visit a website for the first time, you will be asked which of these types of cookies you would like to allow. And of course this decision is also stored in a cookie.

How can I delete cookies?

You decide for yourself how and whether you want to use cookies. Regardless of which service or website the cookies come from, you always have the option of deleting Cookies, only partially allowing them or deactivating them. For example, you can block third-party cookies but allow all other cookies.

If you want to find out which cookies have been stored in your browser, if you want to change or delete cookie settings, you can find this in your browser settings:

Chrome: Delete, enable and manage cookies in Chrome

Safari: Managing Cookies and Website Data with Safari

Firefox: Clear cookies to remove data websites have placed on your computer

Internet Explorer: Delete and manage cookies

Microsoft Edge: Deleting and managing cookies

If you generally do not want any cookies, you can set up your browser so that it always informs you when a cookie is to be set. You can decide for each individual cookie whether you allow the cookie or not. The procedure differs depending on the browser. It is best to search the instructions in Google with the search term “delete cookies Chrome” or “disable cookies Chrome” in case of a Chrome browser or replace the word “Chrome” with the name of your browser, e.g. Edge, Firefox, Safari.

What about my data protection?

The so-called “Cookie Guidelines” have been in place since 2009. It states that the storage of cookies requires the consent of the website visitor (i.e. you). Within the EU countries, however, there are still very different reactions to these directives. In Germany, the cookie guidelines have not been implemented as national law. Instead, this guideline was largely implemented in Section 15 (3) of the Telemedia Act (TMG).

If you want to know more about cookies and don't shy away from technical documentation, I recommend, the Internet Engineering Task Force (IETF) Request for Comments called “HTTP State Management Mechanism”.

storage of personal data


Personal data that you transmit to me electronically on this website, such as name, e-mail address, address or other personal information when submitting a form or comments on the blog, will be stored by me together with the time and the IP Address used only for the purpose stated, kept safe and not passed on to third parties.

I therefore only use your personal data to communicate with those visitors who expressly request contact and to process the services offered on this website. I do not pass on your personal data without consent, but I cannot rule out that this data will be viewed in the event of illegal behavior.

If you send me personal data by e-mail - i.e. outside of this website - I  can not guarantee a secure transmission and the protection of your data. I recommend you never send confidential data unencrypted by email.

The legal basis exists afterArticle 6  paragraph 1 a GDPR(lawfulness of processing) is that you give me consent to process the data you have entered. You can revoke this consent at any time - an informal e-mail is sufficient, you will find my contact details in the imprint.

Rights under the General Data Protection Regulation


According to the provisions of the GDPR, you have the following rights:

  • Right to rectification (Article 16 GDPR)

  • Right to erasure (“right to be forgotten”) (Article 17 GDPR)

  • Right to restriction of processing (Article 18 GDPR)

  • Right to notification – obligation to notify in connection with rectification or erasure of personal data or restriction of processing (Article 19 GDPR)

  • Right to data portability (Article 20 GDPR)

  • Right to object (Article 21 GDPR)

  • Right not to be subject to a decision based solely on automated processing, including profiling (Article 22 GDPR)

If you believe that the processing of your data violates data protection law or your data protection claims have otherwise been violated in any way, you can contact theFederal Commissioner for Data Protection and Freedom of Information (BfDI)turn around.

Evaluation of visitor behavior


In the following data protection declaration, I inform you ich whether and how I evaluate data from your visit to this website. The evaluation of the collected data is usually anonymous and I cannot infer your person from your behavior on this website.

You can find out more about the possibilities of objecting to this evaluation of visit data in the following data protection declaration.

TLS encryption with https


I use https to transmit data securely on the Internet (data protection through technology designArticle 25 paragraph 1 GDPR). By using TLS (Transport Layer Security), an encryption protocol for secure data transmission on the Internet, I  can ensure the protection of confidential data. You can recognize the use of this protection of data transmission by the small lock symbol in the top left corner of the browser and the use of the https scheme (instead of http) as part of my Internet address.

Google Fonts Privacy Policy


I use Google Fonts on this website. These are the “Google fonts” from Google Inc. The company Google Ireland Limited (Gordon House, Barrow Street Dublin 4, Ireland) is responsible for all Google services in Europe.

You do not need to register or enter a password to use Google fonts. Furthermore, no cookies are stored in your browser. The files (CSS, typefaces/fonts) are requested via the Google domains and According to Google, requests for CSS and fonts are completely separate from all other Google services. If you have a Google account, you don't have to worry about your Google account data being transmitted to Google while using Google Fonts. Google records the use of CSS (Cascading Style Sheets) and the fonts used and stores this data securely. How the data storage looks exactly, we will see in detail.

What are Google Fonts?


Google Fonts (formerly Google Web Fonts) is a directory with over 800 fonts that Google  makes it available to its users free of charge.

Viele dieser Schriftarten sind unter der SIL Open Font License veröffentlicht, während andere unter der Apache-Lizenz veröffentlicht wurden. Both are free software licenses.

Why do I use I Google Fonts on our website?


With Google Fonts, I  can use fonts on this website, but do not have to upload them to your own server. Google Fonts is an important building block to keep the quality of my website high. All Google fonts are automatically optimized for the web and this saves data volume and is a great advantage especially for use with mobile devices. When you visit my site, the small file size ensures fast loading time. Furthermore, Google Fonts are secure web fonts. Different image synthesis systems (rendering) in different browsers, operating systems and mobile devices can lead to errors. Such errors can partially distort texts or entire websites. Thanks to the fast Content Delivery Network (CDN), there are no cross-platform problems with Google Fonts. Google Fonts supports all common browsers (Google Chrome, Mozilla Firefox, Apple Safari, Opera) and works reliably on most modern mobile phones Operating systems including Android 2.2+ and iOS 4.2+ (iPhone, iPad, iPod). 

Which data is stored by Google?


When you visit my website, the fonts are reloaded via a Google server. This external call transmits data to the Google servers. In this way, Google also recognizes that you or your IP address are visiting my website. The Google Fonts API was developed to reduce the use, storage and collection of end-user data to what is necessary for proper font delivery. Incidentally, API stands for "Application Programming Interface" and is used at other things as a data transmitter in the software sector.

Google Fonts securely stores CSS and font requests on Google and is therefore protected. Through the collected usage figures, Google can determine how well the individual fonts are received. Google publishes the results on internal analysis pages, such as Google Analytics. Google also uses data from its own web crawler to determine which websites use Google fonts. This data is published in the Google Fonts BigQuery database. Entrepreneurs and developers use the Google Webservice BigQuery to examine and move large amounts of data.

However, it should be remembered that with each Google Font request, information such as language settings, IP address, browser version, browser screen resolution and browser name are automatically transmitted to the Google servers. Whether this data is also stored cannot be clearly determined or is not clearly communicated by Google.

How long and where is the data stored?


Google stores requests for CSS assets for one day on its servers, which are mainly located outside the EU. This enables us to use the fonts using a Google style sheet. A style sheet is a template that you can use to change the design or font of a website, for example, quickly and easily.

The font files are stored by Google for one year. Google is thus pursuing the goal of fundamentally improving the loading time of websites. When millions of websites refer to the same fonts, they are cached after the first visit and immediately reappear on all other websites visited later. Sometimes Google updates font files to reduce file size, increase language coverage, and improve design.

How can I delete my data or prevent data storage?

The data that Google stores for a day or a year cannot simply be deleted. The data is automatically transmitted to Google when the page is accessed. To be able to delete this data prematurely, you must contact Google support contact. In this case, you can only prevent data storage if you do not visit our website.

Unlike other web fonts, Google allows us unlimited access to all fonts. So I have unlimited access to a sea of fonts and thus get the best out of this website. You can find more about Google Fonts and other questions at Although Google addresses data protection issues there, it does not contain really detailed information about data storage. It is relatively difficult to get really precise information about stored data from Google.

You can also find out which data is generally collected by Google and what this data is used for

LinkedIn Privacy Policy

I use  on this website social plug-ins of the social media network LinkedIn, the company LinkedIn Corporation, 2029 Stierlin Court, Mountain View, CA 94043, USA. The social plugins can be feeds, sharing content or linking to my LinkedIn page. The social plug-ins are clearly marked with the well-known LinkedIn logo and allow, for example, interesting content to be shared directly via my website. LinkedIn Ireland Unlimited Company Wilton Place in Dublin is responsible for data processing in the European Economic Area and Switzerland.

By embedding such plug-ins, data can be sent to LinkedIn, stored and processed there. In this data protection declaration, I you would like to inform you what data is involved, how the network uses this data and how you can manage or prevent data storage.

What data does LinkedIn store?


LinkedIn does not store any personal data simply by integrating the social plug-ins. LinkedIn calls this data generated by plug-ins passive impressions. However, if you click on a social plug-in, for example to share my content, the platform saves personal data as so-called "active impressions". This is regardless of whether you have a LinkedIn account or not. If you are logged in, the data collected will be assigned to your account.

Your browser establishes a direct connection to the LinkedIn servers when you interact with my plugins. The company logs various usage data. In addition to your IP address, this can be, for example, registration data, device information or information about your Internet or mobile phone provider. If you call up LinkedIn services via your smartphone, your location can also be determined (after you have allowed this). LinkedIn may also share this data in "hashed" form with third-party advertisers. Hashing means converting a record into a string. This allows the data to be encrypted in such a way that people can no longer be identified.

Most data about your user behavior is stored in cookies. These are small text files that are usually placed in your browser. However, LinkedIn may also use web beacons, pixel tags, display tags and other device identifiers.

Various tests also show which cookies are set when a user interacts with a social plug-in.


The data found cannot claim to be complete and is only used as an example. The following cookies were set without being logged in to LinkedIn:

Name: bcookie
Value: =2&34aab2aa-2ae1-4d2a-8baf-c2e2d7235c16311181089-
Purpose: The cookie is a so-called “browser ID cookie” and consequently stores your identification number (ID).
Expiry date: After 2 years

Name: long
Value: v=2&lang=de-de
Purpose: This cookie saves your default or preferred language.
Expiry date: after the end of the session

Name: lidc
Value: 1818367:t=1571904767:s=AQF6KNnJ0G311181089…
Purpose: This cookie is used for routing. Routing records how you got to LinkedIn and how you navigate through the website there.
Expiry date: after 24 hours

Name: rtc
Value: kt0lrv3NF3x3t6xvDgGrZGDKkX
Purpose:  No further information could be found about this cookie.
Expiry date: after 2 minutes

Value: ajax:3111810892900777718326218137
Purpose: This is a session cookie that LinkedIn uses to maintain anonymous user sessions through the server.
Expiry date: after the end of the session

Name: bscookie
Value: “v=1&201910230812…
Purpose: This cookie is a security cookie. LinkedIn describes it as a secure browser ID cookie.
Expiry date: after 2 years

Name: fid
Value: AQHj7Ii23ZBcqAAAA…
Purpose: No further information could be found for this cookie.
Expiry date: after 7 days

Note: LinkedIn also works with third parties. That's why I recognized the two Google Analytics cookies _ga and _gat in my test.

How long and where is the data stored?


In principle, LinkedIn retains your personal data for as long as the company deems necessary to offer its own services. However, LinkedIn will delete your personal data when you delete your account. In some exceptional cases, LinkedIn retains some data in aggregated and anonymous form even after you delete your account. Once you delete your account, other people will no longer be able to see your data within a day. LinkedIn generally deletes the data within 30 days. However, LinkedIn retains data if it is necessary for legal reasons. Data that can no longer be assigned to a person will remain stored even after the account has been closed. The data is stored on various servers in America and probably also in Europe.

How can I delete my data or prevent data storage?

You have the right to access and delete your personal data at any time. You can manage, change and delete your data in your LinkedIn account. You can also request a copy of your personal data from LinkedIn.

To access account information on your LinkedIn profile:

Click on your profile icon in LinkedIn and select the “Settings and data protection” section. Now click on "Privacy" and then in the section "How LinkedIn uses your data" on "Change". In just a short time you can download selected data about your web activity and your account history.

You also have the option in your browser to prevent data processing by LinkedIn. As mentioned above, LinkedIn stores most of the data via cookies that are set in your browser. You can manage, disable or delete these cookies. Depending on which browser you have, the administration works a little differently. The instructions for the most common browsers can be found here:

Chrome: Delete, enable and manage cookies in Chrome

Safari: Managing Cookies and Website Data with Safari

Firefox: Clear cookies to remove data websites have placed on your computer

Internet Explorer: Delete and manage cookies

Microsoft Edge: Deleting and managing cookies

You can also basically set up your browser in such a way that you are always informed when a cookie is to be set. Then you can always decide individually whether you want to allow the cookie or not.

LinkedIn is an active participant in the EU-US Privacy Shield Framework. This framework ensures correct data transmission between the USA and the European Union. Unter  learn more about it. I habe tried to give you the most important information about data processing by LinkedIn. on


Find out more about data processing by the social media network LinkedIn.



Source: Created with dem Privacy Generatorby AdSimple in cooperation

bottom of page