Forum: CAT Tools Technical Help
Topic: TM anonymization (GDPR)
Poster: Michael Beijer
Post title: AI-powered GDPR data anonymisation (‘pseudonymisation’) tool?
I also know that Memsource recently released an artificial intelligence-powered non-translatables feature. See e.g. [url removed]
Given the fact that AI is popping up literally everywhere these days (Mark Zuckerberg hopes to use it to tackle the massive problem Facebook is currently having with its huge amount of questionable content), I wouldn't be surprised if someone was already working on something AI-powered in this area.
see also:
Pseudonymisation
The GDPR refers to pseudonymisation as a process that transforms personal data in such a way that the resulting data cannot be attributed to a specific data subject without the use of additional information. An example is ENCRYPTION, which renders the original data unintelligible and the process cannot be reversed without access to the correct decryption key. The GDPR requires for the additional information (such as the decryption key) to be kept separately from the pseudonymised data.
Another example of pseudonymisation is TOKENIZATION, which is a non-mathematical approach to protecting data at rest that replaces sensitive data with non-sensitive substitutes, referred to as tokens. The tokens have no extrinsic or exploitable meaning or value. Tokenization does not alter the type or length of data, which means it can be processed by legacy systems such as databases that may be sensitive to data length and type.
That requires much fewer computational resources to process and less storage space in databases than traditionally-encrypted data. That is achieved by keeping specific data fully or partially visible for processing and analytics while sensitive information is kept hidden.
Pseudonymisation is recommended to reduce the risks to the concerned data subjects and also to help controllers and processors to meet their data protection obligations (Recital 28).
Although the GDPR encourages the use of pseudonymisation to "reduce risks to the data subjects" (Recital 28), pseudonymised data is still considered personal data (Recital 26) and so remains covered by the GDPR.
( [url removed] #Pseudonymisation )
Topic: TM anonymization (GDPR)
Poster: Michael Beijer
Post title: AI-powered GDPR data anonymisation (‘pseudonymisation’) tool?
I also know that Memsource recently released an artificial intelligence-powered non-translatables feature. See e.g. [url removed]
Given the fact that AI is popping up literally everywhere these days (Mark Zuckerberg hopes to use it to tackle the massive problem Facebook is currently having with its huge amount of questionable content), I wouldn't be surprised if someone was already working on something AI-powered in this area.
see also:
Pseudonymisation
The GDPR refers to pseudonymisation as a process that transforms personal data in such a way that the resulting data cannot be attributed to a specific data subject without the use of additional information. An example is ENCRYPTION, which renders the original data unintelligible and the process cannot be reversed without access to the correct decryption key. The GDPR requires for the additional information (such as the decryption key) to be kept separately from the pseudonymised data.
Another example of pseudonymisation is TOKENIZATION, which is a non-mathematical approach to protecting data at rest that replaces sensitive data with non-sensitive substitutes, referred to as tokens. The tokens have no extrinsic or exploitable meaning or value. Tokenization does not alter the type or length of data, which means it can be processed by legacy systems such as databases that may be sensitive to data length and type.
That requires much fewer computational resources to process and less storage space in databases than traditionally-encrypted data. That is achieved by keeping specific data fully or partially visible for processing and analytics while sensitive information is kept hidden.
Pseudonymisation is recommended to reduce the risks to the concerned data subjects and also to help controllers and processors to meet their data protection obligations (Recital 28).
Although the GDPR encourages the use of pseudonymisation to "reduce risks to the data subjects" (Recital 28), pseudonymised data is still considered personal data (Recital 26) and so remains covered by the GDPR.
( [url removed] #Pseudonymisation )