Privacy
Averisys Analytics does not state or imply that Microsoft or OpenAI trains on customer prompts by default. Microsoft states that prompts, completions, embeddings, and training data are not available to other customers or to OpenAI. Microsoft also states that this data is not used to improve Microsoft or third-party services, or to train foundation models, without the customer's permission or instruction. Azure documentation further states that the models are stateless and that prompts and completions are not stored in the model.
Averisys Analytics describes privacy by deployment and feature. The platform states clearly when a workflow is stateless and when it uses stored history. Azure documents that some stateful features, such as the Responses API, Assistants Threads, and Stored completions, persist message history or related content. Microsoft states that stored feature data sits in the customer's Azure tenant, in the same geography as the resource, stays encrypted at rest, and can be deleted by the customer at any time.
How Averisys Analytics applies this in practice
Averisys Analytics treats customer data as material held in trust. Access follows the least privilege principle: staff and services receive only the access a specific task requires, and that access is reviewed and removed when the task ends. Data is encrypted in transit and at rest, administrative activity is logged, and separate environments keep testing work away from production records. Where analysis can be performed on aggregated or de-identified data, that is the default rather than the exception.
Practices are documented so a customer's own security, privacy, or procurement reviewer can verify them instead of taking a claim at face value. Averisys Analytics answers security questionnaires, explains how data flows through the platform, and states plainly what it does and does not do with customer information. Subprocessors are limited to those needed to operate the service, and each is selected against the same expectations applied internally.
Policies change as the platform changes. When a new capability handles data differently, documentation is updated alongside it, and customers with an active agreement are notified of material changes. Questions about a specific requirement, contract term, or regional obligation can be sent to support@averisysanalytics.com.