- Joined
- Sep 15, 2014
- Messages
- 4,341
- Likes
- 8,855
- Degree
- 8
Wordpress is at it again! First they added those extra http calls for emoji which @Ryuzaki talked about, NOW they've got a Google font specifically in the admin area of your PBN, which doesn't show up in the visitor area!! This basically means that every time you log into wordpress admin Google knows it's you and your IP.
Now you are thinking, how is that bad? If you've been hiding your footprints from Google by not using Google Chrome, Google Analytics, Google DNS, Google internet service, and and the ducking the myriad of other Google traps to track you - you just wasted your time, cause now Google Font is being called back as soon as you login to your admin. "But, who avoids all those services CCarter?" People running PBN (Private Blog Networks) that do not want Google even getting a signal that they are all controlled or owned by the same person, now every wordpress login even the first one is sent to Google...
They laughed at him when he said "Don't use Wordpress anymore, it's getting too big and will become a security risk" - Who's laughing now...
Sauce: Important: Google WordPress Font Tracking
Google’s privacy statement for the font use says “we detect which websites are using Google Fonts”.
https://developers.google.com/fonts/faq#Privacy
Google’s general privacy policy states the company collects information from various technologies and may combine it with personal information. The policy also says “We use the information we collect from all of our services to provide, maintain, protect and improve them, to develop new ones, and to protect Google…”
http://www.google.com/policies/privacy/#infouse
There is a WordPress plugin that disables the font call:
https://wordpress.org/plugins/disable-google-fonts/
However, if you log into the WordPress admin area to install the plugin it’s too late. Google just got your data. But it’s better than nothing.
There is further discussion about privacy issues on the WordPress developers blog:
https://make.wordpress.org/core/2013/11/11/open-sans-bundling-vs-linking/
In addition to the WordPress core, some themes, including pre-installed themes all call the Google font. But I feel the bigger concern is admin area and information given to Google, even without a cookie, which can be used to connect websites together – even match them with particular users.
Ultimately, since the font call is made immediately upon logging into the WordPress admin area for the first time, it seems to me the identification trigger can only be avoided by modifying the core WordPress files before logging in. While doable, it presents a possible nightmare because WordPress continually updates and some have WordPress installed across dozens, even hundreds of websites.
My recommendation, if you are using a private blog network or linking between your websites is not to use WordPress unless (1) your first login is with a proxy, (2) you immediately install the Google font removal plugin, and (3) do not use any themes making use of Google fonts.
Read more Google Webfonts, The Spy Inside?
It's only going to get worst with Wordpress before it gets better, hence why I suggest getting off of Wordpress if you CAN as soon as possible.