How does Maditon know when a supplier changes their terms?

A supplier who adds a sub-processor or shortens a deletion promise does not write to tell you. Under GDPR Article 28(2) you are entitled to be told about changes to sub-processors, and in practice the way most companies find out is that somebody re-reads the page.

What gets watched. Documents belonging to a supplier you marked as in use, documents of a supplier you chose in a purchase, and anything you switch on yourself.

What a check does. Fetches the page, extracts the text, and compares it with the last stored version. Identical text costs nothing and calls no model. Changed text is diffed — by paragraph, or by sentence when the extracted text has no paragraph breaks — and only the difference is sent to be read.

Material or not. The model is asked whether the change affects what the supplier promises. A change it judges cosmetic is recorded and not flagged. A change it could not read is recorded as unclassified — never as “not material”, because nobody checked it. The diff is always kept, so the summary is a claim you can verify rather than one you have to trust.

When a page disappears. A supplier who moves or removes a document shows up as unreachable rather than vanishing from your register. The document and its history stay; two failed checks in a row put it in the daily email.

Checks are polite: one request per supplier’s host per second, whatever else is queued.