Legal

Security Testing Terms

These terms apply each time you start an offensive security scan. You accept them by ticking the box in the dashboard, or by sending "authorized": true through the API. Swarm Computers is operated by Makerhook Labs LLC, a company in the United States (“we”, “us”). Version 2026-11-21.2.

1. What you confirm

Each time you start an offensive scan, you confirm for every hostname in it:

  • You own the system or have its owner’s written permission to attack it, and you have the authority to approve the test.
  • Where it runs on someone else’s platform, that platform’s rules allow the test.
  • Agents send real attacks. They can create test records, trigger emails or texts, use paid services in your app and cause slowdowns or errors. Those effects and costs are yours.

This is the most important part of these terms, because agents really do attack the systems you point them at. Naming a hostname as the target of an offensive scan is your written authorization for Swarm Computers and its agents to access and test it under these terms. It is your informed consent for the purposes of computer misuse laws, including the U.S. Computer Fraud and Abuse Act (18 U.S.C. § 1030) and similar laws elsewhere. Only the hostnames you name are in scope.

2. Ownership and authority

You own or control each target, or hold its owner’s written permission to have it tested. The person accepting these terms has the authority to do so for the organization that owns the target. Verifying a domain with us shows control of its name. It does not replace this confirmation.

3. Other people’s platforms

Hosting providers, clouds and software services set their own rules for security testing. You are responsible for reading those rules, for getting any consent they require, and for telling them about the test where your contract with them or the law requires it. On shared or multi-tenant systems your permission must cover the test without affecting other tenants. We refuse targets on platforms we know forbid customer testing, but we cannot know every platform behind your systems, and our checks do not shift this responsibility to us.

4. What testing does

Agents use real attack techniques against live systems. They attempt logins, send attack payloads and try to reach data they should not. This can create test accounts and records, trigger emails, texts and other notifications, consume paid services and usage-billed resources in your systems, and cause slowdowns, errors or outages. We do not promise that testing will cause no data loss, slowdown or other effect on your systems, or that it will find every weakness.

Before you test

  • You choose the environment. Test a staging copy where you can, and back up before testing production.
  • Give agents accounts made for the test, holding made-up records. An account called “test” is not safe if it can see real customer data.
  • Change or revoke any passwords, keys or tokens you gave agents once the test is over.
  • If a firewall or bot filter sits in front of the site, expect it to block agents unless you allow them.

5. What we will not do

  • Run denial of service or load tests, or deliberately exhaust your servers.
  • Deliberately delete or destroy your data.
  • Complete real payments or purchases, or message your real customers, on purpose.
  • Point agents at hostnames outside the ones you named.
  • Use what agents find for anything other than your report.

Agents are automated and can act in ways neither of us expects. These are limits we build and enforce, not a promise that no test will ever cause harm.

6. Costs in your systems

Charges that testing causes inside your own systems or accounts with others are yours. Examples are model or API credits, messaging fees, serverless and bandwidth usage, and payment processor fees. Your budget with us limits what you pay us. It does not limit those charges.

7. Claims by others

If someone else brings a claim against Swarm Computers because a test you started was not authorized, broke a platform’s rules, or because something you confirmed above was untrue, you will defend us and cover the resulting losses and costs. That includes claims by the owner, hosting provider or cloud provider of a target, or by another tenant of a shared system. This is not subject to the limit in section 8.

8. Limit of our liability

To the extent the law allows, Swarm Computers is not liable for indirect or consequential loss, lost profits, downtime, or loss or corruption of data arising from testing. Our total liability for a test is limited to the fees you paid us in the 12 months before the event. Nothing here limits liability that cannot be limited by law, such as for fraud or gross negligence.

9. Our right to stop

We may refuse a target, pause or stop any scan, and ask you for proof of authorization at any time. We may suspend testing on your account if your use creates a security, legal or operational risk, or if you do not provide that proof promptly. We will tell you when we reasonably can. You can pause or cancel a scan yourself at any time.

10. Findings and records

Findings are yours and we treat them as confidential. We keep a record of each offensive scan: who started it, when, from which address, for which hostnames, on what proof of control, and which version of these terms was accepted.

11. What you may not do

  • Test systems you have not verified, or try to get around verification or scope.
  • Use the service or its results to attack anyone else.
  • Start tests for someone who has not given you written permission.

12. Changes

When these terms change in substance the version changes, and you are asked to accept the new version before your next offensive scan.