<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Privacy on Alexander Junge&#39;s website</title>
    <link>https://www.alexanderjunge.net/categories/privacy/</link>
    <description>Recent content in Privacy on Alexander Junge&#39;s website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 12 Nov 2022 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.alexanderjunge.net/categories/privacy/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Keeping sensitive information out of Jupyter notebooks stored in git version control</title>
      <link>https://www.alexanderjunge.net/blog/sensitive-info-out-of-jupyter-notebooks/</link>
      <pubDate>Sat, 12 Nov 2022 00:00:00 +0000</pubDate>
      
      <guid>https://www.alexanderjunge.net/blog/sensitive-info-out-of-jupyter-notebooks/</guid>
      <description>Jupyter notebooks are very useful to quickly prototype ideas in data science projects because they allow seeing code, the output of that code, and a narrative explaining its logic right next to each other. But when committing said Jupyter notebooks to version control systems like git, code output containing sensitive information (such as passwords, access tokens, or sensitive data) can easily end up being stored in places where it should not be stored and where it is accessible to others.</description>
    </item>
    
  </channel>
</rss>