unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 43796@debbugs.gnu.org, pelzflorian@pelzflorian.de
Subject: bug#43796: Privacy policy
Date: Sun, 04 Oct 2020 11:56:04 -0400	[thread overview]
Message-ID: <90C37536-BB8F-47D4-ABD8-BA8493E9485E@lepiller.eu> (raw)
In-Reply-To: <20201004153419.kyacfjdwmok6yybg@pelzflorian.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]

Looks nice, but:

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.

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?

Le 4 octobre 2020 11:34:19 GMT-04:00, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> a écrit :
>IANAL but I think Guix needs a privacy policy for both its website and
>the Guix software in general.
>
>Attached is a patch for the website that also documents data use by
>Guix and Guix System.  Maybe I’ve overdone some parts and probably
>something important is missing.
>
>In particular, the GDPR requires IP addresses to be deleted from logs
>after a reasonable time.  I think but am not sure the current process
>for nginx is to delete only when the log files become too big.  A more
>suitable policy must be implemented and the users must be told about
>it, I think.  See <https://gdpr-info.eu/art-13-gdpr/>.
>
>In general I think it is better to have an incomplete policy than to
>have none.
>
>Comments?
>
>Regards,
>Florian

[-- Attachment #2: Type: text/html, Size: 1718 bytes --]

  reply	other threads:[~2020-10-04 15:57 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 [this message]
2020-10-05  9:54   ` pelzflorian (Florian Pelz)
2020-10-05 11:14     ` Julien Lepiller
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=90C37536-BB8F-47D4-ABD8-BA8493E9485E@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).