{"id":4059,"date":"2018-05-08T11:44:07","date_gmt":"2018-05-08T18:44:07","guid":{"rendered":"https:\/\/scottdeluzio.com\/?p=4059"},"modified":"2018-05-17T13:03:04","modified_gmt":"2018-05-17T20:03:04","slug":"gdpr-for-wordpress-plugin-and-theme-developers","status":"publish","type":"post","link":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/","title":{"rendered":"GDPR For WordPress Plugin and Theme Developers"},"content":{"rendered":"

Edit: Updated on 5\/11\/2018 to include adding privacy policy content.<\/em>
\nBy now, I’m assuming most people are at least aware of what GDPR is. If not, go check out GDPR WP’s site<\/a>, or do a quick Google search so you’re familiar with it. Basically, the upcoming enforcement of EU’s privacy laws will become enforceable on May 25, 2018 and it affects all businesses who collect data on European residents. Chances are if your plugin or theme collects personal data, your users will need<\/em> to have GDPR compliance features incorporated.<\/p>\n

Two of the main issues for WordPress site owners are (1) how to show personal data to your site’s users, and (2) how to erase their data from your site.<\/p>\n

WordPress core will have a number of new features that are of particular interest to Plugin and Theme developers. New hooks will allow you to add data from your plugin or theme to the WordPress generated export file, as well as delete data from your plugin or theme upon request.<\/p>\n

Why Should Developers Work With These Hooks?<\/h2>\n

WordPress site owners are\u00a0not<\/em> going to want to be burdened with dozens of different ways to export data from their site. Imagine if every theme or plugin developer decided to come up with their own export tools? It would be madness. There’s no way that your typical site owner will know where to look for all the personal data they have stored on their site.<\/p>\n

By working with the hooks that will be provided in WordPress core (version 4.9.6 or later), you are making life 100 times easier for your plugin or theme’s users.<\/p>\n

How to Include Data in the Export<\/h2>\n

First of all, we will need to register your exporter. WordPress has a new filter\u00a0wp_privacy_personal_data_exporters<\/em> that we will use to register the exporter.<\/p>\n

Register Export Function<\/h3>\n
\r\nfunction register_my_plugin_exporter( $exporters ) {\r\n\t$exporters['my-plugin-exporter'] = array(\r\n\t\t'exporter_friendly_name'\t=> __( 'My Plugin Exporter Name' ),\r\n\t\t'callback'\t\t\t=> 'my_plugin_exporter',\r\n\t);\r\n\treturn $exporters;\r\n}\r\n\r\nadd_filter( 'wp_privacy_personal_data_exporters', 'register_my_plugin_exporter', 10 );\r\n<\/pre>\n
This function adds to the array of $exporters<\/em> that is run when processing your export request. The exporter_friendly_name<\/em> is simply a friendly name that describes your export. This is used by error messages if there are unexpected responses from your exporter. It’s best to use the name of your plugin and some other descriptive information (i.e. My Plugin Order Exporter, My Plugin Contact Details Exporter, etc.) The callback<\/em> is the function that will run to gather the data needed for this export.<\/p>\n
We need to pass two variables to the function. First is the email address of the individual who is requesting their data, which is self-explanitory. The second is the page of personal data for this exporter, which begins at 1.<\/p>\n
We pass a page number to the function so that it can iterate through the function several times. Inside the function itself, we’ll define a $number<\/em> variable that will tell the function to only process $number<\/em> records at a time because we don’t want it to time out.<\/p>\n
Export Function<\/h3>\n
This is an example of the export function from wp-includes\/comment.php<\/em>, which shows how WordPress will export comments.<\/p>\n
You can modify this function to round up all the data in your plugin or theme.<\/p>\n
\r\nfunction my_plugin_exporter( $email_address, $page = 1 ) {\r\n\t\/\/ Limit us to 500 at a time to avoid timing out.\r\n\t$number = 500;\r\n\t$page   = (int) $page;\r\n\r\n\t$data_to_export = array();\r\n\t\/\/ In this example, we're getting comments, but you can use this function to get any data your plugin collects.\r\n\t$comments = get_comments(\r\n\t\tarray(\r\n\t\t\t'author_email'              => $email_address,\r\n\t\t\t'number'                    => $number, \/\/ The max number of comments to retrieve.\r\n\t\t\t'paged'                     => $page, \/\/ The page number of this iteration of the function. $page == 1 returns comments 1-500, $page == 2 returns comments 501-1000, etc.\r\n\t\t\t'order_by'                  => 'comment_ID',\r\n\t\t\t'order'                     => 'ASC',\r\n\t\t\t'update_comment_meta_cache' => false,\r\n\t\t)\r\n\t);\r\n\r\n\t$comment_prop_to_export = array(\r\n\t\t'comment_author'       => __( 'Comment Author' ),\r\n\t\t'comment_author_email' => __( 'Comment Author Email' ),\r\n\t\t'comment_author_url'   => __( 'Comment Author URL' ),\r\n\t\t'comment_author_IP'    => __( 'Comment Author IP' ),\r\n\t\t'comment_agent'        => __( 'Comment Author User Agent' ),\r\n\t\t'comment_date'         => __( 'Comment Date' ),\r\n\t\t'comment_content'      => __( 'Comment Content' ),\r\n\t\t'comment_link'         => __( 'Comment URL' ),\r\n\t);\r\n\r\n\tforeach ( (array) $comments as $comment ) {\r\n\t\t$comment_data_to_export = array();\r\n\r\n\t\tforeach ( $comment_prop_to_export as $key => $name ) {\r\n\t\t\t$value = '';\r\n\r\n\t\t\tswitch ( $key ) {\r\n\t\t\t\tcase 'comment_author':\r\n\t\t\t\tcase 'comment_author_email':\r\n\t\t\t\tcase 'comment_author_url':\r\n\t\t\t\tcase 'comment_author_IP':\r\n\t\t\t\tcase 'comment_agent':\r\n\t\t\t\tcase 'comment_date':\r\n\t\t\t\t\t$value = $comment->{$key};\r\n\t\t\t\t\tbreak;\r\n\r\n\t\t\t\tcase 'comment_content':\r\n\t\t\t\t\t$value = get_comment_text( $comment->comment_ID );\r\n\t\t\t\t\tbreak;\r\n\r\n\t\t\t\tcase 'comment_link':\r\n\t\t\t\t\t$value = get_comment_link( $comment->comment_ID );\r\n\t\t\t\t\t$value = '' . $value . '<\/a>';\r\n\t\t\t\t\tbreak;\r\n\t\t\t}\r\n\r\n\t\t\tif ( ! empty( $value ) ) {\r\n\t\t\t\t$comment_data_to_export[] = array(\r\n\t\t\t\t\t'name'  => $name,\r\n\t\t\t\t\t'value' => $value,\r\n\t\t\t\t);\r\n\t\t\t}\r\n\t\t}\r\n\r\n\t\t$data_to_export[] = array(\r\n\t\t\t'group_id'    => 'comments', \/\/ An ID to identify this particular group of information.\r\n\t\t\t'group_label' => __( 'Comments' ), \/\/ A translatable string to label this group of information.\r\n\t\t\t'item_id'     => \"comment-{$comment->comment_ID}\", \/\/ The item ID of what we're exporting\r\n\t\t\t'data'        => $comment_data_to_export, \/\/ The personal data that should be exported\r\n\t\t);\r\n\t}\r\n\t\/\/ $done identifies whether or not the number of $comments is less than $number. If it is, all comments have been processed and we're done.\r\n\t$done = count( $comments ) < $number;\r\n\t\/\/ The function should return an array with the (array)'data' to be exported and whether or not we're (bool)'done'\r\n\treturn array(\r\n\t\t'data' => $data_to_export,\r\n\t\t'done' => $done,\r\n\t);\r\n}<\/pre>\n
I’ve added some inline comments to the function, which should explain the important parts of the function.<\/p>\n
Including Data to Erase<\/h2>\n
We need to figure out what data we will erase. Fortunately, it’s probably going to be the same data from the export function, because we don’t want to erase data that the user hasn’t seen. So once you have the export function working the rest is pretty straightforward.<\/p>\n
The biggest difference between the export and the eraser functions is what happens to the data. In the export function, we don’t modify, or remove data since we are just exporting it. In the eraser function, we’ll actually be deleting or anonymizing the data.<\/p>\n
Like the export function, we need to register the eraser function. This time we will use the new\u00a0wp_privacy_personal_data_erasers<\/em> filter.<\/p>\n
Register Eraser Function<\/h3>\n
\r\nfunction register_my_plugin_personal_data_eraser( $erasers ) {\r\n\t$erasers['my-plugin-eraser'] = array(\r\n\t\t'eraser_friendly_name' => __( 'WordPress Comments' ),\r\n\t\t'callback'             => 'my_plugin_personal_data_eraser',\r\n\t);\r\n\r\n\treturn $erasers;\r\n}\r\nadd_filter( 'wp_privacy_personal_data_erasers', 'register_my_plugin_personal_data_eraser', 10 );\r\n<\/pre>\n
Same idea as registering the export function so I won’t reiterate what each part is doing.<\/p>\n
Eraser Function<\/h3>\n
Again, we need to pass the email address and the page to the function. I’ll continue using the comment eraser function found in wp-includes\/comment.php<\/em>.<\/p>\n
\r\nfunction my_plugin_personal_data_eraser( $email_address, $page = 1 ) {\r\n\tglobal $wpdb;\r\n\r\n\tif ( empty( $email_address ) ) {\r\n\t\treturn array(\r\n\t\t\t'items_removed'  => false,\r\n\t\t\t'items_retained' => false,\r\n\t\t\t'messages'       => array(),\r\n\t\t\t'done'           => true,\r\n\t\t);\r\n\t}\r\n\r\n\t\/\/ Limit us to 500 comments at a time to avoid timing out.\r\n\t$number         = 500;\r\n\t\/\/ Get us on the right page of comments\r\n\t$page           = (int) $page;\r\n\t$items_removed  = false;\r\n\t$items_retained = false;\r\n\r\n\t$comments = get_comments(\r\n\t\tarray(\r\n\t\t\t'author_email'       => $email_address,\r\n\t\t\t'number'             => $number,\r\n\t\t\t'paged'              => $page,\r\n\t\t\t'order_by'           => 'comment_ID',\r\n\t\t\t'order'              => 'ASC',\r\n\t\t\t'include_unapproved' => true,\r\n\t\t)\r\n\t);\r\n\r\n\t$anon_author = __( 'Anonymous' );\r\n\t$messages    = array();\r\n\t\/\/ In this case WordPress isn't deleting comments, but instead is anonymizing it.\r\n\t\/\/ Your plugin could do something similar, or delete the data altogether.\r\n\tforeach ( (array) $comments as $comment ) {\r\n\t\t$anonymized_comment                         = array();\r\n\t\t$anonymized_comment['comment_agent']        = '';\r\n\t\t$anonymized_comment['comment_author']       = $anon_author;\r\n\t\t$anonymized_comment['comment_author_email'] = wp_privacy_anonymize_data( 'email', $comment->comment_author_email );\r\n\t\t$anonymized_comment['comment_author_IP']    = wp_privacy_anonymize_data( 'ip', $comment->comment_author_IP );\r\n\t\t$anonymized_comment['comment_author_url']   = wp_privacy_anonymize_data( 'url', $comment->comment_author_url );\r\n\t\t$anonymized_comment['user_id']              = 0;\r\n\r\n\t\t$comment_id = (int) $comment->comment_ID;\r\n\r\n\t\t\/**\r\n\t\t * Filters whether to anonymize the comment.\r\n\t\t *\r\n\t\t * @since 4.9.6\r\n\t\t *\r\n\t\t * @param bool|string                    Whether to apply the comment anonymization (bool).\r\n\t\t *                                       Custom prevention message (string). Default true.\r\n\t\t * @param WP_Comment $comment            WP_Comment object.\r\n\t\t * @param array      $anonymized_comment Anonymized comment data.\r\n\t\t *\/\r\n\t\t$anon_message = apply_filters( 'wp_anonymize_comment', true, $comment, $anonymized_comment ); \/\/ Default is true to anonymize comments, but filter could change this behavior to false\r\n\r\n\t\tif ( true !== $anon_message ) {\r\n\t\t\tif ( $anon_message && is_string( $anon_message ) ) {\r\n\t\t\t\t$messages[] = esc_html( $anon_message );\r\n\t\t\t} else {\r\n\t\t\t\t\/* translators: %d: Comment ID *\/\r\n\t\t\t\t$messages[] = sprintf( __( 'Comment %d contains personal data but could not be anonymized.' ), $comment_id );\r\n\t\t\t}\r\n\r\n\t\t\t$items_retained = true;\r\n\r\n\t\t\tcontinue;\r\n\t\t}\r\n\r\n\t\t$args = array(\r\n\t\t\t'comment_ID' => $comment_id,\r\n\t\t);\r\n\r\n\t\t$updated = $wpdb->update( $wpdb->comments, $anonymized_comment, $args );\r\n\r\n\t\tif ( $updated ) {\r\n\t\t\t$items_removed = true;\r\n\t\t\tclean_comment_cache( $comment_id );\r\n\t\t} else {\r\n\t\t\t$items_retained = true;\r\n\t\t}\r\n\t}\r\n\t\/\/ $done identifies whether or not the number of $comments is less than $number. If it is, all comments have been processed and we're done.\r\n\t$done = count( $comments ) < $number;\r\n\t\/\/ The function should return an array with the following:\r\n\t\/\/  (bool) 'items_removed' - were items removed \r\n\t\/\/  (bool) 'items_retained' - were items retained and anonymized\r\n\t\/\/  (array) 'messages' - error messages related to this erasure request\r\n\t\/\/  (bool) 'done' - are we done processing data or is there more to be processed\r\n\treturn array(\r\n\t\t'items_removed'  => $items_removed,\r\n\t\t'items_retained' => $items_retained,\r\n\t\t'messages'       => $messages,\r\n\t\t'done'           => $done,\r\n\t);\r\n}\r\n<\/pre>\n
Adding Privacy Policy Content<\/h2>\n
This feature is not very well documented, at least not as far as I’ve been able to find. Maybe someone else knows of a guide that I’ve missed – if so please add it to the comments.<\/p>\n
I literally dug through WooCommerce’s beta version’s code to figure out how to add privacy policy content for your plugin or theme.<\/p>\n
There is a function wp_add_privacy_policy_content()<\/em> that you’ll use to add your content. I’m assuming that they are using a function like this instead of a filter so that other plugins don’t accidentally (or intentionally) remove another plugin’s privacy policy content.<\/p>\n
The function takes two parameters: (1) your plugin’s name, and (2) the content of your privacy policy content.<\/p>\n
See final thoughts section below for my opinion on this.<\/em><\/p>\n
Here’s how the function works:<\/p>\n
\r\nfunction my_plugin_add_privacy_policy_content(){\r\n\tif( !function_exists( 'wp_add_privacy_policy_content' ) ) {\r\n\t\treturn;\r\n\t}\r\n\t$content = wp_kses_post( wpautop( __( 'Your privacy policy content here', 'my-plugin' ) ) );\r\n\twp_add_privacy_policy_content( 'My Plugin', $content );\r\n}\r\n<\/pre>\n
Final Thoughts<\/h2>\n
Adding a privacy policy statement is a huge<\/em> responsibility to place on plugin and theme developers. I know I’m not a lawyer, so I don’t know all the intricacies of the law and what content does and does not need to be included. I also don’t have the budget to hire a lawyer to draft something that will cover every customer’s use case. With that said, there will still be people who blindly copy and paste the suggested text and use it as the basis of their own policy.<\/p>\n
To address this, I would recommend that any plugin or theme developers not<\/em> write content that could be put in the privacy policy as-is. Instead, provide guidelines as to what data your plugin collects, why it collects that data, where it is stored, and for how long your plugin stores it (i.e. conditions that would cause the data to be removed).<\/p>\n
Something like “XYZ Form Plugin collects data that your users submit through our forms and stores it in the database. Our plugin collects this data to facilitate communication between the site visitors and site administrators. The data is stored in your website’s database and will remain there until it is deleted. Please update your privacy policy to reflect this data storage procedure.”<\/em> Or something along those lines.<\/p>\n
WordPress 4.9.6 is scheduled to be released on Tuesday, May 15th<\/del> 17th<\/a>. That’s just 10<\/del> 8 days before the GDPR regulations become enforceable so there isn’t much time left.<\/p>\n
If you are a plugin or theme developer and your product collects personal data, you can’t wait until May 15th<\/del> 17th. Start working on how your plugin will handle data today!<\/p>\n
You can download WordPress 4.9.6 beta 1 here<\/a> or use the WordPress Beta Tester Plugin<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Edit: Updated on 5\/11\/2018 to include adding privacy policy content. By now, I’m assuming most people are at least aware of what GDPR is. If not, go check out GDPR WP’s site, or do a quick Google search so you’re familiar with it. Basically, the upcoming enforcement of EU’s privacy laws will become enforceable on […]<\/p>\n","protected":false},"author":2,"featured_media":4060,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[1],"tags":[],"series":[],"yoast_head":"\nGDPR For WordPress Plugin and Theme Developers - Scott DeLuzio<\/title>\n<meta name=\"description\" content=\"This GDPR for WordPress Plugin and Theme Developers guide will help developers include personal data collected by their plugin or theme in the WordPress export or eraser functions coming in WordPress 4.9.6.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"GDPR For WordPress Plugin and Theme Developers - Scott DeLuzio\" \/>\n<meta property=\"og:description\" content=\"This GDPR for WordPress Plugin and Theme Developers guide will help developers include personal data collected by their plugin or theme in the WordPress export or eraser functions coming in WordPress 4.9.6.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/\" \/>\n<meta property=\"og:site_name\" content=\"Scott DeLuzio\" \/>\n<meta property=\"article:published_time\" content=\"2018-05-08T18:44:07+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-05-17T20:03:04+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"512\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Scott DeLuzio\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@scottdeluzio\" \/>\n<meta name=\"twitter:site\" content=\"@scottdeluzio\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Scott DeLuzio\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/\",\"url\":\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/\",\"name\":\"GDPR For WordPress Plugin and Theme Developers - Scott DeLuzio\",\"isPartOf\":{\"@id\":\"https:\/\/scottdeluzio.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg\",\"datePublished\":\"2018-05-08T18:44:07+00:00\",\"dateModified\":\"2018-05-17T20:03:04+00:00\",\"author\":{\"@id\":\"https:\/\/scottdeluzio.com\/#\/schema\/person\/a0578da297e094ef0d581122331b5360\"},\"description\":\"This GDPR for WordPress Plugin and Theme Developers guide will help developers include personal data collected by their plugin or theme in the WordPress export or eraser functions coming in WordPress 4.9.6.\",\"breadcrumb\":{\"@id\":\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#primaryimage\",\"url\":\"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg\",\"contentUrl\":\"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg\",\"width\":1024,\"height\":512,\"caption\":\"GDPR For WordPress Plugin and Theme Developers\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/scottdeluzio.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"GDPR For WordPress Plugin and Theme Developers\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/scottdeluzio.com\/#website\",\"url\":\"https:\/\/scottdeluzio.com\/\",\"name\":\"Scott DeLuzio\",\"description\":\"WordPress Development Tutorials\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/scottdeluzio.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/scottdeluzio.com\/#\/schema\/person\/a0578da297e094ef0d581122331b5360\",\"name\":\"Scott DeLuzio\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/scottdeluzio.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/1aab25f8a9570a61b20078bcb4ab4588?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/1aab25f8a9570a61b20078bcb4ab4588?s=96&d=mm&r=g\",\"caption\":\"Scott DeLuzio\"},\"sameAs\":[\"https:\/\/twitter.com\/scottdeluzio\"],\"url\":\"https:\/\/scottdeluzio.com\/author\/scottdeluzio82\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"GDPR For WordPress Plugin and Theme Developers - Scott DeLuzio","description":"This GDPR for WordPress Plugin and Theme Developers guide will help developers include personal data collected by their plugin or theme in the WordPress export or eraser functions coming in WordPress 4.9.6.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/","og_locale":"en_US","og_type":"article","og_title":"GDPR For WordPress Plugin and Theme Developers - Scott DeLuzio","og_description":"This GDPR for WordPress Plugin and Theme Developers guide will help developers include personal data collected by their plugin or theme in the WordPress export or eraser functions coming in WordPress 4.9.6.","og_url":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/","og_site_name":"Scott DeLuzio","article_published_time":"2018-05-08T18:44:07+00:00","article_modified_time":"2018-05-17T20:03:04+00:00","og_image":[{"width":1024,"height":512,"url":"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg","type":"image\/jpeg"}],"author":"Scott DeLuzio","twitter_card":"summary_large_image","twitter_creator":"@scottdeluzio","twitter_site":"@scottdeluzio","twitter_misc":{"Written by":"Scott DeLuzio","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/","url":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/","name":"GDPR For WordPress Plugin and Theme Developers - Scott DeLuzio","isPartOf":{"@id":"https:\/\/scottdeluzio.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#primaryimage"},"image":{"@id":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#primaryimage"},"thumbnailUrl":"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg","datePublished":"2018-05-08T18:44:07+00:00","dateModified":"2018-05-17T20:03:04+00:00","author":{"@id":"https:\/\/scottdeluzio.com\/#\/schema\/person\/a0578da297e094ef0d581122331b5360"},"description":"This GDPR for WordPress Plugin and Theme Developers guide will help developers include personal data collected by their plugin or theme in the WordPress export or eraser functions coming in WordPress 4.9.6.","breadcrumb":{"@id":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#primaryimage","url":"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg","contentUrl":"https:\/\/scottdeluzio.com\/wp-content\/uploads\/2018\/05\/gdpr-plugin-theme-devs.jpg","width":1024,"height":512,"caption":"GDPR For WordPress Plugin and Theme Developers"},{"@type":"BreadcrumbList","@id":"https:\/\/scottdeluzio.com\/gdpr-for-wordpress-plugin-and-theme-developers\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/scottdeluzio.com\/"},{"@type":"ListItem","position":2,"name":"GDPR For WordPress Plugin and Theme Developers"}]},{"@type":"WebSite","@id":"https:\/\/scottdeluzio.com\/#website","url":"https:\/\/scottdeluzio.com\/","name":"Scott DeLuzio","description":"WordPress Development Tutorials","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/scottdeluzio.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/scottdeluzio.com\/#\/schema\/person\/a0578da297e094ef0d581122331b5360","name":"Scott DeLuzio","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/scottdeluzio.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/1aab25f8a9570a61b20078bcb4ab4588?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1aab25f8a9570a61b20078bcb4ab4588?s=96&d=mm&r=g","caption":"Scott DeLuzio"},"sameAs":["https:\/\/twitter.com\/scottdeluzio"],"url":"https:\/\/scottdeluzio.com\/author\/scottdeluzio82\/"}]}},"_links":{"self":[{"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/posts\/4059"}],"collection":[{"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/comments?post=4059"}],"version-history":[{"count":0,"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/posts\/4059\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/media\/4060"}],"wp:attachment":[{"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/media?parent=4059"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/categories?post=4059"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/tags?post=4059"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/scottdeluzio.com\/wp-json\/wp\/v2\/series?post=4059"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}