CodeForPhilly / CodeForPhilly/laddr
Show Cookie declaration and ask for consent before user tracking
- Lenguaje dominante
- Smarty
- Estrellas
- 62
- Forks
- 34
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Due to GDPR and EU Data Protection law, beside previously required showing cookie banner (#192), we now have to ask for user consent before tracking cookies are activated.
The following requirements in the General Data Protection Regulation (GDPR) and the ePrivacy Directive (ePR) has to be implemented:
* Prior consent on other than strictly necessary cookies (ePR)
* Prior consent on personal data (GDPR)
* Personal data is transmitted to 'adequate countries' only (GDPR)
Please also make sure to:
- Inform your visitors in plain language about the purpose of your cookies and trackers before setting other than strictly necessary cookies (ePR)
- Provide options for the visitor to change or withdraw a consent (GDPR/ePR)
- Have a mechanism in place to log and prove consents (GDPR)
- Map and document data streams performed by third parties (GDPR)
- Configure your consent method to use explicit/active consent when processing sensitive personal data on your website (GDPR)
- Provide the identity and contact details of the data controller in your company (GDPR)
- Disclose that the visitor is entitled to access, correct, delete and limit processing of personal data (GDPR)
- Disclose that the visitor is entitled to receive personal data so that they can be used by another processor (GDPR)
- Disclose that the visitor has the right to lodge a complaint with a supervisory authority (GDPR)
- Inform about the occurrence of automatic decisions, including profiling (GDPR)
Some useful examples:
- http://cookiebot.com
- https://github.com/schlos/tarteaucitron.js
- https://github.com/schlos/consentcookie
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Empieza con el trabajo del banner de cookies mencionado en #192 e identifica dónde se activan las cookies de seguimiento y los flujos de datos de terceros. Compara esos puntos de entrada con los requisitos de GDPR y ePrivacy indicados. Para darlo por completado se necesitan finalidades documentadas, consentimiento previo, mecanismos de retirada y registro, un mapeo de los flujos de datos y las divulgaciones de privacidad requeridas.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- security, web-dev
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 20/100