Checklist
What 4 Shopify stores still sent with GPC on, after the Filson order
CalPrivacy's Filson order describes server-side and browser-based sharing. We ran 4 Shopify stores with GPC on and logged what the browser still sent.
In brief
Technical observation, not legal advice. We turned on Global Privacy Control (GPC) in a clean browser and visited four Shopify stores that use server-side tracking. We did not test Filson's website. We recorded what the browser sent. What the stores' servers sent afterwards, server to server, is not visible to us.
The order and our four stores
CalPrivacy's Board adopted a stipulated final order against C.C. Filson Co. on November 6, 2026. Filson admits that it shared personal information through cookies and pixels with AdTech companies that included Meta, Google, Pinterest, Elevar and Zeta Global (paragraphs 28 and 80). The Enforcement Division alleged that Filson shared data in two ways, "Server-side" sharing "through a direct server-to-server connection" and "Browser-based" sharing (paragraph 51), and that Filson failed to honor opt-out preference signals for either (paragraphs 53 to 55). Filson neither admits nor denies those remaining findings and does not admit liability (paragraph 80). The order sets a fine of $217,987 (paragraph 66). Read the CalPrivacy decision page and the CalPrivacy order (PDF) for the exact wording.
With GPC on, here is what the browser sent on each store, the same in 3 of 3 runs:
- Store BB: the browser posted 2 requests to a same-origin Elevar path, and sent Google Ads 6, GA4 6 and Meta 3 requests. Shopify's API read sale of data as no.
- Store BC: the browser sent 0 requests to Meta, Google Ads and GA4. The browser still posted 2 requests to the same-origin Elevar path and 6 to a path on a store subdomain.
- Store BD: the browser posted 2 requests to the Elevar path and sent Meta 6, GA4 4 and Google Ads 32 requests. 24 of those Google Ads requests carried rdp=1. The footer had no "Your Privacy Choices" or "Do Not Sell" link.
- Store BE: the browser sent 13 requests to endpoints on a store subdomain, plus Meta 2, Google Ads 16 to 18 and GA4 10 or 11. We could not tie the subdomain endpoints to a vendor.
What the order says
Swipe to see the order
What the order states
| Paragraph | What the order states |
|---|---|
| 28 | Cookies and pixels on Filson's website "transmitted that data to advertising technology ("AdTech") companies which, at various points during the relevant time period, included Meta, Google, and Pinterest, as well as Elevar and Zeta Global, each a California-registered data broker". Filson admits this paragraph (paragraph 80). |
| 34 | The Enforcement Division alleged that Filson "failed to provide a "Do Not Sell or Share My Personal Information" link, a "Your Privacy Choices" link, or a "Your California Privacy Choices" link on its website". |
| 43 and 45 | The privacy policy's customer care link showed "PAGE NOT FOUND", and the policy referred to a "Your Privacy Choices" link that "did not appear on the website". |
| 51 | Filson shared data through "Server-side" sharing ("sharing personal information through a direct server-to-server connection") and "Browser-based" sharing ("directing a consumer's browser to share personal information with a third-party"). |
| 53 | For server-side sharing, Filson had to stop cross-context behavioral advertising "for any consumer profile that it could associate with the browser or device sending the opt-out preference signal". |
| 54 | For browser-based sharing, Filson could have stopped transmission or sent the data with "a Restricted Data Processing or Limited Data Use flag". |
| 59 | Each visit with an opt-out preference signal meant prohibited sales and shares "to at least five AdTech companies". |
| 67 and 68 | Filson must stop device-based sales and shares to AdTech companies within 30 days, unless an officer or director certifies compliance with paragraphs 69 to 73. |
| 69 | Filson must audit, at least quarterly for three years, its recognition of opt-out preference signals "as applied to Server-side sales and shares as well as its use of Browser-based tracking technologies". |
| 70(b) | Filson must keep a "Do Not Sell or Share My Personal Information", "Your Privacy Choices" or "Your California Privacy Choices" link. |
Paragraphs 25 to 60 are the order's factual findings. Filson admits paragraphs 25 to 28 and neither admits nor denies the rest (paragraph 80).
The test we ran
The method below is ours. The order does not list test steps.
We used headless Chrome on November 19, 2026, between 17:08 and 17:22 PST, from a US IP address outside California (Shopify's API reported Kansas). Every run used a clean profile and HTTP/1.1 only. We ran two states, three times each, on every store:
- Fresh. Open the home page, click nothing, then open a product page.
- GPC on. The same visit, with the
Sec-GPC: 1 header on every request andnavigator.globalPrivacyControlset to true.
We did not click any cookie banner in either state. On each page we waited, scrolled and read Shopify's Customer Privacy API. We counted requests to Meta, Google Ads and Floodlight, and GA4, and every non-asset request to the store's own domain or its subdomains. For Google requests we read the gcs, npa and rdp parameters. For Meta requests we read the dpo parameter, which carries Limited Data Use. Status codes came from Chrome's network log. No counted request returned a 4xx or 5xx, and none used HTTP/2. About 5 percent of counted requests have no recorded status because the page moved on before a response came back.
We call a request an Elevar request only when Elevar's own script was in the request's call stack. Store-domain requests we could not tie to a vendor that way are listed by path as first-party endpoints. We did not record request body values.
At the end of each run we looked for a "Your Privacy Choices" or "Do Not Sell" link and clicked it. That check is not part of the request counts.
Store BB: Elevar, Google and Meta kept sending
Store BB loads Elevar's data layer from a path on its own domain. The browser posts events to /a/elevar/browser/bulk on the same domain. Elevar's script dl-app-embed-block.js, served from /a/elevar/static/, was in the call stack of every one of these posts.
Swipe to see GPC on
Store BB
| Fresh | GPC on | |
|---|---|---|
| Shopify API | marketing yes, sale of data blank | marketing yes, sale of data no, 3 of 3 |
| Elevar /a/elevar/browser/bulk | 2 (status 204) | 2 (status 204), 3 of 3 |
| Google Ads | 6 | 6, 3 of 3 |
| GA4 | 6 | 6, 3 of 3 |
| Meta | 4 (PageView 2, ViewContent 2) | 3 (PageView 2, ViewContent 1), 3 of 3 |
With GPC on, every Google Ads and GA4 request that carried a consent code read gcs G111, which grants ad and analytics storage, with npa=0 and no rdp parameter, 3 of 3. No Meta request carried a Limited Data Use value. The Elevar posts carried the Sec-GPC: 1 header like every other request in the GPC runs. Their body includes a field named consent_v2. We did not record its value.
The footer has a "Your Privacy Choices" link. It opened a page on the store's domain (status 200) with a request form, 6 of 6.
Store BC: Meta and Google stopped, Elevar did not
Store BC uses the same Elevar setup as Store BB, with posts to /a/elevar/browser/bulk and Elevar's dl-app-embed-block.js in the call stack. It also sends requests to /com.snowplowanalytics.snowplow/tp2 on a store subdomain. No script in that request's call stack or field in its body tied it to a vendor, so we list it as a first-party endpoint.
Swipe to see GPC on
Store BC
| Fresh | GPC on | |
|---|---|---|
| Shopify API | marketing yes, sale of data blank | marketing yes, sale of data no, 3 of 3 |
| Elevar /a/elevar/browser/bulk | 2 (status 204) | 2 (status 204), 3 of 3 |
| First-party endpoint on a subdomain | 6 (status 200) | 6 (status 200), 3 of 3 |
| Meta | 2 (PageView 1, ViewContent 1) | 0, 3 of 3 |
| Google Ads | 12 in run 1, 0 in runs 2 and 3 | 0, 3 of 3 |
| GA4 | 2 in run 1, 1 in runs 2 and 3 | 0, 3 of 3 |
With GPC on, the Elevar posts and the subdomain endpoint kept the same counts as on a fresh visit. What Elevar or the subdomain endpoint sends on from the server is the leg we cannot see.
The footer has a "Do Not Sell or Share" link. Our automated click on it did not load a new page in any of the 6 runs. In a separate check an email sign-up pop-up covered the page. Loading the link's address directly returned 200 and showed a page with an opt-out button.
Store BD: Google Ads carried rdp=1, and no opt-out link
Store BD also posts to /a/elevar/browser/bulk, with Elevar's dl-app-embed-block.js in the call stack. It sends requests to /nb-collector on a store subdomain, which we could not tie to a vendor.
Swipe to see GPC on
Store BD
| Fresh | GPC on | |
|---|---|---|
| Shopify API | marketing yes, sale of data blank | marketing yes, sale of data no, 3 of 3 |
| Elevar /a/elevar/browser/bulk | 2 (status 204) | 2 (status 204), 3 of 3 |
| First-party endpoint /nb-collector | 6 or 7 | 7 to 10, 3 of 3 |
| Google Ads | 40 or 41, rdp=0 on 30 | 32, rdp=1 on 24, 3 of 3 |
| GA4 | 4, npa=0 | 4, npa=1, 3 of 3 |
| Meta | 6 (PageView 4, ViewContent 2) | 6 (PageView 4, ViewContent 2), 3 of 3 |
In Google's tags, rdp=1 is the parameter for restricted data processing, the flag paragraph 54 of the order names. On Store BD, 24 of the 32 Google Ads requests carried it with GPC on, 3 of 3. No Meta request carried a Limited Data Use value in either state.
We found no "Your Privacy Choices" or "Do Not Sell" link anywhere on the page, 6 of 6. The footer in the page's HTML links to a privacy policy only.
Store BE: first-party endpoints kept sending with GPC on
Store BE does not use Elevar. Its browser sends requests to /init, /tag, /data, /consent and /providers/consentIQ/save-data on one store subdomain, and to /nb-collector on a second store subdomain. The /tag requests carry event names PageView and ViewContent. Neither the request bodies nor the scripts in the call stack named a vendor, so all of these are first-party endpoints.
Swipe to see GPC on
Store BE
| Fresh | GPC on | |
|---|---|---|
| Shopify API | all blank | sale of data no, others blank, 3 of 3 |
| First-party endpoints on subdomain 1 | 13 (status 200) | 13 (status 200), 3 of 3 |
| First-party endpoint /nb-collector on subdomain 2 | 7 | 0, 3 of 3 |
| Google Ads | 16 or 17, rdp=0 on 10 | 16 to 18, rdp=1 on 10, 3 of 3 |
| GA4 | 10 or 11, npa=0 | 10 or 11, npa=1 on 8, 3 of 3 |
| Meta | 2 (PageView 1, ViewContent 1) | 2 (PageView 1, ViewContent 1), 3 of 3 |
On Store BE, GPC stopped the /nb-collector endpoint and left the subdomain 1 endpoints at the same count, 3 of 3. Store BE showed no cookie banner to our visits. The footer has a "Your Privacy Choices" link. It opened a page on the store's domain (status 200) with a request form, 6 of 6.
What the browser can and cannot show
A browser test shows which endpoints the page called, how often, with which headers and parameters, and what the server answered. It cannot show what a store's server, or Elevar's, sends to Meta, Google or anyone else after that. Paragraph 51 of the order calls that leg "a direct server-to-server connection". On Stores BB, BC and BD the browser posted to Elevar's path with GPC on. On Store BE it posted to subdomain endpoints. What happened next on the server is outside this test.
How to run this check on your own store
- Open a clean browser profile. Turn on GPC (how to turn on GPC in Chrome, Firefox and Brave) and confirm the
Sec-GPC: 1 header with our GPC checker. - In DevTools Network, filter by your own domain, not only by vendor domains. Write down every POST to a path on your domain or a subdomain.
- For each one, open the Initiator tab and note which script sent it. If you cannot name the script, write the path down as a first-party endpoint.
- Load the home page and a product page. Count Meta, Google Ads, GA4 and each first-party endpoint.
- Open the Google requests and note gcs, npa and rdp. Open the Meta requests and note dpo.
- In the console, read Shopify.customerPrivacy.currentVisitorConsent(). Note sale_of_data. Why Shopify's API and the pixels can disagree.
- Repeat from a fresh profile with GPC off and compare.
- Click your "Your Privacy Choices" or "Do Not Sell" link from the footer and confirm it opens.
- Run each state three times. For the server leg, ask your server-side vendor what it forwards when the browser sends
Sec-GPC: 1.
The FedEx quarterly opt-out test adds the Reject path to the GPC check.
What to write down
Swipe to see the example
Example from Store BC
| Field | Example from Store BC |
|---|---|
| Date, time, location | November 19, 2026, 17:08 to 17:22 PST, US IP outside California |
| State | GPC on, no banner click |
| Shopify API | sale of data no |
| Vendor requests | Meta 0, Google Ads 0, GA4 0 |
| First-party endpoints | Elevar /a/elevar/browser/bulk 2, subdomain endpoint 6 |
| Status codes | 200 or 204 |
| Opt-out link | present in footer |
| Runs that matched | 3 of 3 |
Limits
- Four stores, one US location outside California, one evening, November 19, 2026 PST. A store can treat California visitors differently, and a later run can differ.
- None of these stores is Filson. We did not test the website the order describes.
- We saw requests leaving the browser and the status codes that came back. We did not see what Elevar, a store's server or a vendor sent on server to server, or what they did with the data.
- We did not record request body values, so we cannot say what any field inside the Elevar or first-party posts contained.
- We did not click any banner. Stores BB and BC showed a banner with Preferences, Reject and Accept, and we left it alone.
- We tested a clean first visit, not a logged-in visitor or checkout.
FAQ
What did CalPrivacy order Filson to do?
The order requires Filson to pay a $217,987 fine and to stop device-based sales and shares of Californians' personal information to AdTech companies within 30 days, unless an officer or director certifies compliance with its audit, testing and training terms. Filson must also audit its handling of opt-out preference signals for server-side and browser-based tracking at least quarterly for three years. Filson neither admits nor denies the Enforcement Division's findings beyond paragraphs 25 to 28.
Did you test Filson's website?
No. We tested four Shopify stores that use server-side tracking. The results describe those stores on November 19, 2026 PST and say nothing about Filson.
Did the Elevar requests stop with GPC on?
No. On Stores BB, BC and BD the browser posted 2 requests to the store's /a/elevar/browser/bulk path with GPC on, the same as on a fresh visit, 3 of 3, and each got status 204. We cannot see what Elevar's server did with them.
Did Meta and Google stop with GPC on?
On Store BC, Meta, Google Ads and GA4 sent 0 requests, 3 of 3. On Store BB they kept sending, with Google consent code G111 and no rdp parameter. On Stores BD and BE they kept sending, and some Google Ads requests carried rdp=1, 24 of 32 on Store BD and 10 on Store BE.
What is a first-party endpoint?
In this post it is a path on the store's own domain or subdomain that we could not tie to a vendor from the request body or the script that sent it. On Store BE these are /init, /tag, /data, /consent, /providers/consentIQ/save-data and /nb-collector.
Can a browser test show server-to-server sharing?
No. It shows what the browser sends and what comes back. Sharing from a store's server to an ad platform does not pass through the visitor's browser.
Related reading
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.