<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Gdpr on Murat Useinov</title>
    <link>https://useinov.com/tags/gdpr/</link>
    <description>Recent content in Gdpr on Murat Useinov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 May 2018 10:45:00 +0300</lastBuildDate>
    <atom:link href="https://useinov.com/tags/gdpr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GDPR: where the user actually lives</title>
      <link>https://useinov.com/posts/2018/gdpr-data-map/</link>
      <pubDate>Wed, 09 May 2018 10:45:00 +0300</pubDate>
      <guid>https://useinov.com/posts/2018/gdpr-data-map/</guid>
      <description>&lt;p&gt;The row in &lt;code&gt;users&lt;/code&gt;. Then orders, with the delivery address and phone. Then nginx access logs with emails inside GET parameters of an old unsubscribe endpoint. That is how far I got in the first ten minutes of drawing where one user&amp;rsquo;s data lives on one project, and the map did not fit on one page.&lt;/p&gt;
&lt;p&gt;May 25 is close and everyone discusses consent banners. The lawyers can have the banners. The engineering part is the right to erasure. &amp;ldquo;Delete the user&amp;rdquo; sounds like one DELETE statement until you sit down with a pen.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
