Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getlimina.ai/llms.txt

Use this file to discover all available pages before exploring further.

Limina supports over 50 unique entity types, including their counterparts in each of our Core Support languages as detailed on our Supported Languages page. The complete inventory of supported entity types is listed in the charts below, divided into four groups: PII (Personally Identifiable Information), Health Information, PCI (Payment Card Industry), and Beta Entity Types (see that section for information on how to enable Beta classes). In addition to our standard entities, Limina’s Scale plan offers custom entity types. For details, see Pricing. Note that some entities, such as NAME and LOCATION, also have subtypes. For instance, LOCATION_CITY is a subtype of LOCATION. This means that, in a phrase such as I live in Boston, the location name Boston will be detected as both LOCATION and LOCATION_CITY, with the more specific label (in this case, LOCATION_CITY) appearing in the output. Other entity types are groupings of related categories. For example, HEALTHCARE_NUMBER captures health plan beneficiary numbers and medical record numbers, both of which are outlined as identifiers in the HIPAA Safe Harbor provision. Similarly, NUMERICAL_PII covers a broad range of entity types such as MAC addresses and cookie IDs. While our entity types have English names, international variants are also redacted. For example, SSN covers American Social Security Numbers, as well as many equivalent identification numbers used in different regions worldwide, such as the Canadian Social Insurance Number or the German Sozialversicherungsnummer. Where applicable, this information can be viewed under More Details, including the names of entities supported in various languages and locales.
Supported Formats for Numerical EntitiesWhile many of the entity types de-identified by Limina are universal (e.g., EMAIL_ADDRESS, CREDIT_CARD), there are also some country-specific entity types, which vary regionally in terms of format, name, and/or function. For example, Canadian SIN is the regional equivalent of American SSN (both captured as SSN by Limina). Some entity types are also truly unique and do not have equivalents in North America (e.g., Indian Aadhaar number). Limina accounts for these cases — please refer to the list by country below for details on what is supported and the corresponding Limina classification.

​
Supported Regulations

Limina offers coverage of the following regulations: In addition, our entity categorizations are sensitive to unlisted data protection regulations. For example, when using our de-identification tool, you can select between a set of entities defined by the GDPR as personal data and a set of entities defined by the GDPR as sensitive data. Sensitive data is a more restricted subset of personal data that cannot be processed without a documented, lawful reason, according to Article 9 of the GDPR. In general, we recommend using the broader category GDPR. The relevant regulations for each entity type can be found in the charts below. You can learn more about the supported regulations and how to configure the de-identification service to meet your own needs in our Customizing Detection Guide.

​
Other Entity Groupings

In addition to the regulation entity groupings described above, you can select groupings for entity types related to health information (HEALTH_INFORMATION), payment card industry information (PCI), and corporate confidential information (CCI). Note that the PCI grouping includes only those entity types that are unique to PCI (BANK_ACCOUNT, CREDIT_CARD, CREDIT_CARD_EXPIRATION, CVV, ROUTING_NUMBER), although the PCI Data Security Standard (PCI DSS) also covers Cardholder Names and Primary Account Numbers (PAN). These fall under Limina’s more general entity types: NAME, NAME_GIVEN, NAME_FAMILY, and ACCOUNT_NUMBER. Because these entity types will detect all names and account numbers, not only those related to cardholders, they are not included in the PCI grouping, but they can be enabled in combination.

​
PII

Personally Identifiable Information
LabelDescriptionPolicy & Regulatory ComplianceAdded In
ACCOUNT_NUMBERCustomer account or membership identification number
;
Note: Full support for English; Multilingual support in progress		HIPAA_SAFE_HARBOR, CCI3.1.1
AGENumbers associated with an individual’s age
;
More details
When given in years, only the number is flagged, but both number and time unit are flagged when given in other units like months or weeks
Also includes age ranges:
; ;
GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.2.0
DATESpecific calendar dates, which can include days of the week, dates, months, or years
;

See also: DATE_INTERVAL, DOB
More details
If no calendar date is specified, days of the week are not flagged:
Indexical terms are not flagged:
;
HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, CCI1.0.0
DATE_INTERVALBroader time periods, including date ranges, months, seasons, years, and decades
; ;

See also: DATE, DOB

HIPAA_SAFE_HARBOR, CCI2.5.0
DOBDates of birth

See also: DATE, DATE_INTERVAL

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.4.0
DRIVER_LICENSEDriver’s permit numbers

See also: VEHICLE_ID
More detailsIncludes International Driving Permits (IDP) and Pilot’s licenses
CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI2.8.0
DURATIONPeriods of time, specified as a number and a unit of time
;


Note: Full support for English; Multilingual support in progress		3.1.1
EMAIL_ADDRESSEmail addresses

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI1.0.0
EVENTNames of events or holidays
;

1.0.0
FILENAMENames of computer files, including the extension or filepath

CCI2.0.0
GENDERTerms indicating gender identity, including slang terms.
;

CPRA, GDPR, GDPR Sensitive, APPI Sensitive3.9.0
HEALTHCARE_NUMBERHealthcare numbers and health plan beneficiary numbers
More detailsIncludes medical record numbers, health insurance policy/account numbers, and member IDs
CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.0.0
IP_ADDRESSInternet IP address, including IPv4 and IPv6 formats


CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.0.0
LANGUAGENames of natural languages
;

GDPR, GDPR Sensitive, APPI Sensitive1.0.0
LOCATIONMetaclass for any named location reference; See subclasses below
;
More details


GDPR, HIPAA_SAFE_HARBOR, APPI, CCI1.0.0
LOCATION_ADDRESSSpecific mailing addresses (full or partial)



CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI2.4.0
LOCATION_ADDRESS_STREETA building number and street name



CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI3.7.3
LOCATION_CITYMunicipality names, including villages, towns, and cities
; ;

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI2.4.0
LOCATION_COORDINATEGeographic positions using latitude/longitude

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI2.10.0
LOCATION_COUNTRYCountry names
;

GDPR, APPI, CCI2.4.0
LOCATION_STATEState, province, territory, or prefecture names
; ;

GDPR, APPI, CCI2.4.0
LOCATION_ZIPZip codes, postcodes, or postal codes
;
More detailsOptimized for various locales
CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI2.4.0
MARITAL_STATUSTerms indicating marital status
; ; ;

APPI Sensitive2.10.0
MONEYNames and/or amounts of currency
;

CCI1.0.0
NAMENames of individuals
;

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.0.0
NAME_FAMILYFamily or community names
;

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI2.13.0
NAME_GIVENGiven names/First names
;

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI2.13.0
NAME_MEDICAL_PROFESSIONALFull names of medical professionals

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI3.3.3
NUMERICAL_PIIAlphanumeric strings (MAC, Serial, Tracking IDs)
More detailsIncludes device serials, order IDs, and transaction numbers.
CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI1.0.0
OCCUPATIONJob titles or professions
; ; ;

QUEBEC_PRIVACY_ACT, APPI, CCI1.0.0
ORGANIZATIONNames of organizations or departments
; ;
More details
QUEBEC_PRIVACY_ACT, APPI, CCI1.0.0
ORGANIZATION_MEDICAL_FACILITYNames of medical facilities
;
QUEBEC_PRIVACY_ACT, APPI3.3.3
ORIGINNationality, ethnicity, or provenance
;

CPRA, GDPR, GDPR Sensitive, QUEBEC_PRIVACY_ACT, APPI Sensitive2.0.0
PASSPORT_NUMBERPassport numbers
;

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI2.9.0
PASSWORDPasswords, PINs, or access keys
;

CPRA, APPI, CCI1.4.0
PHONE_NUMBERTelephone or fax numbers

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.0.0
PHYSICAL_ATTRIBUTEDistinctive bodily attributes, including race
;

CPRA, GDPR, GDPR Sensitive, APPI Sensitive2.0.0
POLITICAL_AFFILIATIONTerms referring to a political party, movement, or ideology
;

CPRA, GDPR, GDPR Sensitive, QUEBEC_PRIVACY_ACT, APPI Sensitive2.9.0
RELIGIONTerms indicating religious affiliation
;

CPRA, GDPR, GDPR Sensitive, QUEBEC_PRIVACY_ACT, APPI Sensitive1.3.0
SEXUALITYTerms indicating sexual orientation
; ;

CPRA, GDPR, GDPR Sensitive, APPI Sensitive3.9.0
SSNSocial Security Numbers or equivalents
;
More details
Includes international equivalents. Flags mentions of complete numbers and last four digits.
CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.0.0
TIMEExpressions indicating clock times
;

CCI1.0.0
URLInternet addresses

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, CCI1.0.0
USERNAMEUsernames, login names, or handles
;

CPRA, GDPR, APPI1.3.0
VEHICLE_IDVINs, serial numbers, and license plates
;

See also: DRIVER_LICENSE

CPRA, GDPR, HIPAA_SAFE_HARBOR, APPI, CCI2.11.0
ZODIAC_SIGNNames of Zodiac signs
;

2.1.2

​
Health Information

LabelDescriptionPolicy & Regulatory ComplianceAdded In
BLOOD_TYPEBlood types

CPRA, GDPR, QUEBEC_PRIVACY_ACT2.0.0
CONDITIONNames of medical conditions, diseases, syndromes, deficits, disorders
; ;

CPRA, GDPR, QUEBEC_PRIVACY_ACT, APPI Sensitive2.0.0
DOSEMedically prescribed quantity of a medication

2.14.0
DRUGMedications, vitamins, and supplements
; ;

CPRA, GDPR, QUEBEC_PRIVACY_ACT, APPI Sensitive, CCI2.0.0
INJURYBodily injuries, including mutations, miscarriages, and dislocations
;

CPRA, GDPR, QUEBEC_PRIVACY_ACT, APPI Sensitive2.0.0
MEDICAL_PROCESSMedical processes, including treatments, procedures, and tests
;

CPRA, GDPR, QUEBEC_PRIVACY_ACT, APPI Sensitive, CCI2.0.0
STATISTICSMedical statistics

QUEBEC_PRIVACY_ACT2.0.0

​
PCI

LabelDescriptionPolicy & Regulatory ComplianceAdded In
BANK_ACCOUNTBank account numbers and international equivalents, such as IBAN

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI2.3.0
CREDIT_CARDCredit card numbers

More details
Includes debit, ATM, Direct Debit, PrePay, Charge Cards, and support for cards that do not have 16 digits such as American Express or China UnionPay cards. Flags mentions of complete numbers as well as the last four digits only.
CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI1.0.0
CREDIT_CARD_EXPIRATIONExpiration date of a credit card
;

CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI1.4.0
CVV3- or 4-digit card verification codes and equivalents
More details
Includes institution-specific variants:

American Express: CID (card ID), CVD (card verification data) CSC / 3CSC (card security code)
China UnionPay: CVN (card validation number)
CIBC Mastercard: SPC (signature panel code)
Discover: CID (card ID), CVD (card verification data)
ELO (Brazil): CVE (Elo verification code)
JCB (Japan Credit Bureau): CAV (card authentication value)
Mastercard: CVC (card validation code)
VISA: CVV (card verification value)
CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, APPI, CCI1.4.0
ROUTING_NUMBERRouting number associated with a bank or financial institution
More details
Includes international equivalents: Canadian & British sort codes, Australian BSB numbers, Indian Financial System Codes, Branch/transit numbers, Institution numbers, and Swift codes
CCI2.3.0

​
Beta Entity Types

Note that Beta support for the following entity types is currently only available with our English models.
LabelDescriptionPolicy & Regulatory ComplianceAdded In
CREDIT_SCOREA three-digit rating of an individual’s creditworthiness and ability to obtain credit (e.g., FICO scores, VantageScores)
APPI, CPRA, GDPR, QUEBEC_PRIVACY_ACT4.3.1
CORPORATE_ACTIONAny action a company takes that could affect its stock value or its shareholders
CCI3.5.0
DATE_OF_DEATHFull or partial date that is explicitly stated to be the date of an individual’s death (does not include time of death)
APPI, CPRA, GDPR, HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT4.3.0
DAYSub-part of a date representing the day
;
HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, CCI4.0.2
EFFECTWords or phrases describing a medical symptom, effect, or side-effect
4.0.0-final
FINANCIAL_METRICTerms referring to financial metrics or financial ratios
CCI3.5.0
MEDICAL_CODECodes belonging to medical classification systems such as SNOMED, ICD-10, NDC, etc.

CPRA, GDPR, GDPR Sensitive, QUEBEC_PRIVACY_ACT, APPI Sensitive3.7.0
MONTHSub-part of a date representing the month
;
HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, CCI4.0.2
ORGANIZATION_IDUnique numerical or alphanumerical codes assigned to corporations and organizations (e.g., VAT numbers, stock ticker symbols)QUEBEC_PRIVACY_ACT, APPI, CCI4.0.1
PRODUCTNames or model numbers of items made by an organization; includes intangible products like software and games
CCI3.5.0
PROJECTNames or alphanumerical codes of corporate projects
CCI4.0.1
TRENDA description of the “quality” or the direction in which a financial measurement is going
CCI3.5.0
YEARSub-part of a date representing the year
;
HIPAA_SAFE_HARBOR, QUEBEC_PRIVACY_ACT, CCI4.0.2

​
Enabling Beta Entity Types

Each of the beta entities must be enabled explicitly in the deid request. This can be done using the entity_detection.entity_types field. For example, the following request will redact only TREND, FINANCIAL_METRIC and CORPORATE_ACTION from the provided text: 
{
   "text": [
      "In the last quarter, our revenues grew faster which led us to acquire one of our smaller competitors"
   ],
   "link_batch": true,
   "processed_text": {
      "type": "MARKER",
      "pattern": "[BEST_ENTITY_TYPE]"
   },
   "entity_detection": {
      "entity_types": [
        { "type": "ENABLE", "value": ["TREND", "FINANCIAL_METRIC", "CORPORATE_ACTION"]}
      ]
   }
}