At Elucidate, we anonymise and pseudonymise your data. It is important to note that there is a difference between pseudonymised and anonymised data.
Pseudonymisation consists of replacing one data attribute (typically a unique data attribute) in a record by another. This reduces the linkability of a dataset with the original identity of a data subject. You should note, pseudonymisation is a useful security measure but not a method of anonymisation.
Anonymisation consists of a process by which personal data is irreversibly altered in such a way that personal data can no longer be identified directly or indirectly.
To learn about which data needs pseudonymisation, please review our Data Protocols; here you will find detail on which pseudonymisation algorithms can be used ("SHA-3" is our preferred method).
Anonymisation of your data
After, a pre-computed query is used to convert the pseudonymised data into metadata and our proprietary algorithm generates scores based on the resulting metadata.
The selected pseudonymised data together with public data is subject to our internal eventualities. An eventuality is a test performed on your pseudonymised data set, and can be evaluated as either “True” or “False”. This process forms part of our anonymisation technique.
For example, if an eventuality test check “is the percentage of high risk customers doing transactions during the past month > 10%“, the algorithm takes only the value “True” of “False”.
Therefore, EFI score per theme and the EFI rating are based on metadata obtained as a result of Elucidate´s anonymisation techniques.
This metadata does not constitute personal data.
Detailed information is available in the User Agreement signed between Elucidate and your institution and in our Benchmark Statement available on our webpage (Benchmark Statement).