wildfish/django-gdpr-assist

Improve support for models to be exported but not anonymised

radiac opened this issue · 0 comments

There are sometimes models which contain PII so need to be exported, but anonymising them doesn't make sense - mailing lists for example.

We could link the post-anonymise event to delete those objects, but that sounds like it could be unexpected and dangerous.

Lets look at adding a can_anonymise=True flag to the PrivacyMeta class; if it's True we could either:

  • anonymise everything else and show a warning that it hasn't been anonymised
  • show a confirmation page asking if they want to leave or delete those objects (with a standard admin warning about what else will be cascade-deleted).

We should also make can_anonymise=False models not get the anonymised field option - looks odd in an AdminModel which shows all fields.