The application being privacy focused and the marketing site using normal marketing optimization techniques are different things.

On the other hand, it's usually best to lead by example and "put your money where your mouth is".

Yes, and lose a bunch of money. :)

You could argue cold calling is worse than a tracking cookie. But I would still have salesmen cold call for a privacy focused product, for example.

Cookies as tech say nothing about privacy. If you want to store information that you refuse to share your private data - that almost certainly is getting stored in a cookie.

You can route connections on different layers than IP routing. We commonly talk about http request routing as in dispatch based on the domain/path. I'm happy with "routing" as in directing traffic via DNS resolution. I doubt anyone here is confusing that.

> Cookies as tech say nothing about privacy.

But cookie banners do. Essential cookies that are required e.g. to store login data no not require a cookie banner (https://github.blog/2020-12-17-no-cookie-for-you/). So if there is a cookie banner you can assume that the site wants to store analytics, tracking or advertising cookies.

They store a FB cookie and they store it before user accepts the cookie banner.

Sure, that's not very privacy-friendly, but that's a different claim than what OP wrote.

> I'm happy with "routing" as in directing traffic via DNS resolution. I doubt anyone here is confusing that.

I disagree. As a former network engineer the title "We're transforming internet routing" and subtitle "Rethinking Internet Routing" [my emphasis] makes me think of IP based routing first. I think they could have been clearer or picked a less grandiose title.

Don't get me wrong, on the surface this looks like a neat tool.

Absolutely correct on the privacy. We're actually dropping everything from Google / Facebook and anything third-party at the moment (since it's not technically legal in Europe anyway). It will be a bit of a process though.