Google today added Louisiana and Vermont to the list of US states where it reads a browser's privacy signal before it decides how to handle an ad. A help page posted in the Google AdSense Help Center, dated November 16, 2026, says that from November 17, 2026, ad requests from users in the two states that carry a Global Privacy Control signal will be switched into Google's Restricted Data Processing mode. The page frames the move around state laws that it says arrive "on or after January 1st 2027." Louisiana's law does take effect on that date. Vermont's, according to analyses by three law firms, does not take effect until January 1, 2028.

In Short

Google says it will start treating the Global Privacy Control browser setting as an opt-out for users in Louisiana and Vermont from November 17, 2026, which puts their ad requests into a restricted data mode. That matters to publishers who earn money from AdSense, because traffic from those users will be handled with less data, and to anyone tracking how Google interprets the state privacy patchwork. Google's page ties the change to provisions arriving "on or after January 1st 2027," but law firm analyses date Vermont's law to January 1, 2028, and one analysis says Louisiana's text does not mention opt-out preference signals at all. In practice, the switch for both states comes well before either law's requirements, and Google has not said whether publishers can change it.

What the AdSense page says

The page carries the title "Upcoming US states with universal opt-out mechanism" and sits at answer number 18818765 in the AdSense Help Center. It is two sentences long. Both are reproduced here in full because they are the entirety of Google's statement:

"On or after January 1st 2027, Louisiana and Vermont will introduce Universal Opt-Out Mechanism and Opt-Out Preference Signal provisions, joining other US states with similar privacy regulations. Starting on or after November 17, 2026, for users in Louisiana and Vermont, Google will receive Global Privacy Control (GPC) signals directly and trigger Restricted Data Processing (RDP) mode for those ad requests."

No other states, products or settings are named.

Item Louisiana Vermont
Date Google gives for opt-out provisions "On or after January 1st 2027" "On or after January 1st 2027"
Date Google starts receiving GPC "on or after November 17, 2026" "on or after November 17, 2026"
What Google does with the signal Triggers RDP mode for the ad request Triggers RDP mode for the ad request
State law Louisiana Data Privacy Act, SB 386 Vermont Data Privacy and Online Surveillance Act, S.71
Law signed May 29, 2026, by Governor Jeff Landry (according to the Future of Privacy Forum) June 16, 2026, by Governor Phil Scott (according to Hunton and Koley Jessen)
General effective date January 1, 2027 (according to Hunton and the Future of Privacy Forum) January 1, 2028 (according to Hunton, Koley Jessen and Shook, Hardy & Bacon)
Days between Google's switch and the law's effective date 45 (PPC Land calculation) 410 (PPC Land calculation)

The phrase "on or after" does a lot of work in Google's first sentence. January 1, 2028 is technically after January 1, 2027, so the sentence is not wrong about Vermont. It is, however, a loose way to describe a law that does not apply for another 13 months.

How the mechanism works

The two sources describe a short chain of events, from the browser setting to the ad server. Taken together, the steps run as follows.

  1. The user turns the signal on. According to the Global Privacy Control website, the first step is "Turn On GPC," a setting that lives in a browser or extension. The site lists Brave Browser, Disconnect, DuckDuckGo Privacy Browser, Firefox, OptMeowt by privacy-tech-lab, Privacy Badger by EFF and lockrMail by lockr.
  2. The browser sends it to every site. The GPC site calls the second step "Send the Signal": once enabled, the browser attaches the signal to the websites it visits. Technically, the signal travels as an HTTP header, Sec-GPC: 1, and can also be read in the page through a JavaScript property, navigator.globalPrivacyControl.
  3. Google reads it directly. For ad requests from users in Louisiana and Vermont, Google says it "will receive Global Privacy Control (GPC) signals directly." The page does not mention any role for the publisher, its consent management platform or an IAB string in passing the signal along.
  4. The ad request changes mode. Google then triggers "Restricted Data Processing (RDP) mode for those ad requests." The scope is per request, not per account or per site.
  5. The site respects the preference. The GPC site labels its third step "Exercise Your Rights," and says participating websites can then respect the preference.

What RDP does in practice is not spelled out on the AdSense page. Google's separate Help Center page for advertisers on US state privacy laws says that, where applicable, Google turns off ad targeting and activates restricted data processing when it receives GPC in states whose laws require it. In other words, ad personalization built on the user's data stops for that request, and the ad that fills the slot is chosen with far less information about the viewer.

The signal behind the switch

Global Privacy Control is not a Google product. It is a specification developed by a coalition, and its website describes the effort in plain terms: "Together, over a dozen organizations are developing the GPC specification." The project's own FAQ defines it this way: "Global Privacy Control (GPC) is a proposed specification designed to allow Internet users to notify businesses of their privacy preferences, such as whether or not they want their personal information to be sold or shared."

The legal target is spelled out on the site. "The GPC signal is intended to communicate a Do Not Sell or Share request under the California Consumer Privacy Act, and similar state privacy laws that allow users to opt out of data sales or the use of their data for cross-context targeted advertising," it says. The ambition stretches beyond the US: "Under the GDPR, the intent of the GPC signal is to convey a general request that data controllers limit the sale or sharing of the user's personal data to other data controllers (GDPR Articles 7 & 21)."

The site makes a case against the status quo of per-site links. It notes that companies complying with privacy rules have added "Do Not Sell" and "Object To Processing" links across the web, which must be clicked site by site, and argues that GPC replaces them with one setting. The signal, according to the site, is "required under state privacy laws such as the California Consumer Privacy Act (CCPA)."

Its numbers are large, and they are its own. The site invites visitors to "Join over 150 million users" and says the signal can be used "on over 66,000 websites with GPC." Its founding organizations, according to the site, represent "50 million users and hundreds of thousands of websites." It also displays an endorsement from Xavier Becerra, credited as California's attorney general, a post he left in 2021: "CA DOJ is encouraged to see the technology community developing a global privacy control in furtherance of the CCPA and consumer privacy rights."

What the GPC website states Figure or entry
Users "over 150 million"
Websites where the signal can be used "over 66,000"
Founding organizations represent "50 million users and hundreds of thousands of websites"
Organizations developing the specification "over a dozen"
Browsers and extensions featured Brave Browser, Disconnect, DuckDuckGo Privacy Browser, Firefox, OptMeowt, Privacy Badger, lockrMail
Legal basis cited California Consumer Privacy Act; GDPR Articles 7 and 21
Site license Creative Commons Attribution 4.0 International, excluding logos and marks

Two names are missing from that browser list: Google Chrome and Apple's Safari. That gap matters for how many Louisiana and Vermont users will actually trigger Google's new handling. A user on a default Chrome install sends no signal for Google to receive. California has moved on that front. Its Opt Me Out Act, AB 566, signed by Governor Gavin Newsom on October 8, 2025, requires browsers operating in the state to offer opt-out preference signals when the law takes effect in January 2027, according to the California Privacy Protection Agency. That is the same month Google attaches to Louisiana and Vermont.

The GPC project is also a second attempt at an old idea. Do Not Track, an earlier browser header, asked sites not to follow users across the web, but nothing obliged sites to honor it. GPC differs because state laws, rather than goodwill, give it force. The opt-out signal concept written into those laws is the reason Google is reading the header at all.

The two laws, and a date that does not match

The two states on Google's page are at different points in the calendar.

Louisiana's Data Privacy Act, SB 386, takes effect on January 1, 2027, according to both Hunton and the Future of Privacy Forum. Its reach follows the California model, according to the Future of Privacy Forum: it applies to a business operating in Louisiana with annual gross revenues above $25 million, or one that buys, receives, sells or shares the personal data of 75,000 or more consumers, households or devices a year, or one that earns 50% or more of its revenue from selling personal data. The Louisiana attorney general has exclusive enforcement power, and a 30-day cure period runs from January 1, 2027 to July 31, 2027.

How the Louisiana law treats browser signals is a matter of reading. Hunton describes a provision letting consumers designate an authorized agent, including through a technology-based opt-out signal that meets the law's requirements, and gives Global Privacy Control as an example. The Future of Privacy Forum, in its analysis published June 3, 2026, says the law does not reference opt-out preference signals or universal opt-out mechanisms, and describes an authorized agent using a technology such as a global setting on an electronic device. Google's page calls them "Universal Opt-Out Mechanism and Opt-Out Preference Signal provisions."

Vermont's Data Privacy and Online Surveillance Act, S.71, was signed by Governor Phil Scott on June 16, 2026, according to Hunton and Koley Jessen. Hunton, Koley Jessen and an analysis by Shook, Hardy & Bacon published by PYMNTS all give January 1, 2028 as its effective date. Its thresholds are lower than Louisiana's: according to Hunton and Koley Jessen, it covers businesses that processed the personal data of at least 35,000 Vermont consumers in the prior year, the sensitive data of at least 3,000, or that offered for sale the personal data of at least 3,000. Consumer health data provisions carry no numerical threshold. Koley Jessen says controllers must honor opt-out preference signals. Enforcement sits with the Vermont attorney general, with a 60-day cure period from January 1, 2028 to June 30, 2029.

Law detail Louisiana (SB 386) Vermont (S.71)
Effective date January 1, 2027 January 1, 2028
Revenue threshold Above $25 million a year None stated
Volume threshold 75,000 consumers, households or devices 35,000 Vermont consumers
Sensitive data threshold None stated 3,000 Vermont consumers
Data-sale threshold 50% of revenue from selling personal data Offered for sale data of 3,000 consumers
Enforcement Attorney general, exclusive Attorney general, exclusive
Cure period 30 days, until July 31, 2027 60 days, until June 30, 2029
Signal language Disputed between analyses Opt-out preference signals must be honored (Koley Jessen)

Sources for the table: Hunton, the Future of Privacy Forum, Koley Jessen and Shook, Hardy & Bacon. Neither state's penalty amounts appear in those analyses.

Google's change therefore goes live 45 days before Louisiana's law and 410 days before Vermont's. Why start in Vermont more than a year early? The page does not say, and it does not explain whether the shared date is a simplification.

A pattern that runs on a November calendar

Today's page is the latest step in a state-by-state build-out that PPC Land has followed since 2024. In June 2024, AdSense added US state regulations messages for California, Virginia, Colorado, Connecticut and Utah, which publishers had to switch on themselves. The GPC handling came later. On June 30, 2025, Google began receiving GPC signals and triggering RDP for eight more states: Connecticut, Montana, Nebraska, New Hampshire, Texas, Minnesota, New Jersey and Maryland, building on handling already in place for Colorado.

The date of today's change has a precedent. On November 17, 2025, exactly a year before the Louisiana and Vermont start, Google activated the same GPC treatment for Delaware and Oregon. On the same day it extended RDP handling to Indiana, Kentucky and Rhode Island, with account-level settings applied to traffic from those states starting January 1, 2026. That second batch was about account settings rather than browser signals. A month later, in December 2025, AdSense added privacy messages for the same three states along with an option labeled "All current and future supported US States."

Alongside the browser signal, Google has also had to keep up with the industry's own consent strings. In October 2025, AdSense added support for Global Privacy Platform National v2, accepting strings for US National, California, Colorado, Connecticut, Florida and Virginia, and triggering RDP when users opt out of sale, sharing or targeted advertising.

Date States What Google did
Before June 30, 2025 Colorado Universal opt-out handling already in place
June 30, 2025 Connecticut, Montana, Nebraska, New Hampshire, Texas, Minnesota, New Jersey, Maryland Receives GPC, triggers RDP
November 17, 2025 Delaware, Oregon Receives GPC, triggers RDP
November 17, 2025 (announced) Indiana, Kentucky, Rhode Island Account-level RDP settings from January 1, 2026
November 17, 2026 Louisiana, Vermont Receives GPC, triggers RDP

By PPC Land's count, built only from its own coverage, Google's GPC-to-RDP handling covered at least 11 states before today's page. Louisiana and Vermont take that to at least 13. The count does not include California, whose handling has not been described in the items cited here.

What it means for publishers and advertisers

The practical effect lands on the sell side first. Every AdSense ad request from a Louisiana or Vermont user with GPC switched on will now run in a mode that, on Google's own description elsewhere in its Help Center, turns off ad targeting. Restricted requests leave buyers with less information to bid on, and contextual advertising signals carry more of the weight. How much revenue changes hands depends on how many users in those two states use a GPC-enabled browser, and neither Google nor the GPC project offers a state-level figure.

For advertisers, the change narrows the pool of personalized impressions in two more states. Neither is a large market on its own. The direction of travel is the bigger story, since each annual batch adds states where a browser setting, rather than a banner click, decides whether data flows. If browser makers respond to California's requirement by adding the setting for all their users, the number of people able to send the signal would grow in every state where Google reads it.

There is also a question of who is doing the honoring. Google's wording is that it "will receive" the signal "directly." Read literally, the arrangement does not depend on the publisher's own consent tools passing the signal along. It also means Google acts on the signal in Vermont before the state's law requires anyone to.

What the page leaves out

The AdSense page does not say how Google determines that a user is in Louisiana or Vermont, whether the same change applies to Google Ad Manager or AdMob, whether publishers can opt out of or adjust the handling, or what specific data processing stops under RDP. It gives no estimate of revenue impact. It does not explain why Vermont's start date sits more than a year ahead of the law.

Key facts

  • Source document: "Upcoming US states with universal opt-out mechanism," Google AdSense Help, answer 18818765, dated November 16, 2026
  • Source URL: https://support.google.com/adsense/answer/18818765
  • Feature names: Global Privacy Control (GPC); Restricted Data Processing (RDP) mode
  • States added: Louisiana, Vermont
  • Google start date: on or after November 17, 2026
  • Date Google gives for state provisions: on or after January 1, 2027
  • Louisiana law: Louisiana Data Privacy Act, SB 386, effective January 1, 2027
  • Vermont law: Vermont Data Privacy and Online Surveillance Act, S.71, effective January 1, 2028
  • Background source: Global Privacy Control website, https://globalprivacycontrol.org
  • GPC claims: over 150 million users; over 66,000 websites
  • Related state rule: California Opt Me Out Act, AB 566, browser signal requirement from January 2027

Timeline

Summary

Who: Google, through its AdSense Help Center, and the users, publishers and advertisers whose ad requests come from Louisiana and Vermont. The Global Privacy Control project supplies the browser signal involved.

What: Google will receive Global Privacy Control signals directly for users in Louisiana and Vermont and switch those ad requests into Restricted Data Processing mode, which restricts the use of the user's data for ad targeting.

When: The page is dated November 16, 2026, and the handling starts on or after November 17, 2026. Google ties it to state provisions "on or after January 1st 2027"; Louisiana's law takes effect on January 1, 2027 and Vermont's on January 1, 2028.

Where: Louisiana and Vermont, adding to at least 11 US states where PPC Land has recorded Google treating GPC as an opt-out.

Why: New comprehensive privacy laws in both states give consumers a right to opt out of targeted advertising and data sales, and Google is adopting the browser signal as the trigger, in Vermont's case more than a year before the law applies.