Getting ready for GDPR
People not lists
Websand doesn’t work the same way as other email marketing platforms. Our platform works on a single data model, based on the key fields you need to manage consent. Email, date of signup and where people signed up.
Segmentation allows you to group people and view them as a unique audience – like you would with lists, but the data remains in one place. It’s a different approach, but it makes things much easier for you to manage, especially under the new GDPR rules.
Websand is a data processor, you are the controller. In simple terms, if Websand was a racing car, you’d be the driver. Our mandatory fields to process the data you collect is structured to ensure that you are collecting consent in the right way. That’s email address, date of signup, and source of signup. If you are using WordPress, our WordPress widget will makes it easy to collect consent using a signup box like this…
You can add extra fields too, but make sure you are consistent to keep your data accurate.
Because we operate as a single database source, when someone unsubscribes from a message, they have unsubscribed from your marketing. Yes, it’s a hardcore approach, but we’d rather keep you safe. We’ve been operating like this for well over 12 months now, and it’s an approach been very well received, by marketers and their audience alike.
No means No. But of course you can come back at anytime 🙂
Managing the right to be forgotten
You can now delete data within Websand. You can suppress them or delete them as an individual using the ‘forget this customer’ button.
Or you can delete everyone within a segment using the new ‘Purge’ button within the segment.
But be aware, forget means DELETE, we nuke this data and it will remove all trace of the information previously stored.
Also note that this ONLY removes the data held by Websand, it won’t remove the data from the systems you’ve connected to Websand. They will have their own policies and methods to deal with this requirement.
Managing subject access requests
Websand can be used to store both the personal data, the transactional history of the individual (purchase, events attended, survey responses), and also the marketing history.
We trust that you’ll be following the principle of data minimalisation and only store the minimum amount of data within Websand, but if you do store basic information on the profile and transactional history. Not only is this really useful for targeted marketing, it also makes managing subject access requests, really easy.
When you get a request, simply look up the person and you can snapshot the personal, transactional and marketing history (including consent time and source) from one screen!
< here’s a subject access request for our email address, email@example.com
Communication and Transactional History
Websand shows you the real outcomes from your marketing on an individual level. Websand will show you who was selected, who opened, who clicked, but more importantly who actually met the objectives of the campaign and bought something. That way it’s easy to understand where you have engagement and perhaps what data is now irrelevant and should be removed.
Keeping your data clean
Websand is flexible, you can connect the platform to multiple systems through our API or via tools such as Zapier. However, Websand is an endpoint. You can’t edit personal data within Websand, since it collects data from other sources those updates should be done within those systems. The update will then flow through to Websand.