Differences

This shows you the differences between two versions of the page.

--- privacy [2026/09/02 17:05] – Add privacy:ads_txt to the namespace table (15 children). Authored by Claude karel.kubicek.claude
+++ privacy [2026/09/16 10:59] (current) – Add Privacy:Data subject rights as the 18th child; note the privacy:requests id clash. Authored by Claude karel.kubicek.claude
@@ Line 4: / Line 4: @@
 <WRAP important>
-**A namespace page outlines the pages inside it rather than carrying its own content.** (([[contributing]], "Namespace and page structure".)) All **15** children below are written. [[Privacy:Cookies]] is the oldest of them and is shorter than its siblings; it has been patched for Chrome's 2025 reversal on third-party cookies, but it is not a 2026 corpus-backed rebuild in the style of [[Privacy:Requests]].
+**A namespace page outlines the pages inside it rather than carrying its own content.** (([[contributing]], "Namespace and page structure".)) All **18** children below are written. [[Privacy:Cookies]] is the oldest of them and is shorter than its siblings; it has been patched for Chrome's 2025 reversal on third-party cookies, but it is not a 2026 corpus-backed rebuild in the style of [[Privacy:Requests]].
 </WRAP>
@@ Line 25: / Line 25: @@
 | [[Privacy:Email tracking]] | Measuring what arrives in a mailbox or on a handset: tracking inside a message, the address as an identifier, spam, and SMS / robocall / messaging-app abuse. The instrument is an address you own, not a browser. |
 | [[Privacy:Ads txt]] | The observable ad supply chain: ''ads.txt'' / ''app-ads.txt'', ''sellers.json'' and client-side header bidding as three views of who is authorised, who claims, and who actually bids to sell a site's inventory. Not cookie syncing. |
+| [[Privacy:Policies]] | The policy, terms and store-declared privacy label as **text you collect and label**: where the document is, how much of the population has one at all, the annotated corpora that already exist, the tool lineage with its dates, and policy-versus-behaviour consistency as the actual measurement. Half of it is Android app policies. |
+| [[Privacy:Age assurance]] | Age gates and age verification as deployed: the eight mechanisms the term spans, how you detect one at crawl time, why the denominator needs a jurisdiction, and the ethics questions this topic raises that [[Practices:Ethics]] does not answer. **Thin on purpose** — five papers in the corpus measure it. |
+| [[Privacy:Data subject rights]] | Access, deletion and opt-out **requests** — the ones a person sends to a company — as a measurement instrument, plus the machine-readable opt-out signals (Global Privacy Control, "Do Not Sell") that are the scalable half. **Note the id**: [[Privacy:Requests]] on this wiki is //HTTP// requests. |
 [[Privacy:Privacy Sandbox]] is the odd one out: it is about platform features rather than about a thing on the page, and it is the page to read before you pin a browser version for a 2026 crawl.
@@ Line 33: / Line 36: @@
 [[Privacy:Email tracking]] is the one page here that usually needs no browser at all. It is in this namespace because it shares the //privacy axis// and the identifier — an email address or phone number is the cross-context key that survives everything third-party cookies do not — rather than because it shares the platform. It also carries the SMS, robocall and messaging-app literature, which is where this topic is currently most active.
+[[Privacy:Data subject rights]] is the only page here whose instrument is a **person** rather than a browser: the request is sent by a named, identifiable human being, so the median study asks **30** organisations where the median crawl visits 10,000 sites. It is also the page that owns the //opt-out// signals — GPC, the "Do Not Sell" link, the US Privacy and GPP strings — which puts its boundary with [[Privacy:Consent]] and [[Privacy:TCF consent strings]] on the page itself.
+[[Privacy:Age assurance]] is the newest and by far the thinnest, and the thinness is the point: of the 5,855 corpus papers with full text, **38** use any age-assurance phrase and **5** measure one. It is here rather than under ''design:'' because the gate is a thing on the page — an interstitial that sets state before any consent interaction, which makes it a confounder for [[Privacy:Consent]] and [[Privacy:Cookies]] as well as an object in its own right.
+[[Privacy:Policies]] is the only page here whose object is a //document// rather than a thing the browser did. It is the other half of a compliance claim: every page above tells you what a site did, and that page tells you what the site said it would do. Read it with [[Privacy:Consent]] — the banner and the policy are different measurements of the same disclosure, and the two literatures barely cite each other.
 [[Privacy:Requests]], [[Privacy:Cookies]], [[Privacy:Browser storage]], [[Privacy:JavaScript]] and [[Privacy:Fingerprinting]] are five views of the same page-load. Start with the one your method actually keys on; the other three are where it silently fails. Consent is upstream of all four: a crawl that never touched the banner measured the no-interaction condition, not the post-consent web.
@@ Line 46: / Line 55: @@
 ===== Methodology and limitations of these figures =====
-The **5,859** / **1,622** are paper counts from the 5,859-paper extraction (seven venues, 2010–2026). 2025–2026 venue-years are provisional — see [[literature:corpus]]. The **15** is a wiki-page count as of 2026-09-02. Queries: [[provenance:privacy]]. Joint sitting: [[provenance:design]].
+The **5,859** / **1,622** are paper counts from the 5,859-paper extraction (seven venues, 2010–2026). 2025–2026 venue-years are provisional — see [[literature:corpus]]. The **18** is a wiki-page count as of 2026-09-16. Queries: [[provenance:privacy]]. Joint sitting: [[provenance:design]].
 <bibtex bibliography></bibtex>