@Vinayak Pote Please see this page on how the enrollment data is used by Microsoft at different stages of speaker recognition when used with conversation transcription. To summarize, the enrolled audio is associated with a GUID that is unique to the enrollment audio and the voice signature, these are all securely stored in the customer’s Azure tenancy.
Microsoft is not able to connect any customer names, IDs (other than the random GUID), or other personal information to the enrollment audio, voice signatures, or passphrase signatures. Developers can create, update, and delete enrollment data (both the voice signature and related enrollment audio) for individual speaker through API calls. When the subscription is deleted, all the speaker enrollment data associated with the subscription is also deleted.
So, if you plan to keep the enrollment and voice signature you have control over the data and is associated with the GUID until it is deleted by the user. So, all data is encrypted at rest and is only deleted if the user wants to delete it. Thanks!!
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.