-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define privacy policy #5
Comments
Is this a prerequisite for toltec-dev/toltec#15? |
I think it is. I’ll add it to the milestone. Thanks! |
You could probably use fluentd to redirect the logs into some database. From there it would be easier to auto-delete or not add the ip at all to a db. Here is a fluentd.conf i made and used: https://gist.github.com/LinusCDE/9ba8b79f115272dcbe2371cacb815288 There is also a docker-compose you can use to spin up a db and have a simple interface to look into with. The cool thing about fluentd is, that it can take a lot of stuff (docker natively supports logging to them as a driver) and spit out nicely formatted json per log entry that can be sent basically anywhere. Here is a sample entry from my mongo db that fluentd put there (was a nginx log entry with added server_name and got machine_id added by fluentd):
Whether nginx doesn't log the IP, fluentd removes it or it gets periodically removed by some client connected to the database is up to you. One could probably also use a grafana server to have statistics of the data in the MongoDB (or whatever backend you choose). If you need help regarding the fluentd, mongodb or grafana setup, feel free to ask. |
Here’s the relevant section of the GDPR regarding whether it is necessary to obtain user consent before collecting and processing user information. In particular, consent is not required when the processing is necessary for compliance with a legal obligation or for “legitimate interests”. I would say that keeping a log containing IP addresses and user-agents, at least for a set amount of time, is necessary for security purposes. The French law actually mandates that such logs be kept for one year (not sure about other countries). |
The published repository runs nginx, which keeps logs about who accesses the files. Collected information is (following default nginx rules):
We should probably define a retention time for this information, and maybe reduce the scope of collected information (e.g. anonymise IP addresses after a given time). The logs could be used anonymously to publish stats about which packages are used.
The text was updated successfully, but these errors were encountered: