Industries / Technology / Software and SaaS / Ad and marketing tech
Privacy
Privacy in ad tech is the set of standards, browser changes, laws and rulings that limit how far software may follow a person across sites and apps to pick and measure ads.
7
Milestones achieved, from 1997 to 2025.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1997
A standard says block
Lou Montulli wrote Netscape's original cookie specification, and Netscape Navigator supported cookies from its first public version in September 1994. In February 1997 RFC 2109, the first formal cookie standard, written by David Kristol of Bell Labs and Montulli, said browsers should not accept cookies from "unverifiable transactions", such as an ad loaded from another site, unless the user turned that on. Ad networks protested; Kristol wrote in 2001 that the major browser makers "largely ignore" the standard, and RFC 6265 in April 2011 left third-party cookie policy to each browser.
LessonA privacy default written into a standard did not hold once ad businesses had been built on the opposite.
Credit
David Kristol; Lou Montulli; the IETF's HTTP working group
2000
Names kept off profiles
In November 1999 DoubleClick, which tracked web browsing to target banner ads, merged with Abacus Direct, which held catalogue shoppers' names and purchases, and planned to attach names to its browsing profiles. After the Electronic Privacy Information Center (EPIC) complained to the US Federal Trade Commission (FTC) in February 2000, chief executive Kevin O'Connor said on 2 March 2000 that the company had made a "mistake"; the FTC closed its inquiry in January 2001, finding DoubleClick had "never used or disclosed consumers' PII" beyond its privacy policy.
LessonO'Connor blamed the plan on acting "in the absence of government and industry privacy standards".
Credit
EPIC; FTC; DoubleClick
2017
Safari limits tracking cookies
WebKit, the engine behind Apple's Safari, had blocked third-party cookies by default "from the very beginning". In June 2017 WebKit engineer John Wilander announced Intelligent Tracking Prevention, which uses an on-device machine-learning model to find domains able to track people across sites and purges their cookies if the person has not interacted with that site in the last 30 days. Mozilla's Firefox began blocking known third-party tracking cookies by default for all users on 3 September 2019.
Credit
Apple's WebKit team; Mozilla
2019
Do Not Track retired
Do Not Track was a browser setting that asked every site not to track the user, with no law requiring sites to obey. In January 2019 the W3C's Tracking Protection Working Group closed its work, citing too little deployment and no "indications of planned support", and in March 2019 Apple removed the setting from Safari 12.1 "to prevent potential use as a fingerprinting variable", a fingerprint being the set of browser traits that can identify a device.
LessonA signal without legal force was ignored; under California's privacy law a similar signal, Global Privacy Control, must be honoured, and in August 2022 the state's attorney general settled with the retailer Sephora for $1.2 million, partly for failing to process it.
raw.githubusercontent.comapi.github.comdeveloper.apple.comoag.ca.gov
Credit
W3C Tracking Protection Working Group; Apple
2022
Consent framework breaks GDPR
IAB Europe's Transparency and Consent Framework (TCF) records the choices people make in cookie pop-ups as a "TC string" that is passed to ad tech firms bidding in real-time auctions. On 2 February 2022 Belgium's data protection authority found the TCF breached the GDPR, fined IAB Europe €250,000 and gave it two months to present a plan to comply. On 7 March 2024 the EU Court of Justice confirmed that a TC string is personal data and that IAB Europe can be a "joint controller" of it.
LessonThe trade's own tool for complying with the law was itself found to break it.
Credit
Belgian Data Protection Authority; Court of Justice of the European Union
2023
Contract no basis for ads
Behavioural advertising picks ads from a record of what a person has done. On 4 January 2023 Ireland's Data Protection Commission (DPC) announced fines of €210 million for Facebook and €180 million for Instagram, after the European Data Protection Board (EDPB) ruled on 5 December 2022 that Meta could not rely on its terms of service, a contract, as the legal basis for behavioural advertising. Meta was given three months to comply.
LessonThe DPC had backed Meta's reading of the law and was overruled by its fellow European regulators.
Credit
EDPB; Irish DPC; the complainants who filed on 25 May 2018, the day the GDPR took effect
2025
Cookie replacements retired
Having decided to keep third-party cookies in Chrome, Google said on 17 October 2025 that "in light of their low levels of adoption" it would retire most of its Privacy Sandbox tools, including Topics, Protected Audience and the Attribution Reporting API, while keeping CHIPS and FedCM. The same day the UK Competition and Markets Authority (CMA) released Google from its Privacy Sandbox commitments. The CMA's summary of tests run by other firms from late 2023 to mid-2024 found publisher revenue per impression about 30% lower without third-party cookies, even with the Sandbox tools.
LessonReplacements that outside tests found left sellers well short of cookie revenue were not taken up.
Credit
Google; UK CMA
Watch for
Fewer cookie banners in Europe
On 19 November 2025 the European Commission proposed, in its Digital Omnibus, moving the EU's cookie consent rules into the GDPR, requiring a one-click refusal with no new request for six months, and obliging sites to respect choices set once in the browser. According to the law firm Heuking, by October 2026 the Council of the EU's texts kept the rules in the ePrivacy Directive, had deleted the browser-signal duty in June 2026 and cut the wait after a refusal to four months, while the European Parliament had not yet set its position.
Achieved whena final text is adopted, published in the EU's Official Journal and in force.
Claimed by
European Commission, November 2025
Opt-out built into browsers
California's Opt Me Out Act (AB 566), signed by Governor Gavin Newsom on 8 October 2025, requires companies that make web browsers to include a setting that sends an opt-out preference signal, telling every site a person visits not to sell or share their data. It takes effect on 1 January 2027, and the California Privacy Protection Agency, which sponsored the bill, may write rules for it.
Achieved whenChrome, Safari and Edge ship the setting and an outside test finds that sites covered by the law stop sharing data when it is on.
Claimed by
California Privacy Protection Agency, September and October 2025
Open
01
Check declared cookie lifetimes
A crawler that loads 1,000 European websites using the TCF in a fresh automated browser, accepts all purposes, records every cookie each listed ad vendor sets and when it expires, and compares that with the maximum lifetime the vendor declares in IAB Europe's Global Vendor List (GVL) and in its own published storage disclosure file.
The briefCredit · unclaimed02
Probe clean rooms with decoys
A data clean room is a shared database in which two companies, such as an advertiser and a publisher, match customer lists and are meant to see only totals. The job is a public test kit of differencing queries, pairs of queries whose answers differ by one record so that subtracting them reveals it, run against made-up customer tables in the main clean room products with their default protections, reporting which queries expose planted decoy records.
The briefCredit · unclaimed
Open 01 · the brief
Check declared cookie lifetimes
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A crawler that loads 1,000 European websites using the TCF in a fresh automated browser, accepts all purposes, records every cookie each listed ad vendor sets and when it expires, and compares that with the maximum lifetime the vendor declares in IAB Europe's Global Vendor List (GVL) and in its own published storage disclosure file.
Why it is still open
Each vendor's GVL entry has a field for the longest life of its cookies and a link to a disclosure file. The GVL of 19 November 2026 lists 1,037 active vendors; by this session's count, 725 declare a positive maximum, with a median of 365 days, 135 declare more than 13 months and the longest is about 4,000 days. IAB Europe's own compliance team began checking in 2025 for vendors whose cookies last longer than they declare; its 2025 report counts 587 enforcement procedures against vendors, up from 269 in 2024, and 41 temporary suspensions, but names no vendor and publishes no per-vendor results. A search found studies of cookie lifetimes and tests of vendors ignoring consent choices, such as Adalytics' report on partial consent, but no public comparison of declared lifetimes with observed ones.
Built with what exists
the public GVL file and vendors' disclosure files; OpenWPM or Playwright for automated browsing from an EU network address; Python. No real user and no logged-in account are involved.
First step
Download the GVL, list the 50 vendors seen most often on 100 TCF sites, and compare their cookies with their disclosure files.
Done looks like
For at least 500 vendors, a published table of declared and observed cookie lifetimes and the share of vendors whose cookies outlast their declaration, with 50 cases checked by hand and the code released.
Open 02 · the brief
Probe clean rooms with decoys
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A data clean room is a shared database in which two companies, such as an advertiser and a publisher, match customer lists and are meant to see only totals. The job is a public test kit of differencing queries, pairs of queries whose answers differ by one record so that subtracting them reveals it, run against made-up customer tables in the main clean room products with their default protections, reporting which queries expose planted decoy records.
Why it is still open
AWS's own user guide says minimum aggregation thresholds, its rule that each result must cover enough people, do not on their own stop differencing attacks. An August 2026 review of AWS's documentation found that COUNT queries over a single table are exempt from the threshold. Searches found warnings and documentation reviews but no published test across products.
Built with what exists
trial or free-tier accounts on AWS Clean Rooms, Snowflake Data Clean Rooms, Databricks Clean Rooms and BigQuery data clean rooms; synthetic tables from the open-source Synthetic Data Vault or Faker libraries; SQL and Python. Only made-up records are loaded, and findings go to each vendor 90 days before publication.
First step
Build a 100,000-row synthetic customer table with 10 planted decoy records and run five differencing queries on one product.
Done looks like
At least 20 attack queries run on four products, with a published table of which ones recovered a planted record under default settings and which settings stopped them.