Add data processing / deletion notices

[stevieflow]

Add something like

(as seen at https://dataquality.threesixtygiving.org/)

to OFDS CoVE

[duncandewhurst]

The deletion schedule (90 days) is already documented in the second paragraph of the introductory text on the landing page:

Further detail is provided in the T&Cs, which are linked in the website footer.

We could add something the like the text from 360Giving, which appears in a collapsed box at the bottom of the page, but if the workshop participants that raised concerns about the lack of a deletion schedule did not read the introductory text at the top of the page, I'm not convinced that they would read extra information provided further down the page.

@stevesong what do you think?

[stevieflow]

Ah thanks @duncandewhurst ! It was right in front of me!

Maybe @stevesong was referring to the length of the period, and shortening that?

[stevesong]

I think I am a bit of an idiot for not reading that text in the second paragraph. :-) Mostly this is fine. I think for the telecom sector we might want to shorten that period and perhaps have an explicit section as Steven suggests of "What happens to my data?" I got the sense that publicly uploading network data, even when secured through obscure URL, might cause some unease. I would be inclined to use something like 48hrs and make it very clear that only the uploader has access to the url. Open to discussion.

[duncandewhurst]

Sure, I can draft some extra wording, based on the text from 360Giving and making it very clear that only those with the link can access the results.

Regarding the deletion schedule, the main challenge with a short retention period like 48 hours is that it hinders support/collaboration on resolving validation errors. For the Open Contracting Data Standard Data Review Tool, the retention period was originally 7 days, but we increased it to 90 days because it wasn't uncommon for results to expire before the Helpdesk had finished going through them with a publisher. Given that providing remote support usually involves a few rounds of email back-and-forth, I think that would almost always be the case with a 48 hour retention period. However, we could go back down to 7 days if you think that would help to reassure implementers?

[duncandewhurst]

Also, don't worry about not reading the second paragraph, based on our sample of 3, no-one reads it!

[stevesong]

I think 7 days seems like a reasonable compromise. It is always possible to re-upload the original dataset.