The fetcher that reads suppliers' published terms
If MaditonBot has visited your site, this page says who it is, why it came, what it read, and how to stop it. It identifies itself on every request and never pretends to be a browser.
What it is
Maditon is an EU compliance assistant for startups and SMEs. Its customers keep a register of their suppliers and of the legal documents those suppliers publish — privacy policy, terms of service, data processing agreement, sub-processor list, security page — because GDPR Article 28 and Article 30(1)(d) and NIS2 Article 21 ask them to know what their processors have committed to. MaditonBot is the program that fetches those published pages on a customer's behalf and fetches them again later to notice when they change.
How it identifies itself
Every request carries this header, and the address points here:
User-Agent: MaditonBot/1.0 (+https://maditon.com/bot)Requests come from Maditon's own servers in the European Union (Hetzner, Finland and Germany). The bot does not run JavaScript, does not fill in forms, does not sign in, and does not use browser automation, proxies or rotating addresses. What you see in your logs is what it is.
What it fetches
- Only published legal documents. A page is fetched because a Maditon customer registered it as one of their supplier's legal documents, or because your own site linked to it from the homepage or a legal hub as such a document. Nothing behind a login is ever requested.
- Only readable formats. HTML, PDF, Word (.docx) and plain text. Anything else is recorded as unreadable, not guessed at.
- Only so much. At most 15 MB per document, a 30-second timeout, at most five redirects, and every redirect is checked before it is followed.
How often
A document is fetched when a customer adds it or asks for a fresh reading, and — if the customer chose to watch it — once every seven days by default. Runs are spread out so that a supplier's pages are not requested back to back, and the bot never sends more than one request per second to any host.
How to stop it
Answer 403 or 429 to the user agent above. MaditonBot records the refusal, stops trying that document, and tells the customer to upload the document instead. It does not retry, change identity or route around a block. If you would rather we simply never visited, write to support@maditon.com and we exclude your host. MaditonBot does not currently read robots.txt; blocking by user agent or writing to us are the two ways that work today.
What happens to what it reads
The text of a published document is read by an AI model on an EU endpoint to produce a plain-language reading for the customer who registered it, with quotes that point back to your wording. It is your published text, treated as published; nothing about the customer travels with it. Where the reading is done is described in our privacy policy and on the security page.
Questions
support@maditon.com. If a request from this user agent does not match what this page says, we want to know about it.