Trust and security

Last reviewed: 28 September 2026. Written for whoever does vendor review. The binding texts are the privacy policy and the terms; where this page and they differ, they win.

1. Where your code goes

Where your code goes A pull request on GitHub sends its diff to the MagAudit check on one server in Finland. The check posts a comment and a check back to GitHub, keeps the report in memory for up to seven days, stores only metadata, and sends only package names and versions to the package registries. The route to an AI model is blocked at the server boundary. YOUR GITHUB ONE SERVER · FINLAND · EU THIRD PARTIES DIFF FINDINGS NAMES + VERSIONS NEVER Pull request opened or updated Comment + check line, reason, fix MagAudit check deterministic · no AI diff in memory, then discarded Full report memory only · ≤ 7 days Metadata names, counts · no code Package registries PyPI · npm · advisories Any AI model blocked at the boundary
The whole path in one picture. The table below gives the detail; the privacy policy is the binding text.
QuestionAnswer
Where is my code read?On one virtual server we rent from Hetzner Online GmbH in Finland (European Union). Nowhere else. It is not exclusive to this service: other internal projects of ours run on the same machine.
Does any AI model see it?No. The checks are deterministic. Your code is never sent to an AI model, and an automated test blocks our deployment if any part of the service is wired to one.
What leaves the server?Package names — and, for the advisory check, the pinned version — to pypi.org and registry.npmjs.org; to their download counters, api.npmjs.org and, only for Python packages under 90 days old, pypistats.org; and to api.github.com. That list is the whole list.
What do you write to disk?Installation ID, organisation, repository name, pull request number, risk level, counts and billing data. Never your source code and never the value of a secret we detect.
And the report linked from the pull request?Held in memory only, for up to seven days, and lost if the service restarts. It includes the flagged lines so the person reading it can see them.
What happens when I uninstall?Access ends immediately, and the stored data about your organisation is deleted automatically. If you were on a paid plan we keep only the link to your Stripe customer, anonymised, so a subscription can be cancelled or refunded cleanly.

The complete list of organisations that process data for us — hosting, payments, email, this website — and exactly what each one receives is in section 3 of the privacy policy.

2. What we ask GitHub for, and why

GitHub shows you this list when you install. Here is what each permission is for, and what we never do with it.

read

Contents

Download the diff of each pull request, read the files of the install-time scan (limits in our privacy policy) and read your .magaudit.yml.

Never: write, push or delete code. We cannot — the permission is read-only.

write

Pull requests

Post the findings comment and the suggested fixes you can commit with one click.

Never: merge, close, approve or edit your pull requests.

write

Checks

Publish the pass/fail check, which only blocks a merge if you mark it as required.

Never: change your branch protection or anyone else’s checks.

write

Issues

Update our own comment instead of adding a new one, and react 👍 when an owner sends a @magaudit ignore command.

Never: open, close or edit your issues.

read

Metadata

Repository names and visibility. Every GitHub App gets this.

We only see the repositories you select during install, and you can change that list at any time. Uninstalling cuts our access immediately and deletes your data as described in the privacy policy. We never receive your organisation settings, your secrets or your members.

3. For your vendor review

If your review needs either one today, tell us before you install and we will tell you exactly what we can and cannot document. Better to know before a trial than after.

4. How the service is run

5. How often we are wrong

Every false positive we have fixed is pinned by a regression test built from the exact line we got wrong, in a real public repository, with the pull request cited. The record is public →

6. If something goes wrong

If a personal data breach occurs we notify the supervisory authority within 72 hours, as Article 33 GDPR requires, and affected organisations without undue delay. If you find a vulnerability in our service, write to contact@magsolutionsai.com with the subject “Security” and please do not open a public issue.

7. Who is behind it

MagSolutionsAI is built and run by one person in Spain, under Spanish law. The service went live in July 2026 and has no paying customers yet; we will not show logos or testimonials until there are real ones.

Install on GitHub →