Roadmap for this project?

[federicobond]

Hi! Congrats for taking the initiative to implement GDPR compliance helpers for Django apps. I would love to learn more about the scope and licensing of your project because I have started working on something similar and it might be attractive to pool efforts together (the name django-gdpr on PyPI also makes it well positioned to become the go-to solution for GDPR compliance).

Looking forward to hearing from you!

[koslib]

Hello - Kostas from Intelligems here. We are also working on an internal solution for GDPR compliance in Django projects, and it'd be super interesting to join forces if/wherever needed in order to produce something good.

Also looking forward to hear more details about this project!

[koslib]

Hello @druids, any news here?

[LukasRychtecky]

@matllubos will say more about this.

[matllubos]

Hi, firstly I would like to apologize for my response time. Notifications of the druid group are not forwarded to my e-mail. I will fix it.

We are trying to implement a library that solves our major issues with GDPR to the end of May which is collecting purposes for the storage and processing of personal data.

Our roadmap is:

1. end of May - complete models and process for maintaining purposes for storing personal data
2. end of June - implement anonymization, because every purpose can be lost (expiration or with another way)
3. next work is still open because, GDPR has more issues (Log administrators, anonymize test data, etc.)

There is current domain model of the solution:

GDPR-model

Any help or review will be welcome.

[federicobond]

I did some work on consent handling recently, right now I have the following models:

ConsentStatement
    text : CharField

Consent:
   statement : ForeignKey(ConsentStatement)
   provided : DateTimeField
   revoked : DateTimeField
   user : ForeignKey(User)

This let's you record when consent was given or revoked and what words were presented to the user to get that consent.

[matllubos]

I think that word "Consent" is not the right word for GDPR because you don't need agreement for storing customer data in some cases (for example, the customer has a debt to you). Therefore we use the word "purpose" (purpose for storing data)

But your schema is very similar to GDPR-model in general.