Pri­va­cy policy

Who we are

The address of our web­site is: http://nachhaltigkeit.kettelhack.de.

What per­so­nal data we coll­ect and why we coll­ect it

Comm­ents

When visi­tors post comm­ents on the web­site, we coll­ect the data dis­play­ed in the com­ment form, as well as the visitor’s IP address and user agent string (this iden­ti­fies the brow­ser) to help detect spam.

An anony­mi­sed string (also cal­led a hash) can be crea­ted from your email address and pas­sed to the ser­vice Grava­tar to check if you are using it. The pri­va­cy poli­cy of Grava­tar can be found here: https://automattic.com/privacy/. After your com­ment has been appro­ved, your pro­fi­le pic­tu­re is publicly visi­ble in the con­text of your comment.

Media

If you are a regis­tered user and upload pho­tos to this web­site, you should avo­id uploa­ding pho­tos with an EXIF GPS loca­ti­on. Visi­tors to this web­site could down­load pho­tos stored on this web­site and extra­ct their loca­ti­on information.

Cont­act forms

Coo­kies

When you post a com­ment on our web­site, this may con­sti­tu­te con­sent to store your name, email address and web­site in coo­kies. This is a con­ve­ni­ence fea­ture so that you don’t have to re-enter all this data when you post ano­ther com­ment. The­se coo­kies are stored for one year.

If you have an account and log in to this web­site, we will set a tem­po­ra­ry coo­kie to deter­mi­ne whe­ther your brow­ser accepts coo­kies. This coo­kie does not con­tain any per­so­nal data and is dis­card­ed when you clo­se your browser.

When you sign up, we will set up some coo­kies to store your log­in infor­ma­ti­on and vie­w­ing opti­ons. Log­in coo­kies expi­re after two days and coo­kies rela­ting to dis­play opti­ons after one year. If you sel­ect “Stay log­ged in” when regis­tering, your regis­tra­ti­on will be main­tai­ned for a fort­night. When you log out of your account, the log­in coo­kies are deleted.

When you edit or publish an artic­le, an addi­tio­nal coo­kie is stored in your brow­ser. This coo­kie does not con­tain any per­so­nal data and only refers to the post ID of the artic­le you have just edi­ted. The coo­kie expi­res after one day.

Embedded con­tent from other websites

Posts on this web­site may con­tain embedded con­tent (e.g. vide­os, images, artic­les, etc.). Embedded con­tent from other web­sites beha­ves exact­ly as if the visi­tor had visi­ted the other website.

The­se web­sites may coll­ect infor­ma­ti­on about you, use coo­kies, embed addi­tio­nal third par­ty track­ing ser­vices and record your inter­ac­tion with this embedded con­tent, inclu­ding your inter­ac­tion with the embedded con­tent if you have an account and are log­ged into this website.

Ana­ly­sis services

Who we share your data with

How long we store your data for

If you wri­te a com­ment, it will be saved – inclu­ding any meta­da­ta – for an unli­mi­t­ed peri­od of time. By doing so, we can auto­ma­ti­cal­ly detect and appro­ve fol­low-up comm­ents ins­tead of kee­ping them in a mode­ra­ti­on queue.

For users who regis­ter on our web­site, we addi­tio­nal­ly store the per­so­nal infor­ma­ti­on they pro­vi­de in their user pro­files. All users can view, chan­ge or dele­te their per­so­nal infor­ma­ti­on at any time (the user­na­me can­not be chan­ged). Admi­nis­tra­tors of the web­site can also view and modi­fy this information.

What rights you have to your data

If you have an account on this web­site or have pos­ted comm­ents, you may request an export of your per­so­nal infor­ma­ti­on from us, inclu­ding any infor­ma­ti­on you have pro­vi­ded to us. Fur­ther­mo­re, you can request the dele­ti­on of all per­so­nal data that we have stored about you. This does not include data that we are requi­red to retain due to admi­nis­tra­ti­ve, legal or secu­ri­ty-rela­ted reasons.

Whe­re we send your data

Visi­tor comm­ents could be exami­ned by an auto­ma­ted ser­vice for the pur­po­se of spam detection.

Your cont­act information

Fur­ther information

How we pro­tect your data

What mea­su­res we offer in the event of data pro­tec­tion breaches

From which third par­ty pro­vi­ders we recei­ve data

What auto­ma­ted decis­i­on making and/or pro­fil­ing we under­ta­ke with user data

Pre­su­med dis­clo­sure obli­ga­ti­ons of the industry