Imprint & Privacy Policy

This Blog is ran by

Martin Giger

Murtenstrasse 143C
Bern, 3008
Switzerland

Contact

Please contact me with an e-Mail to the above address if possible. For a quicker response, mention me on Twitter or in the Fediverse.

Technology

This Blog is based on WordPress and hosted by cyon in Switzerland.

Content

The texts on this blog are intellectual property of mine (the “me” person is the person given above) and can not be published on any other website or other form of media without my permission. Pictures are, if not otherwise noted, created by me but may contain contents of other persons (Screenshots). If I didn’t give the correct source to a picture or used it without the author’s permission, please contact me.

Excluded are all comments and avatars of the commentators. I may remove comments if they contain libel, reputation damage, sexism or racism.

I am not responsible for the contents of linked pages. I remove links to juridically problematic pages if I am informed about the link.

This website uses cookies. Cookies are small plaintext files, which are saved temporarily or permanently on your computer when you visit this site. These cookies are used for the static analysis of the website usage as well as continuous improvements.

Your browser offers you to deactivate cookies permanently or temporarily. If you deactivate cookies in your browser, some features might not be available or misbehave. Please also consider the Cookie Policy.

Thirdparty Technologies and Data Policy

This website has external scripts, such as from Google (Google+ button), Twitter (Tweet button) or Facebook (Like button). Further articles have embedded content like a YouTube or Soundcloud player. For those the TOS and Privacy Policies of their source apply.

These third parties might save cookies in your browser too.

This site utilizes caching in order to facilitate a faster response time and better user experience. Caching potentially stores a duplicate copy of every web page that is on display on this site. All cache files are temporary, and are never accessed by any third party, except as necessary to obtain technical support from the cache plugin vendor. Cache files expire on a schedule set by the site administrator, but may easily be purged by the admin before their natural expiration, if necessary.

Jetpack Comments

Data Used: Commenter’s name, email address, and site URL (if provided via the comment form), timestamp, and IP address. Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content.

Activity Tracked: The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.

Data Synced (?): All data and metadata (see above) associated with comments. This includes the status of the comment.


Protect

Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.

Activity Tracked: Failed login attempts (these include IP address and user agent). We also set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.

Data Synced (?): Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.


Subscriptions

Data Used: To initiate and process subscriptions, the following information is used: subscriber’s email address and the ID of the post or comment (depending on the specific subscription being processed). In the event of a new subscription being initiated, we also collect some basic server data, including all of the subscribing user’s HTTP request headers, the IP address from which the subscribing user is viewing the page, and the URI which was given in order to access the page (REQUEST_URI and DOCUMENT_URI). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.

Activity Tracked: Functionality cookies are set for a duration of 347 days to remember a visitor’s blog and post subscription choices if, in fact, they have an active subscription.