Responsible for the contents of
+49 177 6467763
Accountability for content
The contents of our pages have been created with the utmost care. However, we cannot guarantee the contents’ accuracy, completeness or topicality. According to statutory provisions, we are furthermore responsible for our own content on these web pages. In this context, please note that I am accordingly not obliged to monitor merely the transmitted or saved information of third parties, or investigate circumstances pointing to illegal activity. Our obligations to remove or block the use of information under generally applicable laws remain unaffected by this as per §§ 8 to 10 of the Telemedia Act (TMG).
Accountability for links
Responsibility for the content of external links (to web pages of third parties) lies solely with the operators of the linked pages. No violations were evident to me at the time of linking. Should any legal infringement become known to me, I will remove the respective link immediately.
App Crash Logs
If you opt in to sending crash logs, I will have a copy of your crash logs.
When one of my apps sends a crash log, it sends only the text of the crash log. No additional information, such as email address, is sent. The web server will, as described below, store some information of the data upload, though, including time and IP address.
Crash logs are stored privately and are kept confidential.
However, I may make significant parts of a crash log available publicly when there's no personal identification in that part of the crash log. For example, I might share something like this:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.CoreFoundation 0x00007fff42df0668 _CFRetain + 65 1 com.apple.CoreFoundation 0x00007fff42cf8b46 -[__NSCFString retain] + 14 2 libswiftCore.dylib 0x00007fff6e756ffe swift_bridgeObjectRetain + 62 3 de.zettelkasten.TheArchive 0x000000010a2c1099 0x10a2ad000 + 82073 4 de.zettelkasten.TheArchive 0x000000010a2f0519 0x10a2ad000 + 275737
This indicates the point of failure in the app and is entirely for the purpose of fixing crashing bugs.
Tracking, Cookies, and 3rd Parties
The comments are powered by Disqus, and your visit to my pages is transmitted to them, too, when the contact forms load. You have to accept Disqus' terms and policies first, though. You login information are handled by Disqus, not me.
You can disable cookies in your browser.
Tracking of website hits
christiantietze.de, I do use session-cookies of VG Wort in Munich, Germany, to let them measure how many people read my articles. I get compensated when I hit a certain threshold of visits per post. The money comes from a "tax" e.g. printer manufacturers have to pay (see the German Wikipedia for info). The usage of this cookie is in accordance with Art. 6 Paragraph 1 DSGVO (aka GDPR).
The data handling is actually done by INFOnline GmbH, Bonn, Germany. You can opt-out completely by having them set an opt-out cookie, ironically, affecting all (German) websites that participate.
My web server automatically collects data for every page you visit as you visit it. Your browser transmits this data, and you can control this from your browser or via plugins, if you want.
The log files on my server include
- browser name and version
- your computer's operating system
- the referrer URL
- the host name
- the time of access
- your IP address
This data is not combined with anything else. This is in accordance with Art. 6 Paragraph 1 DSGVO (aka GDPR).
Links to Amazon.com are often affiliate links. When you click on these, the shop will give me a share of a few % for any product you buy. This does cost you nothing. Using these links does not set any cookies or transfer your IP. Only when you click on them and visit their shop will Amazon know about you. On their pages, the privacy policies of Amazon apply.
External fonts are served by Google Fonts. According to them, (2018-05-26) they do not set cookies during the process. Also, when the fonts are loaded from their server, the result will be cached by your browser for a year without your computer reaching out to their server again.