Data Security Policy
Data Security Policy configuration
This section describes the Policy configuration used by the API Playground. All listed data elements can be used when calling the private endpoints.
Policy Definition
Generic Data Elements
Data Element | Method | Use Case | UTF Set | LP | PP | eIV | Role | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Admin | Finance | Marketing | HR | |||||||||||
P | U | P | U | P | U | P | U | |||||||
datetime | Tokenization | A date or datetime string. Formats accepted: YYYY/MM/DD HH:MM:SS and YYYY/MM/DD. Delimiters accepted: /, - (required). | N/A | N/A | N/A | No | ✓ | X | X | X | X | ✓ | X | X |
datetime_yc | Tokenization | A date or datetime string. Formats accepted: YYYY/MM/DD HH:MM:SS and YYYY/MM/DD. Delimiters accepted: /, - (required). Leaves the year in the clear. | N/A | N/A | N/A | No | ✓ | X | X | X | X | ✓ | X | X |
int | Tokenization | An integer string (4 bytes). | Numeric | No | No | Yes | ✓ | X | X | X | X | ✓ | X | X |
number | Tokenization | A numeric string. May produce leading zeroes. | Numeric | No | No | Yes | ✓ | X | X | X | X | ✓ | X | X |
string | Tokenization | An alphanumeric string. | Latin + Numeric | No | No | Yes | ✓ | X | X | X | X | ✓ | X | X |
long_text | Encryption | A long string (e.g., a comment field) using any character set. Use hex or base64 encoding to utilize. | All | No | No | Yes | ✓ | X | X | X | X | ✓ | X | X |
PCI DSS Data Elements
Data Element | Method | Use Case | UTF Set | LP | PP | eIV | Role | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Admin | Finance | Marketing | HR | |||||||||||
P | U | P | U | P | U | P | U | |||||||
ccn | Tokenization | Credit card numbers. | Numeric | No | No | Yes | ✓ | X | X | ✓ | X | X | X | X |
ccn_bin | Tokenization | Credit card numbers. Leaves 8-digit BIN in the clear. | Numeric | No | No | Yes | ✓ | X | X | ✓ | X | X | X | X |
iban | Tokenization | IBAN numbers. Preserves the length, case, and position of the input characters but may create invalid IBAN codes. | Latin + Numeric | Yes | Yes | No | ✓ | X | X | ✓ | X | X | X | X |
iban_cc | Tokenization | IBAN numbers. Leaves letters in the clear. | Latin + Numeric | Yes | Yes | Yes | ✓ | X | X | ✓ | X | X | X | X |
PII Data Elements
Data Element | Method | Use Case | UTF Set | LP | PP | eIV | Role | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Admin | Finance | Marketing | HR | |||||||||||
P | U | P | U | P | U | P | U | |||||||
address | Tokenization | Street names | Latin + Numeric | No | No | Yes | ✓ | X | X | ✓ | X | X | X | ✓ |
city | Tokenization | Town or city name | Latin | No | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
dob | Tokenization | A date string. Formats accepted: YYYY/MM/DD and YYYY/MM/DD. Delimiters accepted: /, - (required). | N/A | N/A | No | No | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
dob_yc | Tokenization | A date string. Formats accepted: YYYY/MM/DD and YYYY/MM/DD. Delimiters accepted: /, - (required). Leaves the year in the clear. | N/A | N/A | No | No | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
Tokenization | Email address. Leaves the domain in the clear. | Latin + Numeric | No | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ | |
nin | Tokenization | National Insurance Number. Preserves the length, case, and position of the input characters but may create invalid NIN codes. | Latin + Numeric | Yes | Yes | No | ✓ | X | X | X | X | X | X | X |
name | Tokenization | Person's name | Latin | No | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
passport | Tokenization | Passport codes. Preserves the length, case, and position of the input characters but may create invalid passport numbers. | Latin + Numeric | Yes | Yes | No | ✓ | X | X | X | X | X | X | X |
phone | Tokenization | Phone number. May produce leading zeroes. | Latin + Numeric | Yes | No | Yes | ✓ | X | X | X | X | X | X | X |
postcode | Tokenization | Postal codes with digits and characters. Preserves the length, case, and position of the input characters but may create invalid post codes. | Latin + numeric | Yes | Yes | No | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
ssn | Tokenization | Social Security Number (US) | Latin + Numeric | Yes | No | Yes | ✓ | X | X | X | X | X | X | X |
zipcode | Tokenization | Zip codes with digits only. May produce leading zeroes. | Numeric | Yes | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
PII Data Elements
Data Element | Method | Use Case | UTF Set | LP | PP | eIV | Role | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Admin | Finance | Marketing | HR | |||||||||||
P | U | P | U | P | U | P | U | |||||||
address_de | Tokenization | Street names (German) | Latin + German + Numeric | No | No | Yes | ✓ | X | X | ✓ | X | X | X | ✓ |
address_fr | Tokenization | Street names (French) | Latin + French + Numeric | No | No | Yes | ✓ | X | X | ✓ | X | X | X | ✓ |
city_de | Tokenization | Town or city name (German) | Latin + German | No | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
city_fr | Tokenization | Town or city name (French) | Latin + French | No | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
name_de | Tokenization | Person's name (German) | Latin + German | No | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
name_fr | Tokenization | Person's name (French) | Latin + French | No | No | Yes | ✓ | X | X | ✓ | X | ✓ | X | ✓ |
LEGEND
eIV
External IVLP
Length PreservationPP
Position PreservationP
User group can protect dataU
User group can unprotect data
Last modified February 21, 2025