During installation, the "opt-in" box is pre-checked and easy to miss on larger screens. According to the EU, this is considered opt-out, not opt-in.
When you connect your store to Woo's services via "WooCommerce > Extensions," they'll automatically enable tracking for you — this time, without requesting any consent at all.
You can disable this tracking at: WP Admin > WooCommerce > Settings > Advanced > WooCommerce dot com > Allow usage of WooCommerce to be tracked.
All this tracking is done via class WC_Tracker. With this data, they'll know exactly how many customers you have. The file header states: "The WooCommerce tracker class adds functionality to track WooCommerce usage based on if the customer opted in. No personal information is
OK, cool. So, what data do they collect? Here's a small list: - Unique identifier - Domain name - Email address - Theme - WordPress version and locale - Server information - Active plugins and their author names - Inactive plugins and their author names - Jetpack installation
This data includes email addresses and plugin author names, even for plugins not intended for public listing. This is considered personal-identifiable information (PII). Hence, having this tracking be opt-out instead of opt-in is a GDPR violation. 1. curia.europa.eu/juris/liste.js…
Out of curiosity, I reviewed the pull request that added tracking of the first and last 20 orders. No explanation was provided as to why they needed this data. Like much of WordPress, these decisions are made privately, leaving the public in the dark. We only see the code.
Additionally, the tracker spawns many PHP 8 deprecation notices in the logs and quickly exhausts memory thanks to badly developed queries. These are easy to fix, but since they haven't, I can safely assume all WooCommerce developers have tracking disabled.
Also, when tracking is enabled, WooCommerce embeds a pixel in your admin area. So they don't just track your site's data but also your IP and how you're administrating it. Pro dev tip: Stop creating hooks in your constructors. Instead, create a procedural file that contains all
My next rant: WooCommerce's animated logo of inaccessibility and how they promised to remove it a year ago. </🧵>