[ 
https://issues.apache.org/jira/browse/UNOMI-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007945#comment-17007945
 ] 

Serge Huber commented on UNOMI-260:
-----------------------------------

Hello Yakub, 

I understand your point of view, but this is a problem with the GDPR's unclear 
definition of "identifiable" information. From my understanding only 
identifiable data must be deleted, which is what is done. But I could 
understand wanted to go further than that and really deleting it.

I think there are two options to improve this:
- build your own plugin
- improving the existing privacy service implementation and providing a patch

For documentation, there isn't much, the best I can do is point you to the 
existing implementation that does "almost" what you need. You can find it here:

https://github.com/apache/unomi/blob/37e2eefea3a0c42b29b30164bcfa9941463a59fd/extensions/privacy-extension/services/src/main/java/org/apache/unomi/privacy/internal/PrivacyServiceImpl.java#L145

Basically instead of looping on events to update their relationship to an 
anonymous profile they could be deleted. But this will change all the reporting 
data which is what is currently being avoided by the current implementation.

Regards,
  Serge... 

> Delete events based on consent
> ------------------------------
>
>                 Key: UNOMI-260
>                 URL: https://issues.apache.org/jira/browse/UNOMI-260
>             Project: Apache Unomi
>          Issue Type: New Feature
>    Affects Versions: 1.5.0
>            Reporter: Yakub Ilyasov
>            Priority: Major
>             Fix For: 1.5.0
>
>
> If an user on a site consents to his data being gathered, but at a later time 
> does not want that anymore, it would be nice to have the possibility to 
> delete the data through a rule or perhaps an API call.
> At the moment unomi 1.5.0 has a feature to delete a profile, however there's 
> no clear way to delete the captured events related to that profile.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to