Data Handling
Averisys Analytics classifies customer data before use. It stores customer content only in approved Azure services. The platform encrypts persisted AI data at rest by default. Microsoft states that Azure OpenAI automatically encrypts persisted data at rest. Microsoft also states that stored Azure OpenAI feature data stays in the customer's Azure tenant, in the same geography as the resource, with Microsoft-managed encryption by default and customer-managed key support for supported features.
The team uses Azure Key Vault only for keys, secrets, and certificates. It does not use Key Vault as a customer content store. Microsoft states that Key Vault is not a data store and recommends Azure Storage or other approved data services for customer content.
Averisys Analytics discloses geography rules when they matter. If the deployment uses Global or DataZone processing, the platform makes this plain. Microsoft states that Global deployments may process prompts and responses in any geography where the model is deployed, and DataZone deployments may process prompts and responses anywhere inside the selected data zone, even though stored data at rest remains in the customer-designated geography.
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.