Skip to content
Search List Check
DE EN
Sign in My account

Privacy policy

  • Controller
  • Hosting and access data
  • Fonts
  • Cookies, tracking and access data
  • Contact
  • Waitlist
  • Account and sign-in
  • Request “More of this” and feedback
  • Website analysis by DachStack
  • Retention period
  • Your rights
  • Changes

Courtesy translationThis English text is a courtesy translation. The German version is the legally binding one.

1. Controller

Samuel Statz
c/o POSTFLEX PFX-416-167
Emsdettener Straße 10
48268 Greven
Germany
Email: hallo@dachstack.de

2. Hosting and access data

When you visit this website, our hosting provider automatically processes the following data:

  • IP address
  • Date and time of the request
  • Browser and operating system
  • Referrer

The processing takes place to provide the website securely (Art. 6(1)(f) GDPR). The data is deleted automatically after a short time.

We use the following service providers:

  • Hosting: Railway — location: EU West (Amsterdam, Netherlands)
  • CDN / protection: Cloudflare — processing partly in the EU, partly international. Cloudflare is certified under the EU-US Data Privacy Framework (DPF).

3. Fonts

This website uses self-hosted fonts. No external services (e.g. Google Fonts) are included — no data is transmitted to third parties when the page loads.

4. Cookies, tracking and access data

This website uses no tracking cookies and no external analytics tools. Local settings (e.g. search history) are stored exclusively in your browser (localStorage). This data does not leave your device.

To prevent abuse, when a check is made we store the domain and your network address only as a salted hash, that is, without a readable address. These entries are deleted automatically after 7 days.

Measurement: So that we can see whether DachStack is being used, we count page views, checks, searches, exports, server errors, limits reached, requests and returning visits as simple events with a date, a campaign (utm_campaign, if you arrive through a link with a campaign) and, for checks, searches and exports, the hash of the device identifier. We do not store results. For searches and checks we additionally record which filters were selected (for example technology, industry, country) and which domain was checked, in lower case and cut to 60 characters, and whether the search had results. We do not store free text, places, postal codes, email addresses or longer number sequences, and the evaluation shows the selections only per day and does not link them to a device. The selections are only counted into a daily list of the most frequent entries, so that we can see what is needed and what is missing. A further purpose is to detect and prevent abuse, for example when the same domain is checked unusually often, and to keep requests to third-party sites per domain within a polite limit. Server errors are counted without a device identifier. The device identifier comes from the cookie ds_geraet (see below). There is no readable network address, no name, no further cookie and no third-party service for this; the salted hash of the network address serves only the quota (see below). For page views we also store the page called, the domain of the referring page (without path or search term), the device type (mobile, tablet or desktop), the country if an upstream service supplies it, and a daily identifier. The daily identifier is a hash that is re-salted every day; it is used to count unique visitors and to prevent abuse, and it links nothing across days. We delete these events after 90 days. From them we form daily totals (for example, the number of searches per day), which we combine and keep in an internal evaluation without any reference to a person or device. Legal basis: Art. 6(1)(f) GDPR (we want to understand whether the offer is needed).

Cookie for checks and sign-in: When you check a website, we set the technically necessary cookie ds_geraet (HttpOnly, SameSite=Lax). It contains a random identifier with no personal reference, is valid for 180 days, and only serves to count your checks (quota) and to recognize you after sign-in. It is not used for advertising or analytics and is not passed on to third parties. The database holds only a hash of it. The device entry is deleted 400 days after it was last seen at the latest.

Cookie for language: When you choose the language of the page (German or English), we remember this in the technically necessary cookie dachstack_lang (SameSite=Lax, valid for 1 year, not HttpOnly, because the page script also sets it when you click DE or EN). It contains only “de” or “en”, serves only to show the page in your language, and is not used for advertising, analytics or recognition. Without a choice, the language follows the language setting of your browser (the Accept-Language header), which we do not store.

Quota: For the quota (how many checks are possible per day and when it continues) we store the network address and the identifier from the cookie exclusively as a salted hash (not reversible without the secret salt value) together with a counter. These counters are deleted 2 days after the time window ends at the latest. Legal basis: Art. 6(1)(f) GDPR (protection against abuse and overload).

5. Contact

If you contact us by email, we process your details to handle the request. Legal basis: Art. 6(1)(b) or (f) GDPR.

6. Waitlist

When you sign up for the waitlist, we store your email address. Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by email.

6a. Account and sign-in

Signing in is voluntary. It works without a password: you enter your email address and receive a six-digit code by email (without a link). We store your email address, the time of your consent and, if you provide them, your interests (technology, country, industry). The code is stored only as a hash, is valid for 10 minutes and works only once. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.

You can delete your account with interests yourself at any time (signed in, using the “Delete account” function) or have it deleted by email to hallo@dachstack.de. We delete accounts you have not signed in to for 24 months automatically. The codes are sent through an email service provider as soon as one is set up; this policy will then be extended with the provider.

We evaluate the interests stored in accounts (technology, country, industry) only as totals, without any link to an email address, and we look at values only from five accounts upwards. This shows us what people search for and lets us improve the service. Legal basis: Art. 6(1)(f) GDPR.

6b. Request “More of this” and feedback

When you send us a wish through “More of this” (higher limits, automatic reports, CRM connection or other), we store your email address, your selection, your text, the campaign you came through, and the time of your consent. You receive a confirmation by email, and we receive a notice. If you send another request with the same address, we merge it with the first. Legal basis: your consent (Art. 6(1)(a) GDPR). We delete the request 12 months after the last change. You can withdraw it at any time by replying to the confirmation or writing to us.

Feedback: Through the field “What is missing?” you can tell us what is missing or wrong. We store your text, the page you write from, the campaign you came through and the time. We store an email address only if you choose “Yes, get back to me” and give your consent (Art. 6(1)(a) GDPR); otherwise the message stays anonymous. We receive a notice by email. Do not write personal details of third parties in the text. We delete feedback 12 months after it arrives. You can withdraw your consent at any time.

7. Website analysis by DachStack

DachStack analyzes publicly accessible technical information of websites. The following data is collected:

Technical data

  • Technologies used (CMS, frameworks, programming languages, CDN, hosting)
  • HTTP headers and server information
  • SSL/TLS certificate data (issuer, validity, protocol)
  • DNS records (MX, SPF, DMARC, name servers)
  • Presence of third-party integrations (e.g. Google Analytics, Stripe — only whether present, no IDs or credentials)

Company data from the legal notice

Which fields from a legal notice are stored depends on the legal form of the company:

  • For corporations (GmbH, AG, UG, SE, KGaA, eG, gGmbH, foundation, GmbH & Co. KG): company name, legal form, commercial register number (HRB), VAT ID, business address, public role-based email address, business phone number. We do not store the names of managing directors or board members.
  • For sole proprietors, freelancers and partnerships (e. K., GbR, PartG, OHG, medical practices, law firms): company name, legal form, place, postal code, public register references (HRA, VAT ID) and a public role-based email address (e.g. info@, kontakt@, vertrieb@). Personal name, street address and phone number are not stored in these cases, even if they appear in the legal notice.

Email addresses are filtered to role-based mailboxes at the time of collection — personal patterns such as firstname.lastname@, single first names or initials are discarded regardless of the legal form. Raw text or original HTML is never stored; only a SHA-256 hash of the retrieved content is kept.

The basis for this processing is Art. 6(1)(f) GDPR (legitimate interest). Legal notice data of a legal entity must by law be published under § 5 DDG. The Higher Regional Court of Celle (OLG Celle) confirmed with its decision of 24 February 2023 (case no. 9 W 16/23) that data protection rights to object do not conflict with the obligation to publish in the commercial register.

Principles of data collection

  • No protected areas are accessed
  • No user profiles are created
  • Only publicly accessible data is processed
  • Credentials, API keys or tracking IDs of third parties are not stored
  • robots.txt is checked and respected before every page request; the status of every check is logged
  • The click measurement (clicks on buttons and links, time spent in classes, scroll depth in quarters, page and campaign) works without a cookie, without an identifier and without a network address; no person or device is recognized again. The counting of checks, searches and exports is described in the paragraph “Measurement”. Anyone who sends “Do Not Track” or “Global Privacy Control” is not measured. Retention 90 days.
  • The full source code is never stored in the database — only a SHA-256 hash. For re-evaluating new detection patterns without a new request, a filtered page skeleton is kept locally (see “Retention period”)

Website operators can prevent crawling at any time (e.g. through robots.txt or by request).

Who is fetching here?

If DachStack/0.1 (+https://dachstack.de) appears in your access logs, that was our request for your public website, made to detect which technology it uses.

  • Order: First we read your /robots.txt. If the home page is blocked there for DachStack or *, or the file cannot be read (server error), we fetch nothing further.
  • Scope: One request for the home page and, if robots.txt allows it, one after the other your legal notice page and up to five more public pages (according to sitemap.xml or the home page). No sign-in, no forms, no files, no circumventing of protection measures.
  • Pace: At least half a second pause between two requests to your server. A Crawl-delay entry in your robots.txt applies (up to 10 seconds).
  • Stored: detected technology and extensions (plugin, theme and module names read from the page addresses), some features of the page (job page, shop hint, languages, size class) and the public details from your legal notice, not the source code.

8. Retention period

  • Anonymized access data: deleted automatically after 7 days
  • Waitlist emails: until you withdraw your consent
  • Contact requests: 6 months after the request is closed
  • Feedback: 12 months after it arrives
  • Filtered page skeleton (tags and attributes, headers, DNS records; without visible text, structured data, email addresses and author details), kept only locally, not in the database and not passed on: 6 months, then deleted automatically. Deletion per domain on request.
  • Analyzed website data: 12 months from the last successful scan. After that, all entries (domain, technology detections, company data, DNS metadata) are deleted completely by automated daily cleanup jobs. Deletion on request is possible at any time within 7 working days.
  • History of the detected technology of a domain (technology, period, no personal data): 24 months, then deleted.
  • Deletion log (aggregated counts without reference to an entity): 3 years for accountability under Art. 5(2) GDPR

9. Your rights

You have the right to:

  • Access (Art. 15 GDPR)
  • Rectification (Art. 16 GDPR)
  • Erasure (Art. 17 GDPR)
  • Restriction of processing (Art. 18 GDPR)
  • Data portability (Art. 20 GDPR)
  • Objection (Art. 21 GDPR)

You also have the right to lodge a complaint with a data protection authority.

10. Changes

This privacy policy may be updated.

As of: April 2026

This website sets no tracking cookies. We store anonymized access data to prevent abuse.

© 2026

Guides Contact Legal notice Privacy Terms