Subprocessors
Last updated: 7 November 2026
Translation provided for information only. Only the French version of this document is legally binding.
Aurva Software, the publisher of AIForeGuard, uses the providers below to operate the website and the application. Each of them only accesses the data required for its assignment and is bound to the publisher by a contract containing data protection commitments. This list supplements the privacy policy and the data processing agreement (DPA), which forms part of the customer contract alongside the terms of sale.
1. Providers
| Provider | Purpose | Data concerned | Location | Safeguards |
|---|---|---|---|---|
| Vercel Inc. | Hosting of the website and the application; execution of server functions, including scheduled tasks. | Application data in transit and being processed; IP addresses and request logs; demonstration requests sent from the website (email, company, message). | Server functions: Paris, France (cdg1 region). Static files: global delivery network (caching). Company established in the United States. | The provider’s data processing agreement; European Commission standard contractual clauses for any access from a third country. |
| Supabase, Inc. | Dedicated PostgreSQL database for the application and its backups (7 days). | All data stored by the application. | European Union — Paris, France (eu-west-3). Company established in the United States. | The provider’s data processing agreement; European Commission standard contractual clauses for any access from a third country. |
| Microsoft (Azure Key Vault) | Secrets vault: keys, tokens and integration passwords entrusted by customers. The application accesses it through identity federation, with no stored secret. | Secrets of the connections and of the alert destinations. | France (France Central region). | The provider’s data processing agreement; European Commission standard contractual clauses for any access from a third country. |
| Cloudflare, Inc. | Delivery (CDN) of the browser extension’s rule files (rules.aiforeguard.com); DNS for the domain. | Signed and encrypted rule files, which Cloudflare cannot read; IP addresses of the browsers that download them. | Global network. Company established in the United States. | The provider’s data processing agreement; European Commission standard contractual clauses for any access from a third country; files signed and encrypted by the publisher before delivery. |
| Functional Software, Inc. (Sentry) | Technical error tracking. | Technical error messages. No IP address, location, user, cookies, headers or content: the application filters them out before sending. | European Union — Frankfurt, Germany. Company established in the United States. | The provider’s data processing agreement; European Commission standard contractual clauses for any access from a third country. |
| Google (Google Workspace) | Mailboxes for the aiforeguard.com domain (privacy@, contact@, demo@). | Messages received at these addresses (sender, content, attachments). | Google’s global infrastructure. Company established in the United States. | The provider’s data processing agreement; European Commission standard contractual clauses for any access from a third country. |
| Resend | Emailing of the website’s demonstration requests to demo@aiforeguard.com; the website keeps nothing. | Email, company and message entered in the demonstration form. | Company established in the United States. | The provider’s data processing agreement; European Commission standard contractual clauses for any access from a third country. |
Where a provider established in the United States participates in the EU–US Data Privacy Framework, that participation is in addition to the safeguards listed. The safeguards listed are those provided for in the providers’ contractual terms and published documentation; that documentation is available on request at privacy@aiforeguard.com.
Data stored by the application remains in the European Union (database in Paris, secrets vault in France). AIForeGuard uses no artificial-intelligence model provider, no online payment provider (invoicing is by invoice and bank transfer) and no audience measurement tool.
2. Services connected at the customer’s initiative
The following services are used only if an administrator of the customer organisation connects them. AIForeGuard accesses them with the permissions granted by the customer (administrator consent, OAuth, or a role or access key the customer creates) in order to read the configurations and metadata of its AI platforms, authenticate its users, read its directory or send it alerts. The customer remains bound to these providers by its own contract, which determines the applicable location and safeguards; they are not subprocessors of the publisher.
| Service | Use within AIForeGuard |
|---|---|
| Microsoft Entra ID | User sign-in; reading of the directory (users, groups, licences) and of agent creators’ sign-in logs; mapping between groups and roles. |
| Microsoft 365 and Microsoft Purview | Reading of Microsoft 365 Copilot audit logs (metadata only). |
| Microsoft Copilot Studio, Dataverse and Power Platform | Inventory and configuration of agents; live control of Copilot Studio agents’ tools. |
| Microsoft Defender | Detection of AI assistants and MCP servers installed on workstations. |
| Microsoft Sentinel | Sending of alerts. |
| Microsoft Teams (Workflows) | Sending of alerts. |
| Azure AI Foundry | Agent inventory. |
| Amazon Web Services (Bedrock, AgentCore, Quick) | Agent inventory, through temporary access the customer authorises in its AWS account. |
| Google (Gemini Enterprise, Google Workspace directory) | Inventory of Gemini Enterprise agents; read-only access to the directory (department, organisational units, groups). |
| Mistral | Reading of agent configurations. |
| SCIM directories (Okta, OneLogin, JumpCloud, Ping Identity, Microsoft Entra) | Attachment of browsers to the organisation’s departments and groups. |
| Customer’s identity provider (Okta, OpenID Connect) | User sign-in (single sign-on). |
| Slack (AIForeGuard app or webhook) | Sending of alerts; taking charge of and resolving alerts from Slack with the app. |
| Atlassian Jira Cloud (OAuth 2.0) and Jira Data Center | Sending of alerts as tickets. |
| ServiceNow | Sending of alerts. |
| Netskope | Inspection, by the customer’s Netskope tenant, of files sent to AI services (Netskope mode of the browser extension). |
| Customer’s webhook address | Signed sending of alerts. |
3. Services built into the customer’s browser
To apply a changed rule without waiting, AIForeGuard may wake the browser extension with an empty message containing no content. This message goes through the notification service built into the browser the customer deploys (for example Google for Chrome, Microsoft for Edge). That service is determined by the browser and governed by its vendor’s terms; it only receives the browser’s subscription address, never usage data or rules. Without it, the extension fetches its rules at its next periodic check.
4. Changes to this list
Any change to this list is published on this page. Customers are informed in advance of the addition or replacement of a subprocessor, with one month’s notice, and may object to it under the conditions set out in the data processing agreement.