diff --git a/package.json b/package.json
index 0055e30..6f22ac3 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "csgowtf",
-  "version": "0.29.3",
+  "version": "0.30.0",
   "private": true,
   "scripts": {
     "serve": "vue-cli-service serve",
@@ -21,6 +21,7 @@
     "vue": "^3.2.19",
     "vue-matomo": "^4.1.0",
     "vue-router": "next",
+    "vue3-cookies": "^1.0.6",
     "vuex": "^4.0.2"
   },
   "devDependencies": {
diff --git a/src/App.vue b/src/App.vue
index 78315e4..96f9e43 100644
--- a/src/App.vue
+++ b/src/App.vue
@@ -9,14 +9,16 @@
   <footer class="mt-auto">
     <Footer/>
   </footer>
+  <CookieConsentBtn id="cookie-btn"/>
 </template>
 
 <script>
 import Nav from "@/components/Nav";
 import Footer from "@/components/Footer";
+import CookieConsentBtn from "@/components/CookieConsentBtn";
 
 export default {
-  components: {Footer, Nav},
+  components: {Footer, Nav, CookieConsentBtn},
 }
 </script>
 
@@ -29,4 +31,10 @@ export default {
 .spacer {
   height: 70px;
 }
+
+#cookie-btn {
+  position: fixed;
+  bottom: 30px;
+  right: 20px;
+}
 </style>
diff --git a/src/components/CookieConsentBtn.vue b/src/components/CookieConsentBtn.vue
new file mode 100644
index 0000000..80ac2a4
--- /dev/null
+++ b/src/components/CookieConsentBtn.vue
@@ -0,0 +1,72 @@
+<template>
+  <div v-if="!consent" class="card text-end bg-secondary text-white border border-1">
+    <div class="card-body">
+      <form class="mb-1">
+        <div class="form-check">
+          <input id="essential-cookies" checked class="form-check-input" disabled type="checkbox" value="">
+          <label class="form-check-label" for="essential-cookies">
+            Essential
+          </label>
+        </div>
+        <div class="form-check">
+          <input id="tracking" v-model="tracking" class="form-check-input" type="checkbox">
+          <label class="form-check-label" for="tracking">
+            Matomo
+          </label>
+        </div>
+      </form>
+
+      <a href="/privacy-policy" class="text-muted">Privacy Policy</a>
+
+      <div class="d-flex justify-content-between mt-2">
+        <button class="btn btn-outline-primary" type="button" @click="handleConsentForget">Decline</button>
+        <button class="btn btn-info" type="button" @click="handleConsent">Accept</button>
+      </div>
+    </div>
+  </div>
+</template>
+
+<script>
+import {onMounted, ref} from "vue";
+import {useCookies} from 'vue3-cookies'
+
+export default {
+  name: "CookieConsentBtn",
+  setup() {
+    const tracking = ref(true)
+    const {cookies} = useCookies()
+    const consent = ref(false)
+
+    const handleConsent = () => {
+      window._paq.push(['rememberCookieConsentGiven'])
+      cookies.set('consent', 'given')
+
+      if (tracking.value){
+        window._paq.push(['rememberConsentGiven'])
+      }
+      consent.value = true
+    }
+    const handleConsentForget = () => {
+      consent.value = true
+    }
+
+    const hasConsentGiven = () => {
+      if (cookies.get('consent').toString() === 'given')
+        consent.value = true
+    }
+
+    onMounted(() => {
+      hasConsentGiven()
+    })
+
+    return {handleConsent, handleConsentForget, tracking, consent}
+  }
+}
+</script>
+
+<style scoped>
+form {
+  display: flex;
+  gap: 1rem;
+}
+</style>
diff --git a/src/components/Footer.vue b/src/components/Footer.vue
index 63392af..142b0e8 100644
--- a/src/components/Footer.vue
+++ b/src/components/Footer.vue
@@ -1,17 +1,23 @@
 <template>
-  <div class="footer bg-secondary text-center pt-4 pb-4">
+  <div class="footer bg-secondary text-center pt-4 pb-5">
     <div class="icons pb-4">
       <a aria-label="Git Link" class="gitea text-white" href="https://git.harting.dev/CSGOWTF" target="_blank">
-        <i class="fa fa-gitea fa-2x" aria-hidden="true"></i>
+        <i aria-hidden="true" class="fa fa-gitea fa-2x"></i>
       </a>
     </div>
     <div class="text">
       <p>This site is an open source project, originally created and maintained by the <span class="text-warning">CSGOWTF</span>
         team.</p>
-      <p class="text-muted">For feedback open an <a class="text-decoration-none text-warning"
-                                                    href="https://git.harting.dev/CSGOWTF/csgowtf/issues"
-                                                    target="_blank">issue</a>.</p>
-      <p class="text-muted mb-0">Build-Version: <span class="text-white">{{ version }}</span></p>
+
+      <div class="d-flex justify-content-center align-items-center gap-4">
+        <p class="text-muted">For feedback open an <a class="text-decoration-none text-warning"
+                                                      href="https://git.harting.dev/CSGOWTF/csgowtf/issues"
+                                                      target="_blank">issue</a></p>
+        <p>
+          <a class="text-decoration-none text-warning" href="/privacy-policy">Privacy Policy</a>
+        </p>
+        <p class="text-muted">Build-Version: <span class="text-white">{{ version }}</span></p>
+      </div>
     </div>
   </div>
 </template>
@@ -28,11 +34,12 @@ export default {
 
 <style lang="scss" scoped>
 .footer {
-  height: 200px;
+  height: 220px;
 
   .fa:hover {
     color: #609926;
   }
+
   p {
     font-size: .85rem;
   }
diff --git a/src/components/Nav.vue b/src/components/Nav.vue
index 975e923..3ff7a0f 100644
--- a/src/components/Nav.vue
+++ b/src/components/Nav.vue
@@ -29,8 +29,8 @@
           <input id="search" v-model="data.searchInput" aria-label="Search"
                  autocomplete="off"
                  class="form-control bg-transparent border-0"
-                 placeholder="Profile Link or ShareCode"
-                 title="SteamID64, Profile Link, Custom URL, ShareCode"
+                 placeholder="SteamID64, Profile Link or Custom URL"
+                 title="SteamID64, Profile Link or Custom URL"
                  type="search">
           <button
               id="search-button"
diff --git a/src/router/index.js b/src/router/index.js
index 2664a79..442860b 100644
--- a/src/router/index.js
+++ b/src/router/index.js
@@ -20,6 +20,13 @@ const routes = [
       main: lazyLoadView('Home')
     }
   },
+  {
+    path: '/privacy-policy',
+    name: '{PrivacyPolicy}',
+    components: {
+      main: lazyLoadView('PrivacyPolicy')
+    }
+  },
   {
     path: '/matches',
     name: 'Explore',
diff --git a/src/views/Home.vue b/src/views/Home.vue
index b41bf39..51e9aad 100644
--- a/src/views/Home.vue
+++ b/src/views/Home.vue
@@ -1,24 +1,23 @@
 <template>
   <div class="main-content content text-center">
     <div class="head pt-4 pb-4">
-<!--      <h1 class="text-warning fw-bold mt-lg-5">CSGO<span class="text-up text-white">WTF</span></h1>-->
-      <img src="/logo.svg"
-           alt="logo"
-           class="logo mt-lg-5 mt-3 mb-3">
+      <img alt="logo"
+           class="logo mt-lg-5 mt-3 mb-3"
+           src="/logo.svg">
       <h3 class="mb-lg-4">Open source CSGO data platform</h3>
     </div>
     <div v-if="recentVisited !== null" class="recent-search mt-5 mb-5 row gap-2 justify-content-center">
       <div v-for="(player, id) in recentVisited" :key="player.steamid64" class="player-card" tabindex="0"
            @keyup.enter="GoToPlayer(player.vanity_url || player.steamid64)">
-          <div class="p-2" @click="GoToPlayer(player.vanity_url || player.steamid64)">
-            <div class="col-md-4 m-auto">
-              <img :alt="player.name" :src="player.avatar">
-            </div>
-            <div class="col-md-8 m-auto">
-              <p>{{ player.name }}</p>
-            </div>
+        <div class="p-2" @click="GoToPlayer(player.vanity_url || player.steamid64)">
+          <div class="col-md-4 m-auto">
+            <img :alt="player.name" :src="player.avatar">
           </div>
-          <i class="delete fa fa-times" tabindex="0" @click="removeRecentVisited(id)"></i>
+          <div class="col-md-8 m-auto">
+            <p>{{ player.name }}</p>
+          </div>
+        </div>
+        <i class="delete fa fa-times" tabindex="0" @click="removeRecentVisited(id)"></i>
       </div>
     </div>
     <hr v-if="recentVisited !== null" class="m-auto text-muted">
@@ -30,22 +29,27 @@
         <p class="fw-light">All project code is open source and available for contributors to improve and
           modify.</p>
       </div>
+      <div class="col-sm-12 col-md-4 col-lg-3">
+        <i class="fa fa-liberapay"></i>
+        <h4 class="fw-light">
+          <a href="https://liberapay.com/CSGOWTF/donate" target="_blank">
+            <img alt="Donate using Liberapay"
+                 src="https://liberapay.com/assets/widgets/donate.svg"
+                 style="height: 35px">
+          </a>
+        </h4>
+        <p class="fw-light">This service is free of charge. If you want to support us, just follow the donate
+          button!</p>
+        <div class="d-flex flex-column justify-content-center align-items-center gap-2">
+          <img alt="libera-pay patrons" src="https://img.shields.io/liberapay/patrons/CSGOWTF.svg"
+               style="height: 25px"/>
+        </div>
+      </div>
       <div class="col-sm-12 col-md-4 col-lg-3">
         <i class="fa fa-pie-chart"></i>
         <h4 class="fw-light">In-Depth Data</h4>
         <p class="fw-light">Parsing replay files provides highly detailed match data.</p>
       </div>
-      <div class="col-sm-12 col-md-4 col-lg-3">
-        <i class="fa fa-liberapay"></i>
-        <h4 class="fw-light">Free of Charge</h4>
-        <p class="fw-light">This service is free of charge. If you want to support us, just follow the donate button!</p>
-        <div>
-          <a href="https://liberapay.com/CSGOWTF/donate" target="_blank">
-            <img src="https://liberapay.com/assets/widgets/donate.svg"
-                 alt="Donate using Liberapay">
-          </a>
-        </div>
-      </div>
     </div>
   </div>
 </template>
@@ -112,6 +116,7 @@ export default {
     // display jpg
     background-image: url("../assets/images/map_screenshots/default.jpg");
   }
+
   .head {
     // display webp if possible
     background-image: url("../assets/images/map_screenshots/default.webp");
@@ -187,7 +192,7 @@ export default {
       }
     }
   }
-  
+
   @media screen and (max-width: 576px) {
     .logo {
       width: 200px !important;
diff --git a/src/views/PrivacyPolicy.vue b/src/views/PrivacyPolicy.vue
new file mode 100644
index 0000000..2d188b9
--- /dev/null
+++ b/src/views/PrivacyPolicy.vue
@@ -0,0 +1,255 @@
+<template>
+  <div class="container mt-4">
+    <h4>Privacy Policy</h4>
+
+    <p>Data protection is of a particularly high priority for us. The use of CSGOWTF is possible without any indication of personal data; however, if a data subject wants to use special services via our website, processing of personal data could become necessary. If the processing of personal data is necessary and there is no statutory basis for such processing, we generally obtain consent from the data subject.</p>
+
+    <p>The processing of personal data, such as the name, address, e-mail address, or telephone number of a data subject shall always be in line with the General Data Protection Regulation (GDPR), and in accordance with the country-specific data protection regulations applicable. By means of this data protection declaration, we would like to inform the general public of the nature, scope, and purpose of the personal data we collect, use and process. Furthermore, data subjects are informed, by means of this data protection declaration, of the rights to which they are entitled.</p>
+
+    <p>As the controller, we have implemented numerous technical and organizational measures to ensure the most complete protection of personal data processed through this website. However, Internet-based data transmissions may in principle have security gaps, so absolute protection may not be guaranteed.</p>
+
+    <h4>1. Definitions</h4>
+    <p>This data protection declaration is based on the terms used by the European legislator for the adoption of the General Data Protection Regulation (GDPR). Our data protection declaration should be legible and understandable for the general public, as well as our users. To ensure this, we would like to first explain the terminology used.</p>
+
+    <p>In this data protection declaration, we use, inter alia, the following terms:</p>
+
+    <ul style="list-style: none">
+      <li><h4>a)    Personal data</h4>
+        <p>Personal data means any information relating to an identified or identifiable natural person (“data subject”). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.</p>
+      </li>
+      <li><h4>b) Data subject</h4>
+        <p>Data subject is any identified or identifiable natural person, whose personal data is processed by the controller responsible for the processing.</p>
+      </li>
+      <li><h4>c)    Processing</h4>
+        <p>Processing is any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. </p>
+      </li>
+      <li><h4>d)    Restriction of processing</h4>
+        <p>Restriction of processing is the marking of stored personal data with the aim of limiting their processing in the future. </p>
+      </li>
+      <li><h4>e)    Profiling</h4>
+        <p>Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements. </p>
+      </li>
+      <li><h4>f)     Pseudonymisation</h4>
+        <p>Pseudonymisation is the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person. </p>
+      </li>
+      <li><h4>g)    Controller or controller responsible for the processing</h4>
+        <p>Controller or controller responsible for the processing is the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law. </p>
+      </li>
+      <li><h4>h)    Processor</h4>
+        <p>Processor is a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller. </p>
+      </li>
+      <li><h4>i)      Recipient</h4>
+        <p>Recipient is a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not. However, public authorities which may receive personal data in the framework of a particular inquiry in accordance with Union or Member State law shall not be regarded as recipients; the processing of those data by those public authorities shall be in compliance with the applicable data protection rules according to the purposes of the processing. </p>
+      </li>
+      <li><h4>j)      Third party</h4>
+        <p>Third party is a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data.</p>
+      </li>
+      <li><h4>k)    Consent</h4>
+        <p>Consent of the data subject is any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. </p>
+      </li>
+    </ul>
+
+    <h4>2. Name and Address of the controller</h4>
+    <p>Controller for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is:
+
+    </p>
+
+    <p>CSGOWTF Team</p>
+    <p>Email: privacy@csgow.tf</p>
+    <p>Website: csgow.tf</p>
+
+    <h4>3. Cookies</h4>
+    <p>We use cookies. Cookies are text files that are stored in a computer system via an Internet browser.</p>
+
+    <p>Many Internet sites and servers use cookies. Many cookies contain a so-called cookie ID. A cookie ID is a unique identifier of the cookie. It consists of a character string through which Internet pages and servers can be assigned to the specific Internet browser in which the cookie was stored. This allows visited Internet sites and servers to differentiate the individual browser of the subject from other Internet browsers that contain other cookies. A specific Internet browser can be recognized and identified using the unique cookie ID.</p>
+
+    <p>Through the use of cookies, we can provide users of this website with more user-friendly services that would not be possible without the cookie setting.</p>
+
+    <p>By means of a cookie, the information and offers on our website can be optimized with the user in mind. Cookies allow us, as previously mentioned, to recognize our website users. The purpose of this recognition is to make it easier for users to utilize our website. The website user that uses cookies, e.g. does not have to enter access data each time the website is accessed, because this is taken over by the website, and the cookie is thus stored on the user's computer system. Another example is the cookie of a shopping cart in an online shop. The online store remembers the articles that a customer has placed in the virtual shopping cart via a cookie.</p>
+
+    <p>The data subject may, at any time, prevent the setting of cookies through our website by means of a corresponding setting of the Internet browser used, and may thus permanently deny the setting of cookies. Furthermore, already set cookies may be deleted at any time via an Internet browser or other software programs. This is possible in all popular Internet browsers. If the data subject deactivates the setting of cookies in the Internet browser used, not all functions of our website may be entirely usable.</p>
+
+    <h4>4. Collection of general data and information</h4>
+    <p>We collect a series of general data and information when a data subject or automated system calls up the website. This general data and information are stored in the server log files. Collected may be (1) the browser types and versions used, (2) the operating system used by the accessing system, (3) the website from which an accessing system reaches our website (so-called referrers), (4) the sub-websites, (5) the date and time of access to the Internet site, (6) an Internet protocol address (IP address), (7) the Internet service provider of the accessing system, and (8) any other similar data and information that may be used in the event of attacks on our information technology systems.</p>
+
+    <p>When using these general data and information, we do not draw any conclusions about the data subject. Rather, this information is needed to (1) deliver the content of our website correctly, (2) optimize the content of our website as well as its advertisement, (3) ensure the long-term viability of our information technology systems and website technology, and (4) provide law enforcement authorities with the information necessary for criminal prosecution in case of a cyber-attack. Therefore, we analyze anonymously collected data and information statistically, with the aim of increasing the data protection and data security of our site, and to ensure an optimal level of protection for the personal data we process. The anonymous data of the server log files are stored separately from all personal data provided by a data subject.</p>
+
+    <h4>5. Registration on our website</h4>
+    <p>The data subject has the possibility to register on the website of the controller with the indication of personal data. Which personal data are transmitted to the controller is determined by the respective input mask used for the registration. The personal data entered by the data subject are collected and stored exclusively for internal use by the controller, and for his own purposes. The controller may request transfer to one or more processors (e.g. a parcel service) that also uses personal data for an internal purpose which is attributable to the controller.</p>
+
+    <p>By registering on the website of the controller, the IP address—assigned by the Internet service provider (ISP) and used by the data subject—date, and time of the registration are also stored. The storage of this data takes place against the background that this is the only way to prevent the misuse of our services, and, if necessary, to make it possible to investigate committed offenses. Insofar, the storage of this data is necessary to secure the controller. This data is not passed on to third parties unless there is a statutory obligation to pass on the data, or if the transfer serves the aim of criminal prosecution.
+
+    </p>
+
+    <p>The registration of the data subject, with the voluntary indication of personal data, is intended to enable the controller to offer the data subject contents or services that may only be offered to registered users due to the nature of the matter in question. Registered persons are free to change the personal data specified during the registration at any time, or to have them completely deleted from the data stock of the controller.</p>
+
+    <p>The data controller shall, at any time, provide information upon request to each data subject as to what personal data are stored about the data subject. In addition, the data controller shall correct or erase personal data at the request or indication of the data subject, insofar as there are no statutory storage obligations. The entirety of the controller’s employees are available to the data subject in this respect as contact persons.</p>
+
+    <h4>6. Routine erasure and blocking of personal data</h4>
+    <p>The data controller shall process and store the personal data of the data subject only for the period necessary to achieve the purpose of storage, or as far as this is granted by the European legislator or other legislators in laws or regulations to which the controller is subject to.</p>
+
+    <p>If the storage purpose is not applicable, or if a storage period prescribed by the European legislator or another competent legislator expires, the personal data are routinely blocked or erased in accordance with legal requirements.</p>
+
+    <h4>7. Rights of the data subject</h4>
+    <ul style="list-style: none;">
+      <li><h4>a) Right of confirmation</h4>
+        <p>Each data subject shall have the right granted by the European legislator to obtain from the controller the confirmation as to whether or not personal data concerning him or her are being processed. If a data subject wishes to avail himself of this right of confirmation, he or she may, at any time, contact any employee of the controller.</p>
+      </li>
+      <li><h4>b) Right of access</h4>
+        <p>Each data subject shall have the right granted by the European legislator to obtain from the controller free information about his or her personal data stored at any time and a copy of this information. Furthermore, the European directives and regulations grant the data subject access to the following information:</p>
+
+        <ul style="list-style: none;">
+          <li>the purposes of the processing;</li>
+          <li>the categories of personal data concerned;</li>
+          <li>the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations;</li>
+          <li>where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period;</li>
+          <li>the existence of the right to request from the controller rectification or erasure of personal data, or restriction of processing of personal data concerning the data subject, or to object to such processing;</li>
+          <li>the existence of the right to lodge a complaint with a supervisory authority;</li>
+          <li>where the personal data are not collected from the data subject, any available information as to their source;</li>
+          <li>the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) of the GDPR and, at least in those cases, meaningful information about the logic involved, as well as the significance and envisaged consequences of such processing for the data subject.</li>
+
+        </ul>
+        <p>Furthermore, the data subject shall have a right to obtain information as to whether personal data are transferred to a third country or to an international organisation. Where this is the case, the data subject shall have the right to be informed of the appropriate safeguards relating to the transfer.</p>
+
+        <p>If a data subject wishes to avail himself of this right of access, he or she may, at any time, contact any employee of the controller.</p>
+      </li>
+      <li><h4>c) Right to rectification </h4>
+        <p>Each data subject shall have the right granted by the European legislator to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Taking into account the purposes of the processing, the data subject shall have the right to have incomplete personal data completed, including by means of providing a supplementary statement.</p>
+
+        <p>If a data subject wishes to exercise this right to rectification, he or she may, at any time, contact any employee of the controller.</p></li>
+      <li>
+        <h4>d) Right to erasure (Right to be forgotten) </h4>
+        <p>Each data subject shall have the right granted by the European legislator to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies, as long as the processing is not necessary: </p>
+
+        <ul style="list-style: none;">
+          <li>The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed.</li>
+          <li>The data subject withdraws consent to which the processing is based according to point (a) of Article 6(1) of the GDPR, or point (a) of Article 9(2) of the GDPR, and where there is no other legal ground for the processing.</li>
+          <li>The data subject objects to the processing pursuant to Article 21(1) of the GDPR and there are no overriding legitimate grounds for the processing, or the data subject objects to the processing pursuant to Article 21(2) of the GDPR. </li>
+          <li>The personal data have been unlawfully processed.</li>
+          <li>The personal data must be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject.</li>
+          <li>The personal data have been collected in relation to the offer of information society services referred to in Article 8(1) of the GDPR.</li>
+
+        </ul>
+        <p>If one of the aforementioned reasons applies, and a data subject wishes to request the erasure of personal data stored by us, he or she may, at any time, contact us. We shall promptly ensure that the erasure request is complied with immediately.</p>
+
+        <p>Where the controller has made personal data public and is obliged pursuant to Article 17(1) to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform other controllers processing the personal data that the data subject has requested erasure by such controllers of any links to, or copy or replication of, those personal data, as far as processing is not required. We will arrange the necessary measures in individual cases.</p>
+      </li>
+      <li><h4>e) Right of restriction of processing</h4>
+        <p>Each data subject shall have the right granted by the European legislator to obtain from the controller restriction of processing where one of the following applies:</p>
+
+        <ul style="list-style: none;">
+          <li>The accuracy of the personal data is contested by the data subject, for a period enabling the controller to verify the accuracy of the personal data. </li>
+          <li>The processing is unlawful and the data subject opposes the erasure of the personal data and requests instead the restriction of their use instead.</li>
+          <li>The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise or defence of legal claims.</li>
+          <li>The data subject has objected to processing pursuant to Article 21(1) of the GDPR pending the verification whether the legitimate grounds of the controller override those of the data subject.</li>
+
+        </ul>
+        <p>If one of the aforementioned conditions is met, and a data subject wishes to request the restriction of the processing of personal data stored by us, he or she may at any time contact us. We will arrange the restriction of the processing. </p>
+      </li>
+      <li><h4>f) Right to data portability</h4>
+        <p>Each data subject shall have the right granted by the European legislator, to receive the personal data concerning him or her, which was provided to a controller, in a structured, commonly used and machine-readable format. He or she shall have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, as long as the processing is based on consent pursuant to point (a) of Article 6(1) of the GDPR or point (a) of Article 9(2) of the GDPR, or on a contract pursuant to point (b) of Article 6(1) of the GDPR, and the processing is carried out by automated means, as long as the processing is not necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.</p>
+
+        <p>Furthermore, in exercising his or her right to data portability pursuant to Article 20(1) of the GDPR, the data subject shall have the right to have personal data transmitted directly from one controller to another, where technically feasible and when doing so does not adversely affect the rights and freedoms of others.</p>
+
+        <p>In order to assert the right to data portability, the data subject may at any time contact us.</p>
+
+      </li>
+      <li>
+        <h4>g) Right to object</h4>
+        <p>Each data subject shall have the right granted by the European legislator to object, on grounds relating to his or her particular situation, at any time, to processing of personal data concerning him or her, which is based on point (e) or (f) of Article 6(1) of the GDPR. This also applies to profiling based on these provisions.</p>
+
+        <p>We shall no longer process the personal data in the event of the objection, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject, or for the establishment, exercise or defence of legal claims.</p>
+
+        <p>If we processes personal data for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning him or her for such marketing. This applies to profiling to the extent that it is related to such direct marketing. If the data subject objects to us to the processing for direct marketing purposes, we will no longer process the personal data for these purposes.</p>
+
+        <p>In addition, the data subject has the right, on grounds relating to his or her particular situation, to object to processing of personal data concerning him or her by us for scientific or historical research purposes, or for statistical purposes pursuant to Article 89(1) of the GDPR, unless the processing is necessary for the performance of a task carried out for reasons of public interest.</p>
+
+        <p>In order to exercise the right to object, the data subject may contact us. In addition, the data subject is free in the context of the use of information society services, and notwithstanding Directive 2002/58/EC, to use his or her right to object by automated means using technical specifications.</p>
+      </li>
+      <li><h4>h) Automated individual decision-making, including profiling</h4>
+        <p>Each data subject shall have the right granted by the European legislator not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her, or similarly significantly affects him or her, as long as the decision (1) is not is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) is not authorised by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, or (3) is not based on the data subject's explicit consent.</p>
+
+        <p>If the decision (1) is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) it is based on the data subject's explicit consent, we shall implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and contest the decision.</p>
+
+        <p>If the data subject wishes to exercise the rights concerning automated individual decision-making, he or she may, at any time, contact us.</p>
+
+      </li>
+      <li><h4>i) Right to withdraw data protection consent </h4>
+        <p>Each data subject shall have the right granted by the European legislator to withdraw his or her consent to processing of his or her personal data at any time. </p>
+
+        <p>If the data subject wishes to exercise the right to withdraw the consent, he or she may, at any time, contact us.</p>
+
+      </li>
+    </ul>
+    <h4>8. Data protection provisions about the application and use of Matomo</h4>
+    <p>On this website, the controller has integrated the Matomo component. Matomo is an open-source software tool for web analysis. Web analysis is the collection, gathering and evaluation of data on the behavior of visitors from Internet sites. A web analysis tool collects, inter alia, data on the website from which a data subject came to a website (so-called referrer), which pages of the website were accessed or how often and for which period of time a sub-page was viewed. A web analysis is mainly used for the optimization of a website and the cost-benefit analysis of Internet advertising.</p>
+
+    <p>The software is operated on the server of the controller, the data protection-sensitive log files are stored exclusively on this server.</p>
+
+    <p>The purpose of the Matomo component is the analysis of the visitor flows on our website. The controller uses the obtained data and information, inter alia, to evaluate the use of this website in order to compile online reports, which show the activities on our Internet pages.</p>
+
+    <p>Matomo sets a cookie on the information technology system of the data subject. The definition of cookies is explained above. With the setting of the cookie, an analysis of the use of our website is enabled. With each call-up to one of the individual pages of this website, the Internet browser on the information technology system of the data subject is automatically through the Matomo component prompted to submit data for the purpose of online analysis to our server. During the course of this technical procedure, we obtain knowledge about personal information, such as the IP address of the data subject, which serves to understand the origin of visitors and clicks.</p>
+
+    <p>The cookie is used to store personal information, such as the access time, the location from which access was made, and the frequency of visits to our website. With each visit of our Internet pages, these personal data, including the IP address of the Internet access used by the data subject, are transferred to our server. These personal data will be stored by us. We do not forward this personal data to third parties.</p>
+
+    <p>The data subject may, as stated above, prevent the setting of cookies through our website at any time by means of a corresponding adjustment of the web browser used and thus permanently deny the setting of cookies. Such an adjustment to the used Internet browser would also prevent Matomo from setting a cookie on the information technology system of the data subject. In addition, cookies already in use by Matomo may be deleted at any time via a web browser or other software programs.</p>
+
+    <p>In addition, the data subject has the possibility of objecting to a collection of data relating to a use of this Internet site that are generated by Matomo as well as the processing of these data by Matomo and the chance to preclude any such. For this, the data subject must set a "Do Not Track" option in the browser.</p>
+
+    <p>With each setting of the opt-out cookie, however, there is the possibility that the websites of the controller are no longer fully usable for the data subject.</p>
+
+    <p>Further information and the applicable data protection provisions of Matomo may be retrieved under https://matomo.org/privacy/.</p>
+
+    <h4>9. Data protection provisions about the application and use of Twitter</h4>
+    <p>On this website, the controller has integrated components of Twitter. Twitter is a multilingual, publicly-accessible microblogging service on which users may publish and spread so-called ‘tweets,’ e.g. short messages, which are limited to 280 characters. These short messages are available for everyone, including those who are not logged on to Twitter. The tweets are also displayed to so-called followers of the respective user. Followers are other Twitter users who follow a user's tweets. Furthermore, Twitter allows you to address a wide audience via hashtags, links or retweets.</p>
+
+    <p>The operating company of Twitter is Twitter International Company, One Cumberland Place, Fenian Street Dublin 2, D02 AX07, Ireland.</p>
+
+    <p>With each call-up to one of the individual pages of this Internet site, which is operated by the controller and on which a Twitter component (Twitter button) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to download a display of the corresponding Twitter component of Twitter. Further information about the Twitter buttons is available under https://about.twitter.com/de/resources/buttons. During the course of this technical procedure, Twitter gains knowledge of what specific sub-page of our website was visited by the data subject. The purpose of the integration of the Twitter component is a retransmission of the contents of this website to allow our users to introduce this web page to the digital world and increase our visitor numbers.</p>
+
+    <p>If the data subject is logged in at the same time on Twitter, Twitter detects with every call-up to our website by the data subject and for the entire duration of their stay on our Internet site which specific sub-page of our Internet page was visited by the data subject. This information is collected through the Twitter component and associated with the respective Twitter account of the data subject. If the data subject clicks on one of the Twitter buttons integrated on our website, then Twitter assigns this information to the personal Twitter user account of the data subject and stores the personal data.</p>
+
+    <p>Twitter receives information via the Twitter component that the data subject has visited our website, provided that the data subject is logged in on Twitter at the time of the call-up to our website. This occurs regardless of whether the person clicks on the Twitter component or not. If such a transmission of information to Twitter is not desirable for the data subject, then he or she may prevent this by logging off from their Twitter account before a call-up to our website is made.</p>
+
+    <p>The applicable data protection provisions of Twitter may be accessed under https://twitter.com/privacy?lang=en.</p>
+
+    <h4>10. Legal basis for the processing </h4>
+    <p>Art. 6(1) lit. a GDPR serves as the legal basis for processing operations for which we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1) lit. b GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. Is our company subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Art. 6(1) lit. c GDPR.
+      In rare cases, the processing of personal data may be necessary to protect the vital interests of the data subject or of another natural person. This would be the case, for example, if a visitor were injured in our company and his name, age, health insurance data or other vital information would have to be passed on to a doctor, hospital or other third party. Then the processing would be based on Art. 6(1) lit. d GDPR.
+      Finally, processing operations could be based on Article 6(1) lit. f GDPR. This legal basis is used for processing operations which are not covered by any of the abovementioned legal grounds, if processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR).
+    </p>
+
+    <h4>11. The legitimate interests pursued by the controller or by a third party</h4>
+    <p>Where the processing of personal data is based on Article 6(1) lit. f GDPR our legitimate interest is to carry out our business in favor of the well-being of all our employees and the shareholders.</p>
+
+    <h4>12. Period for which the personal data will be stored</h4>
+    <p>The criteria used to determine the period of storage of personal data is the respective statutory retention period. After expiration of that period, the corresponding data is routinely deleted, as long as it is no longer necessary for the fulfillment of the contract or the initiation of a contract.</p>
+
+    <h4>13. Provision of personal data as statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data </h4>
+    <p>We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner).
+
+      Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company signs a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded.
+
+      Before personal data is provided by the data subject, the data subject must contact any employee. The employee clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data.
+    </p>
+
+    <h4>14. Existence of automated decision-making</h4>
+    <p>As a responsible company, we do not use automatic decision-making or profiling.</p>
+
+    <p>Developed by the specialists for <a href="https://willing-able.com/">LegalTech</a> at Willing & Able that also developed the system for <a href="https://abletotrack.com/">Vacation schedule</a>. The legal texts contained in our privacy policy generator have been provided and published by <a href="https://dg-datenschutz.de/">Prof. Dr. h.c. Heiko Jonny Maniero</a> from the German Association for Data Protection and <a href="https://www.wbs-law.de/" rel="nofollow">Christian Solmecke</a> from WBS law.</p>
+
+
+  </div>
+</template>
+
+<script>
+export default {
+  name: "PrivacyPolicy",
+}
+</script>
+
+<style scoped lang="scss">
+h1, h2, h3, h4, h5, h6 {
+  color: var(--bs-primary)
+}
+</style>
diff --git a/yarn.lock b/yarn.lock
index 9af7097..9598c3d 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -329,6 +329,15 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@babel/parser@npm:^7.16.4":
+  version: 7.16.12
+  resolution: "@babel/parser@npm:7.16.12"
+  bin:
+    parser: ./bin/babel-parser.js
+  checksum: af287f0f3dfa564958a7dddfeb62e08c0de9ce9bd8447fcde0997da26ec477bf19f37161b9d970e2c7e0d1f77e441258907d3347beddd0d42cae85ed46947703
+  languageName: node
+  linkType: hard
+
 "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@npm:^7.15.4":
   version: 7.15.4
   resolution: "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@npm:7.15.4"
@@ -1958,6 +1967,18 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/compiler-core@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/compiler-core@npm:3.2.29"
+  dependencies:
+    "@babel/parser": ^7.16.4
+    "@vue/shared": 3.2.29
+    estree-walker: ^2.0.2
+    source-map: ^0.6.1
+  checksum: cc44fd93bb230661cb340e384d3e751c9d18177419eb75614e7b0a6b85cdca3c4b7f1bf0497585e8a5f6b788a9dbba497abdac2207c294f9a43613ec8031545b
+  languageName: node
+  linkType: hard
+
 "@vue/compiler-dom@npm:3.2.20":
   version: 3.2.20
   resolution: "@vue/compiler-dom@npm:3.2.20"
@@ -1978,6 +1999,16 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/compiler-dom@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/compiler-dom@npm:3.2.29"
+  dependencies:
+    "@vue/compiler-core": 3.2.29
+    "@vue/shared": 3.2.29
+  checksum: 46d3d48cbdfe441063f0ecf66740ba83ae8d7cfda982238820ef905a3757e0eda74666f0e557706292a2062243877ba99b251c3929a02aeffbd48d442e505d32
+  languageName: node
+  linkType: hard
+
 "@vue/compiler-sfc@npm:3.2.21":
   version: 3.2.21
   resolution: "@vue/compiler-sfc@npm:3.2.21"
@@ -1996,6 +2027,24 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/compiler-sfc@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/compiler-sfc@npm:3.2.29"
+  dependencies:
+    "@babel/parser": ^7.16.4
+    "@vue/compiler-core": 3.2.29
+    "@vue/compiler-dom": 3.2.29
+    "@vue/compiler-ssr": 3.2.29
+    "@vue/reactivity-transform": 3.2.29
+    "@vue/shared": 3.2.29
+    estree-walker: ^2.0.2
+    magic-string: ^0.25.7
+    postcss: ^8.1.10
+    source-map: ^0.6.1
+  checksum: efef43d1ae28e44d728a8cd5e687ed472e77fbc917dfdf4f3ca34a73418222a1ab2289e1b344789ef99a77f729d43afb0c405a9a5e6ca103f84dacde221f1252
+  languageName: node
+  linkType: hard
+
 "@vue/compiler-sfc@npm:^3.2.19":
   version: 3.2.20
   resolution: "@vue/compiler-sfc@npm:3.2.20"
@@ -2034,6 +2083,16 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/compiler-ssr@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/compiler-ssr@npm:3.2.29"
+  dependencies:
+    "@vue/compiler-dom": 3.2.29
+    "@vue/shared": 3.2.29
+  checksum: 56646786690a8ddb6030651e24804f33ed8f1f6cf887da5d7a04791d2fb9eacce73c2b9d62b223652d467da0c543dfb98c95a97bc96b46fbcb70cd71ef695f30
+  languageName: node
+  linkType: hard
+
 "@vue/component-compiler-utils@npm:^3.1.0, @vue/component-compiler-utils@npm:^3.1.2":
   version: 3.2.2
   resolution: "@vue/component-compiler-utils@npm:3.2.2"
@@ -2071,6 +2130,19 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/reactivity-transform@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/reactivity-transform@npm:3.2.29"
+  dependencies:
+    "@babel/parser": ^7.16.4
+    "@vue/compiler-core": 3.2.29
+    "@vue/shared": 3.2.29
+    estree-walker: ^2.0.2
+    magic-string: ^0.25.7
+  checksum: 52ee8ceaf96c76de5fcf36f9ba25dc3be9775914d0a61c54630c2a5cecdc0296bcce746aac3407bd9a5a6de678067e8e374fe09e2c5972c92026cfb4449f7232
+  languageName: node
+  linkType: hard
+
 "@vue/reactivity@npm:3.2.21":
   version: 3.2.21
   resolution: "@vue/reactivity@npm:3.2.21"
@@ -2080,6 +2152,15 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/reactivity@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/reactivity@npm:3.2.29"
+  dependencies:
+    "@vue/shared": 3.2.29
+  checksum: 07bfca8d6075a984676d8e103584e8447eaf7f60bb777dce652c452507225d077807b79365b8dcfded33a2424ba32f2518efb9ab313d4d59e69ccccf6ea56a5a
+  languageName: node
+  linkType: hard
+
 "@vue/ref-transform@npm:3.2.20":
   version: 3.2.20
   resolution: "@vue/ref-transform@npm:3.2.20"
@@ -2116,6 +2197,16 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/runtime-core@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/runtime-core@npm:3.2.29"
+  dependencies:
+    "@vue/reactivity": 3.2.29
+    "@vue/shared": 3.2.29
+  checksum: 4922001693376a066f0faf7b346f103c806b668daca5ba8cb0b040ab0fd59f41a6c53d2b0f3fa71057cec60f8801e33968caec275fba431d97b28ff33b9ef2be
+  languageName: node
+  linkType: hard
+
 "@vue/runtime-dom@npm:3.2.21":
   version: 3.2.21
   resolution: "@vue/runtime-dom@npm:3.2.21"
@@ -2127,6 +2218,17 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/runtime-dom@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/runtime-dom@npm:3.2.29"
+  dependencies:
+    "@vue/runtime-core": 3.2.29
+    "@vue/shared": 3.2.29
+    csstype: ^2.6.8
+  checksum: bb45006527ddae2934f92fe9b6fb8e3291549302641667f2582871555ceef502e0941ef5b4e2491cce4d7da8483e52b952d2e39950f1555512abd3a559a3a399
+  languageName: node
+  linkType: hard
+
 "@vue/server-renderer@npm:3.2.21":
   version: 3.2.21
   resolution: "@vue/server-renderer@npm:3.2.21"
@@ -2139,6 +2241,18 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/server-renderer@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/server-renderer@npm:3.2.29"
+  dependencies:
+    "@vue/compiler-ssr": 3.2.29
+    "@vue/shared": 3.2.29
+  peerDependencies:
+    vue: 3.2.29
+  checksum: 0321451f9dbce5692584155003eabea008720bd040a8dbb75cf4c626aeb9dda4e560c25e74514361991d1dd6581f39b896f2d2b940a24d6c8dfbe5a88086fc2c
+  languageName: node
+  linkType: hard
+
 "@vue/shared@npm:3.2.20":
   version: 3.2.20
   resolution: "@vue/shared@npm:3.2.20"
@@ -2153,6 +2267,13 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@vue/shared@npm:3.2.29":
+  version: 3.2.29
+  resolution: "@vue/shared@npm:3.2.29"
+  checksum: 0ee2ae764afe438fa378a8bfd751b56d2cd7c2ca225139d7a4ef75848145a3d811edd2a0a16a9392e3f75e5607d6d7392663a27d701eb48fc7abdcbcb33bc7cf
+  languageName: node
+  linkType: hard
+
 "@vue/web-component-wrapper@npm:^1.2.0":
   version: 1.3.0
   resolution: "@vue/web-component-wrapper@npm:1.3.0"
@@ -4116,6 +4237,7 @@ __metadata:
     vue: ^3.2.19
     vue-matomo: ^4.1.0
     vue-router: next
+    vue3-cookies: ^1.0.6
     vuex: ^4.0.2
   languageName: unknown
   linkType: soft
@@ -11763,6 +11885,15 @@ fsevents@~2.3.2:
   languageName: node
   linkType: hard
 
+"vue3-cookies@npm:^1.0.6":
+  version: 1.0.6
+  resolution: "vue3-cookies@npm:1.0.6"
+  dependencies:
+    vue: ^3.0.0
+  checksum: bb3ddabf0c67f17106768c03b345b4ad937bb19082e0d5a8ea762079ece7efecd60c80653251c79fb450ccfc22aa85ce9467d54ba05163cf9c942f6830617bf8
+  languageName: node
+  linkType: hard
+
 "vue@npm:3.2.21, vue@npm:^3.2.19":
   version: 3.2.21
   resolution: "vue@npm:3.2.21"
@@ -11776,6 +11907,19 @@ fsevents@~2.3.2:
   languageName: node
   linkType: hard
 
+"vue@npm:3.2.29, vue@npm:^3.0.0":
+  version: 3.2.29
+  resolution: "vue@npm:3.2.29"
+  dependencies:
+    "@vue/compiler-dom": 3.2.29
+    "@vue/compiler-sfc": 3.2.29
+    "@vue/runtime-dom": 3.2.29
+    "@vue/server-renderer": 3.2.29
+    "@vue/shared": 3.2.29
+  checksum: e9564e79015d4d62ebf97aad93567627e64627d3fd33fc7ba0614e83bca529c9f49085e66d99975219b8eed3fb72f7c034597dcaff2dba99d75457a826177263
+  languageName: node
+  linkType: hard
+
 "vuex@npm:^4.0.2":
   version: 4.0.2
   resolution: "vuex@npm:4.0.2"