Matt Radford

Messing with links since <blink>

WordPress and data collection

Published on 

What does the software we use actually do, and does it work in our favour?

The plugin problem

At work at the end of November 2017, we (10 Degrees) received an email from Rocket Genius – developers of Gravity Forms – offering assistance during a coming upgrade.


In the coming days, we’re going to be releasing version 2.3 of Gravity Forms which contains some significant changes to the database. This means that all your entry data will be copied into new tables and forms will not be able to receive new submissions during the migration.

I’m writing to you because, according to our records, you have some sites with a lot of entries and I’d very much like to oversee your migration personally and make sure that it goes as smoothly and as quickly as possible with minimal downtime for your users.

If you’d like me to give you a hand, please let me know and we’ll make a plan together.


We genuinely appreciate Rocket Genius reaching out to ensure a potentially breaking upgrade went smoothly. It’s a quality plugin and it’s reassuring to know the developers want to ensure things go well for customers. But this line caught our eye:

…according to our records, you have some sites with a lot of entries…

Wait, how do Rocket Genius know how many entries our sites have? Are they recording this data?

We decided to investigate, and found a function called get_remote_post_params() in /gravityforms/common.php.

This function sends an array of data to a URL defined in GRAVITY_MANAGER_PROXY_URL as

Here’s the array it sends:

$post = array(
'of' => 'gravityforms',
'key' => self::get_key(),
'v' => self::$version,
'wp' => get_bloginfo( 'version' ),
'php' => phpversion(),
'mysql' => $wpdb->db_version(),
'version' => '2',
'plugins' => $plugins,
'tn' => $theme_name,
'tu' => $theme_uri,
'tv' => $theme_version,
'ta' => $theme_author,
'tau' => $theme_author_uri,
'im' => $im,
'fc' => $fc,
'ec' => $entry_count,
'emc' => self::get_emails_sent(),
'api' => self::get_api_calls(),
'emeta' => $meta_counts['meta'],
'ed' => $meta_counts['details'],
'en' => $meta_counts['notes'],
'lang' => $lang

This data comprises:

* our licence key
* Gravity Forms version
* WordPress core version
* PHP version
* MySQL version
* active plugins
* active theme name, URI, version, author and author URI
* if it is a multisite
* number of active and inactive forms
* number of entries for active forms
* number of emails sent by Gravity Forms
* number of calls made to the Gravity Forms API
* count of details, meta and notes associated with entries
* language of the WordPress install

That’s a lot of data. It’s also being sent in the clear, not using HTTPS.

We had not been made aware that the Gravity Forms plugin would be sending this back to Rocket Genius.

We emailed Rocket Genius twice about this issue, but have received no response.

This is not cool. This sensitive telemetry about our websites is being collected without informing us, and without allowing us to opt-out.

It’s only metadata

“But it’s only telemetry!”, I hear you say. That doesn’t matter; this is a issue that needs to be addressed. GDPR is going to be enforced from May 2018.

GDPR will be an issue for telemetry data for startups and the industry’s biggest companies alike. Suppose, for example, you think, it’s all good, all the data we collect is scrubbed of personally identifiable information (PII). Yeah that’s right, data in the aggregate is OK of course. But what happens when you hit an exception, and ask the user to send a crash report? Suddenly the scrubbed data potentially becomes identifiable, and you’re storing it without knowing it. Triangulation of data, and the almost comical availability of third party datasets, makes it increasingly hard to assume any data is not personally identifiable.

It’s not just the law, it’s more than “You may be liable under GDPR”. It’s about transparent data collection and user respect. I may choose to share *my* data with Rocket Genius. My clients may choose to share their data. Or they may not, in which case, they need to have the option not to share. In fact, it needs to be assumed that they do not want to share unless explicit permission is given. This has to be the default in future in order that any data collected is agreed upon in advance, and that how that data is stored and destroyed is also made clear.

There is currently no opt-out of data collection when you install Gravity Forms; I’ve just tried out the latest Release Candidate (v2.3 RC4) and this is still the case.

This is against WordPress Developer Guidelines.

7. Plugins may not track users without their consent.

In the interest of protecting user privacy, plugins may not contact external servers without explicit and authorized consent.

Some examples of prohibited tracking include:

Automated collection of user data without explicit confirmation from the user.

Plugins should follow WordPress’ privacy guidelines, and users should expect clear treatment – especially when they are paying customers.

No opt-out, no opt-in

This is not just a single-plugin issue. How widespread is surreptitious data collection, in WordPress plugins and themes? It may be done with the best of intentions – to improve user experience – or it may be done to further business aspirations, but either way: the user has to be told and given the option to say “No”.

WordPress itself does a similar level of data collection with no easy opt-out. As of WP 4.9 there is a filter to disable data being sent back to’s API, using the core_version_check_query_args function, and I built a small plugin around this to make it easy for users. But a developer-focussed function isn’t nearly enough.

There is good discussion happening around data privacy in core – – and a proposed roadmap for GDPR compliance – But there’s currently no proposal to add an opt-in for data collection, or a privacy statement to inform admin users when WordPress is installed. This was proposed and closed in a Trac ticket, but even with that, the focus was “How can we collect data to improve WordPress?” rather than “How can we improve transparency in WordPress?”.

WooCommerce almost gets it right. On first activation you’re asked “Allow WooCommerce to collect non-sensitive diagnostic data and usage information.” But it’s pre-ticked and there’s no link to a data collection or privacy policy.

This isn’t good enough – we are developers and users of Open Source software, and should be open about what that software does.

Right now, the only way to know what data your website is sending to 3rd parties is to install a plugin called Snitch, which monitors network connections. Go on, install it – you’ll be surprised at the data your website is sending to someone else.

WordPress and the software built on top of it needs to address this issue, which isn’t about some annoying European law, it’s about respecting your users. Without that, it will be hard for agencies such as mine to honestly recommend solutions which do not respect us and our clients.

Update 28/2/18

I received a reply from Carl Hancock of Rocket Genius on Twitter.

This is missing the point – I have no problem with plugins sending data back in order to improve user experience and prevent websites breaking, but this must be explicit and opt-in. Saying “We’re doing this to help you” is fine as long as a user agrees to it, but not acceptable if a user has no option.