HN Explorer

Ask HN: GDPR for CMS SaaS app?

2 points by going_to_800 ↗ HN
Let's say you have a SaaS where your customers can create mini-websites which have sign up pages, members area, etc.

MY question, what is the SaaS for the data of those users who sign up on the customers' "mini-portals"?

Is it a processor or a controller? The SaaS customer can customize pages, send emails etc...so it looks like the controller is the customer and the SaaS is just the processor, but after talking with some lawyers I'm not so sure about that.

What do you think?

2 comments

[ 0.16 ms ] story [ 23.2 ms ] thread
smel
Both I think you're responsible for your scope and also customers if they have access to APIs or export feeds.

Any data about final users should be available and controlled via consentement mgt ui