232 APPS TRACKED · 227 CLAUSES ON FILE · 38 WITH NO CLAUSE TO QUOTE
THE GAP

We fetch 233 policies. 232 became verdicts.

The difference is 1 companies, and this page is the whole of it. Each one is a policy we set out to read and didn't, with the reason and the date we last tried. Elsewhere on this site "tracked" means a company with a verdict, the 232, so these 1 are counted nowhere else.

None of these is graded UNCLEAR. UNCLEAR means the policy doesn't answer the question, and that's a finding about a document we've read. We haven't read any of the documents below, so saying anything about what they contain would be inventing the thing this site exists to check.

1
Their robots.txt refuses us
0
We are turned away in practice
0
Nothing is stopping us

Their robots.txt refuses us

A stated instruction, and we follow it. Nothing is fetched from these hosts at all. They're registered here so the weekly run keeps testing whether that has changed, and so the absence is a recorded decision, not an oversight.

YouTubelast tried 10 September 2026
youtube.com's robots.txt disallows the terms page, and the monitor obeys it. A copy saved by hand from a browser can be imported with scripts/import-manual.py, as N26's and DBS's were.
https://www.youtube.com/t/terms

The monitor identifies itself honestly on every request, sends a contact address, and obeys robots.txt. It isn't disguised as a browser, and it isn't made to look like one to get past a block.

That leaves one way in, and it's a person, not a program. These pages open perfectly well in an ordinary browser, and one can be saved by hand and read. Where that has happened the verdict says so. Its clause is marked saved by hand, not re-read automatically, because nothing revisits a page the monitor can't reach, and a quote that no longer moves is worth less than one that does. It's why this list shrinks slowly and by hand, not on its own.

Where a company's robots.txt does refuse us, that's treated differently and it isn't read by hand either. A stated instruction gets honoured, and reading the page anyway because a browser can would make the instruction decorative. One company is in that position today, listed above. The two entries that carried this label until 30 August were our own misreading, not their refusal, and are back in the monitor. If you work at one of these companies and would rather the entry said something else, the fix is the same as everywhere on this site: write to us.