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 activity evidence was also incomplete: request counts are retained lower bounds.
This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds.Details
The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.
At least 136 retained requests observed in one controlled visit.
What was checked
Page
https://www.pinterest.com/
When
Sep 28, 2026, 12:07 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 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
Typed a made-up test value into 1 form field in the No blocking visit and 2 form fields in the Brave-list blocking visit, never submitting the form. 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.
At least 10 retained requests matched Brave Shields filter lists
At least 10 retained 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 at least 0 retained request rows in this visit.Show matched requests
Context
This Shields comparison is not conclusive
The "No blocking" visit's synthetic form-input probe stopped one or more navigations, so its request evidence is incomplete. The "Brave-list blocking" visit's synthetic form-input probe stopped one or more navigations, so its request evidence is incomplete.
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.
Privacy policy read; it made no statement this scan can check
None of the statements this scan knows how to check appear in the policy text. As a result, nothing was compared against this visit's evidence (no catalogued tracking companies observed to check against it). That is a limit of the automated check, not a finding about the site either way.
Evidence collection was cut short, so this covers only what was recorded before the cutoff.Details
Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields. Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped.
Policy at https://*.pinterest.com/en/privacy-policy; 0 checkable statements matched; no catalogued tracking companies observed to check against it.
Context
Other third-party operators were identified outside the tracking-service catalog
Google was named by consent-platform signatures, reviewed ownership, or CNAME evidence without being classified as a tracking service.
Operator identity and tracking classification are separate: naming an operator does not prove that a request was for tracking.Details
This scan could not identify 2 of the 6 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. Evidence collection was cut short, so this covers only what was recorded before the cutoff.
At least 105 retained cross-site requests across at least 6 retained third-party hosts.Show third-party requests
Context
Requests were dispatched to major-platform domains the catalog does not carry
This visit dispatched requests to Google domains that the reviewed ownership map names, though the service catalog carries no entry for them.
Asset and font hosts reach this state often: the ownership map establishes who operates the domain, and nothing here establishes the request's purpose or payload.Details
These domains are not counted as catalog-matched requests. Evidence collection was cut short, so this covers only what was recorded before the cutoff.
The automated visit did not observe third-party cookies.
This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.
8 cookies total in this report.
Context
Input-monitoring signal involving a script from another domain
Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain. This scan did not establish the operator of that 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: 104 interaction-listener registrations with https://accounts.google.com/, https://*.pinimg.com/ and https://www.gstatic.com/ in the registration call chain. Input-monitoring listener coverage: 41 input-listener registrations with https://accounts.google.com/, https://*.pinimg.com/ and https://www.gstatic.com/ in the registration call chain.
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: 1 offline render with audio.OfflineAudioContext.createDynamicsCompressor, audio.OfflineAudioContext.createOscillator and audio.OfflineAudioContext.startRendering. Canvas fingerprinting heuristic: 1 canvas matched; reads: canvas.toDataURL.
Domain evidence
8 recorded domains
These are retained domain rows, not a complete inventory.
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 16.6 s
Catalog match
Role
Resource types
*.pinimg.com
91
No catalog match
third-party
script, font, image, stylesheet
www.pinterest.com
29
No catalog match
first-party
document, other, fetch, xhr, manifest
www.gstatic.com
5
No catalog match
third-party
script, stylesheet, image, other
accounts.google.com
3
No catalog match
third-party
script, stylesheet, document
www.recaptcha.net
3
No catalog match
third-party
script, document
*.gstatic.com
2
No catalog match
third-party
font
*.pinterest.com
2
No catalog match
first-party
document, script
*.google.com
1
No catalog match
third-party
ping
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.
cut short: the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the synthetic form-input probe stopped, or could not read in full, a request that may have carried its test value, so input-capture detection is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.
Variant visit
Started
Run quality
cut short: the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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.
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 .