1Pre Consent
Browse from US-PA · Configure geo proxy · Load Website · Capture initial screenshot before scroll · Check initial screenshot for cookie banner
A Pennsylvania visitor opened gymshark.com. They chose the reject-all consent option. They then browse a product category, open one product, select an available size if required, add it to the cart, then proceed as far as the checkout page without entering any personal, shipping, or payment information and without placing an order.
Browse from US-PA · Configure geo proxy · Load Website · Capture initial screenshot before scroll · Check initial screenshot for cookie banner
Visitor declined · Find privacy choices · Click reject all button · Check for internal preference modal · Reload · Reload page
Browser-Use Journey · search page · Scroll True · Post-consent workflow step 6 · done
| Category | Result | Risk | Evidence & Authority |
|---|---|---|---|
| All-party consent | Mixed | High | The initial-load banner was visibly presented and described “Cookies and Tracking Pixels,” but the tested user selected “Accept only essential cookies”; after reload, Google Analytics, Google Ads, mParticle, Intercom, and Datadog traffic still appeared. The banner’s browsewrap-style language may support an implied-consent defense, but the express reject action materially weakens it. Popa v. Harriet Carter Gifts, Inc. held that the adequacy of notice that communications were sent to a third party is a fact-sensitive consent question. (www2.ca3.uscourts.gov) |
| Contents interception | Elevated | High | Before any choice and again after rejection, GA/Ads requests transmitted persistent IDs, URLs, page titles, scroll activity, product identifiers, selected size, cart event, value, and SKU. The post-reject add-to-cart payload identified the Black Medium joggers and $33.60 value. That is stronger than a bare tracker-load theory, though this run did not show user-entered checkout fields or a replay recording. 18 Pa. C.S. § 5703; compare Popa (third-party routing of website interactions may constitute interception). (www2.ca3.uscourts.gov) |
| Civil private right of action / damages | Elevated | Critical | If interception, disclosure, or use is established, WESCA supplies a private claim with actual damages or at least $100 per day/$1,000, whichever is greater, plus potential punitive damages, fees, and costs. The class-exposure signal is real, although this run lacks proof of typed sensitive data. 18 Pa. C.S. § 5725. As calibration, the Philadelphia Inquirer settlement included a $1.125 million fund and Meta Pixel practice changes tied in part to Pennsylvania Wiretap Act requirements; its video-pixel facts are not identical to this ecommerce flow. (legis.state.pa.us) |
| Category | Result | Risk | Evidence & Authority |
|---|---|---|---|
| Contents interception in transit | Elevated | High | The tested flow shows contemporaneous third-party transmissions of browsing and purchase-intent content—not merely a static script load—including product page, product name/SKU, chosen size, add-to-cart event, and value after rejection. No email, address, phone, or payment fields were typed, so this is not a form-content capture finding. 18 U.S.C. § 2510; compare Price v. Carnival Corp., where alleged session-replay capture of information entered into fields was treated as alleged “contents.” (law.justia.com) |
| Party vs third-party interceptor | Mixed | High | Gymshark is plainly a party to the shopper-site exchange, but Google, Meta/Facebook, Datadog, mParticle, Intercom, Riskified, and Shopify-related endpoints are separate entities. The evidence most strongly supports third-party receipt by Google Analytics/Ads; whether each vendor functioned only as the site’s extension or independently processed captured data needs vendor/configuration discovery. 18 U.S.C. § 2511(2)(d); Price treated alleged heatmapping and fingerprinting beyond a tape-recorder function as potentially outside the party shield. (law.justia.com) |
| One-party consent | Mixed | High | Gymshark may invoke its participation in the web exchange and the displayed banner. But the tested session had a visible banner on initial load, an affirmative “Accept only essential cookies” selection, and continued GA/Ads traffic marked pscdl=denied; those facts may undercut an argument that the visitor consented to the observed nonessential transmissions. 18 U.S.C. § 2511(2)(d); compare Piedmont Healthcare (party exception can defeat an ECPA pixel theory where the website is the intended recipient). (govinfo.gov) |
| Crime-tort exception § 2511(2)(d) | Unclear | Medium | The record supports marketing/analytics collection after rejection, but does not itself show that any party intercepted communications for the purpose of committing a separate crime or tort. Marketing motive alone is not a clean shortcut around the party exception; this theory would need materially stronger purpose evidence. 18 U.S.C. § 2511(2)(d); a recent pixel-tracking dismissal required facts showing the requisite criminal or tortious purpose, not merely knowing collection. (govinfo.gov) |
| Contents vs metadata | Mixed | High | Browser/device attributes, consent flags, and pseudonymous IDs are metadata-like; the selected product, size, cart status, SKU, price, page path, and add-to-cart event are more plausibly substantive website-communication content. The absence of typed checkout data caps the factual fit. 18 U.S.C. § 2510(8); compare In re BPS Direct, which found standing for alleged surreptitious session-replay capture of payment/billing information but not for generalized browsing allegations alone. (law.justia.com) |
The sharper litigation theory is not that trackers merely loaded: it is that, after an express essential-only selection, Google endpoints continued receiving persistent identifiers plus product, size, cart, and value data. WESCA presents the more consequential exposure path for a Pennsylvania session; the federal ECPA claim is more vulnerable to party/consent and crime-tort defenses.