We don’t store IP addresses, user-agent fingerprints, unique identifiers, emails, names—none of it. There’s no telemetry or “anonymous crash reports.”
- Your browser and our server exchange data to deliver pages (that’s how HTTP works). That info is handled transiently and not logged in a way that identifies you on our primary instance. -
-+ 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. +
++ When your browser requests a page, the server (which uses Nginx) 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 connection metadata — it’s automatically generated by all web servers as part of the HTTP standard. +
++ These minimal details may briefly appear in Nginx access logs. + 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. +
++ 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. +
+