Bildschirmfoto 2020-06-24 um 19.13.16.pn

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




Scroll Down


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

Kaiserin-Augusta-Allee 87

10589 Berlin



In accordance with the provisions of the basic data protection regulation (EU) 2016/679, I have written this data protection declaration (version 28.05.2020-311181089) in order to explain to you, what information I collect, how I use data and what decision-making options 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 simple and clear as possible.


Automatic data storage


Nowadays, when you visit websites, certain information is created and stored automatically, as is the case on this website.

When you visit my website as you do now, our web server (computer on which this website is stored) automatically saves data such as:

• the address (URL) of the accessed web page

• Browser and browser version

• the operating system used

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

• the host name and IP address of the device from which access is made

• Date and time

in files (web server log files).

Usually web server log files are stored for two weeks and then automatically deleted. I do not pass on this data, but I cannot exclude the possibility that this data may be viewed in case of illegal behaviour.



My website uses HTTP cookies to store user-specific data.

For better understanding the following privacy policy, I will explain first what cookies are and why they are used. 

What exactly are cookies?

Whenever you surf the Internet, you use a browser. Some 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.

There is one thing that cannot be dismissed: Cookies are really useful little helpers. Almost all websites use cookies. More precisely, they are HTTP cookies, as there are other cookies for other applications. HTTP cookies are small files that are stored on your computer by our website. These cookie files are automatically stored in the cookie folder, which can be seen as 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 about you, such as language or personal page settings. When you visit my site again, your browser transmits the "user-related" information back to our site. With the help of cookies, my website knows who you are and offers you your accustomed standard settings. In some browsers, each cookie has its own file, in others, such as Firefox, all cookies are stored in a single file.

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 sites (e.g. Google Analytics). Each cookie is unique because each cookie stores different data. The expiration 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.

This is how cookie data can look like, for example:

• Name: _ga

• Expiry period: 2 years

• Usage: Differentiation of website visitors

• Example value: GA1.2.1326744211.152311181089

A browser should support the following minimum sizes:

• A cookie should be able to contain at least 4096 bytes

• At least 50 cookies should be able to be stored per domain

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

What types of cookies are there?

The kind of cookies I use strongly depends on the service I use, which is clarified in the following sections of the privacy policy. Here, I would like to briefly explain the different types of HTTP cookies.

You can distinguish 4 types of cookies:

Essential Cookies

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

Functional cookies

These cookies collect information about user behaviour and whether the user receives any error messages. In addition, these cookies also measure the loading time and the behaviour of the website with different browsers.

Advertising cookies

These cookies are also called targeting cookies. They are used to deliver customized advertising to the user. This can be very practical, but also very annoying.

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

How can I delete cookies?

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

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

• Chrome: Delete, activate and manage cookies in Chrome

• Safari: Manage cookies and website data with Safari

• Firefox: Delete cookies to remove data that websites have placed on your computer

• Internet Explorer: Delete and manage cookies

• Microsoft Edge: Delete and manage cookies


If you do not wish to receive cookies, you can set up your browser to inform you when a cookie is to be set. In this way, you can decide for each individual cookie whether you want to allow it or not. The procedure varies depending on the browser. The best thing to do is to look for the instructions in Google using the search term "Delete Chrome cookies" or "Disable Chrome cookies" in the case of a Chrome browser, or replace the word "Chrome" with the name of your browser, e.g. Edge, Firefox, Safari.


What about my privacy?

The so-called "cookie guidelines" have been in place since 2009. This 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 guidelines. In Germany, the cookie guidelines have not been implemented as national law. Instead, the implementation of this directive was largely carried out in § 15 para.3 of the Telemediengesetz (TMG).

If you want to know more about cookies and are not afraid of technical documentation, I recommend https://tools.ietf.org/html/rfc6265, the Request for Comments of the Internet Engineering Task Force (IETF) called "HTTP State Management Mechanism".


Storage of personal data

Personal information that you submit to me electronically on this website, such as your name, e-mail address, postal address or other personal information when submitting a form or comments on the blog, together with the time and IP address, will only be used by us for the purpose stated in each case, will be securely stored and will not be disclosed to third parties.

I will therefore only use your personal data for communication with those visitors who expressly request contact and for the processing of the services offered on this website. I will not pass on your personal data without your consent, but I cannot exclude the possibility that this data may be viewed in the event of illegal behaviour.

If you send me personal data by e-mail - thus off this website - I cannot guarantee secure transmission and protection of your data. I recommend that you never send confidential data by e-mail without encryption.

According to article 6 paragraph 1 a DSGVO (legality of processing) the legal basis is that you give me your 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 basic data protection regulation

In accordance with the provisions of the DSGVO, you are basically entitled to the following rights:

• Right of rectification (Article 16 DSGVO)

• Right of cancellation ("right to be forgotten") (Article 17 DPA)

• Right to restrict processing (Article 18 DSGVO)

• Right of notification - Obligation to notify in connection with the correction or deletion of personal data or the restriction of processing (Article 19 DPA)

• Right to data transferability (Article 20 DSGVO)

• Right of objection (Article 21 DSGVO)

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

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


Evaluation of the visitor behavior

In the following privacy policy I inform you about whether and how I evaluate data of your visit to this website. The evaluation of the collected data is usually anonymous and I cannot draw any conclusions about your person from your behaviour on this website.

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

TLS encryption with https

I use https to transmit data tap-proof on the Internet (data protection through technology design Art. 25 para. 1 DSGVO). By using TLS (Transport Layer Security), an encryption protocol for secure data transmission on the Internet, I can guarantee the protection of confidential data. You can recognize the use of this data transmission security by the small lock symbol in the upper left corner of the browser and by the use of the https scheme (instead of http) as part of my Internet address.


Google Fonts Privacy Policy

On this website I use Google Fonts. These are the "Google Fonts" of the company Google Inc. For the European area the company Google Ireland Limited (Gordon House, Barrow Street Dublin 4, Ireland) is responsible for all Google services.

To use Google fonts, you do not need to log in or set a password. Furthermore, no cookies are stored in your browser. The files (CSS, fonts) are requested via the Google domains fonts.googleapis.com and fonts.gstatic.com. According to Google, the requests for CSS and fonts are completely separated from all other Google services. If you have a Google Account, you don't need to worry about your Google Account information being submitted to Google while using Google Fonts. Google tracks the use of CSS (Cascading Style Sheets) and the fonts which are used and stores this information securely. We'll be taking a closer look at what exactly this data storage looks like.


What are Google Fonts?

Google Fonts (formerly Google Web Fonts) is a directory of over 800 fonts that Google makes available to its users free of charge. Many of these fonts are published under the SIL Open Font License, while others are published under the Apache License. Both are free software licenses.


Why do I use Google Fonts on our website?

With Google Fonts I can use fonts on this website, but I don't have to upload them to my own server. Google Fonts is an important component 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 low file size ensures a 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 visually distort some texts or entire web pages. Due to the fast Content Delivery Network (CDN), there are no cross-platform problems with Google Fonts. Google Fonts supports all major browsers (Google Chrome, Mozilla Firefox, Apple Safari, Opera) and works reliably on most modern mobile 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 transfers data to the Google servers. Thus Google also recognizes that you or your IP address visit my website. The Google Fonts API was developed to reduce the use, storage and collection of end user data to what is necessary for a proper provision of fonts. By the way, API stands for "Application Programming Interface" and serves, among other things, as a data transmitter in the software sector.

Google Fonts stores CSS and font requests securely at 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 Google Fonts' BigQuery database. Entrepreneurs and developers use Google's BigQuery web service to examine and move large amounts of data.

However, it should also be noted that each Google Font request automatically sends information such as language settings, IP address, browser version, browser screen resolution and browser name 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 allows us to use the fonts using a Google style sheet. A stylesheet is a style template that allows you to easily and quickly change, for example, the design or font of a web page.

The font files are stored by Google for one year. Google's goal is to improve the loading time of web pages. When millions of web pages link to the same fonts, they are cached after the first visit and reappear immediately on all other web pages 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 called up. To delete this data prematurely, you must contact Google support at https://support.google.com/?hl=de&tid=311181089. In this case you only prevent data storage if you do not visit my site. 

Unlike other web fonts, Google allows us unlimited access to all fonts. So I have unlimited access to a sea of fonts and can get the most out of this website. You can find more information about Google Fonts and other questions at https://developers.google.com/fonts/faq?tid=311181089. Although Google addresses privacy issues there, it doesn't provide really detailed information about data storage. It's relatively difficult to get really detailed information about data storage from Google.

You can also read about what data Google collects and how it is used at https://www.google.com/intl/de/policies/privacy/.

LinkedIn Privacy policy

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

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


Which data is stored by LinkedIn?

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

Your browser connects directly to LinkedIn's servers when you interact with my plug-ins. This is how the company logs various usage data. In addition to your IP address, this may include, for example, login information, device information, or information about your Internet or mobile service provider. If you access LinkedIn services from your smartphone, your location (after you allow it) can also be determined. LinkedIn may also share this information in "hashed" form with third-party advertisers. Hashing means that a record is converted into a string. This makes it possible to encrypt the data so that people cannot be identified.

Most data on your user behaviour is stored in cookies. These are small text files, which are usually set 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 are only intended as examples. 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 thus stores your identification number (ID).

Expiration date: After 2 years


Name: long

Value: v=2&lang=en-en

Purpose: This cookie saves your preset or preferred language.

Expiration date: after session end


Name: long

Value: v=2&lang=en-en

Purpose: This cookie saves your preset or preferred language.

Expiration date: after session end


Name: lidc

Value: 1818367:t=1571904767:s=AQF6KNnnJ0G311181089...

Purpose: This cookie is used for routing. Routing records how you got to LinkedIn and how you navigate through the website.

Expiration date: after 24 hours


Name: rtc

Value: kt0lrv3NF3x3t6xvDgGrZGDKkX

Purpose: No further information could be found out about this cookie.

Expiration date: after 2 minutes



Value: ajax:3111810892900777718326218137

Purpose: This is a session cookie that LinkedIn uses to maintain anonymous user sessions through the server.

Expiration date: after session end


Name: bscookie

Value: "v=1&201910230812...

Purpose: This cookie is a security cookie. LinkedIn describes it as a secure browser ID cookie.

Expiration date: after 2 years


Name: fid

Value: AQHj7Ii23ZBcqAAAA...

Purpose: No further information could be found for this cookie.

Expiration date: after 7 days


Note: LinkedIn also works together with third party providers. That's why we recognized the two Google Analytics cookies _ga and _gat during our test.



How long and where is the data stored?

Generally, LinkedIn will retain your personal information for as long as the company considers it necessary to provide its services. However, LinkedIn will delete your personal information if you delete your account. In some exceptional cases, LinkedIn may retain some data in aggregate and anonymous form even after your account is deleted. Once you delete your account, other people will not be able to see your information within one day. LinkedIn generally deletes the data within 30 days. LinkedIn does, however, retain data when required by law. Data that can no longer be assigned to any person remains 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. In your LinkedIn account you can manage, change and delete your data. You can also request a copy of your personal information from LinkedIn.

To access the account information in your LinkedIn profile:

In LinkedIn, click on your profile icon and select the "Settings and Privacy" section. Now click "Privacy" and then click "Change" in the "How LinkedIn uses your information" section. In a short time, you will be able to download selected information about your web activity and account history.

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

Chrome: Delete, activate and manage cookies in Chrome

Safari: Manage cookies and website data with Safari

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

Internet Explorer: Delete and manage cookies

Microsoft Edge: Delete and manage cookies

You can also set up your browser so that you are always informed when a cookie is to be set. Then you can always decide individually whether you want to accept the cookie or not. LinkedIn is an active participant in the EU-U.S. Privacy Shield Framework. This framework ensures correct data transmission between the USA and the European Union. You can learn more about it at https://www.privacyshield.gov/participant?id=a2zt0000000L0UZAA0. I have tried to give you the most important information about data processing by LinkedIn. Learn more at https://www.linkedin.com/legal/privacy-policy. Learn more about the data processing of the social media network LinkedIn.


Source: Created with the privacy generator of AdSimple in cooperation with 123familie.de

(c) DR. FABIENNE FERRARA | ConScienceTrain