What you agree to when a unit goes on your network.
Two of these clauses do the real work: the authority you confirm you hold, and the fact that the box is sealed and stays that way. The rest follows from them.
You confirm you own the systems in scope, or hold written authority to test them, for the whole window the unit is live.
You own the hardware once it is paid for. What runs on it is not sold open — it is not to be opened, imaged, cloned or reverse engineered, and the seal is how both sides can tell.
It is not general-purpose access into your network, and nothing may be done to disable the supervision or the record.
The box you tick when you contact us says exactly this: “I will only use PLDrop against systems I own or am authorised in writing to test, and I accept the terms of use.” We record which version you accepted, and when.
What these terms cover
These are the published terms for the supply and use of a PLDrop unit, the PLDrop Virtual build, and the PLDrop Console that drives them. They apply from the moment a unit is dispatched to you or a console account is opened for you.
Where a signed order form, engagement contract or master services agreement says something different, that document prevails. This page is the standing text, not a replacement for the contract you sign.
Authorisation — the warranty you give
You may only use PLDrop against systems you own, or that you hold written authority to test. You warrant that this authority exists for every host, network, application and radio in the agreed scope, and that it covers the whole period the unit is live on your network.
Scope is agreed in writing before a session opens and is not extended by adding hosts at the console. If the target changes, the authority has to change with it, in writing, first.
Where a third party operates part of the estate — a hosting provider, a cloud platform, a managed service provider, a landlord whose air you will be listening to — obtaining their consent is your responsibility, not ours.
If that authority is withdrawn, or you learn it never covered part of the scope, tell us and stop the session. The console lets you cut it in one action; use it.
You own the unit; the build inside it is licensed
Title to the hardware passes to you when we have been paid in full. You are buying the unit, not borrowing it, and there is nothing to send back. Risk passes on delivery.
What you do not buy is what runs on it. The operating build, the supervision model and the PLDrop Console are licensed to you for as long as your console licence is current — separately from the hardware you own, and not transferred by selling the hardware on.
The enclosure carries a tamper-evident seal. Do not open the unit, break the seal, or attempt to access its storage, firmware or internal interfaces. The unit is still yours if you break it — but a broken seal ends the hardware warranty, ends support, and we may refuse to re-provision or re-license that unit, because we can no longer vouch for what is inside it.
You may not copy, image, clone, emulate, decompile, disassemble or otherwise reverse engineer any part of the unit, its operating build, its supervision model, or the console — in whole or in part, by any means, including running it in an environment intended to extract it.
You may not benchmark, dissect or study the product for the purpose of building or assisting a competing product. You may sell or transfer the hardware you own, but the console licence does not travel with it — tell us, and we will re-license the unit to its new holder or decline to, in writing.
The PLDrop Virtual build is licensed for the instances agreed with you, on infrastructure you control. The same restrictions apply to the image as to the hardware.
What the channel may not be used for
PLDrop is supplied for authorised security testing. It may not be used for any unlawful purpose, nor against any system outside the agreed scope, nor to gain or retain access for any reason other than the engagement.
The audited channel is not general-purpose remote access into your network. It is not to be used as a jump host for unrelated administration, nor left in place to provide standing access after the engagement ends.
Destructive testing — denial of service, data destruction, physical damage — happens only where it is named in the signed scope, and never by default.
You may not attempt to disable, evade, blind or tamper with the supervision on the device or the audit record it produces, or to remove the unit from the console that governs it. That machinery is what makes the rest of these terms verifiable for both of us.
Supervision, and the controls you hold
Sessions open only on your approval, for the lifetime you set, and you can end one while it is running. Nothing on the unit grants standing access.
The unit supervises its own workspace and your network for activity that does not belong to the engagement, and raises findings to your console. Findings describe what was seen and when; the data they refer to does not leave the unit.
We may suspend a unit or a session where these terms are breached, where we are required to by law, or where supervision indicates a serious and immediate risk. Where we do, we will tell you what we saw and why.
Your data
Engagement records — commands, transfers, captures and reports — are written to storage you own and control. We do not hold them.
What we do hold is the operational metadata needed to run the service: which unit, which engagement, who was approved, by whom, when, and the status of each session. That is described in full in the security pack.
For engagement data you are the controller and we are not a processor of it, because it never reaches us. Where any processing does arise, it is governed by the data-processing terms in your signed agreement.
Export control and sanctions
PLDrop is security-testing equipment. You may not export or re-export a unit, the virtual build, or access to the console to any destination, entity or person subject to sanctions or export restrictions applicable to us or to you.
You confirm you are not, and are not acting on behalf of, a restricted party, and that you will tell us if the unit is to be used at a site in a jurisdiction other than the one it was shipped to.
Warranties and liability
The unit is supplied in working order against the specification agreed with you, and we will replace a unit that fails through no fault of yours.
Security testing carries inherent risk: live systems can behave unexpectedly under test. We do not warrant that a test will identify every vulnerability, nor that any system will be free of them afterwards. A clean report is a statement about what was found, not a guarantee.
Neither party excludes liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be excluded. Beyond that, our liability is limited as set out in the signed agreement, and neither party is liable for indirect or consequential loss.
Changes to these terms
This is version 2026-07-27. Where you have accepted a version, that is the version recorded against your enquiry or order, and a later edit to this page does not change it retrospectively.
Material changes to the terms applying to a live engagement are agreed with you, not published unilaterally.