2 ms·
> 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
by icebraining 11y ago
> 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/product happen.
The article says precisely the opposite ("Naturally when users enter information themselves that is considered consent"), so why are you saying that?
What you need to do is explain why you're asking for that information, and not use the information for other purposes without asking the user again.
> The law, as mentioned in the article, also has no provisions for legal, financial, or tax purposes.
You can store it as long as there are "legitimate grounds for retaining it". Legal or tax purposes certainly fit. A marketing database doesn't.
> I imagine there is an entire classification of apps that you could never produce useful results out of this, ie, you can't just import it into another service or app and continue on as if nothing changed..
There are plenty of services that provide cheap data transformation/syncing for when you want to move to another service. Sure, the mapping won't be perfect, but so what?