Skip to main content
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

Health Information

PCI

Beta Entity Types

Note that Beta support for the following entity types is currently only available with our English models.

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: