Manages consent for communication with GDPR in mind
Manages consent for email communication with GDPR in mind
- An app for Django - pip install django-consent
- Free software: GNU General Public License v3
- GDPR-friendly models, supporting deletion and anonymization
- Views for unsubscribing
- Utility functions for generating unsubscribe links
- Utility functions for creating consent
- Form mixins for consent
- Abuse-resistent: Someone cannot mass-unsubscribe or otherwise abuse endpoints.
- Denial of Service: Endpoints do not store for instance infinite amounts of opt-outs.
- Can or should consent expire? Currently, we are capturing the creation date of a consent, but we are not using expiration dates.
- Would some email addresses qualify as non-individual, and thus require different types of consent? For instance, should company/customer email addresses be stored in a way so that certain consents become optional? Currently, all consent is explicit and stored that way.
- Should django-consent also capture purpose and more generic ways of storing private data? Currently, we are only capturing email-related consent.
- Do we want to store consent indefinitely? No. If consent is withdrawn, we should delete the entire consent. A person would have to create an entirely new consent.
- Should we store op-outs indefinitely? Partly. In django-consent, we do this because we want opt-outs to remain in effect. But we store a hash of the email such that it we don’t keep a record of emails. Experience with Mailchimp and similar systems tell us that marketing and other eager types will keep re-importing consent and forget to care about previous opt-outs. By storing an opt-out, we can ensure to some degree that mistakes made will not result in clearly non-consensual communication.
Other considerations: Privacy by Design
Your application needs the ability to easily delete and anonymize data. Not just because of GDPR, but because it’s the right thing to do.
No matter the usage of django-consent, you still need to consider this:
- Right to be forgotten: Means that at any time, you should be able to delete the data of any person. Either by request or because the purpose of collecting the data is no longer relevant.
- Anonymize data: When your consent to collect data associated to a person expires and if you need to keep a statistical record, the data must be completely anonymized. For instance, if they made an order in your shop and your stored data about shopping cart activity, you’ll have to delete or anonymize this data.
In any implementation, you should consider how you associate personally identifiable information. This can be a name, email, IP address, physical address and unique combinations (employer, job, department).
In order to design a Django project for privacy, consider the following:
- Right to be forgotten:
- Deletion should be implemented through deletion of a User instance. Do not relate personally identifiable data in other ways.
- All model relations to User.id should use on_delete=models.CASCADE
- When a relation to User.id has null=True and is nullified, then remaining data in the model should not identify the person. You should design your models to only allow null values for User relations when in fact the remaining data in the row and its relations cannot be used to identify the person from your data.
# Enable your Python environment (example) workon myproject # Installation pip install django-consent-temp
Now go to your Django project’s settings and add:
INSTALLED_APPS = [ # ... 'django_consent', ]
To use unsubscribe views, add this to your project’s urls.py:
urlpatterns = [ # ... path('consent/', include('django_consent.urls')), ]
To install an editable version into a project, activate your project’s virtualenv and run this:
# Installs an editable version of django-consent pip install -e . # Installs an editable version of django-consent's development requirements pip install -e '.[develop]' # Enables pre-commit pre-commit install
django-consent 0.2 (2011)
This project is not a fork of the old django-consent but is a new project when the PyPi repo owners gave us permissions to take over. The former package is archived here: https://github.com/d0ugal/django-consent
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for django_consent-0.9.dev0-py3-none-any.whl