Data and privacy for Face
This article provides some high level details regarding how Face processes data provided by customers. Face was designed with compliance, privacy, and security in mind. Biometric identification technologies are intended to process personal data that may be considered sensitive personal information. Please be aware that the laws governing biometric recognition technologies often vary internationally and domestically, including at the federal, state and local levels. In addition to regulating allowed use cases, some jurisdictions impose special legal requirements for the permissions governing collection, transfer, online processing, and storage of biometric data, particularly when used for identification or verification. Before using Face and our Azure services for the collection, transfer, processing and storage of any data subject’s biometric data, you must ensure compliance with the relevant legal requirements that apply to your service application.
- Inform people in your locations with conspicuous disclosure about use of image data and use of facial recognition.
- Comply with all applicable laws and regulations in your jurisdiction.
Note
For our customer’s convenience, please consider utilizing the following disclosure regarding Microsoft's role when you use of Azure AI services Face with your end users: [Company] uses Microsoft face recognition technology to process [Company’s] users’ biometric data as its service provider (“Processor”). Microsoft may process and store face templates for the purposes of providing face verification and/or identification services on [Company]’s behalf, and only as instructed by [Company]. Microsoft will store this data as long as [Company] requests, which shall be no longer than a limited grace period after the date when (i) [Company] ceases to have a relationship with Microsoft or (ii) when [Company] requests deletion.
What data does Face process, how long is it retained and what protections are in place?
Descriptions of Face API processes use the key terms defined here.
Face maintains GDPR data processor classification across all supported regions.
| Face API operation | Feature | Input data | Output | Retention of face template | Customer controls for data retention |
|---|---|---|---|---|---|
| Detect | Detects faces within images Includes the following parameters:
|
Image (binary or URL download) | Coordinates of the bounding box location(s) of the face(s) are generalized regardless of who is in the image. Cannot be used to recognize faces or otherwise uniquely identify individuals. | No template is created | N/A |
| Detect | Returns a face ID to be used for the following Face API calls: Identify API, Verify API, Group API and Find Similar API. Face ID is only supported for customers who have been approved for access. Includes the following parameters:
|
Image (binary or URL download) | FaceID, a randomly generated identifier assigned to a new face feature template for each image submitted to Face API. The FaceID changes for each image submitted, even if the image is of the same face. There's no matching or comparison in Detect API with FaceID. | The face template expires within 24 hours. | The FaceId template expiration date can be adjusted to less than 24 hours with the faceIdTimeToLive parameter. |
| Verify | Performs a one-to-one match between a FaceID and either another FaceID, a PersonGroupPerson, a LargePersonGroupPerson, or a PersonDirectoryPerson. Scenario: Facial Verification and Facial Identification (approved customers only) |
Both of:
|
Determines whether a FaceID is a match compared to the other FaceID. | The FaceID array and associated face template created with Face Detect’s FaceID feature expire within 24 hours. The input PersonGroupId, LargePersonGroupId, or PersonDirectory face templates will not expire. |
The FaceId template expiration date can be adjusted to less than 24 hours with faceIdTimeToLive. PersonGroupId, LargePersonGroupId, PersonIds, and their persistedFaceIds can be managed and deleted by the customer with the following APIs: Person deletion (Deleting a Person also deletes their associated Face templates):
|
| Identify | Given a FaceID, performs a 1-to-N search for similar-looking persons in a FaceID array, a personGroupId, a largePersonGroupId, a dynamicPersonGroupId, or a list of PersonDirectory persons. Scenario: Facial Identification (Approved Customer Only) |
|
For each FaceID provided, a list of candiate PersonIds from the corresponding input search group. | The faceID array and associated face template created with Face Detect’s FaceId feature expire within 24 hours. The input PersonGroupId created by PersonGroup Create API contains PersonGroupPersons with associated persistedFaceId face templates that will not expire. The input LargePersonGroupId created by LargePersonGroup Create API contains LargePersonGroupPersons with associated persistedFaceIds face templates that will not expire. The input PersonDirectory Persons created by PersonDirectory Person Create API and referenced by DynamicPersonGroup Create contains PersonDirectoryPersons with associated persistedFaceIds face templates that will not expire. |
The FaceIDs array template's expiration can be adjusted to less than 24 hours with the Detect API query parameter faceIdTimeToLive faceListId; largeFaceListId; and persistentFaceIds can be managed and deleted by customers with the Face API commands. |
| Find Similar | Given a face, searches for similar-looking faces from a faceID array, a faceListId or a largeFaceListId. Depending on the type of Customer request (for a faceID array or a faceListID), the results returned to customers contain faceIDs or persistedFaceIDs ranked by similarity. Scenario: Facial Identification (Approved Customer Only) |
The FaceID or FaceID Array From Detect API returnFaceId=true faceListID; largeFaceListID |
The matching persistedFaceID, with confidence score | The input faceID array may contain multiple faces detected by Detect API. These faceID array and associated face template expires within 24 hours. The input faceListID is created by FaceList – Create API containing persistedFaceIDs and associated face template that will not expire. The input largeFaceListID is created by LargeFaceList – Create API containing persistedFaceIDs and associated face template that will also not expire. |
FaceIDs array template expiration can be adjusted to less than 24 hours with Detect API query parameter faceIdTimeToLive facelistID; LargeFaceListID; and PersistentfaceIDs can be managed and deleted by Customers via the Face API commands. |
| Group | Group similar faces together Scenario: Facial Identification (Approved Customer Only) |
FaceID Array From Detect API returnFaceId=true |
One or more groups of faceIDs | The grouping of faceID’s is not persisted beyond request. The faceID array and associated face template expires within 24 hours. |
FaceIDs array template expiration can be adjusted to less than 24 hours with Detect API query parameter faceIdTimeToLive |
| FaceList LargeFaceList |
Data structures for storing face templates in FaceLists or LargeFaceLists for use with future FindSimilar or Verify operations. Scenario: Facial Verification & Facial Identification (Approved Customer Only) |
Image | persistedFaceIds | The input faceListID is created by FaceList – Create API containing persistedFaceIDs and associated face template that will not expire. The input largeFaceListID is created by LargeFaceList – Create API containing persistedFaceIDs and associated face template that will also not expire. |
facelistID; LargeFaceListID; and PersistentfaceIDs can be managed and deleted by customer using the corresponding REST CRUD APIs for each data structure. |
| PersonGroup LargePersonGroup PersonDirectory |
Data structures for storing multiple face templates per Preson. PersonGroup(Persons), LargePersonGroup(Persons), PersonDirectory(Persons) are for use with future Identify or Verify operations. Scenario: Facial Verification & Facial Identification (Approved Customer Only) |
Image | persistedFaceIds | The input PersonGroupId created by PersonGroup - Create API contains PersonGroupPersons with associated persistedFaceIds face templates that will not expire. The input LargePersonGroupId created by LargePersonGroup - Create API contains LargePersonGroupPersons with associated persistedFaceIds face templates that will not expire. The input PersonDirectory Persons created by PersonDirectory Person - Create API and referenced by DynamicPersonGroup - Create API contains PersonDirectoryPersons with associated persistedFaceIds face templates that will not |
PersonGroupPersonIds, LargePersonGroupPersonIds, and PersonDirectoryPersonIds can be managed and deleted by customer using the corresponding REST CRUD APIs for each data structure. |
| Detect Liveness Session | Detects whether face within an image is a genuine presentation instead of a spoofing specimen Scenario: Liveness Detection (Approved Customers Only) |
deviceCorrelationId: a non-PII identifier provided by the customer to link sessions from the same device together over a 48-hour period. Liveness Images |
SessionId: a random generated Identifier (GUID), history of session-associated operations (such as facial liveness detection) are linked. Authorization Token: for a client device to authenticate to Face API directly. |
No face template is created. | Session data is automatically deleted after 48 hours or may be deleted by the customer using DetectLivenessvSession - Delete API |
| Liveness Detection | Detects whether face within an image is a genuine presentation instead of a spoofing specimen Scenario: Liveness Detection (Approved Customers Only) |
Liveness Images | Classification result of either live or spoofed faces | No face template is created. | N/A |
| Detect Liveness With Verify Session | Detects whether face within an image is a genuine presentation instead of a spoofing specimen and compares it to a known image of the person providing a face match confidence score to help ensure identity of the individual is the same. Scenario: Liveness Detection & Facial Verification (Approved Customers Only) |
deviceCorrelationId: a non-PII identifier provided by the customer to link sessions from the same device together over a 48 hour period. Liveness Images Reference Image |
SessionId: a random generated Identifier (GUID), history of session-associated operations (such as facial liveness detection) are linked. Authorization Token: for a client device to authenticate to Face API directly. Face Rectangle and classification result of either live or spoofed faces Target Rectangle of reference image and confidence score of match |
If Verification reference image is provided during DetectLivnessWithVery Session - Create API, Face templates is stored for up to 48 hours or session is deleted by the customer. | Session data is automatically deleted after 48 hours or may be deleted by the customer using DetectLiveness Session - Delete API |
| Liveness Detection with Verify | Detects whether face within an image is a genuine presentation instead of a spoofing specimen and compares it to a known image of the person providing a face match confidence score to help ensure identity of the individual is the same. Scenario: Liveness Detection & Facial Verification (Approved Customers Only) |
Liveness Images Reference Image |
Face Rectangle and classification result of either live or spoof face Target Rectangle of reference image and confidence score of match |
If Verification reference image is provided during DetectLivnessWithVery Session - Create API, Face templates is stored for up to 48 hours or session is deleted by the customer. If Verification Image is provided at the same time the liveness payload is provided, then templates are not stored past the length of the call. |
Session data is automatically deleted after 48 hours or may be deleted by the customer using Session DetectLivenessWithVerify SingleModal |
Note
No images sent to the Face service are stored after analysis.
How does the Face process data?
The diagram below illustrates how your data is processed for Face Detection with Face ID (approved customers only).
Security for customers’ data.
The security of customer data is a shared responsibility.
The following are a few best practices for further securing Azure AI services Face:
- Customer managed encryption keys are available.
- Azure AI services Face supports VNET to restrict access to certain IP addresses, IP ranges, or a list of subnets.
- Azure Active Directory (Azure AD) authentication allows you to authenticate to Azure AI services using Azure AD. This capability provides greater flexibility for managing access to Azure AI services and makes it easier to use existing policies for credential rotation and to enforce custom password standards.
- You can also further protect access to sensitive facial feature templates by using Azure role-based access control (Azure RBAC) to use the Cognitive Services Face Recognizer role that restricts access to detect, verify, identify, group, and find similar operations on Face. This role does not allow create or delete enroll operations, which makes it well suited for endpoints that only need inferencing capabilities, following “least privilege” best practices.
For additional security best practices and information, visit Azure AI services security baseline
Should you have any additional questions or concerns, please let us know by opening a support ticket in the Azure portal.
To learn more about Microsoft's privacy and security commitments visit the Microsoft Trust Center.