Impressum
Impressum der Webseite: https://www.holzbootsbau.ch – Axel Thobaben
Als ich meinen Webserver Anfang 2009 in die Schweiz verlegt habe, ist mir aufgefallen, dass die Domain “holzbootsbau.ch” zum einem Erstaunen noch frei war. Als Dipl.-Ing. Schiffbau musste ich also zugreifen und jetzt habe ich endlich einen schönen Domain-Namen um meine Erfahrungen und mein Wissen im Boots- und Schiffbau anderen zur Verfügung zu stellen.
Diese Domain hat rein privaten Charakter – Ich verlinke in meinem Postings teilweise auch auf andere Webseiten. Zum Zeitpunkt der Link-Erstellung schaue ich diese Seite natürlich genau an, aber trotzdem bin ich für die Inhalte der von mir verlinkten Webseiten nicht verantwortlich. Ich habe keinen Einfluss auf Add-Ons, Banner, Malware, Viren oder ähnlichen Dingen, die auf fremden Homepages aktiv sind, oder nach der Verlinkung aktiviert werden könnten. Sollte jemand problematische Inhalte, Rechtsverletzungen oder Ähnliches finden, möchte ich darum bitten, mich kurz zu kontaktieren.
Mit dem Lesen dieses Impressums räumen sie mir das Recht ein, eventuell vorhandene Rechtsverletzungen ohne Strafverfahren und Kosten in einer angemessenen Frist von einem Kalender-Monat zu entfernen. Ich bin gerne bereit, berechtigten Einwänden nachzugehen und etwaige Verstösse schnell zu beheben und respektiere die Persönlichkeitsrechte der Menschen.
Diese Webseite spiegelt ein Hobby von mir wieder – obwohl ich als Schiffbauer natürlich eine relativ fundierte Ausbildung in diesem Fach habe. In der Schweiz arbeite ich NICHT als Schiffbauer sondern in der IT-Branche als Unternehmensberater.
Bitte halten Sie sich das vor Augen, bevor Sie aktiv werden.
Da mein Name relativ selten ist verzichte ich auf die Nennung meiner Post-Anschrift. Sie können mich via Web-Formular erreichen!
Zum Schutz der Privatssphäre meiner Familie bitte ich Sie das so zu akzeptieren
Axel Thobaben
Kontakt Formular
Data Privacy
Activity Log
This feature only records activities of a site’s registered users, and the retention duration of activity data will depend on the site’s plan and activity type.
Data Used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site’s Jetpack version, and the timestamp of the activity. Some activities may also include the actor’s IP address (login attempts, for example) and user agent.
Activity Tracked: Login attempts/actions, post and page update and publish actions, comment/pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and the modification of other various site settings and options. Retention duration of activity data depends on the site’s plan and activity type. See the complete list of currently-recorded activities (along with retention information).
Data Synced (?): Successful and failed login attempts, which will include the actor’s IP address and user agent.
Contact Form
Data Used: If Akismet is enabled on the site, the contact form submission data — IP address, user agent, name, email address, website, and message — is submitted to the Akismet service (also owned by Automattic) for the sole purpose of spam checking. The actual submission data is stored in the database of the site on which it was submitted and is emailed directly to the owner of the form (i.e. the site author who published the page on which the contact form resides). This email will include the submitter’s IP address, timestamp, name, email address, website, and message.
Data Synced (?): Post and post meta data associated with a user’s contact form submission. If Akismet is enabled on the site, the IP address and user agent originally submitted with the comment are synced, as well, as they are stored in post meta.
Mobile Theme
Data Used: A visitor’s preference on viewing the mobile version of a site.
Activity Tracked: A cookie (akm_mobile) is stored for 3.5 days to remember whether or not a visitor of the site wishes to view its mobile version. Learn more about this cookie.
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.
WordPress.com Stats
Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important: The site owner does not have access to any of this information via this feature. For example, a site owner can see that a specific post has 285 views, but he/she cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.
Activity Tracked: Post and page views, video plays (if videos are hosted by WordPress.com), outbound link clicks, referring URLs and search engine terms, and country. When this module is enabled, Jetpack also tracks performance on each page load that includes the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of page load times and resource loading duration (image files, Javascript files, CSS files, etc.). The site owner has the ability to force this feature to honor DNT settings of visitors. By default, DNT is currently not honored.