From: Julien Lepiller <julien@lepiller.eu>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 43796@debbugs.gnu.org
Subject: bug#43796: Privacy policy
Date: Mon, 05 Oct 2020 07:14:21 -0400 [thread overview]
Message-ID: <A1A0F4BE-12DF-4A6C-B5BF-4BC8AF104DC3@lepiller.eu> (raw)
In-Reply-To: <20201005095432.la7qsn3vilmu4a57@pelzflorian.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
I'm pretty sure we log the date anl time along with IP and requested page.
Le 5 octobre 2020 05:54:32 GMT-04:00, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> a écrit :
>On Sun, Oct 04, 2020 at 11:56:04AM -0400, Julien Lepiller wrote:
>> The GDPR is not the only legislation that applies to us. For
>> services hosted in France for instance, there is a legal obligation
>> to keep logs for at least one year (not sure exactly who that
>> applies to). There could be something similar in Germany where
>> berlin is located.
>
>A quick web search does not reveal any such obligation in Germany.
>I also know people who don’t log. But again, IANAL.
>
>The Debian Privacy Policy says they store web logs for 15 days.
>But iplocation.net tells me their server is hosted in the Netherlands.
>
>If the Guix admins do not intend to use such data to “respond to
>excess usage or security attacks” on the website, logging should be
>disabled and I will remove that wording from the proposed patch.
>
>> I think some of the wording is vague. Does "can be used to identify"
>> mean we will use the IP to identify the person (is it the reason we
>> process this data?) Or is it something that we could technically do,
>> but refuse to do?
>
>I changed it to
>
>During your use of Guix’ software in its default configuration,
>your IP address will be revealed to the network services you use.
>From an IP address it may be possible to identify who uses the
>service and from which internet connection. These services include
>
>Attached is the complete patch with this single change.
>
>Are there other things which are badly worded?
>
>Regards,
>Florian
[-- Attachment #2: Type: text/html, Size: 2230 bytes --]
next prev parent reply other threads:[~2020-10-05 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 15:34 bug#43796: Privacy policy pelzflorian (Florian Pelz)
2020-10-04 15:56 ` Julien Lepiller
2020-10-05 9:54 ` pelzflorian (Florian Pelz)
2020-10-05 11:14 ` Julien Lepiller [this message]
2020-10-05 14:14 ` Ludovic Courtès
2020-10-05 7:09 ` bug#43796: (no subject) Tomás Ortín Fernández via Bug reports for GNU Guix
2020-10-05 13:16 ` pelzflorian (Florian Pelz)
2020-10-05 15:29 ` Tomás Ortín Fernández via Bug reports for GNU Guix
2020-10-05 19:53 ` pelzflorian (Florian Pelz)
2020-10-05 10:57 ` bug#43796: Privacy policy Jelle Licht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A1A0F4BE-12DF-4A6C-B5BF-4BC8AF104DC3@lepiller.eu \
--to=julien@lepiller.eu \
--cc=43796@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).