Last updated : November 11, 2026
End-user terms of use (EULA)
Version 1.0, November 2026. The French version prevails.
These end-user terms of use (the "EULA") set out what you may do with LongLife, what we do for you and who is responsible for what. They supplement the General terms of sale (the "Terms of Sale").
1. Acceptance
1.1. By creating an account, installing the agent or using the service, the customer and each user accept the EULA. If you accept on behalf of an organisation, you state that you have authority to bind it.
1.2. LongLife is intended for business use only. It is not intended for consumers.
1.3. If you do not accept the EULA, do not use the service and uninstall the agent.
1.4. In case of conflict between a signed quote, the Terms of Sale and the EULA, the quote prevails, then the Terms of Sale, then the EULA, except for the rules on use of the software, where the EULA prevails.
2. Definitions
- Publisher: OPP! (EURL), 6 rue Rose Dieng-Kuntz, 44300 Nantes, SIREN 921 251 948.
- Service: the LongLife platform available online, the agent and their documentation.
- Agent: the software installed on the customer's Windows workstations.
- Customer: the legal entity holding the subscription.
- User: any person authorised by the customer (administrator, technician, IT director, integrator, end user).
- Workstation: a Windows computer supervised by the agent.
- Plan: the customer's subscription tier.
- Lio: the artificial intelligence assistant built into the platform.
- Customer data: data sent by the agent and data entered in the platform.
- Signed script: an intervention from the publisher's catalogue, signed, that the agent may run on a workstation.
- Documentation: the guides and help pages published by the publisher.
3. Licence
3.1. The publisher grants the customer a personal, non-exclusive, non-transferable, non-sublicensable licence to use the service and the agent, revocable in the cases set out in the EULA.
3.2. The licence is limited to the term of the subscription, the number of workstations in the plan and the customer's internal needs. An integrator or service provider may use the service to manage the fleet of its own customers under the contract binding it to the publisher.
3.3. The agent and the platform are licensed, not sold. No source code is provided.
3.4. All rights not expressly granted are reserved by the publisher.
4. Account, roles and credential security
4.1. Access is through a named account, with a password or a Google or Microsoft sign-in. The customer appoints its administrators and assigns roles to its users.
4.2. The platform distinguishes several roles (administrator, integrator, customer IT director, technician, end user). The customer is responsible for the rights it grants.
4.3. Two-factor authentication (TOTP-type app, with backup codes) is mandatory for accounts other than the end user's. Sensitive actions require the code to be entered again.
4.4. Each user keeps their credentials secret and does not share them. The customer notifies the publisher without delay of any loss, theft or suspicious use. The customer is responsible for actions taken with its users' accounts.
4.5. After five consecutive failed sign-in attempts, the account is locked.
5. The agent installed on workstations
5.1. Scope. The agent works on Windows only, 64-bit versions. It runs as a Windows service and shows a visible icon in the notification area. It reports the state of the hardware, the software and the usage experience. Collection is read-only. Only signed interventions from the catalogue can change a workstation, after approval (see article 6).
5.2. Data collected by default ("technical data" tier). Processor, memory, disks and SMART status, battery, system, installed applications (publisher and version) and applications started at boot, domain names of online services used (without page addresses), performance, boot times, system events, network quality, peripherals (USB, Bluetooth, printers), security posture (antivirus, firewall, BitLocker, user account control, updates), hardware lifecycle, virtual machine detection.
5.3. Tiers disabled by default. Pseudonymised usage data (application usage, session context, experience surveys), Wi-Fi access point location, pseudonymised session identity and user name. The customer enables them at deployment by an explicit choice, and the publisher never collects beyond the tiers chosen. Enabling some tiers requires reinforced confirmation and is logged.
5.4. Data not collected. The agent does not collect the content of files, emails or communications, keystrokes, screenshots, addresses of pages visited, file names or window titles. It does not collect the user name unless the customer enables that option.
5.5. Data that may identify indirectly. Some technical data may indirectly identify a workstation or a person: workstation name, serial numbers, Wi-Fi network, gateway, command lines at boot. The customer takes this into account when informing employees.
5.6. Frequency. Performance measurements are sent about every five minutes and the inventory once a day. The agent queries the platform about every four hours for its updates.
5.7. Network requirements. The agent needs outbound HTTPS access to agent.longlifehq.com. It has no proxy setting and trusts only embedded public certificate authorities: inspection of encrypted traffic is incompatible. To measure network quality, it sends a ping every five minutes to a public server and resolves a public domain name. These exchanges contain no customer data.
5.8. Information of employees. The customer is the controller of the personal data collected. It informs the employees concerned, consults their representatives where the law requires, decides which tiers are enabled and complies with applicable labour law. The publisher provides a template information notice and impact assessment material, to be adapted by the customer. The customer warrants that it installs the agent only on workstations it controls.
6. Signed scripts and remote interventions
6.1. The agent runs only scripts from the publisher's catalogue, signed. It refuses any command lacking the expected signature. Each command is intended for a specific workstation, expires after twenty-four hours and cannot be replayed.
6.2. No intervention is launched without approval by an authorised user of the customer. The customer chooses the workstations targeted and the time of the intervention.
6.3. Interventions run with elevated rights on the workstation. The customer is responsible for the interventions it approves and the parameters it provides.
6.4. Interventions, their authors and their results are logged in an exportable audit log. Script outputs are kept for a limited time (see article 9).
6.5. The customer may disable remote interventions on its scope. The publisher may also revoke a workstation or cut a customer's remote command channel in case of risk.
6.6. An intervention aims to maintain the fleet. It is not a guarantee of result on the state of the workstation.
7. Lio, artificial intelligence assistant
7.1. Lio answers questions about a workstation or the fleet, summarises data, compares workstations, helps understand the application and prepares reports. It works from platform data.
7.2. Lio's answers are indicative. They carry the label "to be checked". The user verifies important information before deciding. Figures shown are calculated by the platform. When data is missing, Lio says so.
7.3. Lio never performs an action on its own. It may prepare an order or an intervention, which the authorised user approves or rejects. It respects the rights of the user who asks it.
7.4. Lio is offered as a beta. It may be wrong, unavailable or change.
7.5. Lio runs on an AI server owned by the publisher, located in France, without using an external AI service. The model is not trained with customer data. The server does not keep the exchanges. Lio receives no name or email of a person, no geolocation, no Wi-Fi network name and no free text.
7.6. Conversations are kept for ninety days, visible only to their author, erasable and included in the personal data export. The "Help improve Lio" option is an explicit choice by the administrator, is never ticked by default, concerns pseudonymised data kept for twelve months and is never sold.
7.7. Lio usage quotas depend on the plan and are stated in the quote, the order or the Pricing page.
7.8. The customer does not base any legal, employment or security decision solely on an answer from Lio.
8. Prohibited uses
Without the publisher's written consent, it is forbidden to:
a) copy, modify, translate, decompile, disassemble or try to reconstruct the code of the agent or the platform, except to the extent the law allows despite any clause to the contrary; b) bypass script signing, security measures, authentication, account locking or plan quotas; c) resell, rent, sublicense or make the service available to third parties, except as provided in article 3.2; d) install the agent on workstations that do not belong to the customer's scope or without following the rules of article 5.8; e) run load, penetration or performance tests on the service without prior written authorisation; f) introduce viruses, malicious code or unlawful content; g) use the service to monitor people unlawfully or contrary to applicable regulations; h) use Lio to obtain data of other customers, bypass its limits or train it outside the service; i) use the service to build a competing product or to extract data in bulk by automated means not provided for in the documentation; j) remove the publisher's proprietary notices and trademarks. k) use the service, give access to it or export it in breach of applicable economic sanctions, embargo or export control measures (see Terms of Sale, article 19).
9. Customer data
9.1. Customer data remains the customer's property. The customer grants the publisher the right to host, process and display it to the extent needed to provide the service.
9.2. The customer exports its data from the platform and may request deletion, per workstation or per user, from the privacy centre. Erasure of a workstation is propagated to all databases and gives rise to an erasure certificate.
9.3. Default retention, which the customer may reduce: detailed measurements thirty days, hourly aggregates one hundred and eighty days, daily aggregates seven hundred and thirty days, audit log five years, script outputs thirty days, backups thirty-five days at most.
9.4. The customer warrants that it has the right to provide the data to the service and that it infringes no third-party right.
9.5. For personal data, see article 17 of the Terms of Sale, the privacy policy and the list of subprocessors.
10. Derived data and aggregated statistics
10.1. The publisher may produce usage statistics of the service and aggregated, anonymised data from the activity of the service, in order to operate, secure and improve the service.
10.2. This data does not allow identification of the customer, its users or its workstations, and is not resold in a form that would.
10.3. The indicators calculated by the platform (health score, risk level, costs, carbon impact, recommendations) remain elements of the service. The customer may use them freely for its internal needs.
11. Hosting in France
11.1. The service is hosted in France. It runs on a virtual private server dedicated to LongLife at OVHcloud, in a data centre in France. Agent data is not transferred outside the European Union.
11.2. Some options enabled by the customer may involve exchanges with third-party services, in particular geolocation (see article 17).
12. Security
12.1. The publisher implements appropriate security measures: TLS encryption of exchanges, isolation of data between customers, two-factor authentication, audit log, signing of programs and commands, passwords stored in hashed form.
12.2. The publisher claims no security certification. LongLife is a fleet hygiene and posture tool. It does not replace an antivirus, a detection solution or the customer's security policy.
12.3. The customer secures its own accounts, networks and workstations, and applies the prerequisites of the documentation.
12.4. Each party informs the other as soon as possible of a security incident concerning it, in accordance with the law. The publisher's security contact is contact@longlifehq.com.
13. Updates of the agent and the platform
13.1. The agent checks the publisher's fingerprint and signature before replacing its programs. A modified or unsigned file is refused.
13.2. After an update, the agent is trialled for about thirty minutes. If reporting fails, it automatically returns to the previous version.
13.3. Updates are rolled out gradually, first to pilots then in waves, and pause automatically in case of failures. "Stable" and "beta" channels exist. No update takes place during an intervention.
13.4. The publisher may evolve the platform, its features and its documentation. It avoids removing an essential feature of the plan without informing the customer in advance.
14. Availability and maintenance
14.1. The publisher endeavours to keep the service accessible. It does not guarantee continuous or error-free availability. No availability rate is promised. A service level agreement applies only if it is expressly annexed to the quote or accepted order.
14.2. Interruptions may be needed for maintenance. The publisher endeavours to plan them and to notify the customer.
14.3. The agent does not depend on a permanent network connection. It resumes reporting when the link returns.
15. Support
15.1. Support is provided as set out in the Terms of Sale. It can be reached by email at contact@longlifehq.com, on business days, with no commitment on response time.
15.2. The assistance request offered to the end user from the agent icon is sent to the customer's IT team and not to the publisher.
15.3. The public documentation supplements support.
15.4. The publisher accesses a customer's data to handle a support request only to the extent needed for that request. The customer may ask for that access to stop.
16. Beta features
16.1. Features marked "beta" are provided as is. They may be modified, suspended or withdrawn without notice and are not covered by any warranty.
16.2. The publisher may ask for feedback on these features. The customer uses them at its own risk and avoids using them for critical operations.
16.3. A beta feature does not commit the publisher to make it available in its current form.
16.4. The Free plan and trials are provided on the terms of article 10.4 of the Terms of Sale.
17. Third-party services and components
17.1. The service relies on open-source or third-party software components subject to their own licences. Those licences prevail for those components.
17.2. If the customer enables geolocation, technical data (Wi-Fi access point identifiers and signal level, site addresses) is sent to positioning, mapping and geocoding providers. They are listed on the subprocessors page. They are subject to their own terms and the customer accepts their use by enabling the option.
17.3. Google or Microsoft sign-ins are subject to those providers' terms.
17.4. The publisher is not responsible for third-party services it does not control, unless the law provides otherwise.
18. Intellectual property and trademarks
18.1. The publisher holds all rights in the service, the agent, the documentation, the interfaces, the databases, the algorithms and the models. They are protected by intellectual property law.
18.2. "LongLife", "Lio" and "OPP!" are trademarks or distinctive signs of the publisher. Their use is forbidden without prior written consent.
18.3. Screenshots and extracts of the documentation may be reused only for internal use.
19. Feedback and suggestions
19.1. The customer may send ideas, feedback or suggestions. It authorises the publisher to use them freely, without compensation, to improve the service, without giving the customer any right in the service.
19.2. The customer does not send, in its feedback, personal or confidential information it does not want reused.
20. Confidentiality
20.1. The confidentiality obligations of the Terms of Sale (article 15) apply to use of the service.
20.2. Non-public documentation, access to the platform, keys and the publisher's security details are confidential information.
20.3. The customer does not use its access to the service to try to discover information of other customers.
20.4. Where a judicial or administrative authority requires the publisher to disclose customer data, it responds only to the extent required by law, checks the basis of the request and informs the customer, unless the law forbids it.
21. Limited warranty and exclusions
21.1. The publisher warrants that the service works substantially in accordance with its documentation. In case of a reported non-conformity, it uses reasonable means to correct it.
21.2. For the rest, the service is provided "as is". The publisher gives no warranty of fitness for a particular purpose or of freedom from errors or interruptions, to the extent permitted by law.
21.3. The publisher does not guarantee the lifespan, condition or performance of the customer's workstations, nor the accuracy of a cost, savings or carbon estimate.
21.4. Excluded from the warranty: use contrary to the documentation or the EULA, workstations whose system is modified in an incompatible way, network environments that block the agent, third-party components and beta features.
22. Limitation of liability
22.1. The limits of liability in the Terms of Sale (article 12) apply to the EULA. The publisher's total liability is limited to the cap, if any, stated in the quote or accepted order, as provided in the Terms of Sale.
22.2. The publisher is not liable for damage resulting from an intervention approved by the customer, from the content of a script requested by the customer, from a decision taken on the basis of an estimate or an answer from Lio, or from the customer's failure to meet its obligations towards its employees.
22.3. These limits do not apply in case of gross negligence or wilful misconduct, personal injury or where the law forbids it.
22.4. Each party is responsible for its legal obligations on personal data protection in its role, as set out in the DPA.
23. Infringement indemnity
23.1. The publisher defends the customer against any third-party action claiming that the service, used in accordance with the EULA, infringes an intellectual property right in France, and bears the damages and costs awarded by final judgment, provided the customer: notifies it without delay, lets it control the defence and cooperates reasonably.
23.2. The publisher may, at its own expense, obtain the right to continue use, modify the service so that it does not infringe or, failing that, terminate the access concerned and refund prepaid sums for the period not covered.
23.3. This indemnity is excluded if the infringement results from a modification not made by the publisher, a combination with a third-party product, non-compliant use or items supplied by the customer. It is the customer's exclusive remedy for infringement, subject to the law.
24. Suspension
24.1. The publisher may immediately suspend access, in whole or in part, if it has a serious reason to believe that the use compromises the security of the service or of other customers, breaks the law or article 8, or in case of non-payment after formal notice.
24.2. The publisher notifies the customer as soon as possible, states the reason and restores access as soon as the cause disappears.
24.3. Suspension does not delete the customer's data and does not suspend its payment obligations.
25. Termination and effects
25.1. The grounds for termination are those of the Terms of Sale (article 8).
25.2. At the end of the contract, the licence ends. The customer stops using the service and uninstalls the agent from its workstations (uninstall by msiexec /x, GPO or Intune, as described in the documentation). While the agent remains installed, it may keep trying to reach the platform without the publisher being bound to accept it.
25.3. The customer may export its data before access ends. After the end of the contract, the publisher deletes the customer's data within a reasonable time, and may issue an erasure certificate on request. Data it must keep by law, such as invoices, is kept for the legal period.
25.4. Articles which by nature are meant to do so survive the end of the contract: intellectual property, confidentiality, liability, governing law.
26. Audit and compliance
26.1. The publisher may verify, from platform data, that the number of workstations and the use comply with the plan.
26.2. If an excess is found, the parties regularise it by a change of plan under the Terms of Sale.
26.3. The customer may ask the publisher for the documentation useful to show its own compliance obligations, including impact assessment material and non-confidential security information.
27. Integrators, service providers and sub-tenants
27.1. This article supplements article 3.2 and article 18 of the Terms of Sale. It applies to accounts holding the integrator role.
27.2. The integrator creates a sub-tenant, meaning a separate space, for each of its customers. The data of each sub-tenant is isolated from that of the others. The integrator sets, within the options of the platform, the visibility between its own space and those of its customers, and informs its customers of it.
27.3. The integrator accesses a customer's fleet only for the assignment agreed with that customer. It assigns the roles in the sub-tenant. It is responsible for the interventions it validates and the scripts it runs on its customers' workstations (article 6), as well as for the collection tiers it enables (article 5.3). It ensures that each customer complies with article 5.8, in particular as regards informing employees, or does so itself.
27.4. Where the integrator processes personal data on behalf of its customer, the roles of each party (controller, processor, sub-processor) are set in the contract between the integrator and that customer and in the data processing agreement concluded with the publisher (Terms of Sale, article 17). The integrator acts only on the documented instructions of its customers.
27.5. The integrator may show its logo and that of its customer on the reports produced by the platform, within the limits of the available functions. It does not suggest any approval, certification or partnership of the publisher that has not been agreed in writing. For any other use of the publisher's trademarks, article 18.2 applies.
27.6. Where a ground for suspension (article 24) concerns only one sub-tenant or one user, the publisher limits the suspension as far as possible to that sub-tenant or user.
28. Indemnity by the customer
28.1. The customer defends the publisher against any third-party action based on: a) the customer's data or its collection on its workstations, in particular a failure to inform or consult employees; b) use of the service contrary to the EULA or the law; c) for an integrator, the services provided to its own customers. It bears the damages and costs awarded by a final judgment or set by a settlement it has accepted.
28.2. This indemnity does not cover the share of the damage caused by a fault of the publisher. It requires the publisher to notify the customer without delay, leave it the conduct of the defence and cooperate reasonably. No settlement involving an admission of fault or a burden on the publisher may be concluded without its consent.
29. Changes to the EULA
27.1. The publisher may change the EULA, in particular to reflect changes to the service or the law.
27.2. It notifies customers by email or by a notice in the platform within a reasonable time before a substantial change takes effect.
27.3. A customer who refuses the change may terminate before that date. Use of the service after the change takes effect means acceptance.
27.4. The applicable version and its date are shown at the top of this document.
30. Governing law, jurisdiction and language
28.1. The EULA is governed by French law.
28.2. The parties first seek an amicable solution.
28.3. Failing that, any dispute falls under the competent courts of the jurisdiction of the publisher's registered office.
28.4. The EULA is written in French. Translations are provided for information and the French version prevails.
28.5. If a clause is held invalid, the others remain applicable. The publisher's failure to exercise a right is not a waiver.