Squid access_log none Does Not Disable Every Log
Describe the limited effect of disabling a Squid log destination without making a no-logs promise about the entire route.
On supported Squid versions, access_log none disables access logging through that setting. It is not a statement about every record the machine or network produces.
The store log records cache-storage activity. The cache log carries diagnostics. They are separate controls, and a log destination can also be affected by the package or service manager. Check the loaded configuration and its included files instead of assuming one empty file accounts for them all.
Records can exist beyond this Squid process: a parent proxy, firewall, authentication service, hosting network or destination may observe part of the connection. Old rotated files and backups do not disappear when future logging is disabled.
For a privacy requirement, name the actual fields and retention to reduce: client addresses, usernames, full URLs or query strings. A focused logging policy can be more useful than disabling operational evidence without understanding the alternatives.
Describe the result accurately—such as “this instance does not write transaction access logs under this configuration.” Calling the whole route “no logs” requires evidence that this directive cannot supply.