Defines which fields of a data entity contain personal data and which field identifies the data subject (owner of the data). Fields configured as personal data are stored separately with encryption and special data residency, are returned masked by default when retrieving documents, and participate in data subject requests such as the right to be forgotten.

ℹ️ Personal data configuration is set at the data entity level, not within individual schemas. This avoids conflicts when multiple schemas coexist for the same data entity.

⚠️ Saving a new configuration triggers a background process that re-tokenizes all existing documents in the entity. While this process runs, this endpoint is locked for the affected entity for up to 12 hours to prevent concurrent reprocessing jobs.

Permissions

Any user or API key must have at least one of the appropriate License Manager resources to be able to successfully run this request. Otherwise they will receive a status code 403 error. These are the applicable resources for this endpoint:

There are no applicable predefined roles for this resource list. You must create a custom role and add at least one of the resources above in order to use this endpoint.To learn more about machine authentication at VTEX, see Authentication overview.

❗ To prevent integrations from having excessive permissions, consider the best practices for managing API keys when assigning License Manager roles to integrations.