AuditMind Acceptable Use Policy

Effective date: October 26, 2026
Last updated: October 26, 2026

This Policy sets out what you may and may not do when using AuditMind (auditmind.tech). It forms an integral part of the Terms of Use. We have kept it short and direct: the service analyses source code, and misusing it can cause real harm to other people.

1. The core rule: only analyse code you have the right to analyse

You may upload and scan source code where at least one of the following is true:

  • the code is yours;
  • the code belongs to an organisation you act for, and you are authorised to have it analysed;
  • the rightsholder has given you permission to analyse it;
  • the code is under an open licence permitting such use.

On public repositories specifically. AuditMind can technically import any public GitHub or GitLab repository without an access token. That exists for convenience with your own and open-source code, not for probing other people's projects. Code being publicly readable does not entitle you to use the vulnerabilities you find against its owner.

If you discover a vulnerability in someone else's project, follow responsible disclosure: notify the maintainer and allow reasonable time to fix it.

2. Prohibited conduct

2.1. Infringing the rights of others

  • uploading code you have no right to analyse;
  • using the service to prepare attacks on systems belonging to others;
  • collecting vulnerability information about third parties to sell, extort with, or exploit.

2.2. Breaking the law

  • uploading material whose distribution is unlawful;
  • using the service for activity that breaches applicable law;
  • circumventing sanctions or export-control restrictions.

2.3. Harming the service

  • generating load beyond your plan, including through automated requests;
  • circumventing limits, quotas, or authentication;
  • scanning, penetration-testing, or otherwise probing AuditMind's infrastructure without our written permission;
  • uploading malware in order to have it execute in our infrastructure;
  • attempting to access other users' data.

2.4. Misusing accounts

  • sharing account access or your API key with third parties;
  • creating multiple accounts to evade free-plan limits;
  • impersonating another person or organisation.

2.5. Using the service outside its purpose

  • reselling scan results as a standalone service without an agreement with us;
  • decompiling, extracting, or reproducing our analysis algorithms;
  • using the service for published benchmarking without our consent.

3. Security research on AuditMind itself

We welcome good-faith reports of vulnerabilities in the service. If you find one:

  • report it to auditmindd@gmail.com with a description and reproduction steps;
  • do not use the vulnerability to access anyone else's data;
  • do not publish details until the issue is fixed or 90 days have passed since your report.

We will not take legal action against researchers who stay within these bounds.

4. Consequences of breach

Depending on severity, we may issue a warning, restrict features, suspend the account, delete the account and its data, or report the matter to the authorities where the law requires it.

Where a breach poses an immediate threat, access is suspended without prior notice.

5. Reporting a violation

If you believe your rights are being infringed through AuditMind — for example, someone is analysing your private code — write to auditmindd@gmail.com and include:

  • what the violation consists of;
  • which rights you rely on and what evidences them;
  • your contact details.

We review such reports within 10 business days.

6. Changes to this Policy

The current version is published on this page with its date. We notify users of material changes by email or in the interface.

7. Contact

Operator: the AuditMind project team
Questions and complaints: auditmindd@gmail.com
Vulnerability reports: auditmindd@gmail.com