From 6851692f551a390b76e7518520e2377ca90c767e Mon Sep 17 00:00:00 2001
From: pascal <pascal@netbird.io>
Date: Thu, 9 Apr 2026 17:11:25 +0200
Subject: [PATCH] add proxy access log retention section

---
 .../manage/reverse-proxy/access-logs.mdx      | 23 +++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/src/pages/manage/reverse-proxy/access-logs.mdx b/src/pages/manage/reverse-proxy/access-logs.mdx
index a972ac2d..108139ee 100644
--- a/src/pages/manage/reverse-proxy/access-logs.mdx
+++ b/src/pages/manage/reverse-proxy/access-logs.mdx
@@ -76,6 +76,29 @@ Access logs support several operational and security workflows:
 - **Monitoring** - Track usage patterns across your services. Identify which services receive the most traffic, peak usage times, and unusual access patterns that may warrant investigation.
 - **Compliance** - Maintain records of service access for regulatory requirements. Access logs provide an auditable trail of who accessed what, when, and from where.
 
+## Retention and Cleanup
+
+For the cloud version of NetBird, access logs are retained for 7 days.
+For the self-hosted version, access log retention can be configured in the `management.json` or `config.yaml` by setting the following config parameters:
+
+```json
+{
+    "ReverseProxy": {
+        "AccessLogRetentionDays": 7,
+        "AccessLogCleanupIntervalHours": 24
+    }
+}
+```
+
+```yaml
+reverseProxy:
+  accessLogRetentionDays: 7
+  accessLogCleanupIntervalHours: 24
+```
+
+- **accessLogRetentionDays** - Define how long access logs are retained before they are automatically deleted.
+- **accessLogCleanupIntervalHours** - Set how often the system checks for and deletes expired access log entries.
+
 ## Related pages
 
 - [Reverse Proxy Overview](/manage/reverse-proxy) - learn how to create and manage reverse proxy services