Fun fact: WooCommerce collects your sensitive information without...

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 tracked, only general WooCommerce settings, general product, order and user counts and admin email for discount code."
- 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 status
- Number of users and their roles
- Number of products and their types
- First and last order date
- Order statuses (completed, failed, refunded, pending, etc.)
- GROSS REVENUE
- Payment provider revenue (PayPal, Stripe, Braintree, etc.)
- Number of reviews on products
- Details of the first and last 20 orders
- Payment gateway configurations
- Enabled WooCommerce features
- Currency
- Postal code
- Selling locations
- Site installation date
- Custom templates
- Checkout settings
- WooCommerce subscription order data (switch count, revenue, resubscribe count, etc.)
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…
2. gdpr.eu/Recital-32-Con…
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. Never the why. Never the how. Never the plan.
And when we're invited to join the discussion, we're often ignored or overwritten.
WordPress is an open-source theater.
github.com/woocommerce/wo…
These are easy to fix, but since they haven't, I can safely assume all WooCommerce developers have tracking disabled.
Pro dev tip: Stop creating hooks in your constructors. Instead, create a procedural file that contains all hooks. It makes your plugin easy to understand and super manageable. You can also remove all those "instances" you need only once.
This is why the community demands a new governance model that holds everyone accountable equally to ensure better software.
</🧵>












