Privacy Policy

Who we are

Our web­site address is: http://www.wenweb.de and this is a private blog

What personal data we collect and why we collect it

Comments

When vis­it­ors leave com­ments on the site we col­lect the data shown in the com­ments form, and also the visitor’s IP address and browser user agent string to help spam detec­tion.

An anonym­ized string cre­ated from your email address (also called a hash) may be provided to the Gravatar ser­vice to see if you are using it. The Gravatar ser­vice pri­vacy policy is avail­able here: https://automattic.com/privacy/. After approv­al of your com­ment, your pro­file pic­ture is vis­ible to the pub­lic in the con­text of your com­ment.

Media

If you upload images to the web­site, you should avoid upload­ing images with embed­ded loc­a­tion data (EXIF GPS) included. Vis­it­ors to the web­site can down­load and extract any loc­a­tion data from images on the web­site.

Contact forms

Cookies

If you leave a com­ment on our site you may opt-in to sav­ing your name, email address and web­site in cook­ies. These are for your con­veni­ence so that you do not have to fill in your details again when you leave anoth­er com­ment. These cook­ies will last for one year.

If you have an account and you log in to this site, we will set a tem­por­ary cook­ie to determ­ine if your browser accepts cook­ies. This cook­ie con­tains no per­son­al data and is dis­carded when you close your browser.

When you log in, we will also set up sev­er­al cook­ies to save your login inform­a­tion and your screen dis­play choices. Login cook­ies last for two days, and screen options cook­ies last for a year. If you select “Remem­ber Me”, your login will per­sist for two weeks. If you log out of your account, the login cook­ies will be removed.

If you edit or pub­lish an art­icle, an addi­tion­al cook­ie will be saved in your browser. This cook­ie includes no per­son­al data and simply indic­ates the post ID of the art­icle you just edited. It expires after 1 day.

Embedded content from other websites

Art­icles on this site may include embed­ded con­tent (e.g. videos, images, art­icles, etc.). Embed­ded con­tent from oth­er web­sites behaves in the exact same way as if the vis­it­or has vis­ited the oth­er web­site.

These web­sites may col­lect data about you, use cook­ies, embed addi­tion­al third-party track­ing, and mon­it­or your inter­ac­tion with that embed­ded con­tent, includ­ing tra­cing your inter­ac­tion with the embed­ded con­tent if you have an account and are logged in to that web­site.

Analytics

Activ­ity Log

This fea­ture only records activ­it­ies of a site’s registered users, and the reten­tion dur­a­tion of activ­ity data will depend on the site’s plan and activ­ity type.

Data Used: To deliv­er this func­tion­al­ity and record activ­it­ies around site man­age­ment, the fol­low­ing inform­a­tion is cap­tured: user email address, user role, user login, user dis­play name, WordPress.com and loc­al user IDs, the activ­ity to be recor­ded, the WordPress.com-connected site ID of the site on which the activ­ity takes place, the site’s Jet­pack ver­sion, and the timestamp of the activ­ity. Some activ­it­ies may also include the actor’s IP address (login attempts, for example) and user agent.

Activ­ity Tracked: Login attempts/actions, post and page update and pub­lish actions, comment/pingback sub­mis­sion and man­age­ment actions, plu­gin and theme man­age­ment actions, wid­get updates, user man­age­ment actions, and the modi­fic­a­tion of oth­er vari­ous site set­tings and options. Reten­tion dur­a­tion of activ­ity data depends on the site’s plan and activ­ity type. See the com­plete list of cur­rently-recor­ded activ­it­ies (along with reten­tion inform­a­tion).

Data Synced (?): Suc­cess­ful and failed login attempts, which will include the actor’s IP address and user agent.

Com­ment Likes

This fea­ture is only access­ible to users logged in to WordPress.com.

Data Used: In order to pro­cess a com­ment like, the fol­low­ing inform­a­tion is used: WordPress.com user ID/username (you must be logged in to use this fea­ture), the loc­al site-spe­cif­ic user ID (if the user is signed in to the site on which the like occurred), and a true/false data point that tells us if the user liked a spe­cif­ic com­ment. If you per­form a like action from one of our mobile apps, some addi­tion­al inform­a­tion is used to track the activ­ity: IP address, user agent, timestamp of event, blog ID, browser lan­guage, coun­try code, and device info.

Activ­ity Tracked: Com­ment likes.

Con­tact Form

Data Used: If Akismet is enabled on the site, the con­tact form sub­mis­sion data — IP address, user agent, name, email address, web­site, and mes­sage — is sub­mit­ted to the Akismet ser­vice (also owned by Auto­mat­tic) for the sole pur­pose of spam check­ing. The actu­al sub­mis­sion data is stored in the data­base of the site on which it was sub­mit­ted and is emailed dir­ectly to the own­er of the form (i.e. the site author who pub­lished the page on which the con­tact form resides). This email will include the submitter’s IP address, timestamp, name, email address, web­site, and mes­sage.

Data Synced (?): Post and post meta data asso­ci­ated with a user’s con­tact form sub­mis­sion. If Akismet is enabled on the site, the IP address and user agent ori­gin­ally sub­mit­ted with the com­ment are synced, as well, as they are stored in post meta.

Gravatar Hov­er­cards

Data Used: This fea­ture will send a hash of the user’s email address (if logged in to the site or WordPress.com — or if they sub­mit­ted a com­ment on the site using their email address that is attached to an act­ive Gravatar pro­file) to the Gravatar ser­vice (also owned by Auto­mat­tic) in order to retrieve their pro­file image.

Jet­pack Com­ments

Data Used: Commenter’s name, email address, and site URL (if provided via the com­ment form), timestamp, and IP address. Addi­tion­ally, a jetpack.wordpress.com IFrame receives the fol­low­ing data: WordPress.com blog ID attached to the site, ID of the post on which the com­ment is being sub­mit­ted, commenter’s loc­al user ID (if avail­able), commenter’s loc­al user­name (if avail­able), commenter’s site URL (if avail­able), MD5 hash of the commenter’s email address (if avail­able), and the com­ment con­tent. If Akismet (also owned by Auto­mat­tic) is enabled on the site, the fol­low­ing inform­a­tion is sent to the ser­vice for the sole pur­pose of spam check­ing: commenter’s name, email address, site URL, IP address, and user agent.

Activ­ity Tracked: The com­ment author’s name, email address, and site URL (if provided dur­ing the com­ment sub­mis­sion) are stored in cook­ies. Learn more about these cook­ies.

Data Synced (?): All data and metadata (see above) asso­ci­ated with com­ments. This includes the status of the com­ment and, if Akismet is enabled on the site, wheth­er or not it was clas­si­fied as spam by Akismet.

Likes

This fea­ture is only access­ible to users logged in to WordPress.com.

Data Used: In order to pro­cess a post like action, the fol­low­ing inform­a­tion is used: IP address, WordPress.com user ID, WordPress.com user­name, WordPress.com-connected site ID (on which the post was liked), post ID (of the post that was liked), user agent, timestamp of event, browser lan­guage, coun­try code.

Activ­ity Tracked: Post likes.

Mobile Theme

Data Used: A visitor’s pref­er­ence on view­ing the mobile ver­sion of a site.

Activ­ity Tracked: A cook­ie (akm_mobile) is stored for 3.5 days to remem­ber wheth­er or not a vis­it­or of the site wishes to view its mobile ver­sion. Learn more about this cook­ie.

Noti­fic­a­tions

This fea­ture is only access­ible to registered users of the site who are logged in to WordPress.com.

Data Used: IP address, WordPress.com user ID, WordPress.com user­name, WordPress.com-connected site ID and URL, Jet­pack ver­sion, user agent, vis­it­ing URL, refer­ring URL, timestamp of event, browser lan­guage, coun­try code. Some vis­it­or-related inform­a­tion or activ­ity may be sent to the site own­er via this fea­ture. This may include: email address, WordPress.com user­name, site URL, email address, com­ment con­tent, fol­low actions, etc.

Activ­ity Tracked: Send­ing noti­fic­a­tions (i.e. when we send a noti­fic­a­tion to a par­tic­u­lar user), open­ing noti­fic­a­tions (i.e. when a user opens a noti­fic­a­tion that they receive), per­form­ing an action from with­in the noti­fic­a­tion pan­el (e.g. lik­ing a com­ment or mark­ing a com­ment as spam), and click­ing on any link from with­in the noti­fic­a­tion panel/interface.

How long we retain your data

If you leave a com­ment, the com­ment and its metadata are retained indef­in­itely. This is so we can recog­nize and approve any fol­low-up com­ments auto­mat­ic­ally instead of hold­ing them in a mod­er­a­tion queue.

For users that register on our web­site (if any), we also store the per­son­al inform­a­tion they provide in their user pro­file. All users can see, edit, or delete their per­son­al inform­a­tion at any time (except they can­not change their user­name). Web­site admin­is­trat­ors can also see and edit that inform­a­tion.

What rights you have over your data

If you have an account on this site, or have left com­ments, you can request to receive an expor­ted file of the per­son­al data we hold about you, includ­ing any data you have provided to us. You can also request that we erase any per­son­al data we hold about you. This does not include any data we are obliged to keep for admin­is­trat­ive, leg­al, or secur­ity pur­poses.

Where we send your data

Vis­it­or com­ments may be checked through an auto­mated spam detec­tion ser­vice.

Your contact information

rgiw(at)freenet.de

Comments are closed.