From: Michael Tremer <michael.tremer@ipfire.org>
To: ipfire-artwork@lists.ipfire.org
Subject: Re: [IPFire Artwork] DSGVO compliant?
Date: Mon, 18 Jun 2018 10:46:42 +0100 [thread overview]
Message-ID: <4e90a3bdfa9d69edc07c42d6112899c720290ede.camel@ipfire.org> (raw)
In-Reply-To: <CAPxcDEusKFBY-1UPbOW30hYKBJuxBpMrE4WEwR+tanZbbUHbyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
Hi,
GDPR (or DSGVO in German) is mainly about personal data like someone's name,
address, etc.
Fireinfo does not fall into that category and therefore is fine.
However, yes, we should not load anything from any external web server. I
recently did that for the LWL website and it doesn't harm performance of the
website at all.
We should not load jQuery and other JS libraries as well as fonts from external
servers. We do not even set any cookies or have any other tracking mechanisms
active.
I updated the disclaimer text recently and that covers all the rest regarding
essential information being on there.
So all in all, this is another reason why we need to be quick with delivering
the new website :)
Thanks for thinking about this. GDPR affects many things now and needs to be
considered with anything that is being done.
Best,
-Michael
On Mon, 2018-06-18 at 08:27 +0200, Maurice Gesswein wrote:
> Very good point, Sven. What about all the statistics IPFire collects from the
> firewall servers? I'm not very familiar with DSGVO but that was the first
> thing which comes into my mind.
>
> Sven <sven.hoehn(a)posteo.de> schrieb am Mo., 18. Juni 2018, 07:57:
> > Hello,
> > does the IPFire website have to be DSGVO compliant?
> >
> > We have a lot to do to do with various sites, and all the lawyer which I
> > spoke have one thing in common: don’t use Google Webfonts, Adobe Typekit or
> > any other Webfont service that tracks user data.
> > I think that the fonts are the only resource that we get from a eternal
> > server all the other scripts can be served from the „local“ web server.
> >
> > Greetings,
> > Sven
next parent reply other threads:[~2018-06-18 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPxcDEusKFBY-1UPbOW30hYKBJuxBpMrE4WEwR+tanZbbUHbyw@mail.gmail.com>
2018-06-18 9:46 ` Michael Tremer [this message]
2018-06-18 5:57 Sven
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e90a3bdfa9d69edc07c42d6112899c720290ede.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=ipfire-artwork@lists.ipfire.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox