> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-docs/user-guide/resolution-6/facial-biometrics/core-procedure/profile-insertion.md).

# Profile insertion

1. The peer receives a batch profile insertion procedure, where it receives multiple batches containing arrays of anonymized biometric assets and arrays of identifiers, where each item in the batch pertains to a different profile.
2. The peer inserts the identifiers it received and the anonymized biometric data into multiple new profiles.
3. The peer returns the operation result.

## Batch profile insertion (non-anonymized)

A Batch profile insertion (non-anonymized) is a proce where the peer receives an array of non-anonymized biometric data that's meant to be anonymized and then inserted as multiple profiles. This operation is best explained through the following diagram:

<figure><img src="https://737907756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI4kncOam5KtDqeGMEiQu%2Fuploads%2FvnmmFxA7j7RjIIjapjkU%2Fbatch-profile-insertion-non-anonymized.svg?alt=media&amp;token=f7886307-713e-4bee-b0ba-cbdfac6574c8" alt=""><figcaption></figcaption></figure>

1. The peer receives a batch profile insertion procedure, where it receives multiple batches containing arrays of non-anonymized biometric assets and arrays of identifiers, where each item in the batch pertains to a different profile.
2. The peer sends the non-anonymized biometric data to a queue, where these assets will be anonymized in the peer's facematch node.
3. The facematch node anonymizes all non-anonymized biometric assets it receives, and then return them to the queue.
4. The queue forwars these anonymized biometric assets back to the peer.
5. The peer inserts the identifiers it received and the anonymized biometric data into multiple new profiles.
6. The peer returns the operation result.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.caf.io/caf-docs/user-guide/resolution-6/facial-biometrics/core-procedure/profile-insertion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
