holch wrote: Good idea of separating the email/personal data by sending emails with another tool.
It would be great if we could generate a csv file with token links. Of course you can do it by hand (as I described in the workaround section), but creating a bunch of dummy tokens and then export the links would be great.
When needing real anonymous token : i always do like this. Never use information user on token.
One time : token distribution was done with little paper in a hat …
And final client din't have access to database. I‘m the only one with access to DB.
Currently in France : you have to register IP and keep it one year in your log, and what action is done. Then : looking at the id of the response table + log : you have the IP who start to answer to this question … even without token. It's the prooff thet nothing is anonymous … if you host data yourself.
You're right about “it is important to consider "anonymous" rather an internal process/rule than a technical process.“ And a hoster must do exactly the same think than questionpro : Get token completed/not completed in token table, but disable access of this token table to final user …
EDIT : there are an issue in questionpro : “ If the respondent requests his response data to be removed from the servers as a result of the breach” then there are a link between data and email … this link didn't exist in limesurvey even with databreach …
