| Both sides previous revisionPrevious revision | |
| privacy [2026/09/23 01:37] – Add Privacy:Advertising to the namespace table (18 -> 19) with a paragraph placing it against Privacy:Ads txt. Authored by Claude. karel.kubicek.claude | privacy [2026/10/08 12:19] (current) – Link and list privacy:pii_leakage (new page). Authored by Claude. karel.kubicek.claude |
|---|
| |
| <WRAP important> | <WRAP important> |
| **A namespace page outlines the pages inside it rather than carrying its own content.** (([[contributing]], "Namespace and page structure".)) All **19** pages in this namespace are listed below and written — this table, not [[start]], is the authority on what is here. [[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 **20** pages in this namespace are listed below and written — this table, not [[start]], is the authority on what is here. [[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> | </WRAP> |
| |
| | [[Privacy:Browser extensions]] | Extensions as the //object// of a measurement: crawling the stores, whether a page can enumerate what you have installed, what extensions leak, and what Manifest V3 did to all three. | | | [[Privacy:Browser extensions]] | Extensions as the //object// of a measurement: crawling the stores, whether a page can enumerate what you have installed, what extensions leak, and what Manifest V3 did to all three. | |
| | [[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: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:PII leakage]] | Personal data — names, emails, phones, passwords, search terms, health or wallet data — reaching third parties from a website: getting a planted value onto the page, finding it again under hashes and encodings, configuration versus transmission, the server-side blind spot, the visit as the disclosure, and the ethics of typing synthetic PII into real sites. | |
| | [[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: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:Advertising]] | Whether and why an ad was **targeted**, and what an advertiser paid: retargeting as a stimulus, trained personas, bids and clearing prices, the platform's own explanations, donated ad data, ads you buy yourself, and ads a crawler collects — each with what it can prove and its unit (ads, impressions, bids, explanations, personas), never sites. | | | [[Privacy:Advertising]] | Whether and why an ad was **targeted**, and what an advertiser paid: retargeting as a stimulus, trained personas, bids and clearing prices, the platform's own explanations, donated ad data, ads you buy yourself, and ads a crawler collects — each with what it can prove and its unit (ads, impressions, bids, explanations, personas), never sites. | |
| |
| [[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: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:PII leakage]] is its counterpart on the page side: the same email address, plus every other personal value, as something a site's embedded code sends away. It is the page to read before you type anything into a form with a crawler; [[Privacy:Email tracking]] keeps the address as an identifier and the mailbox as an instrument. |
| |
| [[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: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. |
| ===== Methodology and limitations of these figures ===== | ===== 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 **19** is **both** the number of rows in the table above //and// the number of pages whose id begins ''privacy:'' in the live wiki index; ''scripts/report_namespace_overviews.mjs'' refuses to pass unless those two are the same **set**, not merely the same size. Re-derived 2026-09-21; 18 → 19 on 2026-09-23, when [[Privacy:Advertising]] was added. ([[Privacy policy]] is a site page, not a child of this namespace, and is not in either count.) 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 **20** is **both** the number of rows in the table above //and// the number of pages whose id begins ''privacy:'' in the live wiki index; ''scripts/report_namespace_overviews.mjs'' refuses to pass unless those two are the same **set**, not merely the same size. Re-derived 2026-09-21; 18 → 19 on 2026-09-23, when [[Privacy:Advertising]] was added; 19 → 20 on 2026-10-08, when [[Privacy:PII leakage]] was added. ([[Privacy policy]] is a site page, not a child of this namespace, and is not in either count.) Queries: [[provenance:privacy]]. Joint sitting: [[provenance:design]]. |
| |
| <bibtex bibliography></bibtex> | <bibtex bibliography></bibtex> |
