&gt; The full IP never makes it to disk.<p>The full IP makes it to <i>Google</i>. We don&#x27;t know what Google actually does with the packets they receive; we only know what they say.<p>&gt; Only the last octet of an IPv4 address is removed.<p>Really? Wow. They aren&#x27;t even pretending to anonymize addresses with a hash. Given that there is certainly more than 8-bits of identifying data in the other data sent to GA, a unique identifier can easily be recovered. Also, the bits they mask are the <i>least interesting</i> part of the address. They are preserving the network part of the address, which probably gives them the AS number.<p>&gt; Considering homebrew&#x27;s use specifically, not just looking at GA in general<p>That&#x27;s the point - homebrew is choosing to add data to GA, which cannot be considered in isolation. The problem with GA isn&#x27;t that they collect data from any particular site. Knowing that you occasionally visit ${website} might be interesting, but it&#x27;s of limited value and relevancy. A list of people that visit ${political_opponent}&#x27;s website might be very interesting, but most of the time nobody is going to care. Knowing that you installed some software isn&#x27;t interesting in most cases.<p>All of those situations change when someone can <i>aggregate</i> the data.  Consider all those data points combined with the other websites that send data to GA, gmail,  when you loaded the Javascript, fonts, etc hosted by Google. Add in all the data that is sent to Google from Android devices, Chrome, Nest, and every other product that Google (err, &quot;Alphabet&quot;) is involved in. In aggregate, just the timestamps and partial address information will produce surprisingly accurate profile of your life. This gets scary when you start to do an actual pattern-of-life analysis and correlate &quot;anonymized&quot; data back to real names.