Many hosting providers claim to keep no logs, but the term is often used loosely. Some providers disable application logs while retaining system logs, netflow data, or SNMP statistics that reveal connection patterns. Others maintain billing records that can be correlated with traffic timestamps. True no-logs hosting must address every layer of the stack where data could be recorded.
At AnubizHost, no-logs means exactly that: zero traffic data is recorded at any level. Our servers are configured with disabled syslog for network interfaces, no netflow or sFlow export, no SNMP traffic counters, and no application-level logging of connections. We do not even maintain bandwidth usage statistics for individual servers beyond what is necessary for aggregate capacity planning.
Our approach goes beyond policy - it is architectural. Servers boot from read-only images with logging directories mounted as tmpfs filesystems that exist only in RAM. In the event of a power interruption or seizure, all temporary data is immediately and irrecoverably lost. There is simply no persistent storage location where logs could accumulate.