How GDPR Will Change The Way You Develop
What&#x27;s troubling to me is that it&#x27;s very unclear what <i>specifically</i> is required. I know the linked post isn&#x27;t legal advice, but in the page about &#x27;privacy by design&#x27; linked to by the origin link, they list &quot;Minimize the amount of collected data&quot; as as an item (supposedly to be achieved to be in compliance with the law).<p>What&#x27;s the minimum amount of data? Who decides that? Is it dependent on context? I&#x27;d hope so!<p>Can any site just &#x27;do an end run around&#x27; the law by requiring their users to agree to allow them to collect whatever data they collect now or that they&#x27;ve already collected? If so, that seems like it&#x27;d be likely as helpful as current terms of service.<p>Another item mentioned is &quot;Where possible, pseudonymize personal data.&quot;. What&#x27;s a practical example of that?<p>Yet another item – &quot;Don’t enable social media sharing by default.&quot;. Is the thinking that user&#x27;s shouldn&#x27;t be able to share something via social media without first explicitly enabling that option? That just seem unfriendly. Or is the idea that doing so protects someone from doing so accidentally? This seems a lot like the &#x27;cookie law&#x27;, itself an annoying mandated nagging that probably backfired (because everyone was effectively trained to just do whatever necessary to get rid of the corresponding notification on every site they visited).<p>Again from the privacy-by-design page:<p>&gt; There is no checklist of ready-made questions that will get you there; General Data Protection Regulation requires developers to come up with the questions as well as the answers.<p>That&#x27;s a really unsettling description of a <i>law</i>.