Data Security Policy

Data Security Policy configuration.

This section describes the Policy configuration used by the AI Developer Edition API Service.

The superuser has all permissions, that is, protect, unprotect, and reprotect operations. Users assigned the admin role will receive protected data when performing an unprotect operation, except in the case of the text data elements, which will return null. All other user roles will receive null as the output for any unprotect operation.

Policy Definition

Generic Data Elements

Data ElementMethodUse CaseUTF SetLPPPeIVRole
AdminFinanceMarketingHR
PUPUPUPU
datetimeTokenizationA date or datetime string. Formats accepted: YYYY/MM/DD HH:MM:SS and YYYY/MM/DD. Delimiters accepted: /, - (required).N/AN/AN/ANo
datetime_ycTokenizationA 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/AN/AN/ANo
intTokenizationAn integer string (4 bytes).NumericNoNoYes
numberTokenizationA numeric string. May produce leading zeroes.NumericYesNoYes
stringTokenizationAn alphanumeric string.Latin + NumericYesNoYes
textEncryptionA long string (e.g., a comment field) using any character set. Use hex or base64 encoding to utilize.AllNoNoYes

PCI DSS Data Elements

Data ElementMethodUse CaseUTF SetLPPPeIVRole
AdminFinanceMarketingHR
PUPUPUPU
ccnTokenizationCredit card numbers.NumericNoNoYesX
ccn_binTokenizationCredit card numbers. Leaves 8-digit BIN in the clear.NumericNoNoYesX
ibanTokenizationIBAN numbers. Preserves the length, case, and position of the input characters but may create invalid IBAN codes.Latin + NumericYesYesNoX
iban_ccTokenizationIBAN numbers. Leaves letters in the clear.Latin + NumericNoNoYesX

PII Data Elements

Data ElementMethodUse CaseUTF SetLPPPeIVRole
AdminFinanceMarketingHR
PUPUPUPU
addressTokenizationStreet namesLatin + NumericYesNoYes
cityTokenizationTown or city nameLatinYesNoYes
emailTokenizationEmail address. Leaves the domain in the clear.Latin + NumericYesNoYes
ninTokenizationNational Insurance Number. Preserves the length, case, and position of the input characters but may create invalid NIN codes.Latin + NumericYesYesNo
nameTokenizationPerson's nameLatinYesNoYes
passportTokenizationPassport codes. Preserves the length, case, and position of the input characters but may create invalid passport numbers.Latin + NumericYesYesNo
phoneTokenizationPhone number. May produce leading zeroes.Latin + NumericYesNoYes
postcodeTokenizationPostal codes with digits and characters. Preserves the length, case, and position of the input characters but may create invalid post codes.Latin + numericYesYesNo
ssnTokenizationSocial Security Number (US)Latin + NumericYesNoYes
zipcodeTokenizationZip codes with digits only. May produce leading zeroes.NumericYesNoYes

PII Data Elements

Data ElementMethodUse CaseUTF SetLPPPeIVRole
AdminFinanceMarketingHR
PUPUPUPU
address_deTokenizationStreet names (German)Latin + German + NumericYesNoYes
address_frTokenizationStreet names (French)Latin + French + NumericYesNoYes
city_deTokenizationTown or city name (German)Latin + GermanYesNoYes
city_frTokenizationTown or city name (French)Latin + FrenchYesNoYes
name_deTokenizationPerson's name (German)Latin + GermanYesNoYes
name_frTokenizationPerson's name (French)Latin + FrenchYesNoYes

LEGEND

  • eIV: External IV
  • LP: Length Preservation
  • PP: Position Preservation
  • P: User group can protect data
  • U: User group can unprotect data

Last modified : November 21, 2025