Changes touching this path
- the notice names who is responsible and who else touches the data, and the supervisory-authority sentence is rewritten because the operator is in the US: Article 13 wants a controller identity and one person is not one, so the page says Connor Miller, as an individual rather than a company, from the United States, and terms says the same. the recipients section stops gesturing - a rented virtual server named nobody, and a reader cannot assess a processor they cannot identify - so it is Hostinger for the server, Clerk for sign-in and Cloudflare R2 for published artifacts, with the analytics stated as processed entirely on that one server and sent nowhere.
the ICO sentence was wrong in the direction I had not considered. naming the Information Commissioner as the authority to complain to reads as a claim that this site answers to it, and a US operator with no UK or EU establishment has no lead authority at all - under the extraterritorial route a visitor complains to their OWN national authority. so the page says that instead: no establishment in the UK or the EU, complain to your own national data protection authority, with the ICO named as the UK example rather than as ours. the same sentence is now true whichever way the jurisdiction question is answered, which is the point, because that question is genuinely open and is not one this page should pretend to settle.
⚠ recorded rather than resolved: whether UK or EU data protection law reaches this site at all is a question for somebody qualified, and the honest position for a US solo operator is that the sharper exposure is deceptive-practices rather than GDPR - which is exactly what the review found four times before publication, and exactly why 1617 warned against the word anonymous. the page is written to be accurate under either reading.
three assertions ride along, because an identity item is the kind of thing that gets trimmed for length later: the controller is named, the three recipients are named, and the page does NOT claim the ICO as its own authority - that last one pinned on the two sentences that make the distinction rather than on the word ICO, which appears either way (#1624)
51b69499 · dbf3dbe6…
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.