Skip to main content

Security and data protection

What we put in place to protect your fleet, your teams and your data. LongLife is built to support GDPR: concrete measures, settings you control and ready-to-use documents.

Access and authentication

Two-factor authentication
Sign-in uses a password and a one-time code (TOTP). It is mandatory for every role except the end user. Single-use backup codes are provided. Sensitive actions, such as launching an intervention, ask for a fresh code.
Passwords
Passwords are hashed with the Argon2 algorithm, and common passwords are rejected.
Google, Microsoft and organization SSO
You can sign in with Google or Microsoft. The Enterprise plan adds your organization's SSO (Microsoft Entra) with role mapping. Sessions use short-lived signed tokens.
Six roles, precise permissions
OPP! super administrator, integrator, client IT manager, technician, accountant and end user. Permissions are checked on every request.

Isolation and data protection

An organization only sees its own PCs
Each organization is isolated from the others at the database level: the organization context is applied to every request.
Audit log
Actions are recorded in an append-only log specific to each organization, kept for 5 years by default and exportable.
Encryption
Traffic between the browser, the agent and the platform is encrypted with TLS. Application secrets stored in the database, such as authentication and integration secrets, are encrypted, with keys kept outside the database.
Pseudonymization
Wi-Fi names, access point addresses and session identifiers are pseudonymized with a key specific to each organization.

Controlled remote interventions

The agent never receives free-form orders. Every intervention follows a closed, logged workflow.

A catalog of selected scripts
Scripts come from a catalog managed by OPP!. There is no free script console.
Signed commands
Each command is signed by the platform, and the agent verifies the signature of the full script before running it.
Human validation
An authorized user creates the command and confirms it with a code. Beyond 10 PCs, a second administrator must approve it. The PC's user can pause interventions for 1 h, 4 h or 24 h, and agents can be cut off in an emergency.

An agent controlled end to end

Signed updates
Agent updates are signed by OPP!. The agent checks the fingerprint and signature before replacing its version, rolls back on its own if something fails, and rollout is progressive.
One identity per PC
Each PC has its own key, preferably held in the TPM chip. It can be revoked, and you can require approval of every new PC.

The data the agent collects

You decide the level of collection. LongLife can never collect beyond the ceiling your IT manager sets when deploying the agent.

Collected by default, technical data
Hardware, performance, installed and running applications, PC security (antivirus, firewall, BitLocker), disk and battery health, startup, network quality and domain names of the services used. This data is attached to the PC.
Optional, off by default
Detailed application usage, pseudonymized session identity, user name, location and network discovery. Activation is done by the IT manager, confirmed by code and logged.
Never collected
File contents, emails and messages, keystrokes, screenshots and addresses of pages visited (only domain names are observed).
Where the data goes
To the LongLife platform, hosted at OVHcloud in a data center in France, over TLS.

GDPR: a clear framework and ready documents

Roles
Your organization is the controller for its fleet data. OPP! acts as processor for that data, and as controller for account data and technical logs.
Documents for your file
We publish the elements for your impact assessment (DPIA) and a template information notice for your employees, to be adapted and validated by your DPO.
Data subject rights
They are exercised with your organization. The platform gives administrators export (JSON or CSV) and erasure of a PC or a user, within one month.
Retention periods
Adjustable by the IT manager. By default: detailed measurements 30 days, hourly aggregates 180 days, daily aggregates 730 days, audit log 5 years, script outputs 30 days.
Hosting and processors
Hosting at OVHcloud, in France. Other providers are the Better Stack monitoring tool (no personal data) and Let's Encrypt (certificates). If you enable geolocation, which is off by default, mapping services may be involved: they are listed in our DPIA elements.

Lio, the AI assistant

Limited data
Lio receives technical measurements of PCs or of the fleet and the network name of the PCs. It never receives people's names or emails, locations or free text.
An OPP! AI server
Lio runs on an OPP! AI server, with no outside AI service. This server does not keep the exchanges.
It prepares, you decide
Lio never performs an action. Its answers are marked "to be verified", and any action goes through the usual validation workflow. Conversations are visible only to their author, kept for 90 days and erasable.

This page describes the measures in place at the date of its last update. It does not replace the contractual terms.

A question about security or your data?

Write to us at contact@longlifehq.com, or request a meeting: we answer your questions and send you the useful documents.

Book a meeting