prefixes

Sharing URLs privatelyNow, if all of this sounds a bit familiar, then that’s likely because you are already familiar with the Safe Browsing Enhanced Mode. The privacy server removes potential user identifiers and forwards the encrypted hash prefixes to the Safe Browsing server via a TLS connection that mixes requests with many other Chrome users. The Safe Browsing server decrypts the hash prefixes and matches them against the server-side database, returning full hashes of all unsafe URLs that match one of the hash prefixes sent by Chrome. This server sits between Chrome and Safe Browsing and strips out any identifying information from the browser request. Thanks to all of this, Google’s Safe Browsing service should never see your IP address.