Terms of use
Version in force as of 7 November 2026
Translation provided for information only. Only the French version of this document is legally binding.
Rules for accessing and using the AIForeGuard application, applicable to the users whom customer organisations authorise to use it.
1. Purpose and scope
These terms of use (“Terms of Use”) set out the rules for accessing and using the AIForeGuard service, an online platform for the governance and security of artificial intelligence in the enterprise, available at app.aiforeguard.com (the “Service”).
The Service makes it possible, in particular, to inventory the customer organisation’s artificial-intelligence agents and uses of AI on the platforms it connects (for example Microsoft Copilot Studio, Microsoft 365 Copilot, Azure AI Foundry, Amazon Web Services, Google Gemini Enterprise or Mistral), to detect changes to them, to observe the use of AI services from browsers by means of an extension, to define policies and rules, to issue alerts, to conduct periodic reviews, to establish mission contracts for agents, to produce audit files and reports, and to control the tools of Microsoft Copilot Studio agents live.
The Service is published by AURVA SOFTWARE, a simplified joint-stock company with a single shareholder (SASU) whose registered office is at 138 avenue de Versailles, 75016 Paris, France, registered under SIREN number 130 051 519 (RCS Paris) (the “Publisher”).
The Service is intended exclusively for professionals, for the purposes of their business.
2. Definitions
- Customer: the legal entity or professional that has subscribed to the Service, either directly with the Publisher or through a reseller.
- Organisation: the Customer’s space within the Service, isolated from those of other customers, which brings together its Users, its connections, its settings and the Customer Data.
- User: any natural person authorised by the Customer to access the application under a named account, whatever their role.
- Administrator: the User who holds the administrator role in the Organisation and who manages, in particular, the Users, roles and permissions, connections, alert destinations and Organisation settings.
- Customer Personnel: the employees and other persons working for the Customer whose activity is observed by means of the Service, in particular through the browser extension, through live control or through the logs of the Connected Services.
- Connected Services: the third-party services that the Customer links to the Service: AI platforms, directories, identity providers, and security, messaging or ticketing tools.
- Customer Data: the data processed in the Organisation: configurations and metadata read from the Connected Services, browser-extension observations, inventory, alerts, decisions, reviews, mission contracts, files, reports and audit log, together with the information entered by the Users and by the Customer Personnel.
- Outputs: the inventories, findings, alerts, live-control decisions, audit files and reports produced by the Service from the Customer Data.
- Order Form: the purchase order, signed quotation or specific contract that sets out, in particular, the offer, scope, term and price of the Service.
- Terms of Sale: the terms of sale of the Service.
- DPA: the data processing agreement entered into under Article 28 GDPR.
3. Acceptance and contractual documents
The Terms of Use apply to every User. They are accepted on first log-in to the Service. The Customer ensures that its Users read and comply with them.
The Customer is bound by the Order Form, the Terms of Sale, the DPA and the Terms of Use. In the event of conflict, these documents prevail in the following order: Order Form, Terms of Sale, DPA, Terms of Use.
4. Access to the Service
An Organisation is opened only with the Publisher’s agreement, under the conditions of the Order Form.
The Service is available online, from a recent browser, 24 hours a day and 7 days a week, subject to maintenance operations and to the cases provided for in Articles 14 and 17. The necessary equipment, software, connections, subscriptions and licences, including those with the providers of the Connected Services, remain the Customer’s responsibility.
Certain features may be offered in beta or early access. They are identified as such, may change or be withdrawn, and are provided without any service level commitment.
The available features and the scope covered depend on the offer and on the Order Form.
5. Accounts and credentials
Each account is personal and named; it may not be shared. The User signs in:
- through the Customer’s identity provider (Microsoft Entra ID, Okta or another OpenID Connect-compatible provider), where the Organisation is configured in this way;
- or with an email-and-password account created by the Publisher; the password is stored only in hashed form.
Users join the Organisation through a time-limited invitation link sent by the Administrator. Sessions expire after 8 hours at most, and after 2 hours of inactivity.
Users are responsible for the confidentiality of their credentials and for any action carried out from their account. Any loss, unauthorised use or suspected compromise must be reported without delay to the Administrator and to contact@aiforeguard.com.
Where sign-in goes through its identity provider, the Customer is responsible for securing it (for example with multi-factor authentication) and for managing the accounts in it. The Customer is responsible for withdrawing the access of persons who are no longer authorised, both in the Organisation and in its identity provider.
6. Roles and permissions
The Administrator assigns each User a role (administrator, security analyst, AI agent manager, auditor or reader) and may adjust its permissions. Roles may also be assigned according to membership of Microsoft Entra ID groups, using the mapping defined by the Administrator.
The Customer assigns roles and permissions according to each person’s needs and to the principle of least privilege, and regularly checks that they remain appropriate.
Certain operations require approval by two different members (the “four-eyes” principle), in particular agents’ mission contracts, changes to an agent’s lifecycle stage and regulatory profiles. Users shall not circumvent this mechanism, for example by using several accounts.
Removing a User ends their access; the history of their actions is kept in the audit log.
7. Users’ obligations
Users undertake to use the Service in accordance with its purpose, with applicable law and with these Terms of Use. In particular, it is prohibited:
- to connect to the Service a tenant, account, directory or any other service that the Customer is not entitled to connect, or to grant permissions without having the authority to do so within the Customer;
- to use the Service against third parties, in particular to observe persons or organisations outside the Customer, or to access third-party systems or data without authorisation;
- to use the Service for unlawful purposes, or to observe the Customer Personnel beyond what the law allows;
- to attempt to access another customer’s data, or to circumvent the isolation between organisations, the security, authentication or dual-approval mechanisms, or the limits of the subscribed offer;
- to reverse-engineer, decompile or extract the code of the Service, of the browser extension or of the relay, or the Publisher’s rules and reference lists, save within the limits permitted by law;
- to enter in the Service’s free-text fields (comments, reasons, descriptions) special categories of personal data (Article 9 GDPR) or data relating to criminal convictions, save where necessary and in compliance with the applicable regulations;
- to upload or transmit unlawful content or malicious software;
- to use the Service to develop a competing product or to extract data on a large scale by automated means;
- to carry out load or penetration testing without the Publisher’s prior written consent;
- to resell, sub-license or make the Service available to third parties beyond what the Order Form provides for.
8. Customer Data and Connected Services
8.1 Rights in the Customer Data
The Customer retains all rights in the Customer Data, including in the Outputs. It grants the Publisher, for the term of the contract only and worldwide, the non-exclusive right to host, reproduce and process that data strictly to the extent necessary to provide, secure and support the Service.
The Customer warrants that it holds the necessary rights and authorisations over the Customer Data and, where it contains personal data, a legal basis for processing it.
The Publisher exercises no prior editorial control over the information entered in the Service. It may however remove or make inaccessible any manifestly unlawful content reported to it.
8.2 Access to the Connected Services
By connecting a Connected Service, the Customer authorises the Publisher to access it on its behalf, with the permissions that the Customer itself grants in its own environments: for example consent to the AIForeGuard application and roles in its Microsoft tenant, a temporary-access role in its Amazon Web Services accounts, read permissions in its Google environments, or access keys to other platforms. The permissions requested are shown at the time of connection; those requested from Microsoft are read permissions.
This access is used solely to read the configurations, metadata and logs needed for the features of the Service (inventory, change detection, alerts, reviews, reports). The Service never keeps the text of conversations, files or the values of agents’ environment variables. From the Microsoft 365 Copilot audit logs, it keeps only metadata, never the prompts or the responses. Live control and Netskope analysis, which the Customer enables itself, are described in Article 9.
The Customer remains bound to the providers of the Connected Services by its own contracts. It may withdraw the permissions granted at any time, from the provider’s console or from the Service; the features that depend on them then stop. The Publisher is not responsible for the availability, changes or own processing of these providers.
The keys, tokens and passwords entrusted for these connections and for alert destinations are kept solely in a secrets vault (Microsoft Azure Key Vault).
9. Browser extension and live control
9.1 Browser extension
The Customer may deploy the AIForeGuard browser extension on the work browsers of its Personnel. The extension observes the use of AI services (origin host and destination host, type of observation, signals, daily counters) and applies the browser rules defined by the Customer (for example a warning, a block or an access request). It never collects prompts, responses, cookies, page titles, or address paths or parameters, and sends no file outside the case described below; the email address of the browser profile is kept only as a fingerprint.
Where the Customer enables Netskope analysis, the content of a file passes through the Service to the Customer’s Netskope tenant without being kept. The Customer may also install a relay on its own premises, which keeps the per-browser detail and sends only totals to the Service.
9.2 Live control
Where the Customer enables it for Microsoft Copilot Studio agents, live control examines the actions of these agents (tool calls) before they run and, depending on the mode and rules chosen by the Customer, either only observes them or lets them through or blocks them. The message of the agent’s user, the conversation history and the values passed to the tools are read in memory and not kept; each decision is kept for 90 days (agent, tool, parameter names, result, references of the user and of the conversation).
The Customer defines the rules, checks them before applying them and bears their effects: a block may prevent an agent from completing an action or a person from accessing a service. The Publisher does not guarantee that the Service will detect or block every undesirable action or use.
9.3 Customer’s obligations before any deployment
The browser extension, live control and the features that use activity logs (for example the Microsoft 365 Copilot audit logs or Microsoft Defender data) make it possible to observe the activity of the Customer Personnel. Before deploying or enabling them, the Customer, as employer and controller, undertakes:
- to bring the system to the prior attention of the Personnel concerned, together with its purposes and the data collected (Article L1222-4 of the French Labour Code), and to provide them with the information required by the GDPR;
- to inform and consult the social and economic committee (comité social et économique, CSE) where the law so requires, before deciding to implement means or techniques that allow employees’ activity to be monitored (Article L2312-38 of the French Labour Code);
- to ensure that the system and the rules applied are justified and proportionate to the aim pursued;
- to determine the legal basis of its processing and to carry out a data protection impact assessment (Article 35 GDPR) where one is required;
- to comply with the equivalent obligations under the law of the other countries where its Personnel is located.
The Publisher does not itself inform the Customer Personnel. The Customer shall indemnify the Publisher against any claim resulting from a breach of these obligations.
10. Alerts sent to the Customer’s tools
The Administrator may have alerts sent to the Customer’s tools: Microsoft Teams, Slack, Jira, ServiceNow, Microsoft Sentinel or a Customer webhook address (signed delivery). An alert contains its title, priority, reason, the name of the agent concerned, the platform and connection, dates and a link to AIForeGuard; in Slack, it also shows the names of the persons who take charge of it and resolve it. It never contains the content of a document.
The Customer chooses destinations whose recipients are authorised to know this information. Once delivered, alerts are subject to the access and retention rules of the destination tool and to the terms of its provider, under the Customer’s responsibility. The Publisher does not guarantee the delivery of every alert where the destination tool is unavailable or misconfigured; alerts remain available in the Service.
11. Artificial intelligence
- No AI model to process data. The Service uses no artificial-intelligence model and no language-model provider to process the Customer Data. Its findings and alerts result from rules and checks defined by the Publisher or by the Customer.
- A tool to govern the Customer’s AI. The Service helps the Customer to know and supervise its own AI agents and uses. Apart from live control (Article 9.2), the connections to the Customer’s AI platforms are used solely to read their configurations and metadata.
- An aid to decision-making. The Outputs depend on the information that the Connected Services expose and on the permissions granted; they may be incomplete. They do not replace the Customer’s own assessment, do not constitute legal advice and do not guarantee the Customer’s compliance with regulations, in particular the European regulation on artificial intelligence (Regulation (EU) 2024/1689) or the GDPR. The Customer remains solely responsible for its AI systems, their classification and its regulatory obligations.
- No training. The Publisher does not use the Customer Data to train artificial-intelligence models.
12. Intellectual property
The Service, its software (including the browser extension and the relay), interfaces, databases, rules and reference lists, report templates, trade marks, logos and documentation are and remain the exclusive property of the Publisher or of its licensors. For the term of the contract, the Publisher grants the Customer a personal, non-exclusive, non-transferable and non-sub-licensable right to use the Service, and to install the extension and the relay on its Personnel’s equipment, for its internal needs and within the limits of the Order Form. No other right is granted.
The trade marks of the Connected Services remain the property of their owners; their mention only indicates technical compatibility or integration.
Improvement suggestions communicated by the Customer or by Users may be freely used by the Publisher, without this conferring any right whatsoever over the Customer Data.
13. Personal data
For the personal data contained in the Customer Data, in particular that of the Users and of the Customer Personnel, the Publisher acts as the Customer’s processor within the meaning of Article 28 GDPR, under the terms of the DPA. The Customer is the controller: it determines the purposes of the processing, ensures its legal basis and informs the data subjects. Requests from data subjects are addressed first to the Customer; the Publisher forwards to it those it receives.
For the management of customer accounts and of the business relationship, billing, the security of the Service, technical logs and error tracking, the Publisher acts as controller, under the conditions of the privacy policy.
The list of the Publisher’s subprocessors is on the Subprocessors page. Any question about personal data can be sent to privacy@aiforeguard.com.
14. Availability, maintenance and support
The Publisher uses reasonable means, in line with the state of the art, to ensure the availability and proper functioning of the Service, as a best-efforts obligation. No numerical availability commitment applies, unless expressly provided for in the Order Form.
The status of the Service is published, for information and without commitment, on the status page app.aiforeguard.com/status.
The Service may be interrupted for maintenance; planned operations likely to significantly affect use are announced in advance where possible. The Publisher may develop the Service, in particular to improve it, to follow changes to the Connected Services or to comply with regulations, without substantially reducing its essential features during the current period.
Information from the Connected Services depends on their availability and on the time they take to make it available, over which the Publisher has no control.
Support is provided by email at contact@aiforeguard.com, in accordance with the terms of the Order Form.
15. Security
The Publisher implements appropriate technical and organisational measures to protect the Service and the Customer Data, including the isolation of organisations in the database, the storage of secrets in a dedicated vault, encryption of exchanges, an audit log that cannot be modified, dual approval of certain operations, short sessions, and signed and encrypted browser rules. These measures are described in the DPA and in the privacy policy.
The Customer undertakes to protect its own environments and accounts, and to report without delay to contact@aiforeguard.com any security flaw or incident of which it becomes aware.
16. Liability
The Publisher’s liability is governed by the Terms of Sale. In particular, the Publisher is not liable for:
- decisions taken on the basis of the Outputs without verification by the Customer;
- agents, uses or risks that the Service has not detected, in particular owing to insufficient permissions or to information not exposed by the Connected Services;
- the effects of the rules, blocks and settings defined by the Customer;
- the Customer’s compliance with its obligations towards its Personnel and with the regulations that apply to it;
- the content of the Customer Data;
- interruptions, changes or malfunctions of the Connected Services and of the alert destination tools.
The Customer is responsible for the use of the Service by its Users and shall indemnify the Publisher against any third-party claim, including from its Personnel, arising from a breach of these Terms of Use or from an infringement of third-party rights caused by the Customer Data.
17. Suspension and end of access
The Publisher may suspend, after prior notice where circumstances permit, the access of a User or of an Organisation in the event of a serious breach of the Terms of Use, of an established risk to the security of the Service or of other customers, or of non-payment under the conditions of the Terms of Sale. Access is restored as soon as the cause of the suspension has ceased.
While an Organisation is suspended, the Customer Data is kept; it may remain available for consultation, but data collection and new connections are stopped.
A User’s access ends when the Administrator removes them from the Organisation. The access of all Users ends at the end of the Customer’s contract, the consequences of which (export, then erasure of data) are governed by the Terms of Sale.
18. Amendments to the Terms of Use
The Publisher may amend the Terms of Use. The Customer and the Users are informed of any substantial amendment by any appropriate means, at least thirty (30) days before it takes effect, save for changes required by law or by the security of the Service. Continued use of the Service after that date constitutes acceptance of the amended Terms of Use.
19. Governing law and disputes
The Terms of Use are governed by French law. In the event of a disagreement, the parties shall seek an amicable solution before taking any action. Failing agreement within thirty (30) days, any dispute relating to their interpretation or performance shall be submitted to the exclusive jurisdiction of the competent courts of Paris, including where there are several defendants or in summary proceedings.
Contact: contact@aiforeguard.com.