3 ms·
> unless your business model is to abuse your customers' personal data. Then it might be hard. It's not only your business model, but also the business model o
by tjansen 5y ago
> unless your business model is to abuse your customers' personal data. Then it might be hard.
It's not only your business model, but also the business model of all third-party services you are using on your site.
Also, part of the reason why it's not that hard is that the GDPR is pretty much one of a kind. Imagine the US and maybe some countries in Asia having similar but different implementations of privacy laws, and you having to work with them simultaneously. Or even different laws in each US state (CCPA?). Imagine every country requiring you to store user data only the user's country of origin, thus managing a separate database for each country.
- M2Ys4U 5y ago>Also, part of the reason why it's not that hard is that the GDPR is pretty much one of a kind. Imagine the US and maybe some countries in Asia having similar but different implementations of privacy laws, and you having to work with them simultaneously. That's why treaties like Convention 108+[0] exist, to provide a common framework for implementing data protection laws. [0] https://search.coe.int/cm/Pages/result_details.aspx?ObjectId=09000016807c65bf https://search.coe.int/cm/Pages/result_details.aspx?ObjectId...
- davidgerard 5y agoas I said: > Note lack of those details in this present discussion, for example. your comments so far have been apocalyptic GDPR fan-fiction, but are notably short on the actual details of what you're doing and how you do it.