Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 712:ai_privacy [2025/09/25 11:09] – Iseler, Marc | 712:ai_privacy [2025/09/25 12:02] (current) – Meier, Erich | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Stages AI Data Privacy ====== | ====== Stages AI Data Privacy ====== | ||
| - | Stages uses Microsoft Azure OpenAI services (Microsoft product name: //Azure OpenAI in Foundry Models//) to implement AI-enabled features such as generating process content and the Stages AI Assistant. The following models are used by default: | + | Stages uses Microsoft Azure OpenAI services (Microsoft product name: **Azure OpenAI in Foundry Models**) to implement AI-enabled features such as generating process content and the Stages AI Assistant. The following models are used by default: |
| * gpt-4o | * gpt-4o | ||
| Line 11: | Line 11: | ||
| The complete process data is always stored in the Stages database and the Stages search engine indices. It is never sent in its entirety to the Azure AI services. | The complete process data is always stored in the Stages database and the Stages search engine indices. It is never sent in its entirety to the Azure AI services. | ||
| - | When used in a Stages Managed Service, it is recommended to use your own Azure AI subscription. In this case, you have full control over your data and usage. If you do not have an Azure AI subscription, | + | When used in a Stages Managed Service, it is recommended to use your own Azure AI subscription. In this case, you have full control over your data and usage. If you do not have an Azure AI subscription, |
| The following statements from Microsoft Azure apply for both cases: | The following statements from Microsoft Azure apply for both cases: | ||