How much do you know about GDPR?
Assess your knowledge on the GDPR by taking this Nebu survey!
Last week you were able to read how Fred and I met and how we started with the idea to develop on the Apple Newton. This week I would like to continue our journey and tell you how we started and changed our path into Market Research.
As I was still in the military service, we quickly got our cooperation going: I started developing in my ample free time. In the spring/summer of 1993, Nebu was born!
The business for the sales applications was pretty successful, having clients like a Dutch lingerie sales organization, Massey Ferguson and Range Rover as clients. We soon needed more capacity for software development and were extremely lucky to run into a 400 and 800-meter sprinter, a tall skinny guy. In December 1994 Jan Raaphorst joined Nebu. And guess what? Next year we celebrate Jan being with us for 25 years!
2018 is an important year for all of us here at Nebu. The company turns 25! On Thursday, June 14 we are organizing a party to celebrate this great event! Everyone who is or has been part of the Nebu journey will be invited, so please keep an eye on your post box!
Nebu's anniversary gave me an opportunity to reminisce about the events of a quarter of a century. In a series of blog posts, I’d like to take you on a trip down memory lane and tell a little bit more about how we started, how we came into Market Research and about some of our highs and lows.
The first Nebu office, located in Fred's house in Uitgeest
It was in 1993 that Fred and I started working together. A long time ago, but I still remember this as if it were yesterday. Just in case 1993 doesn't mean as much to you as it does to me, I'd like to bring up a few iconic events that happened that year. In 1993:
In a series of three blog posts we're considering implications of the GDPR in regards to marketing research industry. The previous two blog article touched upon how GDPR might influence conducting CATI and WAPI interviews. In this one I'd like to ponder on how the new legislation may affect conducting CAPI surveys, as well as Mixed-mode studies and mode independent research projects.
As CAPI mode is a personal (F2F) interview, it gives a chance for collecting different type of data than in WAPI or CATI mode, that also needs different handling:
In a series of three blog posts we're considering implications of the GDPR in regards to marketing research industry. The previous blog article touched upon how GDPR might influence conducting CATI interviews. In this one I'd like to ponder on how the new legislation may affect conducting WAPI surveys.
As you could read in our previous blog post, the EU GDPR affects all companies, that deal with data of EU citizens. Every company needs to be aware their data flows, whether it is related to ‘generic’ customer data, or data is collected for well defined purposes.
Having an overall data-flow, attached to the company procedures in practice, will be your biggest help pinpointing risks, vulnerabilities, or improvement possibilities. Having said that, it has to be one of the very first steps, describing the INs and OUTs of all your data you need to deal with.
Next, and two of the most important, steps are classifying the data, and your role related to it - this requires continuous attention from your staff, as soon as new processes are established, that affect the data-flow. In our previous blog post we described the roles and data classification types. Not all data requires attention - this though sounds to be a case easy to deal with, you still need to guarantee, that a certain point you do not start mixing this data with personal identifiers or sensitive data. For the data, that you need to handle with high attention, the following factors have to be considered:
This list may look a bit abstract at first glance, but let’s examine some market research practices (without the aim of completeness) per different mode, and pinpoint challenges from these aspects.
CATI interviews can start on two different paths:
In both cases, you can end up in a few “feels tricky” situations. First and most important, is that you need to be aware of laws, that apply to your activity. This includes whether or not RDD sample is allowed to use at all, and also indicates, if do not call lists (blacklists) have to be applied.