Users probably won't understand cookies

[michaelmcmillan]

I'm pretty sure the majority of users won't have any idea what a cookie is. Or why they need to clear the form. Or why they need to note down their personal URL.

It's very challenging to find a user and privacy friendly way of solving this issue, but I suspect there is a better way to do this. Maybe we can brainstorm a little bit?

[michaelmcmillan]

I propose that don't mention personal URLs or cookies on the confirmation screen if you've opted in to use a cookie (which I'm pretty sure the majority will opt in to). I fear the number of people who actually note down the URL and revisit the page is very low (especially of those who opt in to cookie) – which means this probably only confuses the user ("why do I need to save the URL?").

So here's an idea:

1. To catch those who try to submit a form on behalf of a family member etc. we could check if they change any form fields which are very likely NOT to change with time ("what's your age?", "whats your sex?", "do you smoke?", "whats your zip code?").

2. If the user tries to change any of these fields on the second form submit we can show a modal/popup which says "Are you registering someone other than yourself? Yes / No".

3. If they press Yes we can take the user to the confirmation page and ask them to note down their personal URL and then let them submit the form on behalf of the other person. If they press No we simply close the modal and treat this form submit as an update to the first one.

[ceremcem]

Regarding to #3: What if a person wants to submit the form on behalf of another person (person B) and then, when he or she comes for the 3rd time in order to update any of those two forms? If "No" is selected, a dropdown list should be issued to select "Person A", "Person B" etc. An alias would be super useful for this purpose.