66

Right now as far as I know, SE stores the IP addresses used to access any SE site forever. Every moderator or employee with moderator powers can see a list of every IP address a user ever accessed the site from.

IP addresses are considered personal data under the GDPR, and I think it is worth discussing how long they should be stored. They are often considered not particularly sensitive information, and in many cases they aren't. An IP address from a mobile phone provider won't tell much about you, and unless you can access or subpoena the provider, knowing the IP address doesn't really reveal anything. But there are also many different cases, and in some cases IP addresses can reveal a lot. If you access SE from a company computer, the IP address could identify which company you work for. They also can give a rough location of where you live and where you travel.

There is a legitimate need for SE to store IP addresses and to make them available to moderators. But keeping all the information indefinitely is a bit harder to justify. I could also imagine treating "well-behaved" users differently here than users suspended for rule violations that involved sock puppets. The curious thing here is that the users that get the most privacy are actually spammers, as their accounts are destroyed entirely.

Is it really necessary to store IP addresses forever, or would a shorter duration be enough? Alternatively I could imagine simply restricting the visibility of historical IP addresses, as there isn't really a need to look them up on their own.

16
  • 8
    I'd be quite interested in the entire data retention schedule. There might be a legitimate interest to store data past account deletion (for example), but the principle of storage limitation still requests standard retention periods.# Commented Aug 5, 2020 at 20:26
  • 9
    @benisuǝqbackwards I'm reasonably sure that there isn't a data retention schedule at all. Data for deleted account is mostly inaccessible to mods, but the underlying data is never deleted (with the exception of underage users). You can see a lot of the stuff that SE tracks in the GDPR dump, if you request one. Commented Aug 5, 2020 at 20:41
  • IP addresses can be extremely useful in catching sockpuppetry. If a clever puppeteer learns to use different IPs for different accounts, but at some point slipped up and had both on the same IP, should the system discard that information just because it was a while ago? Commented Aug 8, 2020 at 15:06
  • 3
    @Randal'Thor X-ref is less problematic than the ability to view the entire IP history on its own, and they could have different limits. I also think that at times there's a bit too much focus on detecting socks when the actual goal is to stop certain behaviour. Socks are a tool for certain misbehaviour, but they're not a problem on their own. And while IP addresses can be very useful, they are not the only and certainly not the best tool. Commented Aug 8, 2020 at 16:19
  • 2
    Since you mention the GPDR: Only as long as technically needed, and not longer. Seven days is acceptable. I suggest the company consults a European expert. I suggest to blank the lower 72 bits (for IPv6 addresses) or 8 bits (for IPv4 addresses) as soon as possible. Commented Aug 12, 2020 at 22:36
  • 2
    For reference, Wikipedia's CheckUser feature only obtains data from the last 90 days, but archives data if it's obtained. Commented Aug 22, 2020 at 4:48
  • @MartinSchröder that entirely depends on what it's being used for. I can't think of many cases (beyond basic operation of the internet) where seven days is long enough.
    – OrangeDog
    Commented Sep 1, 2020 at 14:51
  • @OrangeDog And I believe in Privacy by Design and that SE will have to comply with the GDPR. And that means deleting the full IP as soon as possible. Commented Sep 1, 2020 at 16:45
  • 1
    @SonictheMaskedWerehog: That's if you're logged in. If you edit while logged out, then they keep and publicly display your IP address forever.
    – Kevin
    Commented Sep 1, 2020 at 17:21
  • @MartinSchröder no it doesn't. It means deleting it as soon as it's not technically needed.
    – OrangeDog
    Commented Sep 1, 2020 at 17:22
  • A couple of thoughts off-topic. As SE is a growing network, how do we justify the need to retain the IPs forever, especially when knowing that it'll grow exponentially over time and there's particularly no need to retain a humongous amount of stale data in the DB? Added to the fact that many users will have a dynamic IP, the record of which is discarded by the ISP in about a few years. Commented Oct 11, 2020 at 18:40
  • I've removed both the [feature-request] and [status-planned] tags from this post, as it appears to be exclusively a discussion. If there is a specific feature request, please feel free to make a new question, or add it here (provided that it does not meaningfully alter the discussion here).
    – Slate StaffMod
    Commented Aug 13 at 21:29
  • @Slate this post is too important to remove all the status tags and just leave it as a discussion. It's about privacy policy and user data protection (as the staff answer below says framing it as GDPR) and a for how long the company retains user IPs. So whatever the status tag, some must apply because it's difficult to get good traction on privacy posts and this post got it and thus deserves a company answer.
    – bad_coder
    Commented Aug 15 at 2:26
  • 1
    @bad_coder If an action on the part of staff is needed here, then I would recommend clarifying what kind of staff input would be helpful and flagging for [status-review] to be added. As of right now, it's definitely a discussion, and one that already has a staff response at that.
    – Slate StaffMod
    Commented Aug 15 at 13:40
  • 1
    @Slate It might have a response, it doesn't have an answer. But someone else can ask directly about the retention policy if they want to, or make a feature request to actually limit the retention of this data. I intentionally made this one a discussion, to gauge the reaction by the community a bit. Commented Aug 15 at 18:55

3 Answers 3

10
+500

I've thought about this for a while - and perhaps its worth reframing the question in terms of what sort of information we need, and how this information is best stored, and shared in a way that meets both privacy, and the operational requirements of both mods and the folks who run the site.

TLDR: Its worth considering alternatives to exposing IPs to mods.

As mods we don't actually need access to IPs - If we had a way to reliably, as opposed to semi reliably, ascertain that a certain a user is from the same rough geographical region or ASN, did a reverse DNS look up on the IP. We have a specific, on demand took for Reverse DNS lookup and geo-ip but it sometimes fails.

Fundamentally we need to know if user A and B are linked in some way, and be able to cross reference them

It would also be telling if a user in good standing suddenly went bad, and they suddenly switched locations - which might indicate an account compromise. This might happen after a period of time, especially if the account was abandoned.

Likewise knowing that a certain user shares an ISP/network range (and fuzzy searching on non identical/similar IPs would be nice!).

More or less, for us not to need to store/look up IPs - we'd need the functionality to store/look up what we really need: The relationships between accounts .

So any replacement would be some way to look up relationships between users in terms of 'where' they are. We have part of this, though its IP based at the moment.

I'll leave it to folks to decide if a more general/abstracted way to keep track of users than IP is "good enough"

If we had this, working completely reliably (and the SE reverse look up tool can be a bit... janky) I suspect mods might have almost no need for IPs.

I can't speak for the needs of the company - but I'd think the 'right' approach would look into where specific IP is used, and how-if it can be likewise aggregated in some forms that meets the requirements they have. I'd suspect that there is/ought to be pretty robust tracking of people looking up PII and various safeguards. but I can't really comment on them.

So practically - its hard to decide what's the right amount of time , but its worth exploring alternatives to storing or exposing IPs as another way to do it.

6

Thanks for pointing this out, this is a great question. Our moderators are very technical, and one benefit of that is we can always appreciate you to bring these things up as they come to your attention. We can’t go too deeply into how we store, and our plans around storing IPs due to security reasons. That being said, one big project we have underway across the engineering organization is a data audit specifically around GDPR compliance. The length of time we store IPs is one of the things on a long list of the things we plan on looking into. We're always thinking about our data retention policy, and ensuring we’re thoughtful about GDPR, user safety, and customer security is a priority.

1
  • 5
    What is the actual retention policy right now? When I looked at a GDPR dump of my SE activity a while ago it seems like all information ist stored indefinitely, and there is no deletion of historical interactions at all. Commented May 7, 2021 at 14:53
-18

I'm not sure whether the GDPR as a european regulation is applicable to stackexchange or stackoverflow since the webservers are located in USA and the DB-Server in Canada. Using this service you should be aware that everything you ask resp. post is transmitted into the USA. The privacy notice says:

How long will we use your personal data?

We will keep your personal data only for as long as is necessary for the purposes set out in this privacy notice and to fulfill our legal obligations. We will not keep more data than we need. While you remain a user of the Public Network, we will retain your data in order to keep providing services to you.

We are required to keep some basic information about our customers for a longer period in accordance with applicable tax laws. In some circumstances you can ask us to delete your data.

Furthermore the privacy note tells specifically about the purposes and taht you can ask for your data stored here and also revoke your approval to use your data.

So, in general, if you use this service, you agree that your data is stored according to the privacy note. If you don't want that, don't use it.

2
  • 24
    GDPR applies to European citizens. US companies must follow it for their European users, or they are not allowed to have any.
    – OrangeDog
    Commented Sep 4, 2020 at 11:51
  • 2
    @OrangeDog Actually GDPR applies to anyone in the EU territory -- so SE must apply it to e.g. a US citizen over here on holiday. Location is what matters, not citizenship. Commented Sep 18, 2020 at 12:43

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .