SecureLink Encryption:

SecureLink encryption is used during the SecureLink de-identification process to protect direct identifiers that are transmitted and later converted to de-identified joining keys at a remote recipient. It uses homomorphic encryption, an advanced form of encryption that allows computation on output ciphertexts, which makes it suitable for later use with SecureLink Tokenization.

SecureLink encryption is performed on-site at a SecureLink contributor organization that owns the source data. The direct identifiers are converted to a doubly-encrypted form called a transit token that is used for safely transmitting the dataset to the ultimate recipient. The double encryption means that as the transit token is moved through the SecureLink process, the underlying direct identifier is never visible in raw form.

A variety of options are available to implement SecureLink encryption at a contributor organization. It can be applied as part of a Privitar Policy by the execution engines of the Privitar Platform, or alternatively, lightweight command-line and SDK clients are available that do not require a full Privitar deployment.

Return to glossary