Closed dhlw closed 7 years ago
I think that the two-year timeline is a good balance. I'll get that integrated.
I tried to create a new issue on privacy but I think it didn't work. It is related to this issue.
I think that we should ask for one privacy statement on the testing and for another in the operation. The testing one can be more relaxed, but the second one should be more explicit and specific to the type of service (car sharing, rental, selling), that allow some flexibility to companies.
If we do so, then instead of the two years requirement, that could not make sense for testing, we could ask to inform of any "material change of the privacy policy". This would involve distinct uses of data or a greater disclosure of them than for those considered in the previous policy. Also, in the phase of operation, I would ask the company to make its privacy policy public.
Resolved by fa264c39a3233209faa1e05c8513b4d9a43ec541
Gaites, I cannot understand well the code, but it seems to me that you updated something in an older version. In the doc I sent you yesterday are the last changes and corrections of testing, operation, adminitrative issues (including CyberCATS) and privacy.
Thanks!
2016-12-16 12:35 GMT-08:00 Gaites Swanson notifications@github.com:
Resolved by fa264c3 https://github.com/gaites/av-guidance/commit/fa264c39a3233209faa1e05c8513b4d9a43ec541
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gaites/av-guidance/issues/24#issuecomment-267689982, or mute the thread https://github.com/notifications/unsubscribe-auth/AXav2WBnCVzGrl0Pjx6QO2s9bycL_aoVks5rIvYpgaJpZM4LHcVn .
-- Aida.
Add "upon deployment and every two year thereafter" to top of Privacy section. As it currently reads, it only needs to be done once. The two year period can be changed if others feel strongly one way or another.