diff --git a/admin_manual/groupware/calendar.rst b/admin_manual/groupware/calendar.rst
index 4c7c38d2f46..4ddf2955a91 100644
--- a/admin_manual/groupware/calendar.rst
+++ b/admin_manual/groupware/calendar.rst
@@ -160,3 +160,24 @@ or::
 
   # Allow users to create calendars/subscriptions without restriction
   php occ config:app:set calendar maximumCalendarsSubscriptions --type=integer --value=-1
+
+.. _caldav-data-retention:
+
+Data retention
+--------------
+
+.. versionadded:: 26.0.0
+
+You can configure how long Nextcloud keeps some of the calendar data.
+
+Sync tokens
+~~~~~~~~~~~
+
+The CalDAV backend keeps track of any modifications of calendars. That is anything added, modified or removed. The data is used for differential synchronization of offline clients like Thunderbird. At a certain point in time, the data can be considered outdated assuming there will be no more client needing it. This can help keep the database table `calendarchanges` small::
+
+  php occ config:app:set totalNumberOfSyncTokensToKeep --value=30000
+
+The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active synced calendars the system would only keep an average of 10 changes per calendar. This will lead to premature data deletion and synchronization problems.
+
+
+.. warning:: This setting will also influence :ref:`CardDAV data retention<carddav-data-retention>`.
diff --git a/admin_manual/groupware/contacts.rst b/admin_manual/groupware/contacts.rst
index af8dc150ed7..2dc000222fa 100644
--- a/admin_manual/groupware/contacts.rst
+++ b/admin_manual/groupware/contacts.rst
@@ -49,3 +49,23 @@ Shared items
 .. versionadded:: 5.5.0
 
 For this feature, the shipped `related resources app <https://apps.nextcloud.com/apps/related_resources>`_ needs to be enabled.
+
+.. _carddav-data-retention:
+
+Data retention
+--------------
+
+.. versionadded:: 26.0.0
+
+You can configure how long Nextcloud keeps some of the contacts data.
+
+Sync tokens
+^^^^^^^^^^^
+
+The CardDAV backend keeps track of any modifications of address books. That is anything added, modified or removed. The data is used for differential synchronization of offline clients like Thunderbird. At a certain point in time, the data can be considered outdated assuming there will be no more client needing it. This can help keep the database table `addressbookchanges` small::
+
+  php occ config:app:set totalNumberOfSyncTokensToKeep --value=30000
+
+The default is keeping 10,000 entries. This option should be set adequate to the number of users. E.g. on an installation with 5000 active synced addressbooks the system would only keep an average of 10 changes per sync. This will lead to premature data deletion and synchronization problems.
+
+.. warning:: This setting will also influence :ref:`CalDAV data retention<caldav-data-retention>`.
diff --git a/admin_manual/release_notes/upgrade_to_26.rst b/admin_manual/release_notes/upgrade_to_26.rst
index b97804ca2ac..ef621519a18 100644
--- a/admin_manual/release_notes/upgrade_to_26.rst
+++ b/admin_manual/release_notes/upgrade_to_26.rst
@@ -21,6 +21,10 @@ A brief overview of changes:
 
 See for more information: :ref:`email-smtp-config`.
 
+DAV data retention
+------------------
+
+A mechanism to clean up old CalDAV and CardDAV data has been added. See :ref:`CalDAV retention <caldav-data-retention>` and :ref:`CardDAV retention <carddav-data-retention>` and make sure it fits your installation size.
 
 Web server configuration
 ------------------------