Product idea with a gdpr/data governance & security flavour:
Do you think there is value in allowing event properties to be tagged up with hash/encrypt/boundary/mask booleans (per source) so that we can control what values need to be acted upon at the start of the data pipeline to de-identify and rather than having to keep this knowledge elsewhere we can control it at source within Avo. So alongside the event properties we get an event deidentification key value array with props who's values need to be acted upon before they land downstream.
Created by Solvi Logason
·