PDF converter privacy: Converter File Handling

Every row is a verbatim sentence read from the named source's own page through our fetch service on the date shown, hash-pinned to the stored read (the sha of the page's visible text; the raw page is mirrored to R2).

13 of the 33 named sources that could be read published a usable figure; 20 published none and are recorded as not published, never filled in; 1 could not be read (blocked, dead or unreachable) and count nowhere.

The headline figures (median, minimum, maximum, quartiles) are over ONE figure per source for each breakdown it prices, in day (a source's median where its page yielded several accepted sentences for one breakdown), so a page that gives figures for several breakdowns gives one for each and N counts 14 figures, never sentences; 176 candidate sentence(s) were refused by a reviewer with the reason recorded.

The fuller derivation this dataset is chartered to grow into (not yet what the figures above are; they are each source's own published figure as read): one row per converter per term, each quoted verbatim from the vendor's own policy with the date it was read: stated deletion window for an uploaded file, whether processing happens in the browser or on a server, the processing region, named sub-processors, certification claimed (ISO/IEC 27001, SOC 2), whether a DPA is offered, and whether uploads are used to train a model.

The derivation is the DISTRIBUTION nobody publishes - the median and range of stated deletion windows, how many of the converters a UK buyer meets state one at all, how many process outside the UK, and which of them a UK controller could use for a bank statement without an Article 28 contract - beside what the ICO's own guidance requires; changed-since, which is the news when a policy is quietly rewritten

176 candidate sentences on these pages were refused by a reviewer; each refusal and its reason is recorded in the review ledger.