Common use of Pseudonymization Clause in Contracts

Pseudonymization. (1) Where possible, Juniper Data shall be pseudonymized such that Juniper Data cannot be attributed to a particular individual without use of additional information. (2) Pseudonymization may include hashing, randomizing, obfuscating, truncating, tokenizing, and removing identifiers. (3) The additional information needed to attribute the pseudonymized Juniper Data to an individual must be held in separate repositories by Supplier and subject to strict security measures to prevent combination of the information with the pseudonymized Juniper Data.

Appears in 1 contract

Sources: Data Protection Agreement

Pseudonymization. (1) Where possible, Juniper Data shall be pseudonymized such that Juniper ▇▇▇▇▇▇▇ Data cannot be attributed to a particular individual without use of additional information. (2) Pseudonymization may include hashing, randomizing, obfuscating, truncating, tokenizing, and removing identifiers. (3) The additional information needed to attribute the pseudonymized Juniper ▇▇▇▇▇▇▇ Data to an individual must be held in Juniper Networks Supplier Data Protection Agreement (C2P) 052824 10 separate repositories by Supplier and subject to strict security measures to prevent combination of the information with the pseudonymized Juniper Data▇▇▇▇▇▇▇ ▇▇▇▇.

Appears in 1 contract

Sources: Supplier Data Protection Agreement