From: Sven <sven.hoehn@posteo.de>
To: ipfire-artwork@lists.ipfire.org
Subject: [IPFire Artwork] DSGVO compliant?
Date: Mon, 18 Jun 2018 07:57:16 +0200 [thread overview]
Message-ID: <E833DE5F-ED45-436E-BC30-2F1B5187C116@posteo.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
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 reply other threads:[~2018-06-18 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 5:57 Sven [this message]
[not found] <CAPxcDEusKFBY-1UPbOW30hYKBJuxBpMrE4WEwR+tanZbbUHbyw@mail.gmail.com>
2018-06-18 9:46 ` Michael Tremer
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=E833DE5F-ED45-436E-BC30-2F1B5187C116@posteo.de \
--to=sven.hoehn@posteo.de \
--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