Earlier quoted context omitted.
TypeKit does indeed send tracking data back to Adobe through the domain p.typekit.net. This is also likely reflected in Adobe's privacy policy. Luckily, it is possible to use Content-Security-Policy or client-side scripts to block this domain while allowing use.typekit.net, which simply hosts the font files.
Like I said, they keep track of font usage. The billing is based on usage. That domain sets no cookies and the privacy policy doesn't permit the data to be used for ads: https://www.adobe.com/privacy/policies/adobe-fonts.html It's not ad tech. I think this is the problem with the "high score" approach to measuring the privacy impact of a site. Number of third-party cookies or "trackers" is not a great proxy for how w…
The problem now is a lack of trust, not the least of which because there's often not that much transparency and very little accountability in the way of law, as well as various actors that constantly try to skirt the line (i.e. Facebook, Google, etc.)