AuditMind Privacy Policy

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

This Policy explains what data AuditMind (auditmind.tech, API at api.auditmind.tech) collects, why, how long it is kept, and how to delete it. The data controller is the AuditMind project team.

We describe the data in detail, category by category, on purpose: AuditMind processes source code, and you should know exactly what reaches us.

1. What we collect

1.1. Account

Email address, name, avatar, interface language, plan, whether two-factor authentication is on, and the last 4 characters of your API key so you can recognise it in a list.

1.2. Sign-in data

  • Password hash. We do not store your password and cannot recover it.
  • API key hash.
  • Two-factor secret and backup codes, if you enable 2FA.
  • One-time codes for sign-in and password reset, with a limited lifetime.
  • Revoked token identifiers, so that signing out genuinely ends a session.

1.3. Sessions and devices

For each active session we store the IP address, the browser User-Agent, the creation time, and the time of last activity, so you can see your devices and revoke sessions you do not recognise.

1.4. GitHub and GitLab data

Signing in with GitHub gives us your GitHub account identifier, username, and associated email address.

About permissions. GitHub sign-in also requests access to your repositories (repo). That permission exists so private repositories can be imported. You can revoke it at any time in your GitHub settings.

If you supply a personal access token to work with a private GitHub or GitLab repository, we store it and use it solely to read the repository you specified and to clone it for scanning. The token is deleted together with the repository, and can also be revoked on GitHub's or GitLab's side.

1.5. Source code and scan results — the most sensitive category

This is the core of the service, so we list it in full:

  • uploaded files and archives containing source code;
  • repository contents imported from GitHub and GitLab: the file tree with sizes, and the contents of individual files;
  • your file selection for a scan and the archive assembled from it;
  • scan results: file paths, line numbers, vulnerability classification (CWE, OWASP), confidence level;
  • the data-flow chain — the sequence of expressions from source to sink. It contains excerpts of your source code and file paths with line numbers;
  • the name of the method the problem sits in;
  • model commentary on findings;
  • source code edits you save in the editor: the full contents of the changed file are stored;
  • scan reports in JSON and PDF.

1.6. Technical logs

Service logs record requests and errors. Passwords, tokens, and the contents of your code do not go into logs.

1.7. Cookies

The service uses strictly necessary cookies and browser storage to maintain your session; signing in is impossible without them. We set no advertising or analytics cookies. [IF ANALYTICS IS ADDED, DESCRIBE IT HERE AND ADD A CONSENT BANNER]

2. Why we process data

  • providing the service: analysing code and returning results;
  • authentication, account protection, and preventing unauthorised access;
  • sending operational messages: verification codes and security notifications;
  • user support;
  • keeping the service stable and protecting it from abuse;
  • complying with legal obligations.

We do not sell your data and do not share it for advertising.

We do not use your source code to train models without your separate, explicit consent.

3. Legal bases

We process data on the basis of your consent, performance of a contract (the Terms of Use), our legitimate interest in securing the service, and compliance with legal obligations.

4. Who we share data with

WhoWhat they receiveWhy
Hosting providerAll data held on the serversInfrastructure hosting
GitHubAPI requests made on your behalfRepository import, GitHub sign-in
GitLabAPI requests made on your behalfRepository import
Google (Gmail SMTP)Recipient address and message bodyDelivering verification codes

We may also disclose data in response to a lawful, properly issued request from a competent authority.

5. Where data is stored

AuditMind's infrastructure runs on servers in [HOSTING COUNTRY — CONFIRM WITH THE PROVIDER]. Source code, reports, and archives are held in object storage on the same infrastructure.

[IF THE SERVICE TARGETS USERS IN RUSSIA: state that primary processing of Russian citizens' personal data takes place in databases located in Russia (Art. 18(5) of Federal Law 152-FZ). If the actual hosting is outside Russia, that requirement is not met and must be resolved before publication.]

6. How long we keep data

CategoryRetention
AccountUntil you delete it
Source code, archives, and reportsUntil you delete the scan or the account
Scan results and code editsUntil you delete the scan or the account
Repository access tokenUntil you delete the repository
Sessions and devicesUntil the token expires or the session is revoked
One-time codesMinutes, until used or expired
Technical logsA limited period, until log rotation

Deleting a scan deletes its findings and saved code edits. Deleting your account deletes your credentials, repositories, scans, findings, and uploaded code.

7. How we protect data

  • all traffic is served over HTTPS;
  • passwords are stored as irreversible hashes;
  • optional two-factor authentication;
  • access separation: one user's data is not reachable by another;
  • a list of active sessions, any of which you can revoke;
  • rate limiting on verification code attempts, with a temporary lockout.

No method of transmission or storage is completely secure. If an incident occurs that threatens your rights, we will notify you and the supervisory authority within the periods required by law.

8. Your rights

You have the right to obtain information about the data we process, correct inaccurate data, delete your account and associated data, withdraw consent, restrict or object to processing, receive your data in a machine-readable format, and lodge a complaint with a supervisory authority.

Send requests to auditmindd@gmail.com. We respond within 30 calendar days.

9. Children's data

The service is not intended for people under 18. We do not knowingly collect their data. If such data has reached us, write to auditmindd@gmail.com and we will delete it.

10. Changes to this Policy

The current version is published on this page with its date. We give at least 14 days' notice of material changes by email or in the interface.

11. Contact

Controller: the AuditMind project team
Data protection enquiries: auditmindd@gmail.com
Website: auditmind.tech