// TRUST & SECURITY

What happens to a repository you have checked.

This page says how the check handles other people's code, where the data lives, what we store for how long and where to report a vulnerability. It describes what the code does today (as of 21 November 2026), not what is planned.

// THE CHECK

How the check runs

  • The code is never run, built or installed. The check only reads it as text.
  • Public repositories on github.com, gitlab.com, bitbucket.org and codeberg.org only, over HTTPS only, with no credentials, no port and no IP address in the address.
  • Before every connection we resolve the name ourselves and stop if an address points into an internal network (private networks, loopback, the cloud's metadata addresses). We do not follow redirects to other servers.
  • We fetch a shallow copy: at most 200 commits, no tags, no submodules; at most 50 MB within 60 seconds, at most 20,000 files and 200 MB in the checked commit. Symbolic links are written as ordinary files, and at most 5,000 files are read.
  • A check takes five minutes at most. Then we delete the copy, also when the check fails.
  • Against abuse we count checks per session, per IP address and in all; the counters live in memory only.
  • The AI panel does not get the whole repository but excerpts: at most 40 source files, the first 1,500 characters of each, 24,000 characters in all. The questions of “Defend your repo” refer to excerpts of at most 1,200 characters.
  • Every result is signed with a key in Azure Key Vault; the signing happens inside the vault and the key never leaves it. The public keys to verify a result are at /.well-known/did.json.

// HOSTING

Where the data lives

  • Servers, database, keys and logs: Microsoft Azure, region Germany West Central (Frankfurt am Main).
  • The site is delivered through Azure Front Door, Microsoft's global network: a request reaches the nearest Front Door location and goes from there to our servers in Frankfurt. The servers accept no other way in.
  • The AI panel and the questions of “Defend your repo” run on Azure OpenAI. The account is in Frankfurt, and processing stays in Microsoft's EU data zone. Microsoft may keep prompts and answers for up to 30 days to detect abuse.
  • Secrets such as the sessions' key live only in Key Vault, not in the application's settings.
  • The operator console is open only to people who sign in with Microsoft Entra ID and are on our list.

// STORAGE

What we store and for how long

We store only what the check and the site need. What the analytics tools store after your consent is in the privacy policy.

WhatWhereFor how long
The copy of the repositorythe server's temporary folderuntil the check ends, then deleted
The result: repository address, branch, checked commit, each stage's evidence, the verdict, the signed credential, the questions of “Defend your repo” with their excerpts and, if given, the answersAzure SQL in Frankfurt, under a random session id (no name or email address)with no time limit, until it is deleted; until then anyone who has its verification link can open it, unless it is hidden. After a deletion only a note remains that the run was deleted and when, without its content; backups of the database still hold the result until their retention ends.
The guest sessionyour browser's storage (localStorage)until you clear it in your browser
Counters against abuse (per session, per IP address)the server's memoryone hour at most
Logs for operation and troubleshootingAzure Monitor in Frankfurt30 days
Requests through the help formKontor, our support system on Microsoft Azure in Germany24 months after the request is closed

Whoever started the check can hide its result (you can undo it) or delete it for good: through “Hide or delete” beside the result, in the browser the check ran in. Hidden, the verification link, the report, the badge and the history no longer show it; deleted, the verification link, the reports and the credential answer “no longer available”. A downloaded credential stays valid as signed.

// SUB-PROCESSORS

Sub-processorsDRAFT · LEGAL REVIEW IN PROGRESS

These services process data for Acquispect. The list is a draft: it is under legal review and may change afterwards.

ServiceWhat forWhich dataLocation
Microsoft Azureservers, database, keys, logs, delivery through Azure Front Doorall of the aboveGermany West Central (Frankfurt); Front Door: Microsoft's global network
Microsoft Azure OpenAIAI panel and “Defend your repo”excerpts of the checked code, the questions and your answersEU data zone (account in Frankfurt)
OSV.dev (Google)checking the dependencies against known vulnerabilitiesnames and versions of the packages in the repository's lock filesnot checked by us
Google Fonts (Google Ireland Ltd.)the site's typefacesIP address when the page loadsnot checked by us
Google Analytics and Google Tag Manageraudience measurement: the Tag Manager loads on every visit, with every consent signal set to “denied” until you consent; cookies and measurement only after your consentIP address when the Tag Manager loads; with your consent, what the privacy policy describesnot checked by us
Microsoft Clarityusage analytics, only after your consentas described in the privacy policynot checked by us
Kontor (ballmüller solutions, our own system)help form and the chat with Elizayour request, your email address, the session idMicrosoft Azure in Germany; Eliza on Azure OpenAI in the EU data zone

There is no data processing agreement (DPA) template yet.

// LIMITS

What does not exist yet

  • No deletion period for results: a result stays until it is deleted.
  • No data processing agreement (DPA) template.
  • No independent third-party security report (such as SOC 2 Type II).
  • No choice of hosting location: everything runs in Frankfurt.

// SECURITY

Report a vulnerability

  • If you find a vulnerability in acquispect.com, write to info@ballmuellersolutions.com (subject “Security”). Name the affected address, the steps and what you saw.
  • Test only with your own repositories and your own sessions, without creating load and without fetching other people's data.
  • There is no bug bounty programme.
  • The machine-readable version is at /.well-known/security.txt (RFC 9116).