No-logs policy, explained
A no-logs statement describes the absence of specified logging. Its value depends on the categories, scope and evidence.
Content revised · English
- The field
- Privacy
- Reading time
- 1 minute
- In this entry
- Meaning · relevance · limits
The meaning
A no-logs statement describes the absence of specified logging. Its value depends on the categories, scope and evidence.
Why it matters
Ask which connection, security, billing and account records exist, why they exist and how long they remain.
The boundary
An unqualified slogan is not an audit and does not describe every component or supplier.
Ask which layer and which record
An application disables web access logs while its reverse proxy, authentication service and billing database still keep records. A meaningful no-log statement identifies the layer, the fields excluded and any operational records retained. It also requires a tested configuration; a slogan cannot establish how an entire service handles data.
- Inspect proxy, application, network, authentication and support records separately.
- Do not present the account workflow as an audited no-log production platform.