# Champs d'adresses IP problématiques **URL:** \ **Category:** Feature\ **Tags:** gdpr, privacy\ **Created:** [Mars 25, 2018, 7:06 UTC](https://meta.discourse.org/t/problematic-ip-address-fields/83785 "2018-03-25T07:06:34Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\ **Post date:** [Mars 25, 2018, 7:06 UTC](https://meta.discourse.org/t/problematic-ip-address-fields/83785/1 "2018-03-25T07:06:34Z")
Continuing the discussion from [Providing data for GDPR](https://meta.discourse.org/t/providing-data-for-gdpr/83595/17): I did a first pass over Discourse’s tables, and I found several places where IP addresses are being accidentally correlated with user IDs. This is toxic data generating liability for Discourse forums. List of problematic IP address fields: - ✅ ❌ incoming\_links: stores timestamped IP address correlated with user ID and an exact post ID, topic ID, and Referer: header Fixed Storage: PR#5826 - ✅ ✅ search\_logs: stores timestamped IP address correlated with user ID and exact search term Fixed Storage, Retention: PR#5851 - ✅ topic\_link\_clicks: stores timestamped IP address correlated with user ID and clicked link Fixed Storage: PR#5852 - ✅ topic\_views: stores timestamped IP address Fixed Storage: PR#5850 - user\_profile\_views: stores timestamped IP address Non-problematic IP address fields: - user\_auth\_tokens, user\_auth\_token\_logs: stores timestamped IP address correlated with user ID and device identifier - Data purged periodically, but ⚠ there should be a conditional notice in the Privacy Policy if verbose auth token logs are enabled - screened\_email, screened\_url, screened\_ip\_addresses: Only created when a user is banned for being a spammer. - api\_keys: List of IPs inputted by admin. Filing this as a privacy-bug. --- _[View the full topic](https://meta.discourse.org/t/problematic-ip-address-fields/83785)._