Legal
Last updated 21 September 2026
This policy covers the Adaptive Armor client applications and the Adaptive Armor management console (together, “the Service”). It has two parts, because the two client applications work differently:
Adaptive Armor is sold to organisations, not to individuals. If you use a client application, your employer administers the Service and decides what it is used for. They control the information below; we process it on their behalf.
The desktop client is a security agent your organisation installs to protect its devices and data. Unlike the mobile app, it applies your organisation's security policy to all of the device's network traffic, not only traffic to your organisation's private network.
| Data | Why it is sent |
|---|---|
| Email address | Identifies the signed-in user. Read from the sign-in token. |
| Device identifier, device name, OS version, processor architecture, client version | Shown in the device inventory so an administrator can identify a device and see whether it runs current software. |
| Connection and protection state | Shows whether secure access and web protection are currently active on the device. |
| IP address | Observed when the device contacts the Service; used for connectivity and the approximate location of the connection. |
| Network activity records | Domains and web addresses visited, times, network addresses, the application that made the connection, and the security policy decision taken (allowed, blocked, warned). Used by your organisation to protect, investigate and meet compliance obligations. |
| Content matched by data-protection rules | When content being uploaded, sent or downloaded matches your organisation's data-protection rules, the matching content or an excerpt of it, with the file name and file details. Used to prevent and investigate data loss. |
| AI service use | Which AI services are used from the device, so your organisation can apply its AI usage policy. |
| Device security health | Disk encryption, firewall, screen lock, OS version and security software status. Your organisation can require these before granting access. |
| AI tool inventory | AI developer tools, editor extensions and locally installed AI models, and how they are configured — including whether credentials are stored in them. The credentials themselves are never sent. |
| Diagnostics | Logs, configuration and system information when a diagnostic report is produced, and crash information. Used to troubleshoot the client. |
| Terms of Use acceptance | The version you accepted, when, and the local account that accepted it. |
To apply your organisation's policy to secured (HTTPS) connections, the client installs an Adaptive Armor certificate on the device and decrypts those connections in order to inspect them. Your organisation can exclude sites or categories from inspection.
Personal browsing on the device is subject to the same policy as work activity. Your organisation decides what is kept and who is able to see it; your IT or security team can tell you what applies to you.
We use this information to provide the Service to your organisation and to keep it secure and working. We may also use it to improve the Service, including the AI models it relies on.
Activity records are kept for the period your organisation sets, and deleted after it. Device records are deleted when a device is removed or the organisation's account is closed. The record that you accepted the Terms of Use is kept for as long as it may be needed as evidence of that acceptance.
This part applies to the Adaptive Armor mobile app, which provides secure access to your organisation's private network.
The client reports the following to your organisation's console, so that administrators can see which devices are enrolled and whether they are healthy:
| Data | Why it is sent |
|---|---|
| Email address | Identifies the signed-in user. Read from the sign-in token. |
| Device identifier | A stable per-device value, so a device is recognised across restarts rather than appearing repeatedly. |
| Device name, OS version, processor architecture | Shown in the device inventory so an administrator can identify a device. |
| Application version | Lets administrators see which devices run current software. |
| Connection state | Shows whether secure access is currently active on the device. |
| IP address | Observed when the device contacts the Service; used for connectivity and the approximate location of the connection. |
When you connect, the client establishes an encrypted tunnel and carries traffic destined for your organisation's private network ranges through it. Traffic to the public internet is not routed through the tunnel. Which ranges those are is configured by your organisation's administrators, not by us.
Device records and connection history are kept for as long as your organisation retains them, under settings its administrators control, and are deleted when a device is removed or the organisation's account is closed.
Because your employer controls this data, requests to access, correct or delete it are best directed to them. If you contact us instead, we will refer you to them and help them respond.
Questions about this policy: privacy@adaptivearmor.com.