# Problematic IP address fields

**URL:** <https://meta.discourse.org/t/problematic-ip-address-fields/83785>\
**Category:** Feature\
**Tags:** gdpr, privacy\
**Created:** [25.Март.2018 07:06:34 UTC](https://meta.discourse.org/t/problematic-ip-address-fields/83785 "2018-03-25T07:06:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [25.Март.2018 08:14:45 UTC](https://meta.discourse.org/t/problematic-ip-address-fields/83785/2 "2018-03-25T08:14:45Z")

</div>

> [@riking](#):
>
> several places where IP addresses are being accidentally correlated with user IDs

You mean like this?

 ![image](https://global.discourse-cdn.com/meta/original/3X/f/8/f89c4c174143fafaf4f8f946ec163a73506a9297.png)

I am unclear what you mean by “accidental”?

- incoming links are from a remote client that may or may not be logged in, in which case IP is relevant

- searches are from a remote client that may or may not be logged in, in which case IP is relevant

- outgoing links are clicked by a remote client that may or may not be logged in, in which case IP is relevant

I’ll also remind you the definition of bug, which is listed here,

> A bug report means something is broken, preventing normal/typical use of Discourse

and recategorize this.

---

_[View the full topic](https://meta.discourse.org/t/problematic-ip-address-fields/83785)._