<i>&gt; Somehow, the user inputting data into those fields of their own volition still does not constitute explicit consent to store and use that data for purposes of making the service&#x2F;product happen.</i><p>The article says precisely the opposite (&quot;Naturally when users enter information themselves that is considered consent&quot;), so why are you saying that?<p>What you need to do is explain <i>why</i> you&#x27;re asking for that information, and not use the information for other purposes without asking the user again.<p><i>&gt; The law, as mentioned in the article, also has no provisions for legal, financial, or tax purposes.</i><p>You can store it as long as there are &quot;legitimate grounds for retaining it&quot;. Legal or tax purposes certainly fit. A marketing database doesn&#x27;t.<p><i>&gt; I imagine there is an entire classification of apps that you could never produce useful results out of this, ie, you can&#x27;t just import it into another service or app and continue on as if nothing changed..</i><p>There are plenty of services that provide cheap data transformation&#x2F;syncing for when you want to move to another service. Sure, the mapping won&#x27;t be perfect, but so what?