Site Behavior Lab
Site

eharmony.com

Baseline visit
Requested address
https://www.eharmony.com/
Report ID
20260814-7ab80129880226edb4e86849a225f801
Evidence SHA-256
1a14914f5c40ef2ccae3156498d9630b4a18ae0dd2d0fb34c922d8e085b91b3e
Scanner
playwright-chromium

eharmony.com contacted catalogued Google, Microsoft and Meta domains during the visit labeled GPC off.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

GPC off

eharmony.com itself58 requestsrequests that stayed on the site
Catalogued services20 requests5 names: Google 8, Microsoft 6, Cloudflare 2, Meta 2, Taboola 2
Hosts the catalog does not name35 requests10 hosts; the catalog cannot say who operates them

GPC on

eharmony.com itselfat least 55 retained requestsrequests that stayed on the site
Catalogued servicesat least 14 retained requests4 names: Google 6, Microsoft 4, Cloudflare 2, Meta 2
Hosts the catalog does not nameat least 26 retained requests9 hosts; the catalog cannot say who operates them
Not measuredabsence here is not evidence of absence
  • Other pages on this site
  • Signed-in visitors, other browsers and other regions
  • Anything that loads only after interaction or consent
  • Services the catalog does not name
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • the count is a lower bound; more may exist
  • not measured

5 distinct catalogued tracking-service entities recorded responses across 18 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled GPC off, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script and 4 browser-fingerprinting heuristics matched.

5tracking-service entities
55cross-site requests
8third-party cookie records
4fingerprint-like patterns

Worth checking

Bottom line: this visit has signals worth checking

The scan observed signals a non-expert should not have to decode from raw request tables. Some detector evidence was incomplete; each affected detector card states its own retained or unavailable scope, while completed request, cookie, and storage measurements keep their recorded exactness.

Where severity is ranked, the cohort is a curated set of popular, mostly commercial sites, not a random sample of the web. Details

The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from this report's cohort, with each percentile card naming its metric-specific measured-site denominator; otherwise it uses fixed reference thresholds. That cohort is drawn from a curated set of popular, mostly commercial sites, not a random sample of the web. The request log, domain table, and methodology remain below for verification.

113 requests observed in one controlled visit.

What was checked

Page
https://www.eharmony.com/
When
Aug 14, 2026, 7:05 PM UTC
Setup
Both visits used headless Chromium in a desktop window of 1440 × 980, with en-US language and UTC time zone. Both ran from a scanner host the report does not name; the network region was not recorded.
Visits
Two visits configured to differ in the Global Privacy Control (GPC) signal: GPC off and GPC on.
Interactions
No typing was recorded in either visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence was cut short.

What these visits could not see

  • Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its activity was recorded.
  • Signed-in visitors, other browsers and other regions. Both visits were automated, from a fixed en-US / UTC profile. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Anything that loads only after interaction or consent. Trackers that load that late are not observed, so counts are a lower bound.
  • Services the catalog does not name. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled.
  • Checks with incomplete evidence. In both visits: the typing test. In the GPC on visit only: Brave Shields matches, the consent banner, the privacy policy check, third-party services, named platforms, Google Analytics remarketing and advertising pixels.

Worth checking

49 of 109 requests the engine evaluated matched Brave Shields filter lists

49 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block. Details

Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. This is Site Behavior Lab's list-based simulation, which applies every list to the site's own requests too. Brave's default Standard setting skips most of these lists for such requests, so its results can differ.

The hand-curated service catalog separately matched 20 request rows in this visit.Show matched requests

Context

This GPC comparison supports no comparable delta

The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals.

The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.

2 disqualifying conditions named by the report's claim policy.

Context

Tracking companies the privacy policy does not appear to name

Microsoft, Cloudflare and Taboola were sent requests during this visit. However, the policy text matched none of the names this scan knows those companies by.

Policies often disclose vendor categories rather than company names, so an unnamed vendor is a transparency gap worth reviewing, not automatically a violation. Details

Named in the policy: Google and Meta.

Policy at https://www.eharmony.com/…; 0 checkable statements matched; 2 of 5 observed tracking companies named in the policy.

Look closer

Show catalog-matched requests

Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.

Context

Catalogued service domains recorded responses during this visit

Google, Microsoft and Cloudflare, plus 2 others appeared in the request log.

A catalog match identifies a maintainer-reviewed service/domain mapping; it does not establish why an individual request occurred, what it carried, or whether profiling happened. Details

Functional catalog labels include analytics / tag management, advertising and advertising / analytics. This scan could not identify 6 of the 18 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

55 cross-site requests across 18 third-party hosts.At or above the median for third-party domains across the 51 sites measured for this metric. Modest distinct tracking-service entities count.Show third-party requests

Worth checking

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Google, Meta and Microsoft.

The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.

16 requests to these platforms.Show catalog-matched requests

Context

Google Tag Manager loaded; a remarketing sync cannot be told from this report

This visit contacted Google Tag Manager and recorded no request to a Google Analytics collection host. It also recorded DoubleClick hosts whose names this report generalizes, the remarketing sync host's among them.

This report neither shows nor rules out the sync. Details

Tag Manager is a loader. It can fetch Google Analytics or other tags, or none; this report cannot tell which it fetched here. The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.

googletagmanager.com observed; no google-analytics.com or analytics.google.com request; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Context

Third-party cookies were present

8 third-party cookies showed up during the visit.

This report does not retain cookie values or partition keys, so it does not establish whether a cookie was a persistent identifier or could recognize a visitor across sites. Details

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.

31 cookies total in this report.At or above the median for third-party cookies across the 51 sites measured for this metric.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

Context

Input-monitoring signal involving a third-party script

Listener coverage that could observe typing-related input events was registered through call chains that included a third-party script.

This is a behavioral instrumentation signal from listener registration, stack-attributed script origins, and known-vendor requests: it shows the page was instrumented to observe interaction, not that anything was transmitted. Details

Stack attribution records the script origins present in the bounded registration call chain. A cross-site origin in that chain does not by itself establish that the cross-site script registered the listener. That is because first-party code can register its own listeners through a helper served from elsewhere. A different registrable domain is also not by itself a different operator: sites commonly serve their own scripts from a separate asset domain. The card therefore says third party only when the catalog or reviewed ownership attributes an origin to another organization. On scanners that run the active keystroke-capture probe, actual transmission is tested separately (a synthetic value is typed, never real input, and no typed values are collected). Treat this card as a review prompt rather than proof.

Session-recording listener coverage: 41 interaction-listener registrations with https://*.instana.io/, https://*.iesnare.com/ and https://static.cloudflareinsights.com/, plus 1 other in the registration call chain. Input-monitoring listener coverage: 5 input-listener registrations with https://*.instana.io/, https://*.iesnare.com/ and https://static.cloudflareinsights.com/ in the registration call chain.

Look closer

Show requests involving *.instana.io

Opens this report's request log filtered to *.instana.io, a script origin recorded in the listener's call chain.

Worth checking

Behavioral fingerprinting heuristics matched

4 behavioral heuristics matched: Offline audio rendering heuristic, Canvas font probing heuristic, WebGL entropy-read heuristic and WebRTC peer-connection probing.

They are review prompts for this visit, not proof of cross-site identity tracking. Details

These heuristics look for behavior patterns such as canvas readback after drawing, repeated canvas font measurement, WebGL entropy reads, offline audio rendering, or WebRTC peer-connection setup.

Offline audio rendering heuristic: 5 offline renders with audio.OfflineAudioContext.createDynamicsCompressor, audio.OfflineAudioContext.createOscillator and audio.OfflineAudioContext.startRendering. Canvas font probing heuristic: 516 measureText calls across up to 6 fonts; measured text contents are not stored. WebGL entropy-read heuristic: 72 parameter reads and 2 pixel readbacks; parameters: webgl.getParameter.UNMASKED_RENDERER_WEBGL and webgl.getParameter.UNMASKED_VENDOR_WEBGL. WebRTC peer-connection probing: 1 peer connection with 1 data channel, 1 offer, and 1 local description.

Domain evidence

20 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 6.1 sCatalog matchRoleResource types
www.eharmony.com52No catalog matchfirst-partydocument, stylesheet, font, script, image, ping, xhr, fetch
www.google.com10No catalog matchthird-partyfetch, image
*.cloudflare.com7No catalog matchthird-partyscript, document, xhr, fetch, image
*.bing.com6Microsoft: advertising / analyticsservicescript, image, xhr
*.eharmony.com6No catalog matchfirst-partyscript, document, xhr, image
*.*.usercentrics.eu5No catalog matchthird-partyscript, document
*.liadm.com4No catalog matchthird-partyscript, xhr, document
www.googletagmanager.com3Google: analytics / tag managementservicescript
*.*.doubleclick.net3Google: advertisingservicescript
static.cloudflareinsights.com2Cloudflare: web analyticsservicescript
*.facebook.net2Meta: social / advertising pixelservicescript
ad.doubleclick.net2Google: advertisingservicefetch
*.instana.io2No catalog matchthird-partyscript, ping
*.iesnare.com2No catalog matchthird-partyscript
*.api.*.*.usercentrics.eu2No catalog matchthird-partyfetch
cdn.taboola.com1Taboola: advertising / recommendationsservicescript
*.taboola.com1Taboola: advertising / recommendationsservicescript
*.*.*.usercentrics.eu1No catalog matchthird-partyfetch
*.*.cloudflare.com1No catalog matchthird-partyfetch
*.adxcel-ec2.com1No catalog matchthird-partyimage

Raw evidence

Open the interactive evidence explorer

The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.

This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.

Report ID
20260814-7ab80129880226edb4e86849a225f801
Site
eharmony.com
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: detector output evidence was censored before completion: the synthetic keystroke probe did not complete its test (recorded loss count: 1); recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

Variant visit

Started
Run quality
cut short: request evidence was censored before completion: the producer recorded an additional collection loss (recorded loss count: 1); detector output evidence was censored before completion: the synthetic keystroke probe did not complete its test (recorded loss count: 1); recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.

This report covers what the scanner measures, not everything a site can do. 17 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 14 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.

Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. A study has been recorded for pixel-events and does not support a published rate under the current build. How detector accuracy is measured.

Severity percentiles come from this report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort. Each percentile card's measured sites are among 99 sites with a successful load across all cohorts. Other methodologies and post-choice consent visits are excluded from each card's denominator, while failed or block-page attempts are outside that coverage. Visits with capped or incomplete request evidence are left out of each mark. They tend to be the heaviest pages, so a mark can sit lower than the cohort's true mark.

Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .