# Ensuring GDPR compliance **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2020, 2:18pm UTC](https://discuss.elastic.co/t/ensuring-gdpr-compliance/236912 "2020-06-12T14:18:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![magnalite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnalite/32/69827_2.png) [@magnalite](https://discuss.elastic.co/u/magnalite)\ **Post date:** [June 12, 2020, 2:18pm UTC](https://discuss.elastic.co/t/ensuring-gdpr-compliance/236912/1 "2020-06-12T14:18:13Z")
We are looking to how to ensure we are GDPR compliant with the handling of our data however this is posing a real issue for us. We collect data of users from another (third party) service and can identify them via their user\_id. In the event of a GDPR request we would need to remove all mention of these user\_ids. The main issue is we store snapshots so would be unable to simply delete/modify every doc containing this id (unless there is some way to also remove it from within snapshots?). We have considered instead replacing these ids with fingerprints however we then have the problem of constantly having to manually convert between the fingerprints and user ids any time we want to query this data. Is there a way Kibana can automatically convert between the fingerprints and underlying user\_ids so for example we could directly query using the user\_id or have the user\_id field show the user\_id instead of the fingerprint (even though the underlying data is still the fingerprint)? Or any other solution to be GDPR compliant here without manual conversion? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 12, 2020, 11:38pm UTC](https://discuss.elastic.co/t/ensuring-gdpr-compliance/236912/2 "2020-07-12T23:38:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.