Seed Factory

dsgvo-check: Checking a Website for DSGVO Requirements Before Someone Else Does

An open scanner that shows what your website actually does with visitors’ data — before consent, after rejection, and behind the scenes.

Open SourceDSGVOPrototype

The release was prepared jointly, in collaboration with Ivan Kibets.

dsgvo-check — first screen of the report

Why Businesses Need It

Most websites have a consent banner and a privacy policy. Far fewer have actually checked whether what is written matches what happens in a visitor’s browser.

In practice, discrepancies occur constantly. Analytics starts collecting data before a person clicks “Accept”. Advertising pixels send information about a visitor to an advertiser without any consent. The “Reject” button closes the banner, but trackers continue to operate. Meanwhile, the privacy policy lists entirely different services.

The website owner does not see this: the page looks normal. But it is precisely these discrepancies that become grounds for complaints from visitors, claims from competitors, and questions from supervisory authorities.

dsgvo-check opens a website like an ordinary visitor and records what happened. As a result, you get a report with specific observations and a clear list of “what to fix”.

What the Scanner Checks

  • ✓Data collection before consent. Which analytics and advertising services receive data and set identifiers before the visitor has made any choice.
  • ✓Whether rejection works. The scanner clicks “Reject” and checks.
  • ✓The banner itself. Whether it is possible to reject on the first screen and whether this option is equal to consent.
  • ✓Embedded services. Maps, videos, and other external resources.
  • ✓Legal pages. Whether the Impressum and privacy policy are accessible and whether the policy names the services that actually operate on the website.
  • ✓Basic security. HTTPS and certificate, security headers, protection against sender spoofing.

A total of 20 checks. Each finding receives a severity level — critical.

dsgvo-check — finding card with evidence

What You Get

The report comes in two versions. A short one — for the owner, explaining what to do about it in simple terms. A detailed one — for a developer or agency: which request, on which page, at what moment, with evidence. Both are available in German and English, in HTML and PDF.

dsgvo-check — table “service — before consent — after rejection”

The scanner can be integrated into the website release process. Then the check runs with every update, and a new problem — for example, marketing has added an advertising pixel — is detected before publication, not afterwards.

What the Scanner Does Not Do

It is important to say this directly. dsgvo-check records facts. It writes “a request was observed before consent”, not “the website violates the law”. The report does not replace legal advice and is not a certificate of compliance. The absence of findings means that the scanner did not notice anything on the checked pages, not that the website is flawless.

The scanner operates passively: it does not fill out forms or log into accounts. It does not store cookie values or identifiers — neither in the report nor in the logs.

The project is at the prototype stage. Banners are recognized for ten common solutions, including Cookiebot, Usercentrics, Borlabs, Complianz, and Shopware. If the banner is non-standard, the scanner cannot assess it.

Open Source

dsgvo-check is published under the Apache 2.0 license. You can see how it works and adapt it to your needs.