From fcb66ac1c6a80725d51e0dcf0e79d30cb80e354d Mon Sep 17 00:00:00 2001
From: ashley <iamashley@duck.com>
Date: Sat, 11 Oct 2025 13:56:36 +0200
Subject: [PATCH] fix stuff + add stuff

---
 html/priv.ejs | 30 +++++++++++++++++++++++-------
 1 file changed, 23 insertions(+), 7 deletions(-)

diff --git a/html/priv.ejs b/html/priv.ejs
index fcbd3445..eabfe36d 100644
--- a/html/priv.ejs
+++ b/html/priv.ejs
@@ -255,18 +255,34 @@
     <!-- What we collect -->
     <section id="what-we-collect" aria-labelledby="collect-heading">
       <h2 id="collect-heading" class="section">What We Do/Don’t Collect</h2>
-      <details class="block" open>
+      <details class="block">
         <summary>We collect <em>nothing</em> about you</summary>
         <p>
           We don’t store IP addresses, user-agent fingerprints, unique identifiers, emails, names—none of it. There’s no telemetry or “anonymous crash reports.”
         </p>
       </details>
-      <details class="block">
-        <summary>What exists briefly so the internet works</summary>
-        <p>
-          Your browser and our server exchange data to deliver pages (that’s how HTTP works). That info is handled <em>transiently</em> and not logged in a way that identifies you on our primary instance.
-        </p>
-      </details>
+  <details class="block">
+  <summary>What exists briefly so the internet works</summary>
+  <p>
+    Every time you open a page, your browser and Poke’s server exchange a small amount of technical data — this is simply how the web works.  
+    Without this back-and-forth, pages couldn’t load, images wouldn’t display, and requests wouldn’t reach the right place.
+  </p>
+  <p>
+    When your browser requests a page, the server (which uses <strong>Nginx</strong>) momentarily processes information such as your IP address, the requested URL, the response code, and the time it took to deliver the page.  
+    This data is known as <em>connection metadata</em> — it’s automatically generated by all web servers as part of the HTTP standard.
+  </p>
+  <p>
+    These minimal details may briefly appear in <strong>Nginx access logs</strong>.  
+    Such logs are necessary for the server to function correctly — for example, to detect broken routes, prevent abuse, monitor uptime, or fix routing bugs.  
+    However, on Poke’s primary instance, these logs are kept for the shortest technically feasible duration and are not linked to any personally identifying data.  
+    They exist purely for operational health and security — never for tracking or analytics.
+  </p>
+  <p>
+    No cookies, user-agents, browser fingerprints, or other identifiers are stored or analyzed.  
+    Once the request is processed, the transient connection data fades away — leaving no persistent record that can be used to identify you.
+  </p>
+</details>
+
       <details class="block">
         <summary>Poke Account</summary>
         <p>