Hackeris.lv

Rules of use

Version draft-2026-11-19

Draft. Not legal advice.

This text is a working draft. A licensed lawyer has not reviewed it yet. It does not replace a review by your own lawyer, and nobody should rely on it as final legal text until that review is done.

This product runs real security tests against real systems. Testing a system without permission is a crime. Read these rules before you start a Test. They are short on purpose.

Why these rules exist

Under Latvian law (Criminal Law, section 241) it is a crime to access a computer system without permission. The valid permission of the owner of the system is what makes a security test lawful. Section 244 also covers tools that are used to commit such a crime. A clear, written record of who allowed what protects your company, and it protects us as the maker of the tool.

1. Test only what you may test

A Test may only target:

  • systems that your company owns, or
  • systems that the owner has allowed you, in writing, to test.

A spoken promise, a guess or "it is on the internet anyway" is not permission. If you are not sure, do not start the Test.

2. Name the scope exactly

Before a Test, put the limits in writing. A good authorisation names:

  • the exact targets: IP addresses, domains and host names;
  • the time window in which testing is allowed;
  • the people who are allowed to test;
  • the techniques that are not allowed (for example denial of service or social engineering).

Everything that is not named is out of scope. Enter the same targets in the Test, and nothing more.

3. You must be allowed to decide for your company

The person who accepts these rules confirms that they may bind the company: an owner, a board member, or a person the company has given this right. If that is not you, ask the right person to accept the rules.

4. Systems of someone else: bug bounty programs and training labs

A target of a bug bounty program or a training lab is not your system. You do not own it and your company cannot give permission for it. For these targets you confirm something different: that you have the right to test this exact target under the current rules of the party that runs it.

  • Read the current scope and policy of the program or platform before each Test. They change.
  • Their rules come first. If they forbid a technique, a tool or automated testing, that ban applies to you in this product too.
  • Check on your own what they say about automated tools and AI. Many programs limit them.

Our rules never widen what a third party allows.

HackTheBox: AI agents need a separate agreement with HackTheBox

The Acceptable Use Policy of HackTheBox (version of 2026-04-01) does not allow AI agents or automated systems to access HackTheBox services unless you have an express, separate Service Agreement with HackTheBox. Tests in this product are run by AI agents.

  • If you want to run a Test against a HackTheBox target, it is your own responsibility to have that agreement with HackTheBox first.
  • Accepting the rules on this page does not give you that right, does not replace that agreement and does not excuse a breach of the HackTheBox policy.
  • Without that agreement, do not run Tests against HackTheBox targets.

The policy can change. Read the current text on the HackTheBox website.

5. Permission comes first, the Test second

You must have the permission before a Test starts, not after it. Keep the written authorisation where you can show it. Before a Test may start, we may ask you to prove that you control the target, for example with a DNS record that we give you or a small file placed on the target. You are responsible for every Test that is started from your account.

6. Personal data and AI providers

A Test can find personal data, for example names, e-mail addresses or passwords.

  • For your own systems your company is the controller of that data, and we process it for you. The GDPR (Article 28) requires a data processing agreement between us for this.
  • If you connect an AI provider, results of a Test may be sent to that provider. It can be outside the European Union. You choose the provider, so check that you may send the data there.
  • For a system of someone else you are not the controller of its data. Collect as little as possible and follow the rules of that party.

7. What we record when you agree

When you agree, we record who agreed (your account and company), the date and time, the IP address, and the version of these rules. We keep this record as evidence that your company accepted the rules. It can protect your company as well as us.

Your confirmation

Tick the box to continue.