How does Maditon read a supplier's document, and what is a finding?

The reading is done in three stages, and keeping them apart is what makes the result checkable.

Extraction. The model pulls out what the document actually states — the retention period, the sub-processor notice, the transfer mechanism, the uptime commitment, the support channels — each fact paired with the passage it came from. Nothing enters the record without a quote.

Judgement. Only then does the model compare what was found with what a document of that kind owes. A data processing agreement owes the Article 28 terms; a terms-of-service page does not. Where the document is silent on something it owes, that silence becomes a finding marked not addressed. Where it says something that ought to worry you — a US transfer without a named mechanism, a notice period you cannot live with — that becomes a finding with the quote beside it.

Summary. A short plain-language account of what the document is and what the reading left open, written for the person who will decide what to do.

Every finding carries a severity — high, medium or low — and a suggested question for the supplier. That framing is deliberate: a published page can show what a supplier has committed to in writing, never what it does in practice, so a finding is the start of a conversation, not a verdict. E-mail addresses and phone numbers are masked before any text reaches the model, and the reading runs on Mistral’s EU endpoint with training on submitted data switched off.