From 7d1a436fd1c825a9290f65fed25131e31f56e4ad Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Fri, 24 Jul 2026 15:57:42 +0200
Subject: [PATCH 01/16] WIP

---
 src/backend/api.js                            | 24 ++++++++++++++---
 .../HostingPolicy/HostingPolicyRenderer.vue   |  4 +--
 .../TermsOfUse/TermsOfUseNavigationPanel.vue  | 26 +++++++++++++++----
 .../Pages/TermsOfUse/TermsOfUseRenderer.vue   | 14 ++++++----
 src/router/index.js                           | 21 ++++++++-------
 5 files changed, 64 insertions(+), 25 deletions(-)

diff --git a/src/backend/api.js b/src/backend/api.js
index b74b0264..08108628 100644
--- a/src/backend/api.js
+++ b/src/backend/api.js
@@ -58,6 +58,26 @@ export const getCurrentPolicies = async () => {
   return data.items
 }
 
+export const getPolicyByDate = async ({ policyType, activeFrom }) => {
+  const { data } = await axios.get(`/v1/policies/${policyType}/by_active_from/${activeFrom}`).data
+  return data;
+}
+
+export const getAllPoliciesByType = async ({ policyType }) => {
+  const { data } = await axios.get(`/v1/policies/${policyType}`).data
+  return data.items;
+}
+
+export const getCurrentPolicyByType = async ({ policyType }) => {
+  const { data } = await axios.get(`/v1/policies/${policyType}`).data
+  return data;
+}
+
+export const getUpcomingPolicyByType = async ({ policyType }) => {
+  const { data } = await axios.get(`/v1/policies/${policyType}/upcoming`).data
+  return data;
+}
+
 /* Wiki endpoints */
 export const countWikis = async () => (await axios.get('/wiki/count')).data.data // TODO This doesn't seem to exist and not used?
 export const myWikis = async () => (await axios.post('/wiki/mine')).data
@@ -102,10 +122,6 @@ export const wikiDiscovery = async ({ sort, direction, active, currentPage, resu
   })).data
 }
 
-export const policyByDate = async ({ policyType, activeFrom }) => {
-  return (await axios.get(`/v1/policies/${policyType}/by_active_from/${activeFrom}`)).data
-}
-
 export const importEntities = async ({
   wikiId,
   entityIds = [
diff --git a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
index d21c1430..a39b2def 100644
--- a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
+++ b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
@@ -39,10 +39,10 @@ export default {
   methods: {
     async loadPolicy () {
       try {
-        const policyType = 'hosting-policy' // TODO read this from component property
+        const policyType = 'hosting-policy' // TODO for a generalized component, read this from component property
         const activeFrom = this.policyActiveFrom
 
-        const response = await this.$api.policyByDate({ policyType, activeFrom })
+        const response = await this.$api.getPolicyByDate({ policyType, activeFrom })
 
         const metadata = await response.metadata
         const policy = versions[metadata.content_vue_file]
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
index 2ca6ac6c..a46bc01a 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
@@ -11,11 +11,9 @@ export default {
     PolicyNavigationPanel,
   },
   data: () => ({
-    // TODO read this from API
-    termsOfUseLinks: [
-      { title: 'Upcoming Version', routePath: '/terms-of-use/upcoming' },
-      { title: '11 April 2022 (current)', routePath: '/terms-of-use' },
-    ],
+    termsOfUseLinks: [],
+    policies: undefined,
+    error: undefined,
   }),
   computed: {
     currentLink: function () {
@@ -30,6 +28,24 @@ export default {
       return positionInList
     },
   },
+  methods: {
+    async loadPolicies () {
+      try {
+        const policyType = 'terms-of-use';
+        const response = await this.$api.getAllPoliciesByType({ policyType })
+
+        const items = await response.items;
+
+        this.policies = items;
+      } catch (error) {
+        this.error = error
+        console.error(error)
+      }
+    },
+  },
+  mounted () {
+    this.loadPolicies()
+  },
 }
 
 </script>
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index c3603503..65eac5f6 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -38,15 +38,19 @@ export default {
     return {
       policy: undefined,
       error: undefined,
+      policyType: 'terms-of-use',
     }
   },
   methods: {
     async loadPolicy () {
       try {
-        const policyType = 'terms-of-use' // TODO read this from component property
-        const activeFrom = this.policyActiveFrom
-
-        const response = await this.$api.policyByDate({ policyType, activeFrom })
+        const policyType = this.policyType; // TODO for a generalized component, read this from component property
+        
+        if (this.policyActiveFrom === undefined) {
+          const response = await this.$api.getCurrentPolicyByType({ policyType })
+        } else {
+          const response = await this.$api.getPolicyByDate({ policyType, activeFrom })
+        }
 
         const metadata = await response.metadata
         const policy = versions[metadata.content_vue_file]
@@ -66,7 +70,7 @@ export default {
     this.loadPolicy()
   },
   watch: {
-    policyId: function () {
+    policyActiveFrom: function () {
       this.loadPolicy()
     },
   },
diff --git a/src/router/index.js b/src/router/index.js
index 9c7f89ab..03069d0a 100644
--- a/src/router/index.js
+++ b/src/router/index.js
@@ -73,31 +73,34 @@ const router = new Router({
       name: 'ResetPassword',
       component: ResetPassword,
     },
-    // TODO should be handled by TermsOfUseRenderer
     {
       path: '/terms-of-use',
-      name: 'TermsOfUse',
-      component: TermsOfUse,
+      name: 'TermsOfUseRenderer',
+      component: TermsOfUseRenderer,
     },
-    // TODO should be handled by TermsOfUseRenderer
     {
       path: '/terms-of-use/upcoming',
-      name: 'TermsOfUseUpcoming',
-      component: TermsOfUseUpcoming,
+      name: 'TermsOfUseRendererUpcoming',
+      component: TermsOfUseRenderer,
     },
     {
       path: '/terms-of-use/:activeFrom',
-      name: 'TermsOfUseRenderer',
+      name: 'TermsOfUseRendererExact',
       component: TermsOfUseRenderer,
     },
     {
       path: '/hosting-policy/pilot',
-      name: 'Hosting Policy',
+      name: 'HostingPolicyPilot',
       component: HostingPolicy,
     },
     {
       path: '/hosting-policy/:activeFrom',
-      name: 'Hosting Policy',
+      name: 'HostingPolicyRendererExact',
+      component: HostingPolicyRenderer,
+    },
+    {
+      path: '/hosting-policy/upcoming',
+      name: 'HostingPolicyRendererUpcoming',
       component: HostingPolicyRenderer,
     },
     {

From ba50d69f25424139d570006503dfc3aa0907873d Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Fri, 24 Jul 2026 16:18:05 +0200
Subject: [PATCH 02/16] changes

---
 src/backend/api.js                                        | 8 ++++----
 .../Pages/TermsOfUse/TermsOfUseNavigationPanel.vue        | 7 +++----
 src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue    | 5 +++--
 src/router/index.js                                       | 2 --
 4 files changed, 10 insertions(+), 12 deletions(-)

diff --git a/src/backend/api.js b/src/backend/api.js
index 08108628..2b0a9201 100644
--- a/src/backend/api.js
+++ b/src/backend/api.js
@@ -60,22 +60,22 @@ export const getCurrentPolicies = async () => {
 
 export const getPolicyByDate = async ({ policyType, activeFrom }) => {
   const { data } = await axios.get(`/v1/policies/${policyType}/by_active_from/${activeFrom}`).data
-  return data;
+  return data
 }
 
 export const getAllPoliciesByType = async ({ policyType }) => {
   const { data } = await axios.get(`/v1/policies/${policyType}`).data
-  return data.items;
+  return data.items
 }
 
 export const getCurrentPolicyByType = async ({ policyType }) => {
   const { data } = await axios.get(`/v1/policies/${policyType}`).data
-  return data;
+  return data
 }
 
 export const getUpcomingPolicyByType = async ({ policyType }) => {
   const { data } = await axios.get(`/v1/policies/${policyType}/upcoming`).data
-  return data;
+  return data
 }
 
 /* Wiki endpoints */
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
index a46bc01a..dab0aca3 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
@@ -31,12 +31,11 @@ export default {
   methods: {
     async loadPolicies () {
       try {
-        const policyType = 'terms-of-use';
+        const policyType = 'terms-of-use'
         const response = await this.$api.getAllPoliciesByType({ policyType })
+        const items = await response.items
 
-        const items = await response.items;
-
-        this.policies = items;
+        this.policies = items
       } catch (error) {
         this.error = error
         console.error(error)
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index 65eac5f6..7d71ec27 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -44,8 +44,9 @@ export default {
   methods: {
     async loadPolicy () {
       try {
-        const policyType = this.policyType; // TODO for a generalized component, read this from component property
-        
+        const policyType = this.policyType // TODO for a generalized component, read this from component property
+        const activeFrom = this.activeFrom
+
         if (this.policyActiveFrom === undefined) {
           const response = await this.$api.getCurrentPolicyByType({ policyType })
         } else {
diff --git a/src/router/index.js b/src/router/index.js
index 03069d0a..71c39fab 100644
--- a/src/router/index.js
+++ b/src/router/index.js
@@ -14,8 +14,6 @@ import ResetPassword from '@/components/Pages/ResetPassword'
 import EmailVerification from '@/components/Pages/EmailVerification'
 import CreateWiki from '@/components/Pages/CreateWiki'
 import TabSettings from '@/components/Pages/ManageWiki/TabSettings'
-import TermsOfUse from '@/components/Pages/TermsOfUse/Current.vue'
-import TermsOfUseUpcoming from '@/components/Pages/TermsOfUse/Upcoming.vue'
 import TermsOfUseRenderer from '@/components/Pages/TermsOfUse/TermsOfUseRenderer.vue'
 import Privacy from '@/components/Pages/Privacy/Privacy'
 import User from '@/components/Pages/User'

From 69b740698d7b548522ec270884557fddd5435d49 Mon Sep 17 00:00:00 2001
From: Dat <dat.nguyen@wikimedia.de>
Date: Mon, 27 Jul 2026 13:17:49 +0200
Subject: [PATCH 03/16] feat(ui): source policy navigation from API instead of
 hardcode

---
 src/backend/api.js                            |   8 +-
 .../Components/PolicyNavigationPanel.vue      |   2 +-
 .../TermsOfUse/TermsOfUseNavigationPanel.vue  | 125 ++++++++++++++++--
 3 files changed, 119 insertions(+), 16 deletions(-)

diff --git a/src/backend/api.js b/src/backend/api.js
index 2b0a9201..4c8bbfac 100644
--- a/src/backend/api.js
+++ b/src/backend/api.js
@@ -59,22 +59,22 @@ export const getCurrentPolicies = async () => {
 }
 
 export const getPolicyByDate = async ({ policyType, activeFrom }) => {
-  const { data } = await axios.get(`/v1/policies/${policyType}/by_active_from/${activeFrom}`).data
+  const { data } = await axios.get(`/v1/policies/${policyType}/by_active_from/${activeFrom}`)
   return data
 }
 
 export const getAllPoliciesByType = async ({ policyType }) => {
-  const { data } = await axios.get(`/v1/policies/${policyType}`).data
+  const { data } = await axios.get(`/v1/policies/${policyType}`)
   return data.items
 }
 
 export const getCurrentPolicyByType = async ({ policyType }) => {
-  const { data } = await axios.get(`/v1/policies/${policyType}`).data
+  const { data } = await axios.get(`/v1/policies/${policyType}/current`)
   return data
 }
 
 export const getUpcomingPolicyByType = async ({ policyType }) => {
-  const { data } = await axios.get(`/v1/policies/${policyType}/upcoming`).data
+  const { data } = await axios.get(`/v1/policies/${policyType}/upcoming`)
   return data
 }
 
diff --git a/src/components/Pages/Components/PolicyNavigationPanel.vue b/src/components/Pages/Components/PolicyNavigationPanel.vue
index 1557d78c..180969ee 100644
--- a/src/components/Pages/Components/PolicyNavigationPanel.vue
+++ b/src/components/Pages/Components/PolicyNavigationPanel.vue
@@ -1,5 +1,5 @@
 <template>
-    <v-expansion-panels v-bind:value="$vuetify.breakpoint.mdAndUp ? 0 : null" v-if="links">
+    <v-expansion-panels v-bind:value="$vuetify.breakpoint.mdAndUp ? 0 : null" v-if="links && links.length">
         <v-expansion-panel>
             <v-expansion-panel-header class="grey lighten-3">{{ title }}</v-expansion-panel-header>
 
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
index dab0aca3..a46f5b83 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
@@ -1,28 +1,105 @@
 <template>
-    <PolicyNavigationPanel title="All Versions" :links="termsOfUseLinks"  :currentLink="currentLink" />
+  <PolicyNavigationPanel :title="title" :links="links" :currentLink="currentLink" />
 </template>
 
 <script>
 import PolicyNavigationPanel from '../Components/PolicyNavigationPanel.vue'
 
+const parseActiveFrom = (activeFrom) => {
+  if (activeFrom === null || activeFrom === undefined) {
+    return null
+  }
+
+  return new Date(`${activeFrom}T00:00:00Z`)
+}
+
+const comparePolicies = (left, right) => {
+  const leftActiveFrom = parseActiveFrom(left.metadata.active_from)
+  const rightActiveFrom = parseActiveFrom(right.metadata.active_from)
+
+  if (leftActiveFrom === null && rightActiveFrom === null) {
+    return 0
+  }
+
+  if (leftActiveFrom === null) {
+    return 1
+  }
+
+  if (rightActiveFrom === null) {
+    return -1
+  }
+
+  return rightActiveFrom - leftActiveFrom || right.metadata.policy_id - left.metadata.policy_id
+}
+
 export default {
   name: 'TermsOfUseNavigationPanel',
   components: {
     PolicyNavigationPanel,
   },
+  props: {
+    basePath: {
+      type: String,
+      default: '/terms-of-use',
+    },
+    policyType: {
+      type: String,
+      default: 'terms-of-use',
+    },
+    title: {
+      type: String,
+      default: 'All Versions',
+    },
+  },
   data: () => ({
-    termsOfUseLinks: [],
-    policies: undefined,
+    policies: [],
     error: undefined,
   }),
   computed: {
+    links: function () {
+      const sortedPolicies = [...this.policies].sort(comparePolicies)
+      const today = new Date()
+      today.setHours(0, 0, 0, 0)
+
+      const currentPolicy = sortedPolicies.find(policy => {
+        const activeFrom = parseActiveFrom(policy.metadata.active_from)
+        return activeFrom === null || activeFrom <= today
+      })
+
+      const upcomingPolicy = sortedPolicies.find(policy => {
+        const activeFrom = parseActiveFrom(policy.metadata.active_from)
+        return activeFrom !== null && activeFrom > today
+      })
+
+      const otherPolicies = sortedPolicies.filter(policy => {
+        const policyId = policy.metadata.policy_id
+        const currentPolicyId = currentPolicy ? currentPolicy.metadata.policy_id : null
+        const upcomingPolicyId = upcomingPolicy ? upcomingPolicy.metadata.policy_id : null
+
+        return policyId !== currentPolicyId && policyId !== upcomingPolicyId
+      })
+
+      const orderedPolicies = [currentPolicy, upcomingPolicy, ...otherPolicies].filter(Boolean)
+
+      return orderedPolicies.map(policy => {
+        const activeFrom = policy.metadata.active_from
+        const isCurrentPolicy = currentPolicy && policy.metadata.policy_id === currentPolicy.metadata.policy_id
+        const isUpcomingPolicy = upcomingPolicy && policy.metadata.policy_id === upcomingPolicy.metadata.policy_id
+
+        return {
+          routePath: this.routePathForPolicy({ activeFrom, isCurrentPolicy, isUpcomingPolicy }),
+          title: this.titleForPolicy({ activeFrom, isCurrentPolicy, isUpcomingPolicy }),
+        }
+      })
+    },
     currentLink: function () {
       const isCurrentPath = (element) => element.routePath === this.$route.path
-      const positionInList = this.termsOfUseLinks.findIndex(isCurrentPath)
+      const positionInList = this.links.findIndex(isCurrentPath)
 
       if (positionInList === -1) {
-        // not in a list, must be current version, because the TermsOfUseRenderer only allows accessing the current version by its active_from date
-        return 1
+        const currentVersionIndex = this.links.findIndex(element => element.routePath === this.basePath)
+
+        return currentVersionIndex === -1 ? 0 : currentVersionIndex
       }
 
       return positionInList
@@ -30,21 +107,47 @@ export default {
   },
   methods: {
     async loadPolicies () {
-      try {
-        const policyType = 'terms-of-use'
-        const response = await this.$api.getAllPoliciesByType({ policyType })
-        const items = await response.items
+      this.error = undefined
 
-        this.policies = items
+      try {
+        const response = await this.$api.getAllPoliciesByType({ policyType: this.policyType })
+        this.policies = response
       } catch (error) {
         this.error = error
         console.error(error)
       }
     },
+    routePathForPolicy ({ activeFrom, isCurrentPolicy, isUpcomingPolicy }) {
+      if (isCurrentPolicy) {
+        return this.basePath
+      }
+
+      if (isUpcomingPolicy) {
+        return `${this.basePath}/upcoming`
+      }
+
+      return `${this.basePath}/${activeFrom}`
+    },
+    titleForPolicy ({ activeFrom, isCurrentPolicy, isUpcomingPolicy }) {
+      if (isCurrentPolicy) {
+        return 'Current version'
+      }
+
+      if (isUpcomingPolicy) {
+        return 'Upcoming version'
+      }
+
+      return activeFrom
+    },
   },
   mounted () {
     this.loadPolicies()
   },
+  watch: {
+    policyType () {
+      this.loadPolicies()
+    },
+  },
 }
 
 </script>

From d25202c87bcc5482ec1fe35428dac3061d910e91 Mon Sep 17 00:00:00 2001
From: Dat <dat.nguyen@wikimedia.de>
Date: Mon, 27 Jul 2026 13:20:37 +0200
Subject: [PATCH 04/16] feat(ui): render policies with API

---
 src/components/Layout/Foot.vue                |  2 +-
 .../HostingPolicy/HostingPolicyRenderer.vue   | 56 +++++++++++++++++--
 .../Pages/TermsOfUse/TermsOfUseRenderer.vue   | 48 ++++++++++++++--
 src/components/Pages/TermsOfUse/Upcoming.vue  |  6 --
 src/router/index.js                           |  5 ++
 5 files changed, 102 insertions(+), 15 deletions(-)

diff --git a/src/components/Layout/Foot.vue b/src/components/Layout/Foot.vue
index d3518768..1070f3a2 100644
--- a/src/components/Layout/Foot.vue
+++ b/src/components/Layout/Foot.vue
@@ -21,7 +21,7 @@
           <ul class="footer-list">
             <li><router-link to="/privacy-policy">Privacy Policy</router-link></li>
             <li><router-link to="/terms-of-use">Terms of Use</router-link></li>
-            <li><router-link to="/hosting-policy/pilot">Hosting Policy</router-link></li>
+            <li><router-link to="/hosting-policy">Hosting Policy</router-link></li>
             <li><router-link to="/dsa-info">Digital Services Act Information</router-link></li>
             <li><a target="_blank" rel="noopener noreferrer" href="https://www.wikimedia.de/impressum/">Imprint</a></li>
             <li><router-link to="/complaint">Report illegal content</router-link></li>
diff --git a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
index a39b2def..db752f08 100644
--- a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
+++ b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
@@ -4,8 +4,18 @@
       An error occurred while trying to load the requested policy. Please try again later.
     </v-alert>
     <v-container class="fill-height" fluid v-if="!error">
+      <v-row v-if="isUpcomingPolicy" justify="center">
+        <v-col cols="11">
+          <v-alert type="info">
+            This is an upcoming version. You can find the
+            <router-link class="white--text" to="/hosting-policy">current version here</router-link>.
+          </v-alert>
+        </v-col>
+      </v-row>
+
       <v-row justify="center">
         <v-col cols="11" md="4" order-md="last">
+          <TermsOfUseNavigationPanel basePath="/hosting-policy" policyType="hosting-policy" title="All Versions" />
         </v-col>
 
         <v-col cols="11" md="8">
@@ -18,37 +28,72 @@
 
 <script>
 
+import TermsOfUseNavigationPanel from '../TermsOfUse/TermsOfUseNavigationPanel.vue'
+
 export const versions = {
   'hosting-policy/version-1.vue': () => ({ component: import('./hosting-policy/version-1.vue') }),
 }
 
+const isFutureDate = (activeFrom) => {
+  if (activeFrom === null || activeFrom === undefined) {
+    return false
+  }
+
+  const date = new Date(`${activeFrom}T00:00:00Z`)
+  const today = new Date()
+  today.setHours(0, 0, 0, 0)
+
+  return date > today
+}
+
 export default {
   name: 'HostingPolicyRenderer',
-  components: {},
+  components: {
+    TermsOfUseNavigationPanel,
+  },
   computed: {
     policyActiveFrom: function () {
       return this.$route.params.activeFrom
     },
+    isUpcomingRoute: function () {
+      return this.$route.path === '/hosting-policy/upcoming'
+    },
+    isUpcomingPolicy: function () {
+      return isFutureDate(this.policyMetadata && this.policyMetadata.active_from)
+    },
   },
   data () {
     return {
       policy: undefined,
+      policyMetadata: undefined,
       error: undefined,
     }
   },
   methods: {
     async loadPolicy () {
+      this.policy = undefined
+      this.policyMetadata = undefined
+      this.error = undefined
+
       try {
         const policyType = 'hosting-policy' // TODO for a generalized component, read this from component property
         const activeFrom = this.policyActiveFrom
+        let response
 
-        const response = await this.$api.getPolicyByDate({ policyType, activeFrom })
+        if (this.isUpcomingRoute) {
+          response = await this.$api.getUpcomingPolicyByType({ policyType })
+        } else if (activeFrom === undefined) {
+          response = await this.$api.getCurrentPolicyByType({ policyType })
+        } else {
+          response = await this.$api.getPolicyByDate({ policyType, activeFrom })
+        }
 
-        const metadata = await response.metadata
+        const metadata = response.metadata
         const policy = versions[metadata.content_vue_file]
 
         if (policy !== undefined) {
           this.policy = policy
+          this.policyMetadata = metadata
         } else {
           this.error = 'missing policy'
         }
@@ -62,7 +107,10 @@ export default {
     this.loadPolicy()
   },
   watch: {
-    policyId: function () {
+    policyActiveFrom: function () {
+      this.loadPolicy()
+    },
+    isUpcomingRoute: function () {
       this.loadPolicy()
     },
   },
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index 7d71ec27..d30ee304 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -4,6 +4,15 @@
       An error occurred while trying to load the requested policy. Please try again later.
     </v-alert>
     <v-container class="fill-height" fluid v-if="!error">
+      <v-row v-if="isUpcomingPolicy" justify="center">
+        <v-col cols="11">
+          <v-alert type="info">
+            This is an upcoming version. You can find the
+            <router-link class="white--text" to="/terms-of-use">current version here</router-link>.
+          </v-alert>
+        </v-col>
+      </v-row>
+
       <v-row justify="center">
         <v-col cols="11" md="4" order-md="last">
           <TermsOfUseNavigationPanel />
@@ -22,6 +31,19 @@ import TermsOfUseNavigationPanel from './TermsOfUseNavigationPanel.vue'
 
 export const versions = {
   'terms-of-use/version-1.vue': () => ({ component: import('./terms-of-use/version-1.vue') }),
+  'terms-of-use/version-2.vue': () => ({ component: import('./Upcoming.vue') }),
+}
+
+const isFutureDate = (activeFrom) => {
+  if (activeFrom === null || activeFrom === undefined) {
+    return false
+  }
+
+  const date = new Date(`${activeFrom}T00:00:00Z`)
+  const today = new Date()
+  today.setHours(0, 0, 0, 0)
+
+  return date > today
 }
 
 export default {
@@ -33,31 +55,46 @@ export default {
     policyActiveFrom: function () {
       return this.$route.params.activeFrom
     },
+    isUpcomingRoute: function () {
+      return this.$route.path === '/terms-of-use/upcoming'
+    },
+    isUpcomingPolicy: function () {
+      return isFutureDate(this.policyMetadata && this.policyMetadata.active_from)
+    },
   },
   data () {
     return {
       policy: undefined,
+      policyMetadata: undefined,
       error: undefined,
       policyType: 'terms-of-use',
     }
   },
   methods: {
     async loadPolicy () {
+      this.policy = undefined
+      this.policyMetadata = undefined
+      this.error = undefined
+
       try {
         const policyType = this.policyType // TODO for a generalized component, read this from component property
         const activeFrom = this.activeFrom
+        let response
 
-        if (this.policyActiveFrom === undefined) {
-          const response = await this.$api.getCurrentPolicyByType({ policyType })
+        if (this.isUpcomingRoute) {
+          response = await this.$api.getUpcomingPolicyByType({ policyType })
+        } else if (activeFrom === undefined) {
+          response = await this.$api.getCurrentPolicyByType({ policyType })
         } else {
-          const response = await this.$api.getPolicyByDate({ policyType, activeFrom })
+          response = await this.$api.getPolicyByDate({ policyType, activeFrom })
         }
 
-        const metadata = await response.metadata
+        const metadata = response.metadata
         const policy = versions[metadata.content_vue_file]
 
         if (policy !== undefined) {
           this.policy = policy
+          this.policyMetadata = metadata
         } else {
           this.error = 'missing policy'
         }
@@ -74,6 +111,9 @@ export default {
     policyActiveFrom: function () {
       this.loadPolicy()
     },
+    isUpcomingRoute: function () {
+      this.loadPolicy()
+    },
   },
 }
 </script>
diff --git a/src/components/Pages/TermsOfUse/Upcoming.vue b/src/components/Pages/TermsOfUse/Upcoming.vue
index 4094c294..e236fb4a 100644
--- a/src/components/Pages/TermsOfUse/Upcoming.vue
+++ b/src/components/Pages/TermsOfUse/Upcoming.vue
@@ -8,12 +8,6 @@
 
         <v-col cols="11" md="8">
           <h1>Terms Of Use</h1>
-          <v-alert
-            type="info"
-          >
-           This is an upcoming version. You can find the
-            <router-link class="white--text" to="/terms-of-use">current version here</router-link>.
-          </v-alert>
           <v-alert
             text
             color="info"
diff --git a/src/router/index.js b/src/router/index.js
index 71c39fab..177d61af 100644
--- a/src/router/index.js
+++ b/src/router/index.js
@@ -86,6 +86,11 @@ const router = new Router({
       name: 'TermsOfUseRendererExact',
       component: TermsOfUseRenderer,
     },
+    {
+      path: '/hosting-policy',
+      name: 'HostingPolicy',
+      component: HostingPolicyRenderer,
+    },
     {
       path: '/hosting-policy/pilot',
       name: 'HostingPolicyPilot',

From eb6b03e7e63ef1578e0c96d50edd72a73f266105 Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 11:34:53 +0200
Subject: [PATCH 05/16] fix duplicated navigationpolicy

---
 .../Pages/TermsOfUse/TermsOfUseRenderer.vue   |    2 +-
 src/components/Pages/TermsOfUse/Upcoming.vue  | 1158 -----------------
 .../TermsOfUse/terms-of-use/version-1.vue     |    1 -
 .../TermsOfUse/terms-of-use/version-2.vue     | 1144 ++++++++++++++++
 4 files changed, 1145 insertions(+), 1160 deletions(-)
 delete mode 100644 src/components/Pages/TermsOfUse/Upcoming.vue
 create mode 100644 src/components/Pages/TermsOfUse/terms-of-use/version-2.vue

diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index d30ee304..cae1f91c 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -31,7 +31,7 @@ import TermsOfUseNavigationPanel from './TermsOfUseNavigationPanel.vue'
 
 export const versions = {
   'terms-of-use/version-1.vue': () => ({ component: import('./terms-of-use/version-1.vue') }),
-  'terms-of-use/version-2.vue': () => ({ component: import('./Upcoming.vue') }),
+  'terms-of-use/version-2.vue': () => ({ component: import('./terms-of-use/version-2.vue') }),
 }
 
 const isFutureDate = (activeFrom) => {
diff --git a/src/components/Pages/TermsOfUse/Upcoming.vue b/src/components/Pages/TermsOfUse/Upcoming.vue
deleted file mode 100644
index e236fb4a..00000000
--- a/src/components/Pages/TermsOfUse/Upcoming.vue
+++ /dev/null
@@ -1,1158 +0,0 @@
-<template>
-  <v-main>
-    <v-container class="fill-height" fluid>
-      <v-row justify="center">
-        <v-col cols="11" md="4" order-md="last">
-            <TermsOfUseNavigationPanel />
-        </v-col>
-
-        <v-col cols="11" md="8">
-          <h1>Terms Of Use</h1>
-          <v-alert
-            text
-            color="info"
-          >
-            <div class="light-blue--text text--darken-4">
-              <div class="text-h6 mb-3">What changed from
-                <router-link class="text-decoration-none light-blue--text text--darken-4" to="/terms-of-use">
-                  the previous version</router-link>
-              </div>
-              <p>The Terms of Use were revised to ensure compliance with the European Union’s
-                Digital Services Act (DSA) and to improve transparency about how Wikibase Cloud operates.</p>
-              <v-expand-transition>
-                <div v-if="show || !isMobile">
-                  <div>
-                    <div>Key updates:</div>
-                    <ul class="mb-3">
-                      <li>
-                        We have clarified when and how user accounts or individual instances may be suspended or terminated, including notice periods and proportionality principles.
-                      </li>
-                      <li>
-                        The new version explains more clearly how decisions are made, including how users can raise concerns or file complaints about moderation actions.
-                      </li>
-                      <li>
-                        The responsibilities of instance managers and contributors are described in more detail, especially regarding compliance with applicable laws and acceptable use of the platform.
-                      </li>
-                      <li>
-                        The Terms now explicitly reference applicable GDPR requirements and include updated wording to reflect international data transfer safeguards.
-                      </li>
-                      <li>
-                        The document has been reorganized and clarified to make rights, obligations, and processes easier to understand.
-                      </li>
-                      <li>
-                        We have introduced a separate Hosting Policy that defines additional rules for using the platform. This policy is now explicitly incorporated into the Terms of Use and forms part of the agreement users must accept.
-                      </li>
-                    </ul>
-                  </div>
-                  <div>
-                    These changes do not alter the core purpose of Wikibase Cloud as a free hosting platform for open knowledge projects, but they introduce clearer rules, including a separate Hosting Policy, and provide stronger legal transparency in line with EU regulatory requirements.
-                  </div>
-                </div>
-              </v-expand-transition>
-            </div>
-
-              <div v-if="isMobile" class="mt-2 d-flex justify-space-between">
-                <v-btn
-                  text
-                  class="light-blue--text text--darken-2"
-                  size="small"
-                  @click="show = !show"
-                >
-                  {{ show ? 'See less' : 'See more' }}
-                </v-btn>
-                <v-btn
-                  class="pa-2 mt-auto d-flex justify-end"
-                  icon
-                  @click="show = !show"
-                >
-                  <v-icon>{{ show ? 'mdi-chevron-up' : 'mdi-chevron-down' }}</v-icon>
-                </v-btn>
-              </div>
-          </v-alert>
-          <h2 class="mb-2">1. Definitions</h2>
-          <p>In addition to terms defined elsewhere in this
-            Agreement, the following terms have the following meanings:</p>
-          <p>1.1 “Manager Account” or “Account”: The personal Account provided by Wikibase.cloud
-            to the User on the Platform after the User’s registration.</p>
-          <p>1.2 “Content”: Any type of media (for example text, video files) uploaded to the
-            Platform by a User.</p>
-          <p>1.3 “User”: A natural person that registers for and
-            uses the Platform.</p>
-          <p>1.4 “Wikimedia”: Wikimedia Deutschland – Gesellschaft
-            zur Förderung Freien Wissens e. V.</p>
-          <p>1.5 “Wikibase Instance” or “Site”: an open knowledge base that can be
-            created and run by anyone on Wikibase.cloud.
-          </p>
-          <h2 class="mb-2">2. Scope and Applicability</h2>
-          <p>2.1 Wikimedia, Tempelhofer Ufer 23/24, 10963 Berlin, provides
-            Wikibase.cloud (the „Platform“), a free cloud-based Platform that hosts
-            instances of Wikibase. It offers collaborative space to pool, edit and
-            curate information and is accessible under <router-link to="/">https://www.wikibase.cloud/</router-link>.</p>
-          <p>2.2 These Terms of Use govern the legal relationship between Wikimedia
-            and the User and apply to all actions of the User and Wikimedia on or in
-            connection with the Platform (the „Agreement“).</p>
-          <h2 class="mb-2">3. Conclusion of the Contract and Registration for an Account</h2>
-          <p>3.1 To use the Platform, the
-            User must open a Manager Account. Opening a Manager Account is free of
-            charge for the User. The User can sign up directly by visiting the
-            website <router-link to="/">https://www.wikibase.cloud/</router-link> and clicking “Sign Up”.</p>
-          <p>3.2 When registering, the User is required to provide certain basic
-            information, including an email address and a password.</p>
-          <p>3.3 By clicking
-            on “Create Account”, the User requests Wikimedia to create an Account on
-            the Platform. Wikimedia will send an email with a legally binding offer
-            to open the Account and to confirm the user’s email address. By clicking
-            on “verify email”, the User accepts the offer, concludes the Agreement
-            with Wikimedia and opens the Account.</p>
-          <p>3.4 The User shall keep the Account
-            information, in particular the chosen password, confidential and shall
-            not disclose it to third parties. Any misuse or suspected misuse must be
-            reported to Wikimedia Deutschland immediately.</p>
-          <p> 3.5 The User can access
-            the latest version of these Terms at any time on the Platform. The
-            Agreement is concluded in English and the Terms are only available in
-            English.</p>
-          <h2 class="mb-2">4. Creating a Wikibase Instance and its basic functions</h2>
-          <p>4.1 After creating a Manager Account and logging into it, the User can
-            create a Wikibase Instance on their dashboard page.</p>
-          <p>4.2 To create a
-            Wikibase Instance, the User is required to provide certain basic
-            information, including Site Name, Site Domain and Username.</p>
-          <p>4.3 By
-            clicking on “Create Wiki”, the User submits the form. Once the form has
-            been successfully submitted, the Wikibase Instance will be created and
-            become available on the dashboard.</p>
-          <p>4.4 Wikimedia will send the User an
-            email with Account details, including the username and a temporary
-            password. After logging in with the provided password, the User is
-            prompted to create a new password.</p>
-          <p>4.5 The User shall keep the Account
-            information, in particular the chosen password, confidential and shall
-            not disclose it to third parties. Any misuse or suspected misuse must be
-            reported to Wikimedia immediately.</p>
-          <p>4.6 Once the Wikibase Instance has
-            been created, the basic functions are available to the User, which may
-            change from time to time. For example, the User can create a main page,
-            add a logo and create their own legal terms for their Wiki. The User can
-            also manually enter, import or delete data or any other information or
-            media (the “Content”) using the tools provided. Wikibase is a
-            collaborative Platform. The User can enable other persons to register
-            for an Account on their Wikibase Instance or upload Content.</p>
-          <h2 class="mb-2">5. Rules of the Platform</h2>
-          <p>5.1 The User may only use the Platform in accordance with
-            the Terms of Use and the additional rules laid down in the Hosting
-            Policy, which is hereby explicitly incorporated into the Agreement. In
-            particular, the User may not create, post, share, link to or otherwise
-            interact with Content that violates our rules or any laws.</p>
-          <p>5.2 The User
-            is responsible for any Content that they or other persons publish on
-            their registered Wikibase Instance. The User shall take all reasonable
-            steps to inform other persons using their Wikibase Instance of all
-            restrictions laid down in these Terms of Use and to ensure that these
-            restrictions are obeyed. The User must have all the necessary rights to
-            create, publish or share Content. The User agrees not to upload or share
-            any Content on their Wikibase Instance that infringes the intellectual
-            property rights of third persons or that is otherwise unlawful.</p>
-          <div class="mb-3">5.3 It is specifically prohibited to:
-          <ul>
-            <li>Upload or distribute Content that is
-              insulting, abusive, offensive, racist, threatening, harmful to minors,
-              pornographic, violates personal rights, promotes violence or sedition,
-              incites criminal acts, provides instructions on how to commit criminal
-              acts, or provides services that involve pornographic and/or erotic
-              Content or any other illegal Content</li>
-
-            <li>Upload or distribute Content
-              that is copied as a whole or in part from another protected work or
-              material without the permission of the respective copyright owner;</li>
-
-            <li>Upload or distribute Content that violates or infringes the rights of
-              third parties, in particular personal rights, copyrights or other
-              intellectual property rights or any other rights of third parties</li>
-
-            <li>Upload or distribute Content that contains personal, confidential or
-              non-public information</li>
-            <li>Contact other users of the Platform in a
-              disrespectful and rude manner, as well as to buy or sell products or
-              services;</li>
-            <li>Provide false data or information, as well as false data or
-              information of third parties; or</li>
-            <li>Sell or otherwise transfer the User Account to another person.</li>
-          </ul></div>
-
-          <p>5.4 The User should be aware that the sites
-            may be edited by the public and, as such, may contain inappropriate
-            Content at any time.</p>
-
-          <h2 class="mb-2">6. Moderation of Content</h2>
-          <p>6.1 Wikimedia does not
-            monitor Content on the Platform, but reserves the right to conduct
-            random checks, particularly if there are indications of violations.
-            Wikimedia does not use any automatic moderation technology or similar
-            tools that automatically scan, edit, block or remove Content.</p>
-          <p>6.2 Wikimedia may remove or restrict access to Content and/or delete or
-            restrict access to the User’s Account and/or delete or restrict access
-            to the Wikibase Instance if Wikimedia has reasonable grounds to believe
-            that Content violates the Agreement or applicable law.</p>
-          <p>6.3 If Wikimedia
-            removes or restricts access to Content, Wikimedia will notify the User
-            immediately and explain the reasons for the decision, unless to do so
-            would harm Wikimedia, or other third parties, or Wikimedia is legally
-            prevented from notifying the User.</p>
-          <p>6.4 Wikimedia will always proceed
-            carefully, objectively and proportionately when examining Content and
-            implementing measures, and will take into account the rights and
-            legitimate interests of all parties involved.</p>
-          <div class="mb-3">6.5 If the User believes
-            that Wikimedia has erred in one of the measures mentioned above in this
-            section 6, the User may request a review using the complaint functions
-            and Wikimedia will review and reconsider the decision. The following
-            rules apply to complaints:
-          <ul>
-            <li>The User may file a complaint against the
-              removal of the Content, the suspension or termination of the Account, or
-              the rejection of a report submitted by the User regarding Content that
-              the User considers to be illegal.</li>
-            <li>The User is not entitled to file a
-              complaint if the User has already been warned for improper use of
-              Wikimedia’s complaint system. This is the case, for example, if the User
-              repeatedly submits identical complaints without justification.</li>
-            <li>A
-              complaint must be made within six months of the date on which the User
-              was notified of our decision.</li>
-            <li>Wikimedia deals with complaints
-              promptly, carefully and without discrimination or arbitrariness. In
-              order to do this, Wikimedia needs all relevant information from the User
-              to understand the complaint. Complaints with offensive or inappropriate
-              language may result in the suspension of complaints after a warning.</li>
-            <li>Wikimedia shall promptly decide whether to reverse or uphold the
-              original action. The User will receive the reasoned decision promptly.</li>
-            <li>In considering the complaint, Wikimedia will take into account the
-              seriousness of the breach, the reason for the complaint, the frequency
-              and impact of the breaches and the intention behind the breach.</li>
-            <li>This section is without prejudice to the rights of EU users to take their
-              case to certified out-of-court complaint bodies. For more information,
-              <router-link to="/dsa-info">please click here</router-link>.
-            </li>
-          </ul></div>
-          <h2 class="mb-2">7. Grant of rights of use</h2>
-          <p>7.1 The User grants
-            Wikimedia the rights of use to the uploaded Content for the purpose of
-            Wikimedia’s provision of the Platform.</p>
-          <p>7.2 Wikimedia reserves the right to close, move, merge, or rename a site
-            for any reason. Wikimedia shall not be held liable for any modification,
-            suspension or discontinuance of any site, or of the Platform as a whole.</p>
-
-          <h2 class="mb-2">8. Term and Termination</h2>
-          <p>8.1 The terms of this Agreement commence upon the
-            User’s registration.</p>
-          <p>8.2 The User can delete their Account by contacting
-            Wikimedia, for example, via <router-link to="/contact">https://www.wikibase.cloud/contact.</router-link></p>
-          <p>8.3 Wikimedia can (i) terminate the contract, (ii) suspend single instances,
-            (iii) permanently delete single instances, and/ or (iv) transfer
-            ownership of single instances to another User at any time and without
-            cause, provided that two weeks’ notice is given.</p>
-          <p>8.4 The User can delete
-            their Wikibase Instance at any time through the settings. All data and
-            Content associated with this Wikibase Instance will be permanently
-            deleted after 30 days. The domain may not be available for reuse.</p>
-          <p>8.5 Wikimedia may terminate or suspend any use of the Platform and the
-            User’s Account immediately, without notice or liability, if the User
-            breaches any of the terms and conditions of the Terms of Use. Upon
-            termination of the User’s Account, the User’s right to use the Platform
-            will immediately cease.</p>
-
-          <h2 class="mb-2">9. Availability and Maintenance</h2>
-          <p>9.1 Wikimedia shall implement appropriate measures to ensure the availability and
-            error free functionality of the Platform. However, the User acknowledges
-            that for technical reasons and due to the dependence on external
-            influences, Wikimedia cannot guarantee the uninterrupted availability of
-            the Platform.</p>
-          <p>9.2 Wikimedia will occasionally carry out maintenance work
-            to ensure the functionality or expansion of the Platform. These tasks
-            may result in a temporary impairment of the usability of the Platform.
-            Insofar Wikimedia shall carry out the maintenance work during periods of
-            low use.</p>
-
-          <h2 class="mb-2">10. Liability</h2>
-          <p>10.1 Wikimedia provides a free service that allows
-            the User to create their own Wikibase Instance. Wikimedia assumes no
-            responsibility for any material posted by the User. However, in
-            accordance with Art. 16 DSA Wikimedia provides a mechanism for the User
-            and third parties to report illegal Content hosted on the Platform.</p>
-          <p>10.2 Users are solely responsible for their Content and must ensure
-            compliance with applicable German laws.</p>
-          <p>10.3 The User agrees to indemnify
-            and hold harmless Wikimedia from any claims by third parties arising
-            from Content they publish or actions they take while using our Platform.</p>
-
-          <h2 class="mb-2">11. Data Protection</h2>
-          <p>11.1 For comprehensive information on how Wikimedia
-            collects, processes or uses personal data of the User, please refer to
-            our <router-link to="/privacy-policy">Privacy
-              Policy</router-link>.</p>
-          <p>11.2 To the extent that the Content provided by the
-            User or by contributors and users of the User’s Wikimedia Instance
-            contains personal data of third parties, the User remains the controller
-            of such data and Wikimedia acts as the processor of the User’s personal
-            data under the GDPR. To this end, the Parties enter into the Standard
-            Contractual Clauses (Commission Implementing Decision (EU) 2021/915 of 4
-            June 2021) attached hereto in the Appendix 1.</p>
-          <p>11.3 If and to the extent that the User
-            resides and/or processes personal data in a state outside of the EU and
-            the data transfers between Wikimedia and the User constitute an
-            international data transfer according to Chapter 5 of the GDPR, the User
-            and Wikimedia enter into the Standard Contractual Clauses for transfers
-            of personal data to third countries as laid down in the Commission
-            Implementing Decision (EU) 2021/914 4 June 2021, attached hereto as
-            Appendix 2 (the “International Standard Contractual Clauses”) in form of
-            Module 4 (Processor to Controller). The Annexes I, II, III and IV of
-            Appendix 1 apply accordingly.</p>
-
-          <h2 class="mb-2"  >12. Miscellaneous</h2>
-          <p>12.1 This Agreement is
-            governed by, and shall be interpreted in accordance with, the laws of,
-            and directly applicable in, the Federal Republic of Germany, excluding,
-            however, the provisions of the United Nations Convention on Contracts
-            for the International Sale of Goods and any conflict of law provisions
-            that would require the application of the material law of another
-            country.</p>
-          <p>12.2 The Parties hereby irrevocably submit to the exclusive
-            jurisdiction of the courts of Berlin, Germany, for all disputes or
-            claims arising out of or in connection with this Agreement made
-            hereunder.</p>
-          <p>12.3. If any provision of this Agreement is invalid or
-            unenforceable in whole or in part, this shall not affect the validity
-            and enforceability of any other provision of this Agreement. The invalid
-            or unenforceable provision shall be deemed replaced by a valid and
-            enforceable provision that comes as close as possible to the economic
-            purpose that both parties had in mind with the invalid or unenforceable
-            provision.</p>
-
-          <v-divider class="my-8" />
-
-          <h2>Appendix 1: Standard contractual clauses (Commission Implementing
-            Decision (EU) 2021/915 of 4 June 2021)</h2>
-          <h3>SECTION I</h3>
-
-          <h4 class="mb-2">Clause 1 &mdash; Purpose and scope</h4>
-          <p>(a) The purpose of these Standard
-            Contractual Clauses (the Clauses) is to ensure compliance with Article
-            28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and
-            of the Council of 27 April 2016 on the protection of natural persons
-            with regard to the processing of personal data and on the free movement
-            of such data, and repealing Directive 95/46/EC (General Data Protection
-            Regulation).</p>
-          <p>(b) The controllers and processors listed in Annex I have
-            agreed to these Clauses in order to ensure compliance with Article 28(3)
-            and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of
-            Regulation (EU) 2018/1725.</p>
-          <p>(c) These Clauses apply to the processing of
-            personal data as specified in Annex II.</p>
-          <p>(d) Annexes I to IV are an
-            integral part of the Clauses.</p>
-          <p>(e) These Clauses are without prejudice to
-            obligations to which the controller is subject by virtue of Regulation
-            (EU) 2016/679 and/or Regulation (EU) 2018/1725.</p>
-          <p>(f) These Clauses do not
-            by themselves ensure compliance with obligations related to
-            international transfers in accordance with Chapter V of Regulation (EU)
-            2016/679 and/or Regulation (EU) 2018/1725.</p>
-
-          <h4 class="mb-2">Clause 2 &mdash; Invariability of the Clauses
-          </h4>
-          <p>(a) The Parties undertake not to modify the Clauses, except for
-            adding information to the Annexes or updating information in them.</p>
-          <p>(b) This does not prevent the Parties from including the standard
-            contractual clauses laid down in these Clauses in a broader contract, or
-            from adding other clauses or additional safeguards provided that they do
-            not directly or indirectly contradict the Clauses or detract from the
-            fundamental rights or freedoms of data subjects.</p>
-
-          <h4 class="mb-2">Clause 3 &mdash; Interpretation</h4>
-          <p>(a) Where these Clauses use the terms defined in Regulation (EU)
-            2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall
-            have the same meaning as in that Regulation.</p>
-          <p>(b) These Clauses shall be
-            read and interpreted in the light of the provisions of Regulation (EU)
-            2016/679 or Regulation (EU) 2018/1725 respectively.</p>
-          <p>(c) These Clauses
-            shall not be interpreted in a way that runs counter to the rights and
-            obligations provided for in Regulation (EU) 2016/679 / Regulation (EU)
-            2018/1725 or in a way that prejudices the fundamental rights or freedoms
-            of the data subjects.</p>
-
-          <h4 class="mb-2">Clause 4 &mdash; Hierarchy</h4>
-          <p>In the event of a contradiction
-            between these Clauses and the provisions of related agreements between
-            the Parties existing at the time when these Clauses are agreed or
-            entered into thereafter, these Clauses shall prevail.</p>
-
-          <h3>SECTION II &mdash; OBLIGATIONS OF THE PARTIES</h3>
-
-          <h4 class="mb-2">Clause 5 &mdash; Description of processing(s)</h4>
-          <p>The details of the processing operations, in particular the categories of
-            personal data and the purposes of processing for which the personal data
-            is processed on behalf of the controller, are specified in Annex II.</p>
-
-          <h4 class="mb-2">Clause 6 &mdash; Obligations of the Parties</h4>
-          <h5>6.1. Instructions</h5>
-          <p>(a) The processor
-            shall process personal data only on documented instructions from the
-            controller, unless required to do so by Union or Member State law to
-            which the processor is subject. In this case, the processor shall inform
-            the controller of that legal requirement before processing, unless the
-            law prohibits this on important grounds of public interest. Subsequent
-            instructions may also be given by the controller throughout the duration
-            of the processing of personal data. These instructions shall always be
-            documented.</p>
-          <p>(b) The processor shall immediately inform the controller
-            if, in the processor’s opinion, instructions given by the controller
-            infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the
-            applicable Union or Member State data protection provisions.</p>
-          <h5>6.2. Purpose limitation</h5>
-          <p>The processor shall process the personal data only
-            for the specific purpose(s) of the processing, as set out in Annex II,
-            unless it receives further instructions from the controller.</p>
-          <h5>6.3. Duration of the processing of personal data</h5>
-          <p>Processing by the processor
-            shall only take place for the duration specified in Annex II.</p>
-          <h5>6.4. Security of processing</h5>
-          <p>(a) The processor shall at least implement the
-            technical and organisational measures specified in Annex III to ensure
-            the security of the personal data. This includes protecting the data
-            against a breach of security leading to accidental or unlawful
-            destruction, loss, alteration, unauthorised disclosure or access to the
-            data (personal data breach). In assessing the appropriate level of
-            security, the Parties shall take due account of the state of the art,
-            the costs of implementation, the nature, scope, context and purposes of
-            processing and the risks involved for the data subjects.</p>
-          <p>(b) The
-            processor shall grant access to the personal data undergoing processing
-            to members of its personnel only to the extent strictly necessary for
-            implementing, managing and monitoring of the contract. The processor
-            shall ensure that persons authorised to process the personal data
-            received have committed themselves to confidentiality or are under an
-            appropriate statutory obligation of confidentiality.</p>
-          <h5>6.5. Sensitive data</h5>
-          <p>If the processing involves personal data revealing racial or ethnic
-            origin, political opinions, religious or philosophical beliefs, or trade
-            union membership, genetic data or biometric data for the purpose of
-            uniquely identifying a natural person, data concerning health or a
-            person’s sex life or sexual orientation, or data relating to criminal
-            convictions and offences (“sensitive data”), the processor shall apply
-            specific restrictions and/or additional safeguards.</p>
-          <h5>6.6. Documentation and compliance</h5>
-          <p>(a) The Parties shall be able to demonstrate compliance
-            with these Clauses.</p>
-          <p>(b) The processor shall deal promptly and adequately
-            with inquiries from the controller about the processing of data in
-            accordance with these Clauses.</p>
-          <p>(c) The processor shall make available to
-            the controller all information necessary to demonstrate compliance with
-            the obligations that are set out in these Clauses and stem directly from
-            Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the
-            controller’s request, the processor shall also permit and contribute to
-            audits of the processing activities covered by these Clauses, at
-            reasonable intervals or if there are indications of non-compliance. In
-            deciding on a review or an audit, the controller may take into account
-            relevant certifications held by the processor.</p>
-          <p>(d) The controller may
-            choose to conduct the audit by itself or mandate an independent auditor.
-            Audits may also include inspections at the premises or physical
-            facilities of the processor and shall, where appropriate, be carried out
-            with reasonable notice.</p>
-          <p>(e) The Parties shall make the information
-            referred to in this Clause, including the results of any audits,
-            available to the competent supervisory authority/ies on request.</p>
-          <h5>6.7. Use of sub-processors</h5>
-          <p>(a) GENERAL WRITTEN AUTHORISATION: The processor
-            has the controller’s general authorisation for the engagement of
-            sub-processors from an agreed list. The processor shall specifically
-            inform in writing the controller of any intended changes of that list
-            through the addition or replacement of sub-processors at least two
-            months in advance, thereby giving the controller sufficient time to be
-            able to object to such changes prior to the engagement of the concerned
-            sub-processor(s). The processor shall provide the controller with the
-            information necessary to enable the controller to exercise the right to
-            object.</p>
-          <p>(b) Where the processor engages a sub-processor for carrying out
-            specific processing activities (on behalf of the controller), it shall
-            do so by way of a contract which imposes on the sub-processor, in
-            substance, the same data protection obligations as the ones imposed on
-            the data processor in accordance with these Clauses. The processor shall
-            ensure that the sub-processor complies with the obligations to which the
-            processor is subject pursuant to these Clauses and to Regulation (EU)
-            2016/679 and/or Regulation (EU) 2018/1725.</p>
-          <p>(c) At the controller’s
-            request, the processor shall provide a copy of such a sub-processor
-            agreement and any subsequent amendments to the controller. To the extent
-            necessary to protect business secret or other confidential information,
-            including personal data, the processor may redact the text of the
-            agreement prior to sharing the copy.</p>
-          <p>(d) The processor shall remain
-            fully responsible to the controller for the performance of the
-            sub-processor’s obligations in accordance with its contract with the
-            processor. The processor shall notify the controller of any failure by
-            the sub-processor to fulfil its contractual obligations.</p>
-          <p>(e) The processor shall agree a third party beneficiary clause with the
-            sub-processor whereby - in the event the processor has factually
-            disappeared, ceased to exist in law or has become insolvent - the
-            controller shall have the right to terminate the sub-processor contract
-            and to instruct the sub-processor to erase or return the personal data.</p>
-          <h5>6.8. International transfers</h5>
-          <p>(a) Any transfer of data to a third country
-            or an international organisation by the processor shall be done only on
-            the basis of documented instructions from the controller or in order to
-            fulfil a specific requirement under Union or Member State law to which
-            the processor is subject and shall take place in compliance with Chapter
-            V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.</p>
-          <p>(b) The controller agrees that where the processor engages a sub-processor in
-            accordance with Clause 7.7. for carrying out specific processing
-            activities (on behalf of the controller) and those processing activities
-            involve a transfer of personal data within the meaning of Chapter V of
-            Regulation (EU) 2016/679, the processor and the sub-processor can ensure
-            compliance with Chapter V of Regulation (EU) 2016/679 by using standard
-            contractual clauses adopted by the Commission in accordance with of
-            Article 46(2) of Regulation (EU) 2016/679, provided the conditions for
-            the use of those standard contractual clauses are met.</p>
-
-          <h4 class="mb-2">Clause 7 &mdash; Assistance to the controller</h4>
-          <p>(a) The processor shall promptly notify the
-            controller of any request it has received from the data subject. It
-            shall not respond to the request itself, unless authorised to do so by
-            the controller.</p>
-          <p>(b) The processor shall assist the controller in
-            fulfilling its obligations to respond to data subjects’ requests to
-            exercise their rights, taking into account the nature of the processing.
-            In fulfilling its obligations in accordance with (a) and (b), the
-            processor shall comply with the controller’s instructions</p>
-          <p>(c) In addition to the processor’s obligation to assist the controller pursuant
-            to Clause 8(b), the processor shall furthermore assist the controller in
-            ensuring compliance with the following obligations, taking into account
-            the nature of the data processing and the information available to the
-            processor:</p>
-          <div class="pl-8">
-            <p>(1) the obligation to carry out an assessment of the impact
-              of the envisaged processing operations on the protection of personal
-              data (a ‘data protection impact assessment’) where a type of processing
-              is likely to result in a high risk to the rights and freedoms of natural
-              persons;</p>
-            <p>(2) the obligation to consult the competent supervisory
-              authority/ies prior to processing where a data protection impact
-              assessment indicates that the processing would result in a high risk in
-              the absence of measures taken by the controller to mitigate the risk;</p>
-            <p>(3) the obligation to ensure that personal data is accurate and up to
-              date, by informing the controller without delay if the processor becomes
-              aware that the personal data it is processing is inaccurate or has
-              become outdated;</p>
-            <p>(4) the obligations in Article 32 of Regulation (EU)
-              2016/679.</p>
-          </div>
-          <p>(d) The Parties shall set out in Annex III the appropriate technical and organisational measures by which
-            the processor is required to assist the controller in the application of this Clause as well as the scope
-            and the extent of the assistance required.</p>
-          <h4 class="mb-2">Clause 8 &mdash; Notification of personal data breach</h4>
-          <p>In the event of a personal data
-            breach, the processor shall cooperate with and assist the controller for
-            the controller to comply with its obligations under Articles 33 and 34
-            of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation
-            (EU) 2018/1725, where applicable, taking into account the nature of
-            processing and the information available to the processor.</p>
-          <h5>8.1 Data breach concerning data processed by the controller</h5>
-          <p>In the event of a
-            personal data breach concerning data processed by the controller, the
-            processor shall assist the controller:</p>
-          <p>(a) in notifying the personal
-            data breach to the competent supervisory authority/ies, without undue
-            delay after the controller has become aware of it, where
-            relevant/(unless the personal data breach is unlikely to result in a
-            risk to the rights and freedoms of natural persons);</p>
-          <p>(b) in obtaining
-            the following information which, pursuant to Article 33(3) of Regulation
-            (EU) 2016/679, shall be stated in the controller’s notification, and
-            must at least include:</p>
-          <div class="pl-8">
-            <p>(1) the nature of the personal data including
-              where possible, the categories and approximate number of data subjects
-              concerned and the categories and approximate number of personal data
-              records concerned;</p>
-            <p>(2) the likely consequences of the personal data
-              breach;</p>
-            <p>(3) the measures taken or proposed to be taken by the controller
-              to address the personal data breach, including, where appropriate,
-              measures to mitigate its possible adverse effects.</p>
-          </div>
-          <p>Where, and insofar as, it is not possible to provide all this information at the same time, the initial
-            notification shall contain the information then available and further information shall, as it becomes
-            available, subsequently be provided without undue delay.</p>
-          <p>(c) in complying, pursuant to Article 34 of Regulation (EU) 2016/679,
-            with the obligation to communicate without undue delay the personal data
-            breach to the data subject, when the personal data breach is likely to
-            result in a high risk to the rights and freedoms of natural persons.</p>
-
-          <h5>8.2 Data breach concerning data processed by the processor</h5>
-          <p>In the event of a
-            personal data breach concerning data processed by the processor, the
-            processor shall notify the controller without undue delay after the
-            processor having become aware of the breach. Such notification shall
-            contain, at least:</p>
-          <p>(a) a description of the nature of the breach (including, where
-            possible, the categories and approximate number of data subjects and
-            data records concerned);</p>
-          <p>(b)the details of a contact point where more information concerning the
-            personal data breach can be obtained;</p>
-          <p>(c) its likely consequences and the measures taken or proposed to be
-            taken to address the breach, including to mitigate its possible adverse
-            effects.</p>
-          <p>Where, and insofar as, it is not possible to provide all this
-            information at the same time, the initial notification shall contain the
-            information then available and further information shall, as it becomes
-            available, subsequently be provided without undue delay.</p>
-          <p>The Parties
-            shall set out in Annex III all other elements to be provided by the
-            processor when assisting the controller in the compliance with the
-            controller’s obligations under Articles 33 and 34 of Regulation (EU)
-            2016/679.</p>
-
-          <h3>
-            SECTION III &mdash; FINAL PROVISIONS
-          </h3>
-
-          <h4 class="mb-2">
-            Clause 9 &mdash; Non-compliance with the Clauses and termination
-          </h4>
-          <p>(a) Without prejudice to any provisions of Regulation
-            (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the
-            processor is in breach of its obligations under these Clauses, the
-            controller may instruct the processor to suspend the processing of
-            personal data until the latter complies with these Clauses or the
-            contract is terminated. The processor shall promptly inform the
-            controller in case it is unable to comply with these Clauses, for
-            whatever reason.</p>
-          <p>(b) The controller shall be entitled to terminate the
-            contract insofar as it concerns processing of personal data in
-            accordance with these Clauses if:</p>
-          <div class="pl-8">
-            <p>(1) the processing of personal data by
-              the processor has been suspended by the controller pursuant to point (a)
-              and if compliance with these Clauses is not restored within a reasonable
-              time and in any event within one month following suspension;</p>
-            <p>(2) the
-              processor is in substantial or persistent breach of these Clauses or its
-              obligations under Regulation (EU) 2016/679 and/or Regulation (EU)
-              2018/1725;</p>
-            <p>(3) the processor fails to comply with a binding decision of
-              a competent court or the competent supervisory authority/ies regarding
-              its obligations pursuant to these Clauses or to Regulation (EU) 2016/679
-              and/or Regulation (EU) 2018/1725.</p>
-          </div>
-          <p>(c) The processor shall be entitled to terminate the contract insofar as it concerns processing of personal
-            data under these Clauses where, after having informed the controller that its instructions infringe
-            applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with
-            the instructions.</p>
-          <p>(d) Following termination of the contract, the processor shall, at the choice of the controller, delete all
-            personal data processed on behalf of the controller and certify to the controller that it has done so, or,
-            return all the personal data to the controller and delete existing copies unless Union or Member State law
-            requires storage of the personal data. Until the data is deleted or returned, the processor shall continue
-            to ensure compliance with these Clauses.</p>
-
-          <h4 class="mb-2">ANNEX I</h4>
-          <h5>List of parties</h5>
-          <p>
-            <b>Controller(s):</b> [Identity and contact details
-            of the controller(s), and, where applicable, of the controller’s data
-            protection officer]
-          </p>
-          <p>The User as specified in the Terms of Use.</p>
-
-          <p><b>Processor(s):</b>
-            [Identity and contact details of the processor(s) and,
-            where applicable, of the processor’s data protection officer]</p>
-          <p>Wikimedia
-            Deutschland e. V., Tempelhofer Ufer 23-24, 10369 Berlin</p>
-
-          <h4 class="mb-2">ANNEX II</h4>
-          <h5>Description of the processing</h5>
-          <div>
-            <i>Categories of data subjects
-              whose personal data is processed</i>
-          <ul class="pl-8">
-            <li>Any categories of data subjects
-              contained in the data uploaded by the User.</li>
-          </ul>
-          </div>
-
-          <div>
-            <i>Categories of personal data
-              processed</i>
-          <ul class="pl-8">
-            <li>Any categories of personal data contained in the data
-              uploaded by the User.</li>
-          </ul>
-          </div>
-
-          <div>
-            <i>Sensitive data processed (if applicable) and
-              applied restrictions or safeguards that fully take into consideration
-              the nature of the data and the risks involved, such as for instance
-              strict purpose limitation, access restrictions (including access only
-              for staff having followed specialised training), keeping a record of
-              access to the data, restrictions for onward transfers or additional
-              security measures.</i>
-          <ul class="pl-8">
-            <li>The categories of personal data may include
-              sensitive data depending on the Content uploaded by the User. Since
-              Wikimedia has no knowledge of the specific categories processed it lies
-              in the User’s responsibility to ensure that the safeguards are
-              sufficient to process the specific categories of personal data.</li>
-          </ul>
-          </div>
-
-          <div>
-            <i>Nature of the processing</i>
-          <ul class="pl-8">
-            <li>Any processing necessary to fulfil the contractual
-              purposes. Especially collection, storage, disclosure and dissemination
-              and making publicly available as well as anonymization and/or deletion.</li>
-          </ul>
-          </div>
-
-          <div>
-            <i>Purpose(s) for which the personal data is processed on behalf of the
-              controller</i>
-          <ul class="pl-8">
-            <li>Publishing the Wikibase as well as the data uploaded to and
-              contained in it and making it available to the public. Wikimedia does
-              not act as a processor for the User with regard to the processing of
-              personal data of persons browsing the Wikibase and any personal data
-              that is processed to establish the connection.</li>
-          </ul>
-          </div>
-
-          <div>
-            <i>Duration of the processing</i>
-          <ul class="pl-8">
-            <li>The rules of the Agreement regarding the
-              Term and Termination apply.</li>
-          </ul>
-          </div>
-
-          <p>
-            <i>For processing by (sub-) processors, also specify subject matter, nature
-              and duration of the processing</i>
-          </p>
-
-          <h4 class="mb-2">ANNEX III</h4>
-          <p>Technical and organisational measures including technical
-            and organisational measures to ensure the security of the data</p>
-
-          <p>
-            <i>You may obtain a copy of our technical and organisational measures on request,
-              to do so please send an email to: datenschutz@wikimedia.de.</i>
-          </p>
-
-          <h4 class="mb-2">ANNEX IV</h4>
-          <p class="font-weight-bold">List of sub-processors</p>
-          <p class="font-weight-bold">EXPLANATORY NOTE:</p>
-
-          <p>This Annex needs to
-            be completed in case of specific authorisation of sub-processors (Clause
-            7.7(a), Option 1).</p>
-          <p>The controller has authorised the use of the
-            following sub-processors:</p>
-
-          <ul class="pl-8">
-            <li>
-              <p><b>1. Name: Google Ireland Ltd.</b></p>
-              <p>Address: Gordon House, Barrow Street, Dublin 4</p>
-
-              <p>Contact person’s name, position and contact details: Please contact Wikimedia for the contact
-                information</p>
-
-              <p>Description of the processing (including a clear delimitation of
-                responsibilities in case several sub-processors are authorised): Hosting
-                of the Wikibase.cloud service</p>
-            </li>
-
-            <li>
-              <p><b>2. Name: Mailgun Technologies, Inc</b></p>
-
-              <p>Address: 112 E Pecan St #1135, San Antonio, TX 78205</p>
-              <p>Contact person’s name, position and contact details: Please contact Wikimedia for the
-                contact information</p>
-
-              <p>Description of the processing: Email service
-                provisioning</p>
-            </li>
-          </ul>
-
-          <v-divider class="my-8" />
-
-          <h2>Appendix 2: International Standard Contractual Clauses : MODULE FOUR:
-            Transfer processor to controller</h2>
-          <h3>SECTION I</h3>
-          <h4 class="mb-2">Clause 1 &mdash; Purpose and scope</h4>
-          <p>(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of
-            Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of
-            natural persons with regard to the processing of personal data and on the free movement of such data
-            (General Data Protection Regulation)<router-link :to="{ hash: '#tou-footnote-1' }"
-              id="tou-footnote-link-1">[1]</router-link> for the
-            transfer of personal data to a third country.</p>
-          <p>(b) The Parties:</p>
-          <div class="pl-8">
-            <p>(i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter
-              “entity/ies”) transferring the personal data, as listed in Annex I.A. (hereinafter each “data exporter”),
-            </p>
-            <p>and</p>
-            <p>(ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or
-              indirectly via another entity also Party to these Clauses, as listed in Annex I.A. (hereinafter each “data
-              importer”)</p></div>
-          <p>have agreed to these standard contractual clauses (hereinafter: “Clauses”).</p>
-            <p>(c) These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.</p>
-            <p>(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of
-              these Clauses.</p>
-
-          <h4 class="mb-2">Clause 2 &mdash; Effect and invariability of the Clauses</h4>
-            <p>
-              (a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective
-              legal remedies, pursuant to Article 46(1) and Article 46 (2)(c) of Regulation (EU) 2016/679 and, with
-              respect to data transfers from controllers to processors and/or processors to processors, standard
-              contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified,
-              except to select the appropriate Module(s) or to add or update information in the Appendix. This does not
-              prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider
-              contract and/or to add other clauses or additional safeguards, provided that they do not contradict,
-              directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
-            </p>
-            <p>
-              (b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of
-              Regulation (EU) 2016/679.
-            </p>
-
-          <h4 class="mb-2">Clause 3 &mdash; Third-party beneficiaries</h4>
-            <p>
-              (a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data
-              exporter and/or data importer, with the following exceptions:
-            </p>
-            <div class="pl-8 mb-3">
-              <p>
-                (i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
-              </p>
-              <p>
-                (ii) Clause 8 - Module One: Clause 8.5 (e) and Clause 8.9(b); Module Two: Clause 8.1(b), 8.9(a), (c),
-                (d) and (e); Module Three: Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g);
-                Module Four: Clause 8.1 (b) and Clause 8.3(b);
-              </p>
-              <p>
-                (iii) Clause 9 - Module Two: Clause 9(a), (c), (d) and (e); Module Three: Clause 9(a), (c), (d) and (e);
-              </p>
-              <p>
-                (iv) Clause 12 - Module One: Clause 12(a) and (d); Modules Two and Three: Clause 12(a), (d) and (f);
-              </p>
-              <p>
-                (v) Clause 13;
-              </p>
-              <p>
-                (vi) Clause 15.1(c), (d) and (e);
-              </p>
-              <p>
-                (vii) Clause 16(e);
-              </p>
-              <p>
-                (viii) Clause 18 - Modules One, Two and Three: Clause 18(a) and (b); Module Four: Clause 18.
-              </p>
-            </div>
-            <p>
-              (b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
-            </p>
-
-          <h4 class="mb-2">Clause 4 &mdash; Interpretation</h4>
-          <div class="mb-3">
-            <p>
-              (a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the
-              same meaning as in that Regulation.
-            </p>
-            <p>
-              (b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU)
-              2016/679.
-            </p>
-            <p>
-              (c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided
-              for in Regulation (EU) 2016/679.
-            </p>
-          </div>
-
-          <h4 class="mb-2">Clause 5 &mdash; Hierarchy</h4>
-          <p>In the event of a contradiction between these Clauses and the
-            provisions of related agreements between the Parties, existing at the
-            time these Clauses are agreed or entered into thereafter, these Clauses
-            shall prevail.</p>
-
-          <h4 class="mb-2">Clause 6 &mdash; Description of the transfer(s)</h4>
-          <p>The details of the transfer(s), and in particular the categories of
-            personal data that are transferred and the purpose(s) for which they are
-            transferred, are specified in Annex I.B.</p>
-
-          <h4 class="mb-2">Clause 7 &mdash; Optional Docking clause</h4>
-          <div class="mb-3">
-            <p>
-              (a) An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these
-              Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and
-              signing Annex I.A.
-            </p>
-            <p>
-              (b) Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to
-              these Clauses and have the rights and obligations of a data exporter or data importer in accordance with
-              its designation in Annex I.A.
-            </p>
-            <p>
-              (c) The acceding entity shall have no rights or obligations arising under these Clauses from the period
-              prior to becoming a Party.
-            </p>
-          </div>
-
-          <h3>SECTION II &mdash; OBLIGATIONS OF THE PARTIES</h3>
-
-          <h4 class="mb-2">
-            Clause 8 &mdash; Data protection
-            safeguards
-          </h4>
-
-          <p>The data exporter warrants that it has used reasonable efforts to
-            determine that the data importer is able, through the implementation of
-            appropriate technical and organisational measures, to satisfy its
-            obligations under these Clauses.</p>
-
-          <h5>8.1 Instructions</h5>
-          <div class="mb-3 pl-8">
-            <p>
-              (a) The data exporter shall process the personal data only on documented instructions from the data
-              importer acting as its controller.
-            </p>
-            <p>
-              (b) The data exporter shall immediately inform the data importer if it is unable to follow those
-              instructions, including if such instructions infringe Regulation (EU) 2016/679 or other Union or Member
-              State data protection law.
-            </p>
-            <p>
-              (c) The data importer shall refrain from any action that would prevent the data exporter from fulfilling
-              its obligations under Regulation (EU) 2016/679, including in the context of sub-processing or as regards
-              cooperation with competent supervisory authorities.
-            </p>
-            <p>
-              (d) After the end of the provision of the processing services, the data exporter shall, at the choice of
-              the data importer, delete all personal data processed on behalf of the data importer and certify to the
-              data importer that it has done so, or return to the data importer all personal data processed on its
-              behalf and delete existing copies.
-            </p>
-          </div>
-
-          <h5>8.2 Security of processing</h5>
-          <div class="mb-3 pl-8">
-            <p>
-              (a) The Parties shall implement appropriate technical and organisational measures to ensure the security
-              of the data, including during transmission, and protection against a breach of security leading to
-              accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access (hereinafter
-              “personal data breach”). In assessing the appropriate level of security, they shall take due account of
-              the state of the art, the costs of implementation, the nature of the personal data<router-link
-                :to="{ hash: '#tou-footnote-2' }" id="tou-footnote-link-2">[2]</router-link>, the nature, scope, context
-              and purpose(s) of
-              processing and the risks involved in the processing for the data subjects, and in particular consider
-              having recourse to encryption or pseudonymisation, including during transmission, where the purpose of
-              processing can be fulfilled in that manner.
-            </p>
-            <p>
-              (b) The data exporter shall assist the data importer in ensuring appropriate security of the data in
-              accordance with paragraph (a). In case of a personal data breach concerning the personal data processed by
-              the data exporter under these Clauses, the data exporter shall notify the data importer without undue
-              delay after becoming aware of it and assist the data importer in addressing the breach.
-            </p>
-            <p>
-              (c) The data exporter shall ensure that persons authorised to process the personal data have committed
-              themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
-            </p>
-          </div>
-
-          <h5>8.3 Documentation and compliance</h5>
-          <div class="mb-3 pl-8">
-            <p>
-              (a) The Parties shall be able to demonstrate compliance with these Clauses.
-            </p>
-            <p>
-              (b) The data exporter shall make available to the data importer all information necessary to demonstrate
-              compliance with its obligations under these Clauses and allow for and contribute to audits.
-            </p>
-          </div>
-
-          <h4 class="mb-2">Clause 9 [not applicable] &mdash; Use of sub-processors</h4>
-
-          <h4 class="mb-2">Clause 10 &mdash; Data subject rights</h4>
-          <p>The Parties shall assist each other in responding to enquiries and
-            requests made by data subjects under the local law applicable to the
-            data importer or, for data processing by the data exporter in the EU,
-            under Regulation (EU) 2016/679.</p>
-
-          <h4 class="mb-2">Clause 11 &mdash; Redress</h4>
-          <div class="mb-3">
-              (a) The data importer shall inform data subjects in a transparent and easily accessible format, through
-              individual notice or on its website, of a contact point authorised to handle complaints. It shall deal
-              promptly with any complaints it receives from a data subject.
-          </div>
-
-          <h4 class="mb-2">Clause 12 &mdash; Liability</h4>
-          <div class="mb-3">
-            <p>
-              (a) Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any
-              breach of these Clauses.
-            </p>
-            <p>
-              (b) Each Party shall be liable to the data subject, and the data subject shall be entitled to receive
-              compensation, for any material or non-material damages that the Party causes the data subject by breaching
-              the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the
-              data exporter under Regulation (EU) 2016/679.
-            </p>
-            <p>
-              (c) Where more than one Party is responsible for any damage caused to the data subject as a result of a
-              breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data
-              subject is entitled to bring an action in court against any of these Parties.
-            </p>
-            <p>
-              (d) The Parties agree that if one Party is held liable under paragraph (c), it shall be entitled to claim
-              back from the other Party/ies that part of the compensation corresponding to its / their responsibility
-              for the damage.
-            </p>
-            <p>
-              (e) The data importer may not invoke the conduct of a processor or sub-processor to avoid its own
-              liability.
-            </p>
-          </div>
-
-          <h4 class="mb-2">Clause 13 [not applicable] &mdash; Supervision</h4>
-
-          <h3>SECTION III &mdash; LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC
-            AUTHORITIES</h3>
-          <h4 class="mb-2">Clause 14 [not applicable]</h4>
-          <h4 class="mb-2">Clause 15 [not applicable]</h4>
-
-          <h3>SECTION IV &mdash; FINAL PROVISIONS</h3>
-          <h4 class="mb-2">Clause 16 &mdash; Non-compliance with the Clauses and termination</h4>
-          <div class="mb-3">
-            <p>
-              (a) The data importer shall promptly inform the data exporter if it is unable to comply with these
-              Clauses, for whatever reason.
-            </p>
-            <p>
-              (b) In the event that the data importer is in breach of these Clauses or unable to comply with these
-              Clauses, the data exporter shall suspend the transfer of personal data to the data importer until
-              compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
-            </p>
-            <p>
-              (c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing
-              of personal data under these Clauses, where:
-            </p>
-
-            <div class="pl-8 mb-3">
-              <p>
-                (i) the data exporter has suspended the transfer of personal data to the data importer pursuant to
-                paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any
-                event within one month of suspension;
-              </p>
-              <p>
-                (ii) the data importer is in substantial or persistent breach of these Clauses; or
-              </p>
-              <p>
-                (iii) the data importer fails to comply with a binding decision of a competent court or supervisory
-                authority regarding its obligations under these Clauses.
-                In these cases, it shall inform the competent supervisory authority of
-                such non-compliance. Where the contract involves more than two Parties,
-                the data exporter may exercise this right to termination only with
-                respect to the relevant Party, unless the Parties have agreed
-                otherwise.
-              </p>
-            </div>
-            <p>
-              (d) Personal data collected by the data exporter in the EU that has been transferred prior to the
-              termination of the contract pursuant to paragraph (c) shall immediately be deleted in its entirety,
-              including any copy thereof. The data importer shall certify the deletion of the data to the data exporter.
-              Until the data is deleted or returned, the data importer shall continue to ensure compliance with these
-              Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the
-              transferred personal data, the data importer warrants that it will continue to ensure compliance with
-              these Clauses and will only process the data to the extent and for as long as required under that local
-              law.
-            </p>
-            <p>
-              (e) Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission
-              adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of
-              personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal
-              framework of the country to which the personal data is transferred. This is without prejudice to other
-              obligations applying to the processing in question under Regulation (EU) 2016/679.
-            </p>
-          </div>
-
-          <h4 class="mb-2">Clause 17 &mdash; Governing law</h4>
-          <p>These Clauses shall be governed by the law of a country allowing for
-            third-party beneficiary rights. The Parties agree that this shall be the
-            law of Germany (specify country).</p>
-
-          <h4 class="mb-2">Clause 18 &mdash; Choice of forum and jurisdiction</h4>
-          <p>Any dispute arising from these Clauses shall be resolved by the
-            courts of Germany (specify country).</p>
-
-          <v-divider class="my-4" />
-
-          <p id="tou-footnote-1">
-            <router-link :to="{ hash: '#tou-footnote-link-1' }">[1]</router-link> Where the data exporter is a processor
-            subject to Regulation (EU) 2016/679 acting on behalf of a Union
-            institution or body as controller, reliance on these Clauses when engaging another processor
-            (sub-processing) not subject to Regulation (EU) 2016/679 also ensures compliance with Article 29(4) of
-            Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection
-            of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices
-            and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No
-            1247/2002/EC (OJ L 295 of 21.11.2018, p. 39), to the extent these Clauses and the data protection
-            obligations as set out in the contract or other legal act between the controller and the processor pursuant
-            to Article 29(3) of Regulation (EU) 2018/1725 are aligned. This will in particular be the case where the
-            controller and processor rely on the standard contractual clauses included in Decision 2021/915.
-          </p>
-
-          <p id="tou-footnote-2">
-            <router-link :to="{ hash: '#tou-footnote-link-2' }">[2]</router-link> This includes whether the transfer and
-            further processing involves personal data revealing racial or
-            ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic
-            data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a
-            person’s sex life or sexual orientation, or data relating to criminal convictions or offences.
-          </p>
-        </v-col>
-      </v-row>
-    </v-container>
-  </v-main>
-</template>
-
-<script>
-import TermsOfUseNavigationPanel from './TermsOfUseNavigationPanel.vue'
-
-export default {
-  name: 'TermsOfUseUpcoming',
-  components: {
-    TermsOfUseNavigationPanel,
-  },
-  computed: {
-    isMobile () {
-      return this.$vuetify.breakpoint.xs
-    },
-  },
-  data: () => ({
-    show: false,
-  }),
-}
-</script>
-
-<style scoped>
-h3 {
-  margin-top: 8px;
-}
-
-h4,
-h5 {
-  margin-top: 4px;
-}
-</style>
diff --git a/src/components/Pages/TermsOfUse/terms-of-use/version-1.vue b/src/components/Pages/TermsOfUse/terms-of-use/version-1.vue
index aa61a3b9..9a230190 100644
--- a/src/components/Pages/TermsOfUse/terms-of-use/version-1.vue
+++ b/src/components/Pages/TermsOfUse/terms-of-use/version-1.vue
@@ -1282,7 +1282,6 @@
 
 <script>
 export default {
-  name: 'TermsOfUse',
   components: {},
   computed: {},
 }
diff --git a/src/components/Pages/TermsOfUse/terms-of-use/version-2.vue b/src/components/Pages/TermsOfUse/terms-of-use/version-2.vue
new file mode 100644
index 00000000..a1e5a54b
--- /dev/null
+++ b/src/components/Pages/TermsOfUse/terms-of-use/version-2.vue
@@ -0,0 +1,1144 @@
+<template>
+  <div>
+    <h1>Terms Of Use</h1>
+    <v-alert text color="info">
+      <div class="light-blue--text text--darken-4">
+        <div class="text-h6 mb-3">What changed from
+          <router-link class="text-decoration-none light-blue--text text--darken-4" to="/terms-of-use">
+            the previous version</router-link>
+        </div>
+        <p>The Terms of Use were revised to ensure compliance with the European Union’s
+          Digital Services Act (DSA) and to improve transparency about how Wikibase Cloud operates.</p>
+        <v-expand-transition>
+          <div v-if="show || !isMobile">
+            <div>
+              <div>Key updates:</div>
+              <ul class="mb-3">
+                <li>
+                  We have clarified when and how user accounts or individual instances may be suspended or terminated,
+                  including notice periods and proportionality principles.
+                </li>
+                <li>
+                  The new version explains more clearly how decisions are made, including how users can raise concerns
+                  or file complaints about moderation actions.
+                </li>
+                <li>
+                  The responsibilities of instance managers and contributors are described in more detail, especially
+                  regarding compliance with applicable laws and acceptable use of the platform.
+                </li>
+                <li>
+                  The Terms now explicitly reference applicable GDPR requirements and include updated wording to reflect
+                  international data transfer safeguards.
+                </li>
+                <li>
+                  The document has been reorganized and clarified to make rights, obligations, and processes easier to
+                  understand.
+                </li>
+                <li>
+                  We have introduced a separate Hosting Policy that defines additional rules for using the platform.
+                  This policy is now explicitly incorporated into the Terms of Use and forms part of the agreement users
+                  must accept.
+                </li>
+              </ul>
+            </div>
+            <div>
+              These changes do not alter the core purpose of Wikibase Cloud as a free hosting platform for open
+              knowledge projects, but they introduce clearer rules, including a separate Hosting Policy, and provide
+              stronger legal transparency in line with EU regulatory requirements.
+            </div>
+          </div>
+        </v-expand-transition>
+      </div>
+
+      <div v-if="isMobile" class="mt-2 d-flex justify-space-between">
+        <v-btn text class="light-blue--text text--darken-2" size="small" @click="show = !show">
+          {{ show ? 'See less' : 'See more' }}
+        </v-btn>
+        <v-btn class="pa-2 mt-auto d-flex justify-end" icon @click="show = !show">
+          <v-icon>{{ show ? 'mdi-chevron-up' : 'mdi-chevron-down' }}</v-icon>
+        </v-btn>
+      </div>
+    </v-alert>
+    <h2 class="mb-2">1. Definitions</h2>
+    <p>In addition to terms defined elsewhere in this
+      Agreement, the following terms have the following meanings:</p>
+    <p>1.1 “Manager Account” or “Account”: The personal Account provided by Wikibase.cloud
+      to the User on the Platform after the User’s registration.</p>
+    <p>1.2 “Content”: Any type of media (for example text, video files) uploaded to the
+      Platform by a User.</p>
+    <p>1.3 “User”: A natural person that registers for and
+      uses the Platform.</p>
+    <p>1.4 “Wikimedia”: Wikimedia Deutschland – Gesellschaft
+      zur Förderung Freien Wissens e. V.</p>
+    <p>1.5 “Wikibase Instance” or “Site”: an open knowledge base that can be
+      created and run by anyone on Wikibase.cloud.
+    </p>
+    <h2 class="mb-2">2. Scope and Applicability</h2>
+    <p>2.1 Wikimedia, Tempelhofer Ufer 23/24, 10963 Berlin, provides
+      Wikibase.cloud (the „Platform“), a free cloud-based Platform that hosts
+      instances of Wikibase. It offers collaborative space to pool, edit and
+      curate information and is accessible under <router-link to="/">https://www.wikibase.cloud/</router-link>.</p>
+    <p>2.2 These Terms of Use govern the legal relationship between Wikimedia
+      and the User and apply to all actions of the User and Wikimedia on or in
+      connection with the Platform (the „Agreement“).</p>
+    <h2 class="mb-2">3. Conclusion of the Contract and Registration for an Account</h2>
+    <p>3.1 To use the Platform, the
+      User must open a Manager Account. Opening a Manager Account is free of
+      charge for the User. The User can sign up directly by visiting the
+      website <router-link to="/">https://www.wikibase.cloud/</router-link> and clicking “Sign Up”.</p>
+    <p>3.2 When registering, the User is required to provide certain basic
+      information, including an email address and a password.</p>
+    <p>3.3 By clicking
+      on “Create Account”, the User requests Wikimedia to create an Account on
+      the Platform. Wikimedia will send an email with a legally binding offer
+      to open the Account and to confirm the user’s email address. By clicking
+      on “verify email”, the User accepts the offer, concludes the Agreement
+      with Wikimedia and opens the Account.</p>
+    <p>3.4 The User shall keep the Account
+      information, in particular the chosen password, confidential and shall
+      not disclose it to third parties. Any misuse or suspected misuse must be
+      reported to Wikimedia Deutschland immediately.</p>
+    <p> 3.5 The User can access
+      the latest version of these Terms at any time on the Platform. The
+      Agreement is concluded in English and the Terms are only available in
+      English.</p>
+    <h2 class="mb-2">4. Creating a Wikibase Instance and its basic functions</h2>
+    <p>4.1 After creating a Manager Account and logging into it, the User can
+      create a Wikibase Instance on their dashboard page.</p>
+    <p>4.2 To create a
+      Wikibase Instance, the User is required to provide certain basic
+      information, including Site Name, Site Domain and Username.</p>
+    <p>4.3 By
+      clicking on “Create Wiki”, the User submits the form. Once the form has
+      been successfully submitted, the Wikibase Instance will be created and
+      become available on the dashboard.</p>
+    <p>4.4 Wikimedia will send the User an
+      email with Account details, including the username and a temporary
+      password. After logging in with the provided password, the User is
+      prompted to create a new password.</p>
+    <p>4.5 The User shall keep the Account
+      information, in particular the chosen password, confidential and shall
+      not disclose it to third parties. Any misuse or suspected misuse must be
+      reported to Wikimedia immediately.</p>
+    <p>4.6 Once the Wikibase Instance has
+      been created, the basic functions are available to the User, which may
+      change from time to time. For example, the User can create a main page,
+      add a logo and create their own legal terms for their Wiki. The User can
+      also manually enter, import or delete data or any other information or
+      media (the “Content”) using the tools provided. Wikibase is a
+      collaborative Platform. The User can enable other persons to register
+      for an Account on their Wikibase Instance or upload Content.</p>
+    <h2 class="mb-2">5. Rules of the Platform</h2>
+    <p>5.1 The User may only use the Platform in accordance with
+      the Terms of Use and the additional rules laid down in the Hosting
+      Policy, which is hereby explicitly incorporated into the Agreement. In
+      particular, the User may not create, post, share, link to or otherwise
+      interact with Content that violates our rules or any laws.</p>
+    <p>5.2 The User
+      is responsible for any Content that they or other persons publish on
+      their registered Wikibase Instance. The User shall take all reasonable
+      steps to inform other persons using their Wikibase Instance of all
+      restrictions laid down in these Terms of Use and to ensure that these
+      restrictions are obeyed. The User must have all the necessary rights to
+      create, publish or share Content. The User agrees not to upload or share
+      any Content on their Wikibase Instance that infringes the intellectual
+      property rights of third persons or that is otherwise unlawful.</p>
+    <div class="mb-3">5.3 It is specifically prohibited to:
+      <ul>
+        <li>Upload or distribute Content that is
+          insulting, abusive, offensive, racist, threatening, harmful to minors,
+          pornographic, violates personal rights, promotes violence or sedition,
+          incites criminal acts, provides instructions on how to commit criminal
+          acts, or provides services that involve pornographic and/or erotic
+          Content or any other illegal Content</li>
+
+        <li>Upload or distribute Content
+          that is copied as a whole or in part from another protected work or
+          material without the permission of the respective copyright owner;</li>
+
+        <li>Upload or distribute Content that violates or infringes the rights of
+          third parties, in particular personal rights, copyrights or other
+          intellectual property rights or any other rights of third parties</li>
+
+        <li>Upload or distribute Content that contains personal, confidential or
+          non-public information</li>
+        <li>Contact other users of the Platform in a
+          disrespectful and rude manner, as well as to buy or sell products or
+          services;</li>
+        <li>Provide false data or information, as well as false data or
+          information of third parties; or</li>
+        <li>Sell or otherwise transfer the User Account to another person.</li>
+      </ul>
+    </div>
+
+    <p>5.4 The User should be aware that the sites
+      may be edited by the public and, as such, may contain inappropriate
+      Content at any time.</p>
+
+    <h2 class="mb-2">6. Moderation of Content</h2>
+    <p>6.1 Wikimedia does not
+      monitor Content on the Platform, but reserves the right to conduct
+      random checks, particularly if there are indications of violations.
+      Wikimedia does not use any automatic moderation technology or similar
+      tools that automatically scan, edit, block or remove Content.</p>
+    <p>6.2 Wikimedia may remove or restrict access to Content and/or delete or
+      restrict access to the User’s Account and/or delete or restrict access
+      to the Wikibase Instance if Wikimedia has reasonable grounds to believe
+      that Content violates the Agreement or applicable law.</p>
+    <p>6.3 If Wikimedia
+      removes or restricts access to Content, Wikimedia will notify the User
+      immediately and explain the reasons for the decision, unless to do so
+      would harm Wikimedia, or other third parties, or Wikimedia is legally
+      prevented from notifying the User.</p>
+    <p>6.4 Wikimedia will always proceed
+      carefully, objectively and proportionately when examining Content and
+      implementing measures, and will take into account the rights and
+      legitimate interests of all parties involved.</p>
+    <div class="mb-3">6.5 If the User believes
+      that Wikimedia has erred in one of the measures mentioned above in this
+      section 6, the User may request a review using the complaint functions
+      and Wikimedia will review and reconsider the decision. The following
+      rules apply to complaints:
+      <ul>
+        <li>The User may file a complaint against the
+          removal of the Content, the suspension or termination of the Account, or
+          the rejection of a report submitted by the User regarding Content that
+          the User considers to be illegal.</li>
+        <li>The User is not entitled to file a
+          complaint if the User has already been warned for improper use of
+          Wikimedia’s complaint system. This is the case, for example, if the User
+          repeatedly submits identical complaints without justification.</li>
+        <li>A
+          complaint must be made within six months of the date on which the User
+          was notified of our decision.</li>
+        <li>Wikimedia deals with complaints
+          promptly, carefully and without discrimination or arbitrariness. In
+          order to do this, Wikimedia needs all relevant information from the User
+          to understand the complaint. Complaints with offensive or inappropriate
+          language may result in the suspension of complaints after a warning.</li>
+        <li>Wikimedia shall promptly decide whether to reverse or uphold the
+          original action. The User will receive the reasoned decision promptly.</li>
+        <li>In considering the complaint, Wikimedia will take into account the
+          seriousness of the breach, the reason for the complaint, the frequency
+          and impact of the breaches and the intention behind the breach.</li>
+        <li>This section is without prejudice to the rights of EU users to take their
+          case to certified out-of-court complaint bodies. For more information,
+          <router-link to="/dsa-info">please click here</router-link>.
+        </li>
+      </ul>
+    </div>
+    <h2 class="mb-2">7. Grant of rights of use</h2>
+    <p>7.1 The User grants
+      Wikimedia the rights of use to the uploaded Content for the purpose of
+      Wikimedia’s provision of the Platform.</p>
+    <p>7.2 Wikimedia reserves the right to close, move, merge, or rename a site
+      for any reason. Wikimedia shall not be held liable for any modification,
+      suspension or discontinuance of any site, or of the Platform as a whole.</p>
+
+    <h2 class="mb-2">8. Term and Termination</h2>
+    <p>8.1 The terms of this Agreement commence upon the
+      User’s registration.</p>
+    <p>8.2 The User can delete their Account by contacting
+      Wikimedia, for example, via <router-link to="/contact">https://www.wikibase.cloud/contact.</router-link></p>
+    <p>8.3 Wikimedia can (i) terminate the contract, (ii) suspend single instances,
+      (iii) permanently delete single instances, and/ or (iv) transfer
+      ownership of single instances to another User at any time and without
+      cause, provided that two weeks’ notice is given.</p>
+    <p>8.4 The User can delete
+      their Wikibase Instance at any time through the settings. All data and
+      Content associated with this Wikibase Instance will be permanently
+      deleted after 30 days. The domain may not be available for reuse.</p>
+    <p>8.5 Wikimedia may terminate or suspend any use of the Platform and the
+      User’s Account immediately, without notice or liability, if the User
+      breaches any of the terms and conditions of the Terms of Use. Upon
+      termination of the User’s Account, the User’s right to use the Platform
+      will immediately cease.</p>
+
+    <h2 class="mb-2">9. Availability and Maintenance</h2>
+    <p>9.1 Wikimedia shall implement appropriate measures to ensure the availability and
+      error free functionality of the Platform. However, the User acknowledges
+      that for technical reasons and due to the dependence on external
+      influences, Wikimedia cannot guarantee the uninterrupted availability of
+      the Platform.</p>
+    <p>9.2 Wikimedia will occasionally carry out maintenance work
+      to ensure the functionality or expansion of the Platform. These tasks
+      may result in a temporary impairment of the usability of the Platform.
+      Insofar Wikimedia shall carry out the maintenance work during periods of
+      low use.</p>
+
+    <h2 class="mb-2">10. Liability</h2>
+    <p>10.1 Wikimedia provides a free service that allows
+      the User to create their own Wikibase Instance. Wikimedia assumes no
+      responsibility for any material posted by the User. However, in
+      accordance with Art. 16 DSA Wikimedia provides a mechanism for the User
+      and third parties to report illegal Content hosted on the Platform.</p>
+    <p>10.2 Users are solely responsible for their Content and must ensure
+      compliance with applicable German laws.</p>
+    <p>10.3 The User agrees to indemnify
+      and hold harmless Wikimedia from any claims by third parties arising
+      from Content they publish or actions they take while using our Platform.</p>
+
+    <h2 class="mb-2">11. Data Protection</h2>
+    <p>11.1 For comprehensive information on how Wikimedia
+      collects, processes or uses personal data of the User, please refer to
+      our <router-link to="/privacy-policy">Privacy
+        Policy</router-link>.</p>
+    <p>11.2 To the extent that the Content provided by the
+      User or by contributors and users of the User’s Wikimedia Instance
+      contains personal data of third parties, the User remains the controller
+      of such data and Wikimedia acts as the processor of the User’s personal
+      data under the GDPR. To this end, the Parties enter into the Standard
+      Contractual Clauses (Commission Implementing Decision (EU) 2021/915 of 4
+      June 2021) attached hereto in the Appendix 1.</p>
+    <p>11.3 If and to the extent that the User
+      resides and/or processes personal data in a state outside of the EU and
+      the data transfers between Wikimedia and the User constitute an
+      international data transfer according to Chapter 5 of the GDPR, the User
+      and Wikimedia enter into the Standard Contractual Clauses for transfers
+      of personal data to third countries as laid down in the Commission
+      Implementing Decision (EU) 2021/914 4 June 2021, attached hereto as
+      Appendix 2 (the “International Standard Contractual Clauses”) in form of
+      Module 4 (Processor to Controller). The Annexes I, II, III and IV of
+      Appendix 1 apply accordingly.</p>
+
+    <h2 class="mb-2">12. Miscellaneous</h2>
+    <p>12.1 This Agreement is
+      governed by, and shall be interpreted in accordance with, the laws of,
+      and directly applicable in, the Federal Republic of Germany, excluding,
+      however, the provisions of the United Nations Convention on Contracts
+      for the International Sale of Goods and any conflict of law provisions
+      that would require the application of the material law of another
+      country.</p>
+    <p>12.2 The Parties hereby irrevocably submit to the exclusive
+      jurisdiction of the courts of Berlin, Germany, for all disputes or
+      claims arising out of or in connection with this Agreement made
+      hereunder.</p>
+    <p>12.3. If any provision of this Agreement is invalid or
+      unenforceable in whole or in part, this shall not affect the validity
+      and enforceability of any other provision of this Agreement. The invalid
+      or unenforceable provision shall be deemed replaced by a valid and
+      enforceable provision that comes as close as possible to the economic
+      purpose that both parties had in mind with the invalid or unenforceable
+      provision.</p>
+
+    <v-divider class="my-8" />
+
+    <h2>Appendix 1: Standard contractual clauses (Commission Implementing
+      Decision (EU) 2021/915 of 4 June 2021)</h2>
+    <h3>SECTION I</h3>
+
+    <h4 class="mb-2">Clause 1 &mdash; Purpose and scope</h4>
+    <p>(a) The purpose of these Standard
+      Contractual Clauses (the Clauses) is to ensure compliance with Article
+      28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and
+      of the Council of 27 April 2016 on the protection of natural persons
+      with regard to the processing of personal data and on the free movement
+      of such data, and repealing Directive 95/46/EC (General Data Protection
+      Regulation).</p>
+    <p>(b) The controllers and processors listed in Annex I have
+      agreed to these Clauses in order to ensure compliance with Article 28(3)
+      and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of
+      Regulation (EU) 2018/1725.</p>
+    <p>(c) These Clauses apply to the processing of
+      personal data as specified in Annex II.</p>
+    <p>(d) Annexes I to IV are an
+      integral part of the Clauses.</p>
+    <p>(e) These Clauses are without prejudice to
+      obligations to which the controller is subject by virtue of Regulation
+      (EU) 2016/679 and/or Regulation (EU) 2018/1725.</p>
+    <p>(f) These Clauses do not
+      by themselves ensure compliance with obligations related to
+      international transfers in accordance with Chapter V of Regulation (EU)
+      2016/679 and/or Regulation (EU) 2018/1725.</p>
+
+    <h4 class="mb-2">Clause 2 &mdash; Invariability of the Clauses
+    </h4>
+    <p>(a) The Parties undertake not to modify the Clauses, except for
+      adding information to the Annexes or updating information in them.</p>
+    <p>(b) This does not prevent the Parties from including the standard
+      contractual clauses laid down in these Clauses in a broader contract, or
+      from adding other clauses or additional safeguards provided that they do
+      not directly or indirectly contradict the Clauses or detract from the
+      fundamental rights or freedoms of data subjects.</p>
+
+    <h4 class="mb-2">Clause 3 &mdash; Interpretation</h4>
+    <p>(a) Where these Clauses use the terms defined in Regulation (EU)
+      2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall
+      have the same meaning as in that Regulation.</p>
+    <p>(b) These Clauses shall be
+      read and interpreted in the light of the provisions of Regulation (EU)
+      2016/679 or Regulation (EU) 2018/1725 respectively.</p>
+    <p>(c) These Clauses
+      shall not be interpreted in a way that runs counter to the rights and
+      obligations provided for in Regulation (EU) 2016/679 / Regulation (EU)
+      2018/1725 or in a way that prejudices the fundamental rights or freedoms
+      of the data subjects.</p>
+
+    <h4 class="mb-2">Clause 4 &mdash; Hierarchy</h4>
+    <p>In the event of a contradiction
+      between these Clauses and the provisions of related agreements between
+      the Parties existing at the time when these Clauses are agreed or
+      entered into thereafter, these Clauses shall prevail.</p>
+
+    <h3>SECTION II &mdash; OBLIGATIONS OF THE PARTIES</h3>
+
+    <h4 class="mb-2">Clause 5 &mdash; Description of processing(s)</h4>
+    <p>The details of the processing operations, in particular the categories of
+      personal data and the purposes of processing for which the personal data
+      is processed on behalf of the controller, are specified in Annex II.</p>
+
+    <h4 class="mb-2">Clause 6 &mdash; Obligations of the Parties</h4>
+    <h5>6.1. Instructions</h5>
+    <p>(a) The processor
+      shall process personal data only on documented instructions from the
+      controller, unless required to do so by Union or Member State law to
+      which the processor is subject. In this case, the processor shall inform
+      the controller of that legal requirement before processing, unless the
+      law prohibits this on important grounds of public interest. Subsequent
+      instructions may also be given by the controller throughout the duration
+      of the processing of personal data. These instructions shall always be
+      documented.</p>
+    <p>(b) The processor shall immediately inform the controller
+      if, in the processor’s opinion, instructions given by the controller
+      infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the
+      applicable Union or Member State data protection provisions.</p>
+    <h5>6.2. Purpose limitation</h5>
+    <p>The processor shall process the personal data only
+      for the specific purpose(s) of the processing, as set out in Annex II,
+      unless it receives further instructions from the controller.</p>
+    <h5>6.3. Duration of the processing of personal data</h5>
+    <p>Processing by the processor
+      shall only take place for the duration specified in Annex II.</p>
+    <h5>6.4. Security of processing</h5>
+    <p>(a) The processor shall at least implement the
+      technical and organisational measures specified in Annex III to ensure
+      the security of the personal data. This includes protecting the data
+      against a breach of security leading to accidental or unlawful
+      destruction, loss, alteration, unauthorised disclosure or access to the
+      data (personal data breach). In assessing the appropriate level of
+      security, the Parties shall take due account of the state of the art,
+      the costs of implementation, the nature, scope, context and purposes of
+      processing and the risks involved for the data subjects.</p>
+    <p>(b) The
+      processor shall grant access to the personal data undergoing processing
+      to members of its personnel only to the extent strictly necessary for
+      implementing, managing and monitoring of the contract. The processor
+      shall ensure that persons authorised to process the personal data
+      received have committed themselves to confidentiality or are under an
+      appropriate statutory obligation of confidentiality.</p>
+    <h5>6.5. Sensitive data</h5>
+    <p>If the processing involves personal data revealing racial or ethnic
+      origin, political opinions, religious or philosophical beliefs, or trade
+      union membership, genetic data or biometric data for the purpose of
+      uniquely identifying a natural person, data concerning health or a
+      person’s sex life or sexual orientation, or data relating to criminal
+      convictions and offences (“sensitive data”), the processor shall apply
+      specific restrictions and/or additional safeguards.</p>
+    <h5>6.6. Documentation and compliance</h5>
+    <p>(a) The Parties shall be able to demonstrate compliance
+      with these Clauses.</p>
+    <p>(b) The processor shall deal promptly and adequately
+      with inquiries from the controller about the processing of data in
+      accordance with these Clauses.</p>
+    <p>(c) The processor shall make available to
+      the controller all information necessary to demonstrate compliance with
+      the obligations that are set out in these Clauses and stem directly from
+      Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the
+      controller’s request, the processor shall also permit and contribute to
+      audits of the processing activities covered by these Clauses, at
+      reasonable intervals or if there are indications of non-compliance. In
+      deciding on a review or an audit, the controller may take into account
+      relevant certifications held by the processor.</p>
+    <p>(d) The controller may
+      choose to conduct the audit by itself or mandate an independent auditor.
+      Audits may also include inspections at the premises or physical
+      facilities of the processor and shall, where appropriate, be carried out
+      with reasonable notice.</p>
+    <p>(e) The Parties shall make the information
+      referred to in this Clause, including the results of any audits,
+      available to the competent supervisory authority/ies on request.</p>
+    <h5>6.7. Use of sub-processors</h5>
+    <p>(a) GENERAL WRITTEN AUTHORISATION: The processor
+      has the controller’s general authorisation for the engagement of
+      sub-processors from an agreed list. The processor shall specifically
+      inform in writing the controller of any intended changes of that list
+      through the addition or replacement of sub-processors at least two
+      months in advance, thereby giving the controller sufficient time to be
+      able to object to such changes prior to the engagement of the concerned
+      sub-processor(s). The processor shall provide the controller with the
+      information necessary to enable the controller to exercise the right to
+      object.</p>
+    <p>(b) Where the processor engages a sub-processor for carrying out
+      specific processing activities (on behalf of the controller), it shall
+      do so by way of a contract which imposes on the sub-processor, in
+      substance, the same data protection obligations as the ones imposed on
+      the data processor in accordance with these Clauses. The processor shall
+      ensure that the sub-processor complies with the obligations to which the
+      processor is subject pursuant to these Clauses and to Regulation (EU)
+      2016/679 and/or Regulation (EU) 2018/1725.</p>
+    <p>(c) At the controller’s
+      request, the processor shall provide a copy of such a sub-processor
+      agreement and any subsequent amendments to the controller. To the extent
+      necessary to protect business secret or other confidential information,
+      including personal data, the processor may redact the text of the
+      agreement prior to sharing the copy.</p>
+    <p>(d) The processor shall remain
+      fully responsible to the controller for the performance of the
+      sub-processor’s obligations in accordance with its contract with the
+      processor. The processor shall notify the controller of any failure by
+      the sub-processor to fulfil its contractual obligations.</p>
+    <p>(e) The processor shall agree a third party beneficiary clause with the
+      sub-processor whereby - in the event the processor has factually
+      disappeared, ceased to exist in law or has become insolvent - the
+      controller shall have the right to terminate the sub-processor contract
+      and to instruct the sub-processor to erase or return the personal data.</p>
+    <h5>6.8. International transfers</h5>
+    <p>(a) Any transfer of data to a third country
+      or an international organisation by the processor shall be done only on
+      the basis of documented instructions from the controller or in order to
+      fulfil a specific requirement under Union or Member State law to which
+      the processor is subject and shall take place in compliance with Chapter
+      V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.</p>
+    <p>(b) The controller agrees that where the processor engages a sub-processor in
+      accordance with Clause 7.7. for carrying out specific processing
+      activities (on behalf of the controller) and those processing activities
+      involve a transfer of personal data within the meaning of Chapter V of
+      Regulation (EU) 2016/679, the processor and the sub-processor can ensure
+      compliance with Chapter V of Regulation (EU) 2016/679 by using standard
+      contractual clauses adopted by the Commission in accordance with of
+      Article 46(2) of Regulation (EU) 2016/679, provided the conditions for
+      the use of those standard contractual clauses are met.</p>
+
+    <h4 class="mb-2">Clause 7 &mdash; Assistance to the controller</h4>
+    <p>(a) The processor shall promptly notify the
+      controller of any request it has received from the data subject. It
+      shall not respond to the request itself, unless authorised to do so by
+      the controller.</p>
+    <p>(b) The processor shall assist the controller in
+      fulfilling its obligations to respond to data subjects’ requests to
+      exercise their rights, taking into account the nature of the processing.
+      In fulfilling its obligations in accordance with (a) and (b), the
+      processor shall comply with the controller’s instructions</p>
+    <p>(c) In addition to the processor’s obligation to assist the controller pursuant
+      to Clause 8(b), the processor shall furthermore assist the controller in
+      ensuring compliance with the following obligations, taking into account
+      the nature of the data processing and the information available to the
+      processor:</p>
+    <div class="pl-8">
+      <p>(1) the obligation to carry out an assessment of the impact
+        of the envisaged processing operations on the protection of personal
+        data (a ‘data protection impact assessment’) where a type of processing
+        is likely to result in a high risk to the rights and freedoms of natural
+        persons;</p>
+      <p>(2) the obligation to consult the competent supervisory
+        authority/ies prior to processing where a data protection impact
+        assessment indicates that the processing would result in a high risk in
+        the absence of measures taken by the controller to mitigate the risk;</p>
+      <p>(3) the obligation to ensure that personal data is accurate and up to
+        date, by informing the controller without delay if the processor becomes
+        aware that the personal data it is processing is inaccurate or has
+        become outdated;</p>
+      <p>(4) the obligations in Article 32 of Regulation (EU)
+        2016/679.</p>
+    </div>
+    <p>(d) The Parties shall set out in Annex III the appropriate technical and organisational measures by which
+      the processor is required to assist the controller in the application of this Clause as well as the scope
+      and the extent of the assistance required.</p>
+    <h4 class="mb-2">Clause 8 &mdash; Notification of personal data breach</h4>
+    <p>In the event of a personal data
+      breach, the processor shall cooperate with and assist the controller for
+      the controller to comply with its obligations under Articles 33 and 34
+      of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation
+      (EU) 2018/1725, where applicable, taking into account the nature of
+      processing and the information available to the processor.</p>
+    <h5>8.1 Data breach concerning data processed by the controller</h5>
+    <p>In the event of a
+      personal data breach concerning data processed by the controller, the
+      processor shall assist the controller:</p>
+    <p>(a) in notifying the personal
+      data breach to the competent supervisory authority/ies, without undue
+      delay after the controller has become aware of it, where
+      relevant/(unless the personal data breach is unlikely to result in a
+      risk to the rights and freedoms of natural persons);</p>
+    <p>(b) in obtaining
+      the following information which, pursuant to Article 33(3) of Regulation
+      (EU) 2016/679, shall be stated in the controller’s notification, and
+      must at least include:</p>
+    <div class="pl-8">
+      <p>(1) the nature of the personal data including
+        where possible, the categories and approximate number of data subjects
+        concerned and the categories and approximate number of personal data
+        records concerned;</p>
+      <p>(2) the likely consequences of the personal data
+        breach;</p>
+      <p>(3) the measures taken or proposed to be taken by the controller
+        to address the personal data breach, including, where appropriate,
+        measures to mitigate its possible adverse effects.</p>
+    </div>
+    <p>Where, and insofar as, it is not possible to provide all this information at the same time, the initial
+      notification shall contain the information then available and further information shall, as it becomes
+      available, subsequently be provided without undue delay.</p>
+    <p>(c) in complying, pursuant to Article 34 of Regulation (EU) 2016/679,
+      with the obligation to communicate without undue delay the personal data
+      breach to the data subject, when the personal data breach is likely to
+      result in a high risk to the rights and freedoms of natural persons.</p>
+
+    <h5>8.2 Data breach concerning data processed by the processor</h5>
+    <p>In the event of a
+      personal data breach concerning data processed by the processor, the
+      processor shall notify the controller without undue delay after the
+      processor having become aware of the breach. Such notification shall
+      contain, at least:</p>
+    <p>(a) a description of the nature of the breach (including, where
+      possible, the categories and approximate number of data subjects and
+      data records concerned);</p>
+    <p>(b)the details of a contact point where more information concerning the
+      personal data breach can be obtained;</p>
+    <p>(c) its likely consequences and the measures taken or proposed to be
+      taken to address the breach, including to mitigate its possible adverse
+      effects.</p>
+    <p>Where, and insofar as, it is not possible to provide all this
+      information at the same time, the initial notification shall contain the
+      information then available and further information shall, as it becomes
+      available, subsequently be provided without undue delay.</p>
+    <p>The Parties
+      shall set out in Annex III all other elements to be provided by the
+      processor when assisting the controller in the compliance with the
+      controller’s obligations under Articles 33 and 34 of Regulation (EU)
+      2016/679.</p>
+
+    <h3>
+      SECTION III &mdash; FINAL PROVISIONS
+    </h3>
+
+    <h4 class="mb-2">
+      Clause 9 &mdash; Non-compliance with the Clauses and termination
+    </h4>
+    <p>(a) Without prejudice to any provisions of Regulation
+      (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the
+      processor is in breach of its obligations under these Clauses, the
+      controller may instruct the processor to suspend the processing of
+      personal data until the latter complies with these Clauses or the
+      contract is terminated. The processor shall promptly inform the
+      controller in case it is unable to comply with these Clauses, for
+      whatever reason.</p>
+    <p>(b) The controller shall be entitled to terminate the
+      contract insofar as it concerns processing of personal data in
+      accordance with these Clauses if:</p>
+    <div class="pl-8">
+      <p>(1) the processing of personal data by
+        the processor has been suspended by the controller pursuant to point (a)
+        and if compliance with these Clauses is not restored within a reasonable
+        time and in any event within one month following suspension;</p>
+      <p>(2) the
+        processor is in substantial or persistent breach of these Clauses or its
+        obligations under Regulation (EU) 2016/679 and/or Regulation (EU)
+        2018/1725;</p>
+      <p>(3) the processor fails to comply with a binding decision of
+        a competent court or the competent supervisory authority/ies regarding
+        its obligations pursuant to these Clauses or to Regulation (EU) 2016/679
+        and/or Regulation (EU) 2018/1725.</p>
+    </div>
+    <p>(c) The processor shall be entitled to terminate the contract insofar as it concerns processing of personal
+      data under these Clauses where, after having informed the controller that its instructions infringe
+      applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with
+      the instructions.</p>
+    <p>(d) Following termination of the contract, the processor shall, at the choice of the controller, delete all
+      personal data processed on behalf of the controller and certify to the controller that it has done so, or,
+      return all the personal data to the controller and delete existing copies unless Union or Member State law
+      requires storage of the personal data. Until the data is deleted or returned, the processor shall continue
+      to ensure compliance with these Clauses.</p>
+
+    <h4 class="mb-2">ANNEX I</h4>
+    <h5>List of parties</h5>
+    <p>
+      <b>Controller(s):</b> [Identity and contact details
+      of the controller(s), and, where applicable, of the controller’s data
+      protection officer]
+    </p>
+    <p>The User as specified in the Terms of Use.</p>
+
+    <p><b>Processor(s):</b>
+      [Identity and contact details of the processor(s) and,
+      where applicable, of the processor’s data protection officer]</p>
+    <p>Wikimedia
+      Deutschland e. V., Tempelhofer Ufer 23-24, 10369 Berlin</p>
+
+    <h4 class="mb-2">ANNEX II</h4>
+    <h5>Description of the processing</h5>
+    <div>
+      <i>Categories of data subjects
+        whose personal data is processed</i>
+      <ul class="pl-8">
+        <li>Any categories of data subjects
+          contained in the data uploaded by the User.</li>
+      </ul>
+    </div>
+
+    <div>
+      <i>Categories of personal data
+        processed</i>
+      <ul class="pl-8">
+        <li>Any categories of personal data contained in the data
+          uploaded by the User.</li>
+      </ul>
+    </div>
+
+    <div>
+      <i>Sensitive data processed (if applicable) and
+        applied restrictions or safeguards that fully take into consideration
+        the nature of the data and the risks involved, such as for instance
+        strict purpose limitation, access restrictions (including access only
+        for staff having followed specialised training), keeping a record of
+        access to the data, restrictions for onward transfers or additional
+        security measures.</i>
+      <ul class="pl-8">
+        <li>The categories of personal data may include
+          sensitive data depending on the Content uploaded by the User. Since
+          Wikimedia has no knowledge of the specific categories processed it lies
+          in the User’s responsibility to ensure that the safeguards are
+          sufficient to process the specific categories of personal data.</li>
+      </ul>
+    </div>
+
+    <div>
+      <i>Nature of the processing</i>
+      <ul class="pl-8">
+        <li>Any processing necessary to fulfil the contractual
+          purposes. Especially collection, storage, disclosure and dissemination
+          and making publicly available as well as anonymization and/or deletion.</li>
+      </ul>
+    </div>
+
+    <div>
+      <i>Purpose(s) for which the personal data is processed on behalf of the
+        controller</i>
+      <ul class="pl-8">
+        <li>Publishing the Wikibase as well as the data uploaded to and
+          contained in it and making it available to the public. Wikimedia does
+          not act as a processor for the User with regard to the processing of
+          personal data of persons browsing the Wikibase and any personal data
+          that is processed to establish the connection.</li>
+      </ul>
+    </div>
+
+    <div>
+      <i>Duration of the processing</i>
+      <ul class="pl-8">
+        <li>The rules of the Agreement regarding the
+          Term and Termination apply.</li>
+      </ul>
+    </div>
+
+    <p>
+      <i>For processing by (sub-) processors, also specify subject matter, nature
+        and duration of the processing</i>
+    </p>
+
+    <h4 class="mb-2">ANNEX III</h4>
+    <p>Technical and organisational measures including technical
+      and organisational measures to ensure the security of the data</p>
+
+    <p>
+      <i>You may obtain a copy of our technical and organisational measures on request,
+        to do so please send an email to: datenschutz@wikimedia.de.</i>
+    </p>
+
+    <h4 class="mb-2">ANNEX IV</h4>
+    <p class="font-weight-bold">List of sub-processors</p>
+    <p class="font-weight-bold">EXPLANATORY NOTE:</p>
+
+    <p>This Annex needs to
+      be completed in case of specific authorisation of sub-processors (Clause
+      7.7(a), Option 1).</p>
+    <p>The controller has authorised the use of the
+      following sub-processors:</p>
+
+    <ul class="pl-8">
+      <li>
+        <p><b>1. Name: Google Ireland Ltd.</b></p>
+        <p>Address: Gordon House, Barrow Street, Dublin 4</p>
+
+        <p>Contact person’s name, position and contact details: Please contact Wikimedia for the contact
+          information</p>
+
+        <p>Description of the processing (including a clear delimitation of
+          responsibilities in case several sub-processors are authorised): Hosting
+          of the Wikibase.cloud service</p>
+      </li>
+
+      <li>
+        <p><b>2. Name: Mailgun Technologies, Inc</b></p>
+
+        <p>Address: 112 E Pecan St #1135, San Antonio, TX 78205</p>
+        <p>Contact person’s name, position and contact details: Please contact Wikimedia for the
+          contact information</p>
+
+        <p>Description of the processing: Email service
+          provisioning</p>
+      </li>
+    </ul>
+
+    <v-divider class="my-8" />
+
+    <h2>Appendix 2: International Standard Contractual Clauses : MODULE FOUR:
+      Transfer processor to controller</h2>
+    <h3>SECTION I</h3>
+    <h4 class="mb-2">Clause 1 &mdash; Purpose and scope</h4>
+    <p>(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of
+      Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of
+      natural persons with regard to the processing of personal data and on the free movement of such data
+      (General Data Protection Regulation)<router-link :to="{ hash: '#tou-footnote-1' }"
+        id="tou-footnote-link-1">[1]</router-link> for the
+      transfer of personal data to a third country.</p>
+    <p>(b) The Parties:</p>
+    <div class="pl-8">
+      <p>(i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter
+        “entity/ies”) transferring the personal data, as listed in Annex I.A. (hereinafter each “data exporter”),
+      </p>
+      <p>and</p>
+      <p>(ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or
+        indirectly via another entity also Party to these Clauses, as listed in Annex I.A. (hereinafter each “data
+        importer”)</p>
+    </div>
+    <p>have agreed to these standard contractual clauses (hereinafter: “Clauses”).</p>
+    <p>(c) These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.</p>
+    <p>(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of
+      these Clauses.</p>
+
+    <h4 class="mb-2">Clause 2 &mdash; Effect and invariability of the Clauses</h4>
+    <p>
+      (a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective
+      legal remedies, pursuant to Article 46(1) and Article 46 (2)(c) of Regulation (EU) 2016/679 and, with
+      respect to data transfers from controllers to processors and/or processors to processors, standard
+      contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified,
+      except to select the appropriate Module(s) or to add or update information in the Appendix. This does not
+      prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider
+      contract and/or to add other clauses or additional safeguards, provided that they do not contradict,
+      directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
+    </p>
+    <p>
+      (b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of
+      Regulation (EU) 2016/679.
+    </p>
+
+    <h4 class="mb-2">Clause 3 &mdash; Third-party beneficiaries</h4>
+    <p>
+      (a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data
+      exporter and/or data importer, with the following exceptions:
+    </p>
+    <div class="pl-8 mb-3">
+      <p>
+        (i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
+      </p>
+      <p>
+        (ii) Clause 8 - Module One: Clause 8.5 (e) and Clause 8.9(b); Module Two: Clause 8.1(b), 8.9(a), (c),
+        (d) and (e); Module Three: Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g);
+        Module Four: Clause 8.1 (b) and Clause 8.3(b);
+      </p>
+      <p>
+        (iii) Clause 9 - Module Two: Clause 9(a), (c), (d) and (e); Module Three: Clause 9(a), (c), (d) and (e);
+      </p>
+      <p>
+        (iv) Clause 12 - Module One: Clause 12(a) and (d); Modules Two and Three: Clause 12(a), (d) and (f);
+      </p>
+      <p>
+        (v) Clause 13;
+      </p>
+      <p>
+        (vi) Clause 15.1(c), (d) and (e);
+      </p>
+      <p>
+        (vii) Clause 16(e);
+      </p>
+      <p>
+        (viii) Clause 18 - Modules One, Two and Three: Clause 18(a) and (b); Module Four: Clause 18.
+      </p>
+    </div>
+    <p>
+      (b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
+    </p>
+
+    <h4 class="mb-2">Clause 4 &mdash; Interpretation</h4>
+    <div class="mb-3">
+      <p>
+        (a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the
+        same meaning as in that Regulation.
+      </p>
+      <p>
+        (b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU)
+        2016/679.
+      </p>
+      <p>
+        (c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided
+        for in Regulation (EU) 2016/679.
+      </p>
+    </div>
+
+    <h4 class="mb-2">Clause 5 &mdash; Hierarchy</h4>
+    <p>In the event of a contradiction between these Clauses and the
+      provisions of related agreements between the Parties, existing at the
+      time these Clauses are agreed or entered into thereafter, these Clauses
+      shall prevail.</p>
+
+    <h4 class="mb-2">Clause 6 &mdash; Description of the transfer(s)</h4>
+    <p>The details of the transfer(s), and in particular the categories of
+      personal data that are transferred and the purpose(s) for which they are
+      transferred, are specified in Annex I.B.</p>
+
+    <h4 class="mb-2">Clause 7 &mdash; Optional Docking clause</h4>
+    <div class="mb-3">
+      <p>
+        (a) An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these
+        Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and
+        signing Annex I.A.
+      </p>
+      <p>
+        (b) Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to
+        these Clauses and have the rights and obligations of a data exporter or data importer in accordance with
+        its designation in Annex I.A.
+      </p>
+      <p>
+        (c) The acceding entity shall have no rights or obligations arising under these Clauses from the period
+        prior to becoming a Party.
+      </p>
+    </div>
+
+    <h3>SECTION II &mdash; OBLIGATIONS OF THE PARTIES</h3>
+
+    <h4 class="mb-2">
+      Clause 8 &mdash; Data protection
+      safeguards
+    </h4>
+
+    <p>The data exporter warrants that it has used reasonable efforts to
+      determine that the data importer is able, through the implementation of
+      appropriate technical and organisational measures, to satisfy its
+      obligations under these Clauses.</p>
+
+    <h5>8.1 Instructions</h5>
+    <div class="mb-3 pl-8">
+      <p>
+        (a) The data exporter shall process the personal data only on documented instructions from the data
+        importer acting as its controller.
+      </p>
+      <p>
+        (b) The data exporter shall immediately inform the data importer if it is unable to follow those
+        instructions, including if such instructions infringe Regulation (EU) 2016/679 or other Union or Member
+        State data protection law.
+      </p>
+      <p>
+        (c) The data importer shall refrain from any action that would prevent the data exporter from fulfilling
+        its obligations under Regulation (EU) 2016/679, including in the context of sub-processing or as regards
+        cooperation with competent supervisory authorities.
+      </p>
+      <p>
+        (d) After the end of the provision of the processing services, the data exporter shall, at the choice of
+        the data importer, delete all personal data processed on behalf of the data importer and certify to the
+        data importer that it has done so, or return to the data importer all personal data processed on its
+        behalf and delete existing copies.
+      </p>
+    </div>
+
+    <h5>8.2 Security of processing</h5>
+    <div class="mb-3 pl-8">
+      <p>
+        (a) The Parties shall implement appropriate technical and organisational measures to ensure the security
+        of the data, including during transmission, and protection against a breach of security leading to
+        accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access (hereinafter
+        “personal data breach”). In assessing the appropriate level of security, they shall take due account of
+        the state of the art, the costs of implementation, the nature of the personal data<router-link
+          :to="{ hash: '#tou-footnote-2' }" id="tou-footnote-link-2">[2]</router-link>, the nature, scope, context
+        and purpose(s) of
+        processing and the risks involved in the processing for the data subjects, and in particular consider
+        having recourse to encryption or pseudonymisation, including during transmission, where the purpose of
+        processing can be fulfilled in that manner.
+      </p>
+      <p>
+        (b) The data exporter shall assist the data importer in ensuring appropriate security of the data in
+        accordance with paragraph (a). In case of a personal data breach concerning the personal data processed by
+        the data exporter under these Clauses, the data exporter shall notify the data importer without undue
+        delay after becoming aware of it and assist the data importer in addressing the breach.
+      </p>
+      <p>
+        (c) The data exporter shall ensure that persons authorised to process the personal data have committed
+        themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
+      </p>
+    </div>
+
+    <h5>8.3 Documentation and compliance</h5>
+    <div class="mb-3 pl-8">
+      <p>
+        (a) The Parties shall be able to demonstrate compliance with these Clauses.
+      </p>
+      <p>
+        (b) The data exporter shall make available to the data importer all information necessary to demonstrate
+        compliance with its obligations under these Clauses and allow for and contribute to audits.
+      </p>
+    </div>
+
+    <h4 class="mb-2">Clause 9 [not applicable] &mdash; Use of sub-processors</h4>
+
+    <h4 class="mb-2">Clause 10 &mdash; Data subject rights</h4>
+    <p>The Parties shall assist each other in responding to enquiries and
+      requests made by data subjects under the local law applicable to the
+      data importer or, for data processing by the data exporter in the EU,
+      under Regulation (EU) 2016/679.</p>
+
+    <h4 class="mb-2">Clause 11 &mdash; Redress</h4>
+    <div class="mb-3">
+      (a) The data importer shall inform data subjects in a transparent and easily accessible format, through
+      individual notice or on its website, of a contact point authorised to handle complaints. It shall deal
+      promptly with any complaints it receives from a data subject.
+    </div>
+
+    <h4 class="mb-2">Clause 12 &mdash; Liability</h4>
+    <div class="mb-3">
+      <p>
+        (a) Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any
+        breach of these Clauses.
+      </p>
+      <p>
+        (b) Each Party shall be liable to the data subject, and the data subject shall be entitled to receive
+        compensation, for any material or non-material damages that the Party causes the data subject by breaching
+        the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the
+        data exporter under Regulation (EU) 2016/679.
+      </p>
+      <p>
+        (c) Where more than one Party is responsible for any damage caused to the data subject as a result of a
+        breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data
+        subject is entitled to bring an action in court against any of these Parties.
+      </p>
+      <p>
+        (d) The Parties agree that if one Party is held liable under paragraph (c), it shall be entitled to claim
+        back from the other Party/ies that part of the compensation corresponding to its / their responsibility
+        for the damage.
+      </p>
+      <p>
+        (e) The data importer may not invoke the conduct of a processor or sub-processor to avoid its own
+        liability.
+      </p>
+    </div>
+
+    <h4 class="mb-2">Clause 13 [not applicable] &mdash; Supervision</h4>
+
+    <h3>SECTION III &mdash; LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC
+      AUTHORITIES</h3>
+    <h4 class="mb-2">Clause 14 [not applicable]</h4>
+    <h4 class="mb-2">Clause 15 [not applicable]</h4>
+
+    <h3>SECTION IV &mdash; FINAL PROVISIONS</h3>
+    <h4 class="mb-2">Clause 16 &mdash; Non-compliance with the Clauses and termination</h4>
+    <div class="mb-3">
+      <p>
+        (a) The data importer shall promptly inform the data exporter if it is unable to comply with these
+        Clauses, for whatever reason.
+      </p>
+      <p>
+        (b) In the event that the data importer is in breach of these Clauses or unable to comply with these
+        Clauses, the data exporter shall suspend the transfer of personal data to the data importer until
+        compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
+      </p>
+      <p>
+        (c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing
+        of personal data under these Clauses, where:
+      </p>
+
+      <div class="pl-8 mb-3">
+        <p>
+          (i) the data exporter has suspended the transfer of personal data to the data importer pursuant to
+          paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any
+          event within one month of suspension;
+        </p>
+        <p>
+          (ii) the data importer is in substantial or persistent breach of these Clauses; or
+        </p>
+        <p>
+          (iii) the data importer fails to comply with a binding decision of a competent court or supervisory
+          authority regarding its obligations under these Clauses.
+          In these cases, it shall inform the competent supervisory authority of
+          such non-compliance. Where the contract involves more than two Parties,
+          the data exporter may exercise this right to termination only with
+          respect to the relevant Party, unless the Parties have agreed
+          otherwise.
+        </p>
+      </div>
+      <p>
+        (d) Personal data collected by the data exporter in the EU that has been transferred prior to the
+        termination of the contract pursuant to paragraph (c) shall immediately be deleted in its entirety,
+        including any copy thereof. The data importer shall certify the deletion of the data to the data exporter.
+        Until the data is deleted or returned, the data importer shall continue to ensure compliance with these
+        Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the
+        transferred personal data, the data importer warrants that it will continue to ensure compliance with
+        these Clauses and will only process the data to the extent and for as long as required under that local
+        law.
+      </p>
+      <p>
+        (e) Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission
+        adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of
+        personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal
+        framework of the country to which the personal data is transferred. This is without prejudice to other
+        obligations applying to the processing in question under Regulation (EU) 2016/679.
+      </p>
+    </div>
+
+    <h4 class="mb-2">Clause 17 &mdash; Governing law</h4>
+    <p>These Clauses shall be governed by the law of a country allowing for
+      third-party beneficiary rights. The Parties agree that this shall be the
+      law of Germany (specify country).</p>
+
+    <h4 class="mb-2">Clause 18 &mdash; Choice of forum and jurisdiction</h4>
+    <p>Any dispute arising from these Clauses shall be resolved by the
+      courts of Germany (specify country).</p>
+
+    <v-divider class="my-4" />
+
+    <p id="tou-footnote-1">
+      <router-link :to="{ hash: '#tou-footnote-link-1' }">[1]</router-link> Where the data exporter is a processor
+      subject to Regulation (EU) 2016/679 acting on behalf of a Union
+      institution or body as controller, reliance on these Clauses when engaging another processor
+      (sub-processing) not subject to Regulation (EU) 2016/679 also ensures compliance with Article 29(4) of
+      Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection
+      of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices
+      and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No
+      1247/2002/EC (OJ L 295 of 21.11.2018, p. 39), to the extent these Clauses and the data protection
+      obligations as set out in the contract or other legal act between the controller and the processor pursuant
+      to Article 29(3) of Regulation (EU) 2018/1725 are aligned. This will in particular be the case where the
+      controller and processor rely on the standard contractual clauses included in Decision 2021/915.
+    </p>
+
+    <p id="tou-footnote-2">
+      <router-link :to="{ hash: '#tou-footnote-link-2' }">[2]</router-link> This includes whether the transfer and
+      further processing involves personal data revealing racial or
+      ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic
+      data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a
+      person’s sex life or sexual orientation, or data relating to criminal convictions or offences.
+    </p>
+  </div>
+</template>
+
+<script>
+export default {
+  components: {
+  },
+  computed: {
+    isMobile() {
+      return this.$vuetify.breakpoint.xs
+    },
+  },
+  data: () => ({
+    show: false,
+  }),
+}
+</script>
+
+<style scoped>
+h3 {
+  margin-top: 8px;
+}
+
+h4,
+h5 {
+  margin-top: 4px;
+}
+</style>

From 942de570a5b4fa273353ab0171cf85e421384a8b Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 12:31:42 +0200
Subject: [PATCH 06/16] fix routing for upcoming policies without a date

---
 .../TermsOfUse/TermsOfUseNavigationPanel.vue    |  2 ++
 .../Pages/TermsOfUse/TermsOfUseRenderer.vue     | 17 +++++------------
 2 files changed, 7 insertions(+), 12 deletions(-)

diff --git a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
index a46f5b83..5ffd8584 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
@@ -1,3 +1,5 @@
+<!-- TODO do we wanna move this into TermsOfUseRenderer.vue ? -->
+<!-- TODO make sure any upcoming policy links always go to /upcoming and not /activeFrom -->
 <template>
   <PolicyNavigationPanel :title="title" :links="links" :currentLink="currentLink" />
 </template>
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index cae1f91c..8e5b085e 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -4,21 +4,17 @@
       An error occurred while trying to load the requested policy. Please try again later.
     </v-alert>
     <v-container class="fill-height" fluid v-if="!error">
-      <v-row v-if="isUpcomingPolicy" justify="center">
-        <v-col cols="11">
-          <v-alert type="info">
-            This is an upcoming version. You can find the
-            <router-link class="white--text" to="/terms-of-use">current version here</router-link>.
-          </v-alert>
-        </v-col>
-      </v-row>
-
       <v-row justify="center">
         <v-col cols="11" md="4" order-md="last">
           <TermsOfUseNavigationPanel />
         </v-col>
 
         <v-col cols="11" md="8">
+          <v-alert type="info" v-if="isUpcomingRoute">
+            This is an upcoming version. You can find the
+            <router-link class="white--text" to="/terms-of-use">current version here</router-link>.
+          </v-alert>
+
           <component :is="policy" v-if="policy" />
         </v-col>
       </v-row>
@@ -58,9 +54,6 @@ export default {
     isUpcomingRoute: function () {
       return this.$route.path === '/terms-of-use/upcoming'
     },
-    isUpcomingPolicy: function () {
-      return isFutureDate(this.policyMetadata && this.policyMetadata.active_from)
-    },
   },
   data () {
     return {

From 0a31f74204f7cfbd91ae4b28e548d01f77ec5678 Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 12:33:16 +0200
Subject: [PATCH 07/16] cleanup

---
 .../Pages/TermsOfUse/TermsOfUseRenderer.vue          | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index 8e5b085e..f986b114 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -30,18 +30,6 @@ export const versions = {
   'terms-of-use/version-2.vue': () => ({ component: import('./terms-of-use/version-2.vue') }),
 }
 
-const isFutureDate = (activeFrom) => {
-  if (activeFrom === null || activeFrom === undefined) {
-    return false
-  }
-
-  const date = new Date(`${activeFrom}T00:00:00Z`)
-  const today = new Date()
-  today.setHours(0, 0, 0, 0)
-
-  return date > today
-}
-
 export default {
   name: 'TermsOfUseRenderer',
   components: {

From 875addccfa734f56f5f1e5baf2fd358ac7c05fd0 Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 12:43:48 +0200
Subject: [PATCH 08/16] fix policy route handling

---
 src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index f986b114..f0272926 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -42,6 +42,9 @@ export default {
     isUpcomingRoute: function () {
       return this.$route.path === '/terms-of-use/upcoming'
     },
+    isCurrentRoute: function() {
+      return this.policyActiveFrom === undefined
+    }
   },
   data () {
     return {
@@ -59,12 +62,12 @@ export default {
 
       try {
         const policyType = this.policyType // TODO for a generalized component, read this from component property
-        const activeFrom = this.activeFrom
+        const activeFrom = this.policyActiveFrom
         let response
 
         if (this.isUpcomingRoute) {
           response = await this.$api.getUpcomingPolicyByType({ policyType })
-        } else if (activeFrom === undefined) {
+        } else if (this.isCurrentRoute) {
           response = await this.$api.getCurrentPolicyByType({ policyType })
         } else {
           response = await this.$api.getPolicyByDate({ policyType, activeFrom })

From 86c9384b421100490c50735c8c9cb0706809b616 Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 13:06:57 +0200
Subject: [PATCH 09/16] fix terms of use policy panel

---
 .../Pages/TermsOfUse/TermsOfUseNavigationPanel.vue       | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
index 5ffd8584..8e562a4d 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
@@ -65,12 +65,12 @@ export default {
 
       const currentPolicy = sortedPolicies.find(policy => {
         const activeFrom = parseActiveFrom(policy.metadata.active_from)
-        return activeFrom === null || activeFrom <= today
+        return activeFrom <= today
       })
 
       const upcomingPolicy = sortedPolicies.find(policy => {
         const activeFrom = parseActiveFrom(policy.metadata.active_from)
-        return activeFrom !== null && activeFrom > today
+        return activeFrom > today || activeFrom === null
       })
 
       const otherPolicies = sortedPolicies.filter(policy => {
@@ -145,11 +145,6 @@ export default {
   mounted () {
     this.loadPolicies()
   },
-  watch: {
-    policyType () {
-      this.loadPolicies()
-    },
-  },
 }
 
 </script>

From b7f6fb8ea60e573f9d7ad6c7b352231d31509671 Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 13:13:43 +0200
Subject: [PATCH 10/16] cleanup

---
 src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
index 8e562a4d..1b2b3e78 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
@@ -1,5 +1,3 @@
-<!-- TODO do we wanna move this into TermsOfUseRenderer.vue ? -->
-<!-- TODO make sure any upcoming policy links always go to /upcoming and not /activeFrom -->
 <template>
   <PolicyNavigationPanel :title="title" :links="links" :currentLink="currentLink" />
 </template>

From 16dcf3d61c642cbb53b565f61600b9704242ddbe Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 13:15:00 +0200
Subject: [PATCH 11/16] change footer link to hosting policy pilot

---
 src/components/Layout/Foot.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/components/Layout/Foot.vue b/src/components/Layout/Foot.vue
index 1070f3a2..d3518768 100644
--- a/src/components/Layout/Foot.vue
+++ b/src/components/Layout/Foot.vue
@@ -21,7 +21,7 @@
           <ul class="footer-list">
             <li><router-link to="/privacy-policy">Privacy Policy</router-link></li>
             <li><router-link to="/terms-of-use">Terms of Use</router-link></li>
-            <li><router-link to="/hosting-policy">Hosting Policy</router-link></li>
+            <li><router-link to="/hosting-policy/pilot">Hosting Policy</router-link></li>
             <li><router-link to="/dsa-info">Digital Services Act Information</router-link></li>
             <li><a target="_blank" rel="noopener noreferrer" href="https://www.wikimedia.de/impressum/">Imprint</a></li>
             <li><router-link to="/complaint">Report illegal content</router-link></li>

From e8c32e1851a2b1c45ee1032252641632a044aa66 Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 14:32:42 +0200
Subject: [PATCH 12/16] generalize TermsOfUseNavigationPanel

---
 .../Components/PolicyNavigationPanel.vue      | 139 +++++++++++++++-
 .../HostingPolicy/HostingPolicyRenderer.vue   |   6 +-
 .../TermsOfUse/TermsOfUseNavigationPanel.vue  | 150 ------------------
 .../Pages/TermsOfUse/TermsOfUseRenderer.vue   |   6 +-
 4 files changed, 141 insertions(+), 160 deletions(-)
 delete mode 100644 src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue

diff --git a/src/components/Pages/Components/PolicyNavigationPanel.vue b/src/components/Pages/Components/PolicyNavigationPanel.vue
index 180969ee..1c74d72b 100644
--- a/src/components/Pages/Components/PolicyNavigationPanel.vue
+++ b/src/components/Pages/Components/PolicyNavigationPanel.vue
@@ -25,12 +25,143 @@
 </template>
 
 <script>
+const parseActiveFrom = (activeFrom) => {
+  if (activeFrom === null || activeFrom === undefined) {
+    return null
+  }
+
+  return new Date(`${activeFrom}T00:00:00Z`)
+}
+
+const comparePolicies = (left, right) => {
+  const leftActiveFrom = parseActiveFrom(left.metadata.active_from)
+  const rightActiveFrom = parseActiveFrom(right.metadata.active_from)
+
+  if (leftActiveFrom === null && rightActiveFrom === null) {
+    return 0
+  }
+
+  if (leftActiveFrom === null) {
+    return 1
+  }
+
+  if (rightActiveFrom === null) {
+    return -1
+  }
+
+  return rightActiveFrom - leftActiveFrom || right.metadata.policy_id - left.metadata.policy_id
+}
+
 export default {
-  name: 'NavigationPanel',
+  name: 'PolicyNavigationPanel',
+  components: {
+  },
   props: {
-    title: String,
-    currentLink: Number,
-    links: Array,
+    basePath: {
+      type: String,
+    },
+    policyType: {
+      type: String,
+    },
+    title: {
+      type: String,
+      default: 'All Versions',
+    },
+  },
+  data: () => ({
+    policies: [],
+    error: undefined,
+  }),
+  computed: {
+    links: function () {
+      const sortedPolicies = [...this.policies].sort(comparePolicies)
+      const today = new Date()
+      today.setHours(0, 0, 0, 0)
+
+      const currentPolicy = sortedPolicies.find(policy => {
+        const activeFrom = parseActiveFrom(policy.metadata.active_from)
+        return activeFrom <= today
+      })
+
+      const upcomingPolicy = sortedPolicies.find(policy => {
+        const activeFrom = parseActiveFrom(policy.metadata.active_from)
+        return activeFrom > today || activeFrom === null
+      })
+
+      const otherPolicies = sortedPolicies.filter(policy => {
+        const policyId = policy.metadata.policy_id
+        const currentPolicyId = currentPolicy ? currentPolicy.metadata.policy_id : null
+        const upcomingPolicyId = upcomingPolicy ? upcomingPolicy.metadata.policy_id : null
+
+        return policyId !== currentPolicyId && policyId !== upcomingPolicyId
+      })
+
+      const orderedPolicies = [currentPolicy, upcomingPolicy, ...otherPolicies].filter(Boolean)
+
+      return orderedPolicies.map(policy => {
+        const activeFrom = policy.metadata.active_from
+        const isCurrentPolicy = currentPolicy && policy.metadata.policy_id === currentPolicy.metadata.policy_id
+        const isUpcomingPolicy = upcomingPolicy && policy.metadata.policy_id === upcomingPolicy.metadata.policy_id
+
+        return {
+          routePath: this.routePathForPolicy({ activeFrom, isCurrentPolicy, isUpcomingPolicy }),
+          title: this.titleForPolicy({ activeFrom, isCurrentPolicy, isUpcomingPolicy }),
+        }
+      })
+    },
+    currentLink: function () {
+      const isCurrentPath = (element) => element.routePath === this.$route.path
+      const positionInList = this.links.findIndex(isCurrentPath)
+
+      if (positionInList === -1) {
+        const currentVersionIndex = this.links.findIndex(element => element.routePath === this.basePath)
+
+        return currentVersionIndex === -1 ? 0 : currentVersionIndex
+      }
+
+      return positionInList
+    },
+  },
+  methods: {
+    async loadPolicies () {
+      this.error = undefined
+
+      try {
+        const response = await this.$api.getAllPoliciesByType({ policyType: this.policyType })
+        this.policies = response
+      } catch (error) {
+        this.error = error
+        console.error(error)
+      }
+    },
+    routePathForPolicy ({ activeFrom, isCurrentPolicy, isUpcomingPolicy }) {
+      if (isCurrentPolicy) {
+        return this.basePath
+      }
+
+      if (isUpcomingPolicy) {
+        return `${this.basePath}/upcoming`
+      }
+
+      return `${this.basePath}/${activeFrom}`
+    },
+    titleForPolicy ({ activeFrom, isCurrentPolicy, isUpcomingPolicy }) {
+      if (isCurrentPolicy) {
+        return 'Current version'
+      }
+
+      if (isUpcomingPolicy) {
+        return 'Upcoming version'
+      }
+
+      return activeFrom
+    },
+  },
+  mounted () {
+    this.loadPolicies()
   },
 }
+
 </script>
+
+<style scoped></style>
diff --git a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
index db752f08..4fe5c97a 100644
--- a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
+++ b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
@@ -15,7 +15,7 @@
 
       <v-row justify="center">
         <v-col cols="11" md="4" order-md="last">
-          <TermsOfUseNavigationPanel basePath="/hosting-policy" policyType="hosting-policy" title="All Versions" />
+          <PolicyNavigationPanel basePath="/hosting-policy" policyType="hosting-policy" />
         </v-col>
 
         <v-col cols="11" md="8">
@@ -28,7 +28,7 @@
 
 <script>
 
-import TermsOfUseNavigationPanel from '../TermsOfUse/TermsOfUseNavigationPanel.vue'
+import PolicyNavigationPanel from '../Components/PolicyNavigationPanel.vue'
 
 export const versions = {
   'hosting-policy/version-1.vue': () => ({ component: import('./hosting-policy/version-1.vue') }),
@@ -49,7 +49,7 @@ const isFutureDate = (activeFrom) => {
 export default {
   name: 'HostingPolicyRenderer',
   components: {
-    TermsOfUseNavigationPanel,
+    PolicyNavigationPanel,
   },
   computed: {
     policyActiveFrom: function () {
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue b/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
deleted file mode 100644
index 1b2b3e78..00000000
--- a/src/components/Pages/TermsOfUse/TermsOfUseNavigationPanel.vue
+++ /dev/null
@@ -1,150 +0,0 @@
-<template>
-  <PolicyNavigationPanel :title="title" :links="links" :currentLink="currentLink" />
-</template>
-
-<script>
-import PolicyNavigationPanel from '../Components/PolicyNavigationPanel.vue'
-
-const parseActiveFrom = (activeFrom) => {
-  if (activeFrom === null || activeFrom === undefined) {
-    return null
-  }
-
-  return new Date(`${activeFrom}T00:00:00Z`)
-}
-
-const comparePolicies = (left, right) => {
-  const leftActiveFrom = parseActiveFrom(left.metadata.active_from)
-  const rightActiveFrom = parseActiveFrom(right.metadata.active_from)
-
-  if (leftActiveFrom === null && rightActiveFrom === null) {
-    return 0
-  }
-
-  if (leftActiveFrom === null) {
-    return 1
-  }
-
-  if (rightActiveFrom === null) {
-    return -1
-  }
-
-  return rightActiveFrom - leftActiveFrom || right.metadata.policy_id - left.metadata.policy_id
-}
-
-export default {
-  name: 'TermsOfUseNavigationPanel',
-  components: {
-    PolicyNavigationPanel,
-  },
-  props: {
-    basePath: {
-      type: String,
-      default: '/terms-of-use',
-    },
-    policyType: {
-      type: String,
-      default: 'terms-of-use',
-    },
-    title: {
-      type: String,
-      default: 'All Versions',
-    },
-  },
-  data: () => ({
-    policies: [],
-    error: undefined,
-  }),
-  computed: {
-    links: function () {
-      const sortedPolicies = [...this.policies].sort(comparePolicies)
-      const today = new Date()
-      today.setHours(0, 0, 0, 0)
-
-      const currentPolicy = sortedPolicies.find(policy => {
-        const activeFrom = parseActiveFrom(policy.metadata.active_from)
-        return activeFrom <= today
-      })
-
-      const upcomingPolicy = sortedPolicies.find(policy => {
-        const activeFrom = parseActiveFrom(policy.metadata.active_from)
-        return activeFrom > today || activeFrom === null
-      })
-
-      const otherPolicies = sortedPolicies.filter(policy => {
-        const policyId = policy.metadata.policy_id
-        const currentPolicyId = currentPolicy ? currentPolicy.metadata.policy_id : null
-        const upcomingPolicyId = upcomingPolicy ? upcomingPolicy.metadata.policy_id : null
-
-        return policyId !== currentPolicyId && policyId !== upcomingPolicyId
-      })
-
-      const orderedPolicies = [currentPolicy, upcomingPolicy, ...otherPolicies].filter(Boolean)
-
-      return orderedPolicies.map(policy => {
-        const activeFrom = policy.metadata.active_from
-        const isCurrentPolicy = currentPolicy && policy.metadata.policy_id === currentPolicy.metadata.policy_id
-        const isUpcomingPolicy = upcomingPolicy && policy.metadata.policy_id === upcomingPolicy.metadata.policy_id
-
-        return {
-          routePath: this.routePathForPolicy({ activeFrom, isCurrentPolicy, isUpcomingPolicy }),
-          title: this.titleForPolicy({ activeFrom, isCurrentPolicy, isUpcomingPolicy }),
-        }
-      })
-    },
-    currentLink: function () {
-      const isCurrentPath = (element) => element.routePath === this.$route.path
-      const positionInList = this.links.findIndex(isCurrentPath)
-
-      if (positionInList === -1) {
-        const currentVersionIndex = this.links.findIndex(element => element.routePath === this.basePath)
-
-        return currentVersionIndex === -1 ? 0 : currentVersionIndex
-      }
-
-      return positionInList
-    },
-  },
-  methods: {
-    async loadPolicies () {
-      this.error = undefined
-
-      try {
-        const response = await this.$api.getAllPoliciesByType({ policyType: this.policyType })
-        this.policies = response
-      } catch (error) {
-        this.error = error
-        console.error(error)
-      }
-    },
-    routePathForPolicy ({ activeFrom, isCurrentPolicy, isUpcomingPolicy }) {
-      if (isCurrentPolicy) {
-        return this.basePath
-      }
-
-      if (isUpcomingPolicy) {
-        return `${this.basePath}/upcoming`
-      }
-
-      return `${this.basePath}/${activeFrom}`
-    },
-    titleForPolicy ({ activeFrom, isCurrentPolicy, isUpcomingPolicy }) {
-      if (isCurrentPolicy) {
-        return 'Current version'
-      }
-
-      if (isUpcomingPolicy) {
-        return 'Upcoming version'
-      }
-
-      return activeFrom
-    },
-  },
-  mounted () {
-    this.loadPolicies()
-  },
-}
-
-</script>
-
-<style scoped></style>
diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index f0272926..ba10fd9a 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -6,7 +6,7 @@
     <v-container class="fill-height" fluid v-if="!error">
       <v-row justify="center">
         <v-col cols="11" md="4" order-md="last">
-          <TermsOfUseNavigationPanel />
+          <PolicyNavigationPanel policyType="terms-of-use" basePath="/terms-of-use" />
         </v-col>
 
         <v-col cols="11" md="8">
@@ -23,7 +23,7 @@
 </template>
 
 <script>
-import TermsOfUseNavigationPanel from './TermsOfUseNavigationPanel.vue'
+import PolicyNavigationPanel from '../Components/PolicyNavigationPanel.vue'
 
 export const versions = {
   'terms-of-use/version-1.vue': () => ({ component: import('./terms-of-use/version-1.vue') }),
@@ -33,7 +33,7 @@ export const versions = {
 export default {
   name: 'TermsOfUseRenderer',
   components: {
-    TermsOfUseNavigationPanel,
+    PolicyNavigationPanel,
   },
   computed: {
     policyActiveFrom: function () {

From 9e9704cd15e1656654a4486bc5b98bec93915d95 Mon Sep 17 00:00:00 2001
From: dena <dena@wikimedia.de>
Date: Tue, 28 Jul 2026 14:35:15 +0200
Subject: [PATCH 13/16] formatting

---
 src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue     | 4 ++--
 src/components/Pages/TermsOfUse/terms-of-use/version-2.vue | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
index ba10fd9a..aee72e48 100644
--- a/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
+++ b/src/components/Pages/TermsOfUse/TermsOfUseRenderer.vue
@@ -42,9 +42,9 @@ export default {
     isUpcomingRoute: function () {
       return this.$route.path === '/terms-of-use/upcoming'
     },
-    isCurrentRoute: function() {
+    isCurrentRoute: function () {
       return this.policyActiveFrom === undefined
-    }
+    },
   },
   data () {
     return {
diff --git a/src/components/Pages/TermsOfUse/terms-of-use/version-2.vue b/src/components/Pages/TermsOfUse/terms-of-use/version-2.vue
index a1e5a54b..c892a081 100644
--- a/src/components/Pages/TermsOfUse/terms-of-use/version-2.vue
+++ b/src/components/Pages/TermsOfUse/terms-of-use/version-2.vue
@@ -1122,7 +1122,7 @@ export default {
   components: {
   },
   computed: {
-    isMobile() {
+    isMobile () {
       return this.$vuetify.breakpoint.xs
     },
   },

From 7d799ee12f2750ab547c2b500df32965cc92025f Mon Sep 17 00:00:00 2001
From: Dat WMDE <dat.nguyen@wikimedia.de>
Date: Wed, 29 Jul 2026 12:34:39 +0200
Subject: [PATCH 14/16] Use API-driven current/upcoming policy selection
 (#1156)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

**CHANGES**
1. `HostingPolicyRenderer.vue`
- Replaced banner condition from computed date logic to route/API
- Removed `isFutureDate` helper
- Added `isCurrentRoute` + `policyType` parity with `TermsOfUseRenderer`

2. `PolicyNavigationPanel.vue`
- Removed date parsing/comparison helpers
- Added API-driven state fields `currentPolicyId` and `upcomingPolicyId`
- Links now resolve current/upcoming via those IDs from API responses
instead of local date logic
- loadPolicies now fetches:
  - all policies
  - current policy (via `getCurrentPolicyByType`)
  - upcoming policy (via `getUpcomingPolicyByType`, with 404 handled as
“none”)

Bug: T432965
Co-authored-by: Thomas Arrow <thomas.arrow@wikimedia.de>
---
 .../Components/PolicyNavigationPanel.vue      | 104 +++++++++---------
 .../HostingPolicy/HostingPolicyRenderer.vue   |  23 +---
 2 files changed, 57 insertions(+), 70 deletions(-)

diff --git a/src/components/Pages/Components/PolicyNavigationPanel.vue b/src/components/Pages/Components/PolicyNavigationPanel.vue
index 1c74d72b..d711e6ef 100644
--- a/src/components/Pages/Components/PolicyNavigationPanel.vue
+++ b/src/components/Pages/Components/PolicyNavigationPanel.vue
@@ -7,7 +7,7 @@
             <v-list class="wrap">
                 <v-list-item v-for="(link, index) in links" :key="link.routePath">
                     <v-list-item-content>
-                        <v-list-item-title v-if="index == currentLink">
+                        <v-list-item-title v-if="index == currentlyRenderedLink">
                             {{ link.title }}
                         </v-list-item-title>
 
@@ -25,32 +25,6 @@
 </template>
 
 <script>
-const parseActiveFrom = (activeFrom) => {
-  if (activeFrom === null || activeFrom === undefined) {
-    return null
-  }
-
-  return new Date(`${activeFrom}T00:00:00Z`)
-}
-
-const comparePolicies = (left, right) => {
-  const leftActiveFrom = parseActiveFrom(left.metadata.active_from)
-  const rightActiveFrom = parseActiveFrom(right.metadata.active_from)
-
-  if (leftActiveFrom === null && rightActiveFrom === null) {
-    return 0
-  }
-
-  if (leftActiveFrom === null) {
-    return 1
-  }
-
-  if (rightActiveFrom === null) {
-    return -1
-  }
-
-  return rightActiveFrom - leftActiveFrom || right.metadata.policy_id - left.metadata.policy_id
-}
 
 export default {
   name: 'PolicyNavigationPanel',
@@ -70,33 +44,34 @@ export default {
   },
   data: () => ({
     policies: [],
+    currentPolicyId: null,
+    upcomingPolicyId: null,
     error: undefined,
   }),
   computed: {
     links: function () {
-      const sortedPolicies = [...this.policies].sort(comparePolicies)
-      const today = new Date()
-      today.setHours(0, 0, 0, 0)
-
-      const currentPolicy = sortedPolicies.find(policy => {
-        const activeFrom = parseActiveFrom(policy.metadata.active_from)
-        return activeFrom <= today
-      })
+      const policyById = new Map(this.policies.map(policy => [policy.metadata.policy_id, policy]))
+      const currentPolicy = policyById.get(this.currentPolicyId)
+      const upcomingPolicy = policyById.get(this.upcomingPolicyId)
 
-      const upcomingPolicy = sortedPolicies.find(policy => {
-        const activeFrom = parseActiveFrom(policy.metadata.active_from)
-        return activeFrom > today || activeFrom === null
-      })
-
-      const otherPolicies = sortedPolicies.filter(policy => {
+      const otherPolicies = this.policies.filter(policy => {
         const policyId = policy.metadata.policy_id
-        const currentPolicyId = currentPolicy ? currentPolicy.metadata.policy_id : null
-        const upcomingPolicyId = upcomingPolicy ? upcomingPolicy.metadata.policy_id : null
+        const currentPolicyId = this.currentPolicyId
+        const upcomingPolicyId = this.upcomingPolicyId
 
         return policyId !== currentPolicyId && policyId !== upcomingPolicyId
+      }).sort((left, right) => {
+        const leftActiveFrom = left.metadata.active_from || ''
+        const rightActiveFrom = right.metadata.active_from || ''
+
+        if (leftActiveFrom === rightActiveFrom) {
+          return right.metadata.policy_id - left.metadata.policy_id
+        }
+
+        return rightActiveFrom.localeCompare(leftActiveFrom)
       })
 
-      const orderedPolicies = [currentPolicy, upcomingPolicy, ...otherPolicies].filter(Boolean)
+      const orderedPolicies = [upcomingPolicy, currentPolicy, ...otherPolicies].filter(Boolean)
 
       return orderedPolicies.map(policy => {
         const activeFrom = policy.metadata.active_from
@@ -109,14 +84,13 @@ export default {
         }
       })
     },
-    currentLink: function () {
-      const isCurrentPath = (element) => element.routePath === this.$route.path
-      const positionInList = this.links.findIndex(isCurrentPath)
+    currentlyRenderedLink: function () {
+      const isRenderedPath = (element) => element.routePath === this.$route.path
+      const positionInList = this.links.findIndex(isRenderedPath)
 
       if (positionInList === -1) {
-        const currentVersionIndex = this.links.findIndex(element => element.routePath === this.basePath)
-
-        return currentVersionIndex === -1 ? 0 : currentVersionIndex
+        const renderedVersionIndex = this.links.findIndex(element => element.routePath === this.basePath)
+        return renderedVersionIndex === -1 ? 0 : renderedVersionIndex
       }
 
       return positionInList
@@ -127,8 +101,33 @@ export default {
       this.error = undefined
 
       try {
-        const response = await this.$api.getAllPoliciesByType({ policyType: this.policyType })
-        this.policies = response
+        const policies = await this.$api.getAllPoliciesByType({ policyType: this.policyType })
+
+        this.policies = policies
+
+        // We look up the Current and Upcoming policy of this type to avoid needing to have the complex
+        // date calculations in the frontend and instead do them in the platform api.
+        // This is quite inefficient but it keeps the frontend less complex to reason about.
+        // We need to consider that there may be neither an upcoming or current policy and gracefully handle that,
+        try {
+          const upcomingPolicy = await this.$api.getUpcomingPolicyByType({ policyType: this.policyType })
+          this.upcomingPolicyId = upcomingPolicy.metadata.policy_id
+        } catch (error) {
+          if (!(error && error.response && error.response.status === 404)) {
+            console.error(error)
+          }
+          this.upcomingPolicyId = null
+        }
+
+        try {
+          const currentPolicy = await this.$api.getCurrentPolicyByType({ policyType: this.policyType })
+          this.currentPolicyId = currentPolicy.metadata.policy_id
+        } catch (error) {
+          if (!(error && error.response && error.response.status === 404)) {
+            console.error(error)
+          }
+          this.currentPolicyId = null
+        }
       } catch (error) {
         this.error = error
         console.error(error)
@@ -149,7 +148,6 @@ export default {
       if (isCurrentPolicy) {
         return 'Current version'
       }
-
       if (isUpcomingPolicy) {
         return 'Upcoming version'
       }
diff --git a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
index 4fe5c97a..8121eb16 100644
--- a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
+++ b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
@@ -4,7 +4,7 @@
       An error occurred while trying to load the requested policy. Please try again later.
     </v-alert>
     <v-container class="fill-height" fluid v-if="!error">
-      <v-row v-if="isUpcomingPolicy" justify="center">
+      <v-row v-if="isUpcomingRoute" justify="center">
         <v-col cols="11">
           <v-alert type="info">
             This is an upcoming version. You can find the
@@ -34,18 +34,6 @@ export const versions = {
   'hosting-policy/version-1.vue': () => ({ component: import('./hosting-policy/version-1.vue') }),
 }
 
-const isFutureDate = (activeFrom) => {
-  if (activeFrom === null || activeFrom === undefined) {
-    return false
-  }
-
-  const date = new Date(`${activeFrom}T00:00:00Z`)
-  const today = new Date()
-  today.setHours(0, 0, 0, 0)
-
-  return date > today
-}
-
 export default {
   name: 'HostingPolicyRenderer',
   components: {
@@ -58,8 +46,8 @@ export default {
     isUpcomingRoute: function () {
       return this.$route.path === '/hosting-policy/upcoming'
     },
-    isUpcomingPolicy: function () {
-      return isFutureDate(this.policyMetadata && this.policyMetadata.active_from)
+    isCurrentRoute: function () {
+      return this.policyActiveFrom === undefined
     },
   },
   data () {
@@ -67,6 +55,7 @@ export default {
       policy: undefined,
       policyMetadata: undefined,
       error: undefined,
+      policyType: 'hosting-policy',
     }
   },
   methods: {
@@ -76,13 +65,13 @@ export default {
       this.error = undefined
 
       try {
-        const policyType = 'hosting-policy' // TODO for a generalized component, read this from component property
+        const policyType = this.policyType // TODO for a generalized component, read this from component property
         const activeFrom = this.policyActiveFrom
         let response
 
         if (this.isUpcomingRoute) {
           response = await this.$api.getUpcomingPolicyByType({ policyType })
-        } else if (activeFrom === undefined) {
+        } else if (this.isCurrentRoute) {
           response = await this.$api.getCurrentPolicyByType({ policyType })
         } else {
           response = await this.$api.getPolicyByDate({ policyType, activeFrom })

From 4ad335f7cd322033997e7c6a24be1645bc1e41eb Mon Sep 17 00:00:00 2001
From: Thomas Arrow <thomas.arrow@wikimedia.de>
Date: Wed, 29 Jul 2026 11:36:44 +0100
Subject: [PATCH 15/16] keep both renders with similar markup for upcoming
 banner

---
 .../Pages/HostingPolicy/HostingPolicyRenderer.vue  | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
index 8121eb16..fafbf6a9 100644
--- a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
+++ b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
@@ -4,21 +4,17 @@
       An error occurred while trying to load the requested policy. Please try again later.
     </v-alert>
     <v-container class="fill-height" fluid v-if="!error">
-      <v-row v-if="isUpcomingRoute" justify="center">
-        <v-col cols="11">
-          <v-alert type="info">
-            This is an upcoming version. You can find the
-            <router-link class="white--text" to="/hosting-policy">current version here</router-link>.
-          </v-alert>
-        </v-col>
-      </v-row>
-
       <v-row justify="center">
         <v-col cols="11" md="4" order-md="last">
           <PolicyNavigationPanel basePath="/hosting-policy" policyType="hosting-policy" />
         </v-col>
 
         <v-col cols="11" md="8">
+          <v-alert type="info" v-if="isUpcomingRoute">
+            This is an upcoming version. You can find the
+            <router-link class="white--text" to="/hosting-policy">current version here</router-link>.
+          </v-alert>
+
           <component :is="policy" v-if="policy" />
         </v-col>
       </v-row>

From 5909dc5f4ee75af6e2dd9cf38b92f5fce8fbe017 Mon Sep 17 00:00:00 2001
From: Thomas Arrow <tarrow@users.noreply.github.com>
Date: Wed, 29 Jul 2026 13:04:49 +0100
Subject: [PATCH 16/16] Handle special case of Pilot for Hosting Policy (#1159)

A rather unelegant workaround to handle the case of no currrent hosting
policy to redirect people to the pilot.

This allows us to change the footer link to be just '/hosting-policy'
and have it handled by the HostingPolicyRenderer but still redirect to
the pilot component.

Added comments to ensure we remove this cruft as soon as the pilot
policy is redundant.

Bug: T432965
---
 src/components/Layout/Foot.vue                              | 2 +-
 .../Pages/HostingPolicy/HostingPolicyRenderer.vue           | 5 +++++
 .../Pages/{HostingPolicy.vue => HostingPolicyPilot.vue}     | 1 +
 src/router/index.js                                         | 6 +++---
 4 files changed, 10 insertions(+), 4 deletions(-)
 rename src/components/Pages/{HostingPolicy.vue => HostingPolicyPilot.vue} (99%)

diff --git a/src/components/Layout/Foot.vue b/src/components/Layout/Foot.vue
index d3518768..1070f3a2 100644
--- a/src/components/Layout/Foot.vue
+++ b/src/components/Layout/Foot.vue
@@ -21,7 +21,7 @@
           <ul class="footer-list">
             <li><router-link to="/privacy-policy">Privacy Policy</router-link></li>
             <li><router-link to="/terms-of-use">Terms of Use</router-link></li>
-            <li><router-link to="/hosting-policy/pilot">Hosting Policy</router-link></li>
+            <li><router-link to="/hosting-policy">Hosting Policy</router-link></li>
             <li><router-link to="/dsa-info">Digital Services Act Information</router-link></li>
             <li><a target="_blank" rel="noopener noreferrer" href="https://www.wikimedia.de/impressum/">Imprint</a></li>
             <li><router-link to="/complaint">Report illegal content</router-link></li>
diff --git a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
index fafbf6a9..4c6b58db 100644
--- a/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
+++ b/src/components/Pages/HostingPolicy/HostingPolicyRenderer.vue
@@ -69,6 +69,11 @@ export default {
           response = await this.$api.getUpcomingPolicyByType({ policyType })
         } else if (this.isCurrentRoute) {
           response = await this.$api.getCurrentPolicyByType({ policyType })
+          if (response === undefined) {
+            // Special case to redirect users to the pilot policy if there is no current policy
+            // Remove afer T408316
+            this.$router.replace({ path: '/hosting-policy/pilot' })
+          }
         } else {
           response = await this.$api.getPolicyByDate({ policyType, activeFrom })
         }
diff --git a/src/components/Pages/HostingPolicy.vue b/src/components/Pages/HostingPolicyPilot.vue
similarity index 99%
rename from src/components/Pages/HostingPolicy.vue
rename to src/components/Pages/HostingPolicyPilot.vue
index 24fd7f73..b0b828b4 100644
--- a/src/components/Pages/HostingPolicy.vue
+++ b/src/components/Pages/HostingPolicyPilot.vue
@@ -279,6 +279,7 @@
 </template>
 
 <script>
+// Legacy file. Remove after T408316
 export default {
   name: 'HostingPolicy',
 }
diff --git a/src/router/index.js b/src/router/index.js
index 177d61af..4c22ff57 100644
--- a/src/router/index.js
+++ b/src/router/index.js
@@ -19,7 +19,7 @@ import Privacy from '@/components/Pages/Privacy/Privacy'
 import User from '@/components/Pages/User'
 import Discovery from '@/components/Pages/Discovery/Discovery'
 import Complaint from '@/components/Pages/Complaint.vue'
-import HostingPolicy from '@/components/Pages/HostingPolicy.vue'
+import HostingPolicyPilot from '@/components/Pages/HostingPolicyPilot.vue'
 import HostingPolicyRenderer from '@/components/Pages/HostingPolicy/HostingPolicyRenderer.vue'
 import DsaInfo from '@/components/Pages/DsaInfo/DsaInfo'
 
@@ -92,9 +92,9 @@ const router = new Router({
       component: HostingPolicyRenderer,
     },
     {
-      path: '/hosting-policy/pilot',
+      path: '/hosting-policy/pilot', // Remove after T408316
       name: 'HostingPolicyPilot',
-      component: HostingPolicy,
+      component: HostingPolicyPilot,
     },
     {
       path: '/hosting-policy/:activeFrom',