holch wrote: On another note:

Scale : Last month we worked on a project for a major U.K. retailer and sent around 350,000 invites out to a survey hosted on LS .. to which we got around 20K completes ... and an additional 6K opt outs flagged (not sure if these would have been a delete request if the option was there) so even if there was say 20% of those that took the delete option this would mean 1200 emails to be delt with.

I found this very interesting and we always have questions here in the forum on how it scales. Unfortunately there is very little real life expierence with big sample sizes. Many market research surveys in the adhoc sector are a lot smaller.
Would you mind to share a little showcase about how Limesurvey worked for this project, how you hosted LS and how you guaranteed performance? But that would be something for another trhead. It would be nice if you could share a little bit about your experience with big samples.

Would be happy post on a showcase on here about this for others if they found it useful .. just tell me where you would like it and I will do that ...

Great! That is already a very good starting point for discussion.
[quote[The right to restrict processing: a cookie cutter question on the end screen that gives consent to process the data if it is not checked then that data is not included in any reports or exports[/quote]
Wouldn't it make more sense to have this question already at the beginning and just not continue if they do not agree? Why going through all the survey to just say: do not include me in the reports?

holch wrote: Great! That is already a very good starting point for discussion.
[quote[The right to restrict processing: a cookie cutter question on the end screen that gives consent to process the data if it is not checked then that data is not included in any reports or exports

Wouldn't it make more sense to have this question already at the beginning and just not continue if they do not agree? Why going through all the survey to just say: do not include me in the reports?[/quote]

This is where it gets tricky and I know others in the industry face this problem ... we are explicitly not allowed to refuse people the right to give data under the legislation ... i.e. we cannot exclude them ... but we have to offer them the ability to refuse processing where this processing is done on an automated basis (segmentation for example where an algorithm is used)

In our surveys we have started to have explicit consent questions added to the start of the survey ... but they also have to have the opportunity to refuse process so ....

Start - do you agree to share your thoughts etc. - Yes
Take survey and collect data
Normal process - end survey and use data based on consent collected at the start ....
If we started to put in a full explanation of how we will process this data and when at the start then we run the risk of the respondent bailing at that point ...

Our interpretation of the new legislation

Start - do you agree to share your thoughts etc. - Yes
Take survey and collect data
End of survey - Thank you for sharing your insights, this data will be run through a series of processes where we may group you with other like minded individuals for reporting purposes. This is an automatic process where none of your personally identifiable information will be reported out to our clients or any other 3rd party. Do you agree to this processing of your data ... Yes / No

By the time a respondent has gone through the survey and completed it we would expect a minimal refusal rate here so we feel as though this would be the better option.

It is all about transparency and we feel that this would comply to the letter of the regulation in this way.

Hope that makes sense?

holch wrote: The right to restrict processing: a cookie cutter question on the end screen that gives consent to process the data if it is not checked then that data is not included in any reports or exports

I thought that was the purpose of the privacy policy feature which is already implemented in LS 3.X.Y? You cannot continue without consent. The boxes still show the wrong text in 3.5.4.