Page MenuHomePhabricator

Don't store IP addresses in content sources
ClosedPublic

Authored by epriestley on Oct 21 2015, 7:36 PM.
Tags
None
Referenced Files
F15434735: D14315.id34557.diff
Tue, Mar 25, 5:04 AM
F15419536: D14315.id34558.diff
Fri, Mar 21, 6:50 AM
F15388157: D14315.id34557.diff
Sat, Mar 15, 3:23 AM
F15379943: D14315.id.diff
Fri, Mar 14, 12:29 AM
F15344954: D14315.id34557.diff
Mon, Mar 10, 7:38 AM
F15332747: D14315.diff
Fri, Mar 7, 7:54 PM
F15317582: D14315.id34557.diff
Thu, Mar 6, 7:40 PM
Unknown Object (File)
Feb 14 2025, 3:47 AM
Subscribers
None

Details

Reviewers
chad
Commits
Restricted Diffusion Commit
rP4afeebe83489: Don't store IP addresses in content sources
Summary

We don't use these for anything, we're inconsistent about recording them, and there's some mild interaction with privacy concerns and data retention. Every other log we store any kind of information in can be given a custom retention policy after recent GC changes.

If we did put this back eventually it would probably be better to store a session identifier anyway, since that's more granular and more detailed.

You can fetch this info out of access logs anyway, too.

Test Plan

Left a couple of comments.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Don't store IP addresses in content sources.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Oct 21 2015, 7:37 PM
This revision was automatically updated to reflect the committed changes.