Suggestion to add clearer caveats to privacy tool recommendations

I don’t disagree with you on this specific instance (pay for service, stop paying don’t get service). But the other points on your general ideas aren’t as encouraging and dismissive. Yes, PG should not write the ToS for every service as people need to learn it on their own. But also PG should raise awareness of footguns and things worth considering before utilizing a critical service. Doesn’t even need to be a a flashing neon sign, a quick blurb on “ensure you understand how aliases are used should you need to cancel or migrate providers” isn’t exactly harmful.