AI Policy Log

Methodology and editorial rules

AI Policy Log records what official vendor pages say about training, retention, zero data retention (ZDR), data-processing agreements, and related exceptions, as of a stated check date. It is a quotation log, not a legal opinion.

Where the facts come from

What we will not write

How plans are listed

One row per plan or product tier the vendor actually names on the official pages we read. If the vendor does not currently describe a commonly used informal name (for example a “Team” plan), we do not invent that row.

Exception cells are for cases the vendor itself flags: feedback that can still be used after an opt-out, temporary chats, Trusted Access or similar programs, features carved out of a BAA, aggregator/provider-specific rules, and so on.

How monitoring works

A script fetches each monitored official URL, stores a dated text snapshot, and diffs it against the previous snapshot. Trivial noise (cookie banners, asset hashes, “updated 2 days ago” relative timestamps without a policy change) is ignored. Meaningful diffs go into a review queue as pending human approval. They are never written into the published tool pages automatically.

Corrections

If a quote is wrong or incomplete, the fix is to re-read the official page, update the quote and date, and record the correction in the changelog.