Site Behavior Lab
Site

bumble.com

Baseline visit
Requested address
https://bumble.com/
Report ID
20260810-ddda97740795c86dc9d18524a1799dc7
Evidence SHA-256
3b72edc44797aff4941262a58912501188501ad559dfc459cdc25e413fc40e13
Scanner
playwright-chromium

bumble.com recorded 42 fewer third-party requests in the visit configured for Brave-list blocking.

Where this page's requests went

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

No blocking

bumble.com itself74 requestsrequests that stayed on the site
Catalogued services31 requests5 names: LinkedIn 11, Google 10, Pinterest 6, Meta 3, Taboola 1
Hosts the catalog does not name11 requests4 hosts; the catalog cannot say who operates them

Brave-list blocking

bumble.com itself33 requestsrequests that stayed on the site
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name0 requestsno other cross-site host on record
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
  • one request on record, same site
  • one request on record, cross-site
  • not measured

The visit with no blocking made 116 requests; the visit configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit) recorded 42 fewer third-party requests. The blocker directly stopped 2 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance.

5tracking-service entities
42cross-site requests
9third-party cookie records

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.

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.

116 requests observed in one controlled visit.

What was checked

Page
https://bumble.com/
When
Aug 10, 2026, 6:54 AM 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 GitHub Actions Ubuntu runner; the network region was not recorded. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
Interactions
No typing was recorded in either visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed.

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.

Worth checking

38 requests matched Brave Shields filter lists

38 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 31 request rows in this visit.Show matched requests

Not flagged

Lower values observed across comparable metrics in the Brave-list blocking attempt

The blocking visit ran with the scanner configured to apply Brave's ad-block engine and default Shields filter lists. It was a simulation in this scanner's browser, not a live Brave-browser visit, and application was not verified. Compared with the unblocked visit, it showed 42 fewer third-party requests, 9 fewer third-party cookies and 31 fewer tracking-related service requests.

Treat this as an observed difference, not a measured blocking rate. Details

Services only seen in the unblocked visit: LinkedIn, Google and Pinterest, plus 2 others. The blocking visit's engine directly blocked 2 requests; the remaining difference may include follow-on requests that never started once their sources were blocked. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments).

Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests

Context

Tracking companies the privacy policy does not appear to name

Taboola was sent requests during this visit. However, the policy text matched none of the names this scan knows that company 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: LinkedIn, Google and Pinterest, plus 1 other.

Policy at https://bumble.com/privacy-policy/en; 0 checkable statements matched; 4 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

LinkedIn, Google and Pinterest, 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 social / advertising pixel, analytics / tag management and advertising. This scan could not identify 1 of the 15 third-party hosts recorded here, so it cannot say who operates it. That is a limit of identity coverage, not evidence about the site.

42 cross-site requests across 15 third-party hosts.At or above the median for third-party domains across the 86 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 LinkedIn, plus 1 other.

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

30 requests to these platforms.Show catalog-matched requests

Context

Advertising pixel requests contained event labels

Meta Pixel requests contained event labels during this visit.

Event labels do not establish user actions or successful delivery. Details

No advanced-matching identifier fields are recorded in the decoded evidence. Unsupported payload formats and later interactions may carry other fields; older decoders did not record every decoding gap.

Meta Pixel: PageView (1 request).Show catalog-matched requests

Context

Google Analytics present; a remarketing sync cannot be told from this report

Google Analytics was observed, with requests to DoubleClick hosts whose names this report generalizes. The remarketing sync host is one such name, so the sync cannot be told apart from them.

This report neither shows nor rules out the sync. Details

The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.

Google Analytics host observed; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Worth checking

Third-party cookies were present

9 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.

25 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 86 sites measured for this metric.

Not flagged

No fingerprint-like API calls observed

The scan did not observe the instrumented high-entropy browser APIs.

This is an observation layer, not proof that fingerprinting is impossible.

0 API families recorded.

Domain evidence

17 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 9.1 sCatalog matchRoleResource types
bumble.com63No catalog matchfirst-partydocument, font, stylesheet, script, image, other
*.bumble.com11No catalog matchfirst-partyscript, xhr, document, stylesheet
*.ads.linkedin.com7LinkedIn: social / advertising pixelserviceimage, xhr, fetch
www.google.com7No catalog matchthird-partyfetch, image
*.pinterest.com6Pinterest: social / advertising pixelserviceimage, xhr, fetch, document
www.googletagmanager.com4Google: analytics / tag managementservicescript
*.*.doubleclick.net3Google: advertisingserviceping, script
analytics.google.com2Google: analytics / tag managementservicefetch
*.facebook.net2Meta: social / advertising pixelservicescript
*.licdn.com2LinkedIn: social / advertising pixelservicescript
www.linkedin.com2LinkedIn: social / advertising pixelserviceimage
*.pinimg.com2No catalog matchthird-partyscript
ad.doubleclick.net1Google: advertisingservicefetch
www.facebook.com1Meta: social / advertising pixelserviceimage
cdn.taboola.com1Taboola: advertising / recommendationsservicescript
fonts.googleapis.com1No catalog matchthird-partystylesheet
*.gstatic.com1No catalog matchthird-partyfont

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
20260810-ddda97740795c86dc9d18524a1799dc7
Site
bumble.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

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. 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 .