← All guides

IP processing and IP storage: the crucial difference

When an Internet connection is established, the IP address is technically processed so that answers find their way back to the correct connection. However, processing is broader than storage. For “We don’t save!” The core question is therefore not “does an IP appear technically?”, but rather “who stores it after the request, for what purpose and for how long?”.

Check

Control access logs, application, proxy, CDN and provider separately and document retention period and purpose for each level.

Principle

“We don’t save!” does not evaluate whether an IP address becomes visible during technical communication, but rather whether this results in unnecessary persistent storage, recognition or sharing.

Related guides

• Umami: cookieless does not mean without visitor identification
• Checklist: does my website store unnecessary visitor data?
• PHP: Check REMOTE_ADDR and passed client IP
• Plausible: Understanding IP processing and daily visitor recognition

Sources and verification

This guide is based on multiple current sources. Vendor documentation is not treated as proof that every concrete installation automatically follows the same privacy characteristics.

• Source 1
• Source 2

Important: IP processing is not IP storage

An IP address has to be processed to establish and deliver a network connection. Hosting providers, firewalls or DDoS protection may also process or retain it for a limited time for security purposes. No Logging distinguishes this security layer from unnecessary persistent visitor logging by the website, application and ordinary access logs.