maxime-rainville
commented
1 year ago Off the top of my head, I don't remember us pondering this question. There is a task to periodically purge old sessions ... however I'm not sure to what degree this mitigates GDPR concerns.
This modules is somewhat CMS user focus. We didn't look at how this would impact users, that don't have back end access.
If your use case requires users to register to gain access to front end features, you probably have broader GDPR concerns that go beyond just logging IP addresses.
Our general approach has been to put compliance with local laws back on project owners ... which is admittedly unsatisfying. At the same time we are not lawyers and we can't possibly foresee all the possible interactions of use cases.
Steps we could take:
- Provide explicit documentation to let project owners know about the IP address tracking implication of using this module,
- Provide some alternative middleware that allows users without CMS access to bypass the session manager logic
- Use a one way hashing function to hash the IP address before we store it in the DB. That might still be problematic because it allows us to finger print the user ... which is the entire point of storing the IP in the first place.
lekoala
GuySartorelli
Because we're storing the IP address of a logged in member (not just CMS members), has GDPR compliance been considered? I would have thought we should have a warning somewhere about this new functionality, maybe even just in the changelogs so people can update their privacy policy accordingly...
PRs