At MT-forum some people (as I do) had not enabled Chrome advanced protection because of the privacy issues it will give (full url and page data send to Chrome).
Recently on
@Sampei.Nihira securiy config the issue was mentioned again.
@TairikuOkami posted he even had a bad experience with it relating to privacy and google data collection.
So I thought I have a look how bad the data collection really is and honestly I was suprised (see pictiure below)
View attachment 296039
On top of that Chrome promises that "data is used exclusively for security purposes" (which is good) and "is anonymized" (which is good also), but "retained only as long as necessary" (despite the "only" I don't like the "as long as necessary"
Question what is your opinion or experience with Enhanced protection.
Enhanced Protection in Chrome is essentially a “more telemetry for more protection” trade-off. It can be a meaningful security upgrade for high-risk browsing patterns, but it is also reasonable to avoid it if minimizing data disclosure to Google is a priority.
What Enhanced Protection changes (in practical terms)
Compared to Standard Protection, Enhanced Protection is more willing to send extra context to Google Safe Browsing when Chrome can’t confidently classify a site or detects suspicious behavior. Depending on the situation, that can include:
- Full URLs (not just hashed/partial lookups)
- “Bits of page content” (small samples used for classification/signals)
- Additional security-related signals (e.g., suspicious downloads, suspected phishing pages)
That extra context can improve detection of brand-new phishing pages, fast-flux malicious infrastructure, and “fresh” scam campaigns where local/hashing approaches may lag.
Privacy implications (what to take seriously)
Even when Google says the data is used “exclusively for security purposes” and “anonymized,” a few points still matter:
- Full URL exposure can be sensitive: URLs can contain identifiers, internal paths, query parameters, ticket numbers, document names, etc.
- “Bits of page content” can be sensitive in some contexts (for example, webmail portals, internal dashboards, customer/account portals). It’s not “the whole page,” but it can still be more than many users are comfortable sharing.
- Retention language is vague: “retained only as long as necessary” is standard compliance wording, but it doesn’t tell you a concrete duration, and “necessary” can vary by product/legal requirements.
So your discomfort with that wording is understandable. It’s not proof of abuse, but it is a real “trust and policy” decision, not just a technical one.
Security value (who benefits most)
Enhanced Protection tends to make the most sense for:
- Users frequently hitting unfamiliar sites (social media links, search results, ad-driven browsing)
- Less technical household members who may click through lures
- People who regularly download executables or open many new domains
- Users targeted by phishing/scams (business email, crypto, marketplaces, etc.)
If your browsing is mostly known destinations, you already run a strong AV, and you’re careful with links/downloads, the marginal benefit can be smaller.
If you don’t enable it, you can still stay safe
You can keep Standard Protection and still improve protection without the same level of URL/content sharing:
- Keep Chrome auto-updates enabled (this is often the biggest real-world security factor).
- Use a reputable DNS filter (e.g., Quad9 for security-focused blocking; or another provider you trust).
- Use an AV with strong web protection (and accept its own privacy trade-offs—most do some form of cloud lookups).
- Be strict about extensions (few, reputable, and regularly reviewed).
Bottom line
Enhanced Protection can improve detection, especially against new and fast-moving phishing/malware campaigns, but it does so by sharing more browsing context (including full URLs and limited page data in certain cases). If privacy/minimal data sharing is your priority, sticking to Standard Protection is a defensible choice—just compensate with updates, cautious browsing habits, and layered protections like DNS filtering and a reputable AV.
Sources