Title: webdessie's Replies | WordPress.org

---

# webdessie

  [  ](https://wordpress.org/support/users/webdessie/)

 *   [Profile](https://wordpress.org/support/users/webdessie/)
 *   [Topics Started](https://wordpress.org/support/users/webdessie/topics/)
 *   [Replies Created](https://wordpress.org/support/users/webdessie/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/webdessie/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/webdessie/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/webdessie/engagements/)
 *   [Favorites](https://wordpress.org/support/users/webdessie/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [How to check a plugin for data breach](https://wordpress.org/support/topic/how-to-check-a-plugin-for-data-breach/)
 *  Thread Starter [webdessie](https://wordpress.org/support/users/webdessie/)
 * (@webdessie)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/how-to-check-a-plugin-for-data-breach/#post-10171673)
 * It would be great if WordPress.org had a GDPR Compliant “stamp” for each plugin
   that the developer could point in “YES” / “NO” and then provide what data is 
   collected and where they are sent.
 * I guess that plugin developers who inform ind the Details about the plugin will
   have much more success among european users.
 * Anyway, what should I look for in the code to see if it calls another plugin,
   uses userdata or communicates data somewhere?

Viewing 1 replies (of 1 total)