10+
April 11, 2025
September 29, 2023
Anonymize personal data (PII) in WordPress databases for development and testing. Comply with rules and regulations, prevent data leaks.
WordPress database are often copied from production to test and development environments. This ensures a representative WordPress installation for productive programming and testing.
However, most production databases contain Personal Identifiable Information, so you need to have effective security controls in place to comply with rules and regulations such as EU GDPR.
This plugin supports you with complying with rules and regulations and prevent data leaks originating from dev/test WordPress installations, while retaining the database structure and integrity.
You can create rules to skip specific records that contain PII of admins, developers and testers. This prevents locking yourself out of WordPress and ensures that you and test users can perform their tasks while personal data from customers and other users is anonymized.
The manual is published on the DIM Plugins web site.
Learn about supported data types, special functions to transform data hidden in meta data, JSON or serialized arrays and all possible ways to anonymize personal data.
Upgrade to unlock additional features.
Yes, it does. Most transformations require that the table has a primary key of one column, except the all-purpose transformations One value and Empty. These can be used on any table.
Transformations may have additional requirements with regard to the column length and type.
The plugin has special features to process meta data, JSON and serialized arrays stored in WordPress database tables.
Most lists originate from Chat GPT, generated from a US / European perspective.
The non-existing IBANs originate from Random Iban Generator.
No. In this Free version, it is not possible to customize this data. You need the Enterprise edition to do that.
In this Free version, it is not possible to export or import transformation rules.
In this Free version, you have to write those rules yourself. It’s not complicated, but it can take some time. The Enterprise edition has built-in rules for common plugins (see features above).
These are stored in the WordPress options table. If you overwrite the database with a new copy, the rules will be lost.
Yes. As of version 2.0, this plugin can be used on live sites (production environments).
It will anonymize a copy of the production database as a file that you can download.
You can then import this file into another (dev / test) environment.
On dev/test environments, this plugin will anonymize the database in place.
You should never configure the plugin to anonymize data directly in a production database.
No, most certainly not. This plugin can support you and your organization in becoming or staying compliant.
It remains the responsibility of you and your organization to configure this plugin, to run it and to delete any back-ups that remain.
Next to that, there are many more aspects to data protection compliancy than PII anonymization of non-production databases.