I am from Germany.
And I wanna make a (new) website.

This is fucking exhausting 😩
(Do I have to translate it to english as well? The site will be bilingual).

I miss the time when I was a careless teenage who would just code and not care about bureaucracy...

https://www.iubenda.com
https://cookieconsent.insites.com

my solution for a similar problem:

1) drop the German version.

2) host offshore where there is no imprint and where German authorities have a history of being told GFY.

3) not implementing FB shit buttons, Google ANALytics, Twatter fuck and all that garbage.

4) privacy statement boils down to "this website doesn't collect shit".

@JoshBent They look super smooth to use, thanks for sharing!

@Fast-Nop (except for the country thing) that is what I'm doing. I'm more telling what my website does not that what it does. I only use google fonts, 1&1 integrated analytics and mailchimp. (probably). That's it.

So basically that whole DSGVo stuff is just an implementation of an EU regulation. Technically You should add an english vers... oh fuck I need to translate a whole bunch of legal notices

Btw, for the legalese stuff - this is exactly NOT what GDPR demands. The point is not to drown the user in 20 pages of dense legalese hoping to get away with disregard for the users' privacy as before.

If you can't say in everyday language what data you collect, what you are using them for and for how long you store them, then you probably shouldn't be collecting them anyway.

Plus that there simply is no legalese that would allow you to collect data nilly-willy like 10 years ago. That's the point of the legalese that the EU has made.

Fun fact: when I hacked my website together before GDPR was a thing, I thought about social media buttons and shit, but I was too lazy.

Turned out that early lazyness saved me even more work later. :-)

I've been responsible for creating the privacy policy for https://hackingvision.com as well (subscribe to notifs!! :3) but still believe that I haven't been briefed about all the crap that makes up that whole thing (mailing for example). The website is hosted on WordPress and the founder thinks that a plugin is the solution for everything, including plagiarism.. just to give you a general idea. So now I'm thinking about creating a beta based on Hugo there (I have server access so that shouldn't be a problem to deploy, just that it's a shared host so no sudo) and gradually cause our audience to migrate to that (as it should be much faster, have no unnecessary trackers etc etc). But given my laziness and pending projects, that's gonna take a while. I think that it'd be much easier to build a privacy policy against that though.