Free lead review ↗

Policy

Acceptable Use Policy

Last updated: 11 September 2026. This policy applies to this website, all AiActions systems, and in particular to the AiActions Security Testing platform. It exists because the tools involved are capable of real impact — read it before requesting or running any engagement.

1. Scope

This policy applies to anyone using aiactions.co.uk, any AiActions-delivered system, and specifically to any person granted access to the AiActions Security Testing platform, whether as an AiActions team member or an invited client.

2. Authorised use only

Security testing features must only be used against systems, devices, networks or accounts you own, or for which you hold clear, current, written authorisation from the owner to test. "I'm pretty sure it's fine" is not authorisation. Every engagement on the platform requires an explicit written scope — target list, permitted dates, maximum testing mode and allowed ports — agreed and sealed before any active check can run. Attempting to test a target outside that sealed scope is a breach of this policy regardless of intent.

3. Prohibited activity

  • Testing, scanning or attempting to access any system without the owner's explicit written permission
  • Using AiActions systems to disrupt, damage, deny service to, or degrade the performance of any system, whether in scope or not
  • Any activity that would constitute an offence under the Computer Misuse Act 1990 or equivalent legislation in the jurisdiction of the target
  • Credential theft, credential stuffing, or use of compromised credentials against any target
  • Exfiltrating, retaining or distributing data beyond what is strictly needed to evidence a finding within the agreed engagement
  • Sharing platform access, API keys or engagement credentials with anyone not named on the engagement
  • Using the platform's active/deep/lab testing modes against production systems without a change window or rollback plan agreed with the system owner
  • Circumventing, disabling or attempting to bypass the platform's scope enforcement, rate limiting or emergency stop

4. Permitted use

Permitted use includes: authorised penetration testing and vulnerability assessment of targets you own or have written permission to test; internal security audit and compliance evidence-gathering; security training and awareness within a lab environment you control; and evaluating your own systems ahead of a launch or renewal.

5. Client and user responsibility

If you are a client requesting an engagement, you are responsible for confirming you have the right to authorise testing of every target you provide, and for the accuracy of the scope, dates and contacts you give us. If you are a user with direct platform access, you are responsible for keeping your credentials confidential and for every action taken under your account. Emergency stop is available throughout every engagement — use it immediately if a test produces an unexpected effect on a live system.

6. Enforcement

We may suspend or terminate access to AiActions systems immediately, without notice, for any suspected breach of this policy, and reserve the right to refuse an engagement where authorisation cannot be confirmed to our reasonable satisfaction. Where we believe unlawful activity has occurred, we may be required to report it to the relevant authorities. Breach of this policy may also terminate the related service agreement under our Terms of Service.

7. Reporting a concern

If you believe an AiActions system has been used against a target without authorisation, or you've found a security issue in an AiActions-delivered system, tell us: info@aiactions.co.uk.